After having run arch-chroot /mnt /usr/bin/bash one of the things I do is to run alsactl store. alsactl store returns error 125 /var/lib/alsa/asound.state no such file or directory. Certainly there's no such file since when alsa was run before arch-chroot got run on system boot /mnt/var/lib/alsa directory was empty having just run pacstrap on /mnt. So since this is supposed to work, could it be arch-chroot script fails to collect and pass along enough of the right environment information to its chrooted environment for alsactl store to run? Details are available at: information at: http://www.alsa-project.org/db/?f=43f6670eb3bde26ad6491d2faa631625109f88d0
--
On 18-02-18 13:27, Jude DaShiell wrote:
After having run arch-chroot /mnt /usr/bin/bash one of the things I do is to run alsactl store. alsactl store returns error 125 /var/lib/alsa/asound.state no such file or directory. Certainly there's no such file since when alsa was run before arch-chroot got run on system boot /mnt/var/lib/alsa directory was empty having just run pacstrap on /mnt. So since this is supposed to work, could it be arch-chroot script fails to collect and pass along enough of the right environment information to its chrooted environment for alsactl store to run? Details are available at: information at: http://www.alsa-project.org/db/?f=43f6670eb3bde26ad6491d2faa631625109f88d0
Kernel release: 4.13.3-1-ARCH
Looks like you are using an older iso to install ? If so, have you tried with the 2018.02.01 iso ?
LW
I'll try that iso next and see if I get lucky.
On Mon, 19 Feb 2018, LoneVVolf wrote:
Date: Mon, 19 Feb 2018 06:17:16 From: LoneVVolf lonewolf@xs4all.nl Reply-To: General Discussion about Arch Linux arch-general@archlinux.org To: arch-general@archlinux.org Subject: Re: [arch-general] archlinux install bottleneck
On 18-02-18 13:27, Jude DaShiell wrote:
After having run arch-chroot /mnt /usr/bin/bash one of the things I do is to run alsactl store. alsactl store returns error 125 /var/lib/alsa/asound.state no such file or directory.? Certainly there's no such file since when alsa was run before arch-chroot got run on system boot /mnt/var/lib/alsa directory was empty having just run pacstrap on /mnt.? So since this is supposed to work, could it be arch-chroot script fails to collect and pass along enough of the right environment information to its chrooted environment for alsactl store to run?? Details are available at: information at: http://www.alsa-project.org/db/?f=43f6670eb3bde26ad6491d2faa631625109f88d0
Kernel release: 4.13.3-1-ARCH
Looks like you are using an older iso to install ? If so, have you tried with the 2018.02.01 iso ?
LW
--
On Sun, 18 Feb 2018 07:27:11 -0500 Jude DaShiell jdashiel@panix.com wrote:
After having run arch-chroot /mnt /usr/bin/bash one of the things I do is to run alsactl store. alsactl store returns error 125 /var/lib/alsa/asound.state no such file or directory. Certainly there's no such file since when alsa was run before arch-chroot got run on system boot /mnt/var/lib/alsa directory was empty having just run pacstrap on /mnt. So since this is supposed to work, could it be arch-chroot script fails to collect and pass along enough of the right environment information to its chrooted environment for alsactl store to run? Details are available at: information at: http://www.alsa-project.org/db/?f=43f6670eb3bde26ad6491d2faa631625109f88d0
As a sidenote: Why are you running alsactl store inside the chroot?
It is a step helpful for the totally blind who are using the Talking Arch installation system. Without it, getting speech working reliably is complicated.
Sent from my iPhone
On Feb 19, 2018, at 7:00 PM, Øyvind Heggstad mrelendig@har-ikkje.net wrote:
On Sun, 18 Feb 2018 07:27:11 -0500 Jude DaShiell jdashiel@panix.com wrote:
After having run arch-chroot /mnt /usr/bin/bash one of the things I do is to run alsactl store. alsactl store returns error 125 /var/lib/alsa/asound.state no such file or directory. Certainly there's no such file since when alsa was run before arch-chroot got run on system boot /mnt/var/lib/alsa directory was empty having just run pacstrap on /mnt. So since this is supposed to work, could it be arch-chroot script fails to collect and pass along enough of the right environment information to its chrooted environment for alsactl store to run? Details are available at: information at: http://www.alsa-project.org/db/?f=43f6670eb3bde26ad6491d2faa631625109f88d0
As a sidenote: Why are you running alsactl store inside the chroot?
Because I want the sound card operational on first boot. I have two sets of speakers connected to the computer when I failed on that first install. So I disconnected the usb set and the install failed again with the same error. Finally after each install, I boot into arch and don't hear grub beep or any sound after that. It could be the torrent I used was hacked since grub at least should have beeped even if the sound card didn't work. Now it's possible I may need to use the be my eyes app on my iPhone to examine the screen for me to see if archlinux can't for some reason find the sound card and was maybe asking for some assistive input from me to get it going.
On Mon, 19 Feb 2018, ?yvind Heggstad wrote:
Date: Mon, 19 Feb 2018 07:00:58 From: ?yvind Heggstad mrelendig@har-ikkje.net Reply-To: General Discussion about Arch Linux arch-general@archlinux.org To: arch-general@archlinux.org Subject: Re: [arch-general] archlinux install bottleneck
On Sun, 18 Feb 2018 07:27:11 -0500 Jude DaShiell jdashiel@panix.com wrote:
After having run arch-chroot /mnt /usr/bin/bash one of the things I do is to run alsactl store. alsactl store returns error 125 /var/lib/alsa/asound.state no such file or directory. Certainly there's no such file since when alsa was run before arch-chroot got run on system boot /mnt/var/lib/alsa directory was empty having just run pacstrap on /mnt. So since this is supposed to work, could it be arch-chroot script fails to collect and pass along enough of the right environment information to its chrooted environment for alsactl store to run? Details are available at: information at: http://www.alsa-project.org/db/?f=43f6670eb3bde26ad6491d2faa631625109f88d0
As a sidenote: Why are you running alsactl store inside the chroot?
--
arch-general@lists.archlinux.org