Jump to content

nrc

Members
  • Content Count

    80
  • Joined

  • Last visited

  • Days Won

    18

nrc last won the day on May 2 2019

nrc had the most liked content!

1 Follower

About nrc

  • Rank
    Advanced Member

Personal

  • Location
    Columbus, Ohio, USA

Recent Profile Visitors

1,328 profile views
  1. Once upon a time Funtoo just pointed to Gentoo packages. Those tend to be very fresh but created a lot of breakage. Now updates on most packages are curated to keep things more stable. Community members are encouraged to provide pull requests to rev packages if they like. The cool new thing is autogen packages which can automatically generate a new ebuild for a release. These are fairly easy and bulletproof for binary packages which is why some of those are fresher than the source packages.
  2. On --depclean, it doesn't really matter. It just cleans up packages that weren't explicitly installed or required by something that was. So it's a cleanup process to keep things tidy. On libtool, I've never seen that recommended, but usually on a x86-64bit system /usr/lib is a symlink to /usr/lib64.
  3. For the Funtoo live image make sure that you're using the version downloaded from the funtoo.org site. The 'file' utility should report it as having a DOS/MBR partition and not just and ISO-9660 file system. The ISO-9660 image that Area31 creates won't boot from a USB drive on some systems. # file funtoo-livecd-area31-5.1-beta-r1.iso funtoo-livecd-area31-5.1-beta-r1.iso: DOS/MBR boot sector; partition 1 : ID=0x17, active, start-CHS (0x0,0,1), end-CHS (0x3ff,63,32), startsector 0, 3217408 sectors
  4. I use Cyberpower UPSs and I run their utility. I installed from the tarball download and everything worked with no problem. I like the fact that it lets me turn off the UPS alarm which drives our dogs nuts. I must admit that I've never been around when it has reached the point of shutdown and I've never verified the shutdown from the log files.
  5. Run `ego sync` and then do a full update `emerge -auvDN @world` and try again. 2.4.0 is the current dev-python/testtools and it doesn't list a python_targets_python2_7 USE flag.
  6. I'm glad it was helpful. @drobbins had fixed the image on build.funtoo.org. I'm not sure if it regressed or if we just need to get the hackerspace folks to update theirs.
  7. I figured this out. I found that sound works in the container with pacat under the root account but not when I su to the steam account. Whenever I create an account I use the same UID which is not 1000. Using 1111 for this example. It seems like the root environment that you get when you attach to the container gets the environmental variable passed to the container at runtime that points to the correct pulseaudio socket. PULSE_SERVER=unix:/run/user/1111/pulse/native But when you su to the steam account that variable isn't set. So it's trying to use the default socket. If you specify the server in the pacat command line it works as expected. pacat -s unix:/run/user/1111/pulse/native /dev/urandom So looking at where the default server is defined when not overridden by $PULSE_SERVER I find that /etc/pulse/client.conf contains a default setting. # Connect to the host's server using the mounted UNIX socket default-server = unix:/run/user/1000/pulse/native This will work if the userid launcing pulseaudio is 1000, but not otherwise. I changed it to hard code my UID but it could probably be dynamic for any UID using the environment variable. I'll report a bug on this.
  8. I'm having a similar issue. Steam is looking for ALSA. In my case restarting Pulse does not fix it. I assume this is on the host system since I don't see PA running in the container. Sound is fine from pacat in the container and it shows as a stream in pavucontrol. The steam client itself never shows up in pavucontrol. Background - I had to install PA (ptui!) since I've been an ALSA holdout. But first I tried tinkering around a bit trying to get ALSA working. Installed alsa-utils in the container and tried some different run options on the docker launch. No luck so I wiped the container, installed PA, and reinstalled the container. But I it appears that the Steam install persists now. Is it possible that steam is remembering the ghost of alsa-utils past? I see a line in my log that says PulseAudio access denied but I followed the config instructions to set anonymous access and pacat works. PulseAudio connect failed (used only for Mic Volume Control) with error: Access denied ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned err or: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [1230/211250.330147:ERROR:alsa_util.cc(204)] PcmOpen: default,No such file or directory ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default [1230/211250.331123:ERROR:alsa_util.cc(204)] PcmOpen: plug:default,No such file or directory Is there a prescribed process for starting the container storage from scratch other than just removing SteamData? error.log
  9. Ok, I'll create a ticket on this but I wanted to close the loop on this thread. I confirmed that following the install instruction creates a USB drive that won't boot on my UEFI boot Alienware Alpha or BIOS boot Latitude 13. These are older systems (2015 and 2010) so maybe that's part of it. The problem is that following the install instructions creates a device that is a bootable ISO 9660 CD-ROM image with no partitioning. Maybe newer systems are smart enough to treat that as a USB CDROM but no settings on my systems would boot with it. Copying the sysrescueCD ISO file, by comparison, creates a partitioned device which includes an EFI boot partition and boots on both systems with no problem. The problem is that the Funtoo Live CD image is not a hybrid mode ISO. The solution is to convert it to hybrid mode with isohybrid: isohybrid -u funtoo-livecd-area31-5.1-beta.iso This is actually mentioned on the Funtoo LiveCD page here: https://www.funtoo.org/LiveUSB
  10. Alienware Steam Machine which is the Alienware Alpha shipped with SteamOS. Let me verify that this is still an issue. In resolving the problem that I was trying to use a rescue boot for, I discovered that something writing dumps to /sys/firmware/efi/efivars had filled the efivars storage. So it's not out of the question that the USB boot problem was related to EFI being borked in general.
  11. Has anyone been able to boot the new Funtoo LiveCD from USB under UEFI? I've created a sysrescuecd USB using essentially the same instructions and it boots under UEFI with no problem. My first attempt with the Funtoo LiveCD on USB using the 'dd' copy wasn't recognized as bootable under UEFI. I mounted the ISO and used the included script 'usb_install.sh" to install it on the USB drive. The result was recognized as bootable by UEFI but when attempting to boot it fails silently and then moves on to the next option.
  12. It's been a while. Of course I usually lag the curve far enough for prices to be reasonable. My gaming is pretty old school and as long as it can build a kernel in a reasonable amount of time, I'm good.
  13. This was the problem that I ran into during my upgrade. PYTHON_TARGETS was still set in /etc/portage/make.conf so 3.6 was still showing as a dependency. It made quite a mess.
  14. Naah. The GNOME Foundation has been a major enabler of Redhat co-opting the majority of the Linux FOSS ecosystem through systemd and it's ever expanding tenticals. Let them get money from their corporate sponsors at Redhat/IBM, Canonical, and Google.
  15. Glad that you've got things working again!
×
×
  • Create New...