From ruben at mrbrklyn.com Wed Sep 2 20:14:43 2020 From: ruben at mrbrklyn.com (Ruben Safir) Date: Wed, 2 Sep 2020 14:14:43 -0400 Subject: [artix-general] reboot errors after update Message-ID: <20200902181443.GA4834@www2.mrbrklyn.com> for the first time, I did an update and the computer couldn't reboot. It claimed, that is grub claimed, not to be able to find vzlinux to boot I rebooted with a opensuse image in recovery and looks it over. It was sitting there on the drive where it belonged. I looked at the /etc/grub.d entries and they looked ok I then rebooted and it found everything. I know this report isn't that helpful, but it seemed that everything fixed itself as if by magic. I tried to run grubimstall or whatever it is, but it didn't find the images since it was hand mounted on the rescue image. I'm just putting it out there. That is all I know. It is hard to do an update and not be able to reboot. Also is it still hanging between haveg and syslogng - your true friend Reuvain -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 From je-vv at e.email Fri Sep 4 01:41:27 2020 From: je-vv at e.email (Javier) Date: Thu, 3 Sep 2020 17:41:27 -0600 Subject: [artix-general] pandoc-crossref missing in galaxy? Message-ID: Hi, I noticed galaxy, included: pandoc-bin pandoc-citeproc-bin But the set of pandoc binaries is missing: pandoc-crossref-bin Is it possible to include it as well, to have the complete set of pandoc-bin packages? Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Fri Sep 4 03:17:21 2020 From: je-vv at e.email (Javier) Date: Thu, 3 Sep 2020 19:17:21 -0600 Subject: [artix-general] pandoc-crossref-bin missing in galaxy? (fixing -bin) In-Reply-To: References: Message-ID: <28601459-93d2-1852-09c5-55f1f538c4e1@e.email> On 9/3/20 5:41 PM, Javier via artix-general wrote: > Hi, > > I noticed galaxy, included: > > pandoc-bin > pandoc-citeproc-bin > > But the set of pandoc binaries is missing: > > pandoc-crossref-bin > > Is it possible to include it as well, to have the complete set of pandoc-bin packages? > > Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From moody at posixcafe.org Sat Sep 5 22:41:19 2020 From: moody at posixcafe.org (Jacob Moody) Date: Sat, 5 Sep 2020 15:41:19 -0500 Subject: [artix-general] S6 not starting default bundle on boot Message-ID: Hello, I recently migrated from openrc to s6 with the help of this forum post here: https://forum.artixlinux.org/index.php/topic,1369.msg9492.html#msg9492. However upon creating the default bundle it seems to not want to start on boot. I have ensured that both the default bundle and the services it's calling are in the current database but upon boot it seems to not start it. I even tried hacking the rc.init by changing the rl variable to default but still can't seem to get it to run on boot. I was wondering if anyone here knows if perhaps this forum post skips a step or there is some additional configuration that needs to be done. Thanks, Moody From moody at posixcafe.org Sun Sep 6 22:20:35 2020 From: moody at posixcafe.org (Jacob Moody) Date: Sun, 6 Sep 2020 15:20:35 -0500 Subject: [artix-general] S6 not starting default bundle on boot In-Reply-To: References: Message-ID: <35aa8fc3-0ff8-d7a8-c84c-7e06f8bd468b@posixcafe.org> I have figured this out but I thought I would include what I learned for those who are also curious about doing a migration. The first step was walking through and checking the errors that run on startup, for s6 the output you see on your console during boot is stored in /run/uncaught_logs/. With the current file in that dir actually containing text output. Trailing through I found some warning regarding the /var/log/dmesg file, it seems that when s6 was starting it was trying to create that as a directory where as normally with something like openrc, it is a file. Removing the dmesg file seemed to clear that right up and on the next boot I had my default bundle working. I am not quite sure of the interaction here that causes this detail to result in the default bundle not running but I believe it has something to do with the init system blocking until the catch all logger is started. My guess is that this has something to do with this comment in the source code: https://github.com/skarnet/s6-linux-init/blob/master/src/init/s6-linux-init.c#L109 This might be worth mentioning if migration ever gets its own wiki page. Thanks, Moody On 9/5/20 3:41 PM, Jacob Moody via artix-general wrote: > Hello, > > I recently migrated from openrc to s6 with the help of this forum post > here: > https://forum.artixlinux.org/index.php/topic,1369.msg9492.html#msg9492. > > However upon creating the default bundle it seems to not want to start > on boot. I have ensured that both the default bundle and the services > it's calling are in the current database but upon boot it seems to not > start it. I even tried hacking the rc.init by changing the rl variable > to default but still can't seem to get it to run on boot. I was > wondering if anyone here knows if perhaps this forum post skips a step > or there is some additional configuration that needs to be done. > > > Thanks, > Moody From dudemanguy at artixlinux.org Mon Sep 7 05:03:56 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 6 Sep 2020 22:03:56 -0500 Subject: [artix-general] S6 not starting default bundle on boot In-Reply-To: <35aa8fc3-0ff8-d7a8-c84c-7e06f8bd468b@posixcafe.org> References: <35aa8fc3-0ff8-d7a8-c84c-7e06f8bd468b@posixcafe.org> Message-ID: I actually think it's just a permissions issue here. s6-scripts starts up dmesg and pipes it to s6-log for logging reasons. This is stored in /var/log/dmesg. However, this process is done by the s6log uid/gid. So if /var/log/dmesg already existed and was owned by something else (likely root), then this would fail. The startup script has the -e which means it exits immediately if it receives an error code (i.e. the /var/log/dmesg failure). The dmesg oneshot is started with the boot bundle, so that means the default one was never executed because the script always exited due to the error. On 9/6/20 3:20 PM, Jacob Moody via artix-general wrote: > I have figured this out but I thought I would include what I learned for > those who are also curious about doing a migration. The first step was > walking through and checking the errors that run on startup, for s6 the > output you see on your console during boot is stored in > /run/uncaught_logs/. With the current file in that dir actually > containing text output. Trailing through I found some warning regarding > the /var/log/dmesg file, it seems that when s6 was starting it was > trying to create that as a directory where as normally with something > like openrc, it is a file. Removing the dmesg file seemed to clear that > right up and on the next boot I had my default bundle working. I am not > quite sure of the interaction here that causes this detail to result in > the default bundle not running but I believe it has something to do with > the init system blocking until the catch all logger is started. My guess > is that this has something to do with this comment in the source code: > > https://github.com/skarnet/s6-linux-init/blob/master/src/init/s6-linux-init.c#L109 > > > This might be worth mentioning if migration ever gets its own wiki page. > > Thanks, > Moody > > On 9/5/20 3:41 PM, Jacob Moody via artix-general wrote: >> Hello, >> >> I recently migrated from openrc to s6 with the help of this forum post >> here: >> https://forum.artixlinux.org/index.php/topic,1369.msg9492.html#msg9492. >> >> However upon creating the default bundle it seems to not want to start >> on boot. I have ensured that both the default bundle and the services >> it's calling are in the current database but upon boot it seems to not >> start it. I even tried hacking the rc.init by changing the rl variable >> to default but still can't seem to get it to run on boot. I was >> wondering if anyone here knows if perhaps this forum post skips a step >> or there is some additional configuration that needs to be done. >> >> >> Thanks, >> Moody From shironeko at waifu.club Tue Sep 15 17:38:33 2020 From: shironeko at waifu.club (Yunxiang Li) Date: Tue, 15 Sep 2020 11:38:33 -0400 Subject: [artix-general] Fixes to connman-openrc Message-ID: <4b87476c1063aff0d8500fc69b2443521da51ed1.camel@waifu.club> Hi, I've find that connman is overwriting my /etc/resolv.conf with just a single line of # Generated by Connection Manager with no nameserver in it, possibly because I'm using wifi so internet connection come late. One evidence to support the idea is it would populate it correctly if I restart connman. Reading the log it seems like it's doing so because [connmand] Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf so I suggest the init script should first create /var/run/connman before it starts connman. I've talked to the connman guys in there IRC a few times and it seems like they are not sure if it's their job to do it in the software itself. TBH it does seem like a software issue since it does the correct thing of populating /var/run/connman/resolv.conf but they haven't been very responsive about a fix. I've tested the suggested fix, and it fixes my issue. I just need to symlink /etc/resolv.conf to /var/run/connman/resolv.conf to use the build in resolver or populating /etc/resolv.conf like one usually do without connman constantly overwriting it. From dudemanguy at artixlinux.org Tue Sep 15 22:33:02 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Tue, 15 Sep 2020 15:33:02 -0500 Subject: [artix-general] Fixes to connman-openrc In-Reply-To: <4b87476c1063aff0d8500fc69b2443521da51ed1.camel@waifu.club> References: <4b87476c1063aff0d8500fc69b2443521da51ed1.camel@waifu.club> Message-ID: On 9/15/20 10:38 AM, Yunxiang Li via artix-general wrote: > [connmand] Cannot create /var/run/connman/resolv.conf falling back to > /etc/resolv.conf Seems like strange behavior. Shouldn't it just read /etc/resolv.conf? But I guess a workaround is reasonable. Does anyone know if this also happens on runit or s6? From artist at artixlinux.org Tue Sep 15 22:41:36 2020 From: artist at artixlinux.org (artist) Date: Tue, 15 Sep 2020 22:41:36 +0200 Subject: [artix-general] Fixes to connman-openrc In-Reply-To: References: <4b87476c1063aff0d8500fc69b2443521da51ed1.camel@waifu.club> Message-ID: <03e3f3fb-68dc-df8d-305b-1254523f61c8@artixlinux.org> NetworkManager will not modify /etc/resolv.conf if that file contains line: nm_controlled=no I'd expect connman to have something similar. On 9/15/20 10:33 PM, Dudemanguy via artix-general wrote: > On 9/15/20 10:38 AM, Yunxiang Li via artix-general wrote: > > [connmand] Cannot create /var/run/connman/resolv.conf falling back to > > > /etc/resolv.conf > > Seems like strange behavior. Shouldn't it just read /etc/resolv.conf? > But I guess a workaround is reasonable. Does anyone know if this also > happens on runit or s6? From je-vv at e.email Sun Sep 20 05:39:12 2020 From: je-vv at e.email (Javier) Date: Sat, 19 Sep 2020 21:39:12 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop Message-ID: Hi, With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever running "sudo poweroff", or "sudo reboot", the laptop actually kills several things, and sends the message on console saying something like "system shutting down" or similar. However once there, the laptop just hangs forever. When using Arch this doesn't happen at all, and also on other boxes with S6 as well I don't experience this. Not sure if this only affects laptops, neither if it's related to S6 for laptops, or if on S6 there's a particular additional setting or service I should enable... This is not a BIOS issues since this has never happened before with Arch. The same happens if using the "shutdown" or "reboot" buttons from LXQt. Any help would be appreciated. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 05:48:23 2020 From: je-vv at e.email (Javier) Date: Sat, 19 Sep 2020 21:48:23 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop Message-ID: Hi ! With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" Hardware is initialized using a generic method alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) s6-rc: warning: unable to start service alsa: command exited 99 Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 05:51:05 2020 From: je-vv at e.email (Javier) Date: Sat, 19 Sep 2020 21:51:05 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: References: Message-ID: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> On 9/19/20 9:48 PM, Javier via artix-general wrote: > Hi ! > > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: > > alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 > Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" > Hardware is initialized using a generic method > alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) > s6-rc: warning: unable to start service alsa: command exited 99 > > Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. > > Thanks ! BTW, same happens with: % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 05:53:41 2020 From: je-vv at e.email (Javier) Date: Sat, 19 Sep 2020 21:53:41 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> Message-ID: <71000625-2676-1782-27ef-9b1368039142@e.email> On 9/19/20 9:51 PM, Javier wrote: > On 9/19/20 9:48 PM, Javier via artix-general wrote: >> Hi ! >> >> With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: >> >> alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 >> Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" >> Hardware is initialized using a generic method >> alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) >> s6-rc: warning: unable to start service alsa: command exited 99 >> >> Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. >> >> Thanks ! > > BTW, same happens with: > > % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa BTW, this was not occurring on Arch, but particularly I was having no issues with audio on Arch... -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 06:27:25 2020 From: je-vv at e.email (Javier) Date: Sat, 19 Sep 2020 22:27:25 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <71000625-2676-1782-27ef-9b1368039142@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> Message-ID: <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> On 9/19/20 9:53 PM, Javier via artix-general wrote: > On 9/19/20 9:51 PM, Javier wrote: >> On 9/19/20 9:48 PM, Javier via artix-general wrote: >>> Hi ! >>> >>> With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: >>> >>> alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 >>> Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" >>> Hardware is initialized using a generic method >>> alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) >>> alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) >>> s6-rc: warning: unable to start service alsa: command exited 99 >>> >>> Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. >>> >>> Thanks ! >> >> BTW, same happens with: >> >> % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa > > BTW, this was not occurring on Arch, but particularly I was having no issues with audio on Arch... OK, found out I have no issues with audio, in the sense that I can listen and I can record audio. Great !!! My fault !!! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 06:35:17 2020 From: je-vv at e.email (Javier) Date: Sat, 19 Sep 2020 22:35:17 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> Message-ID: <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> On 9/19/20 10:27 PM, Javier via artix-general wrote: > On 9/19/20 9:53 PM, Javier via artix-general wrote: >> On 9/19/20 9:51 PM, Javier wrote: >>> On 9/19/20 9:48 PM, Javier via artix-general wrote: >>>> Hi ! >>>> >>>> With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: >>>> >>>> alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 >>>> Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" >>>> Hardware is initialized using a generic method >>>> alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) >>>> alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) >>>> s6-rc: warning: unable to start service alsa: command exited 99 >>>> >>>> Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. >>>> >>>> Thanks ! >>> >>> BTW, same happens with: >>> >>> % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa >> >> BTW, this was not occurring on Arch, but particularly I was having no issues with audio on Arch... > > OK, found out I have no issues with audio, in the sense that I can listen and I can record audio. Great !!! My fault !!! However, I still have the issue with alsa on boot. What happens is that the alsa setting can't be recovered on boot, which is really annoying, given one really needs to remember resetting alsa, or deal with that resetting when urged to do so. Any help on preventing the alsa oneshot failure is appreciated ! Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Sun Sep 20 06:59:32 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sat, 19 Sep 2020 23:59:32 -0500 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> Message-ID: <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> On 9/19/20 11:35 PM, Javier via artix-general wrote: > However, I still have the issue with alsa on boot. What happens is that the alsa setting can't be recovered on boot, which is really annoying, given one really needs to remember resetting alsa, or deal with that resetting when urged to do so. Does running "alsactl restore" in the terminal work after boot up? I assume that sound works normally otherwise. From dudemanguy at artixlinux.org Sun Sep 20 07:02:11 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 20 Sep 2020 00:02:11 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: Message-ID: On 9/19/20 10:39 PM, Javier via artix-general wrote: > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever running "sudo poweroff", or "sudo reboot", the laptop actually kills several things, and sends the message on console saying something like "system shutting down" or similar. Well it's definitely s6 binaries that do init/shutdown. Does this happen regularly? One thing you could attempt is to reinstall s6-linux-init again. It would remake new init/poweroff/etc. binaries. Unsure if that would actually fix your issue however. From je-vv at e.email Sun Sep 20 10:10:37 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 02:10:37 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: Message-ID: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> On 9/19/20 11:02 PM, Dudemanguy via artix-general wrote: > On 9/19/20 10:39 PM, Javier via artix-general wrote: >> With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever running "sudo poweroff", or "sudo reboot", the laptop actually kills several things, and sends the message on console saying something like "system shutting down" or similar. > > Well it's definitely s6 binaries that do init/shutdown. Does this happen > regularly? One thing you could attempt is to reinstall s6-linux-init > again. It would remake new init/poweroff/etc. binaries. Unsure if that > would actually fix your issue however. Only once like in 20 times a reboot has succeeded, and no luck with poweroff at all. I'll try your suggestion Tomorrow. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 10:18:22 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 02:18:22 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> Message-ID: <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> On 9/19/20 10:59 PM, Dudemanguy via artix-general wrote: > On 9/19/20 11:35 PM, Javier via artix-general wrote: >> However, I still have the issue with alsa on boot.? What happens is that the alsa setting can't be recovered on boot, which is really annoying, given one really needs to remember resetting alsa, or deal with that resetting when urged to do so. > > Does running "alsactl restore" in the terminal work after boot up? > I assume that sound works normally otherwise. Unfortunately not, it's the same as when as try the oneshot service, and as on boot: > % sudo alsactl restore > [sudo] password for vasqueja: > alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 > Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" > Hardware is initialized using a generic method > alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) > alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) So no luck with "alsactl restore", :( And yes, sound is working fine, just that I have to set several things manually through alsactl after boot, particularly for the mic... Really weird. -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 10:29:27 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 02:29:27 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> Message-ID: <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> On 9/20/20 2:10 AM, Javier via artix-general wrote: > On 9/19/20 11:02 PM, Dudemanguy via artix-general wrote: >> On 9/19/20 10:39 PM, Javier via artix-general wrote: >>> With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever running "sudo poweroff", or "sudo reboot", the laptop actually kills several things, and sends the message on console saying something like "system shutting down" or similar. >> >> Well it's definitely s6 binaries that do init/shutdown. Does this happen >> regularly? One thing you could attempt is to reinstall s6-linux-init >> again. It would remake new init/poweroff/etc. binaries. Unsure if that >> would actually fix your issue however. > > Only once like in 20 times a reboot has succeeded, and no luck with poweroff at all. I'll try your suggestion Tomorrow. > > Thanks ! I decided to try it at once, and no luck, :(. After reinstalling s6-linux-init (pacman -S s6-linux-init), I tried rebooting 3 times, and reboot always hanged (had to force the power down with the power button)... -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From charliebrownau at protonmail.com Sun Sep 20 10:37:59 2020 From: charliebrownau at protonmail.com (charliebrownau) Date: Sun, 20 Sep 2020 08:37:59 +0000 Subject: [artix-general] artix-general Digest, Vol 19, Issue 3 In-Reply-To: References: Message-ID: <7ug4wZN0UyGbh2LoaAA_RyjoQUqxxh2PuG979QRn_nRR8DCYyR-f_NmSUBSBo7ndVI0CotcwwCJtpnHPQiPLmJJuouoSjiAYGtGvu2r0Fwk=@protonmail.com> Gday Does the OS pickup the audio chipset for the laptop ? Check using hardware info or lspci command HP EliteBook 840 G3 audio is using - Conexant ISST HD Audio Driver 2015 ref - https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-840-g3-notebook-pc/7815294 I am using Artix with Presonus Audiobox USB (recording interface) Mine doesnt work with ALSA sound volume/mixer either I recommend using * LibreWolf for Browser Sound (works with ALSA) - https://librewolf-community.gitlab.io/ * SMplayer for movies/media * Strawberry for podcasts - https://www.strawberrymusicplayer.org/ Also try to get people to migrate from Skype+Zoom over to Jitsi meet - No program needed, its all via free https server - https://meet.jit.si/ Regards Charliebrownau Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Sunday, September 20, 2020 8:10 AM, wrote: > Send artix-general mailing list submissions to > artix-general at artixlinux.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.artixlinux.org/listinfo/artix-general > or, via email, send a message with subject or body 'help' to > artix-general-request at artixlinux.org > > You can reach the person managing the list at > artix-general-owner at artixlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of artix-general digest..." > > Today's Topics: > > 1. Re: [s6] alsa failing on boot for laptop (Javier) > 2. Re: [s6] alsa failing on boot for laptop (Javier) > 3. Re: [s6] alsa failing on boot for laptop (Javier) > 4. Re: [s6] alsa failing on boot for laptop (Dudemanguy) > 5. Re: [s6] not booting/rebooting laptop (Dudemanguy) > 6. Re: [s6] not booting/rebooting laptop (Javier) > > > Message: 1 > Date: Sat, 19 Sep 2020 21:53:41 -0600 > From: Javier je-vv at e.email > To: artix-general at artixlinux.org > Subject: Re: [artix-general] [s6] alsa failing on boot for laptop > Message-ID: 71000625-2676-1782-27ef-9b1368039142 at e.email > Content-Type: text/plain; charset="utf-8" > > On 9/19/20 9:51 PM, Javier wrote: > > > On 9/19/20 9:48 PM, Javier via artix-general wrote: > > > > > Hi ! > > > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: > > > alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 > > > Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" > > > Hardware is initialized using a generic method > > > alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) > > > alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) > > > s6-rc: warning: unable to start service alsa: command exited 99 > > > Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. > > > Thanks ! > > > > BTW, same happens with: > > % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa > > BTW, this was not occurring on Arch, but particularly I was having no issues with audio on Arch... > > ----------------------------------------------------------------------------------------------------- > > Javier > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20200919/ccced9ad/attachment-0001.sig > > -- > > Message: 2 > Date: Sat, 19 Sep 2020 22:27:25 -0600 > From: Javier je-vv at e.email > To: artix-general at artixlinux.org > Subject: Re: [artix-general] [s6] alsa failing on boot for laptop > Message-ID: 82dcbcfc-f977-99d4-b6a1-4b03daaba228 at e.email > Content-Type: text/plain; charset="utf-8" > > On 9/19/20 9:53 PM, Javier via artix-general wrote: > > > On 9/19/20 9:51 PM, Javier wrote: > > > > > On 9/19/20 9:48 PM, Javier via artix-general wrote: > > > > > > > Hi ! > > > > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: > > > > alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 > > > > Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" > > > > Hardware is initialized using a generic method > > > > alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) > > > > alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) > > > > s6-rc: warning: unable to start service alsa: command exited 99 > > > > Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. > > > > Thanks ! > > > > > > BTW, same happens with: > > > % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa > > > > BTW, this was not occurring on Arch, but particularly I was having no issues with audio on Arch... > > OK, found out I have no issues with audio, in the sense that I can listen and I can record audio. Great !!! My fault !!! > > --------------------------------------------------------------------------------------------------------------------------- > > Javier > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20200919/6540c4d5/attachment-0001.sig > > -- > > Message: 3 > Date: Sat, 19 Sep 2020 22:35:17 -0600 > From: Javier je-vv at e.email > To: artix-general at artixlinux.org > Subject: Re: [artix-general] [s6] alsa failing on boot for laptop > Message-ID: 2bb917f2-f043-0f45-1643-d424f7e5e08e at e.email > Content-Type: text/plain; charset="utf-8" > > On 9/19/20 10:27 PM, Javier via artix-general wrote: > > > On 9/19/20 9:53 PM, Javier via artix-general wrote: > > > > > On 9/19/20 9:51 PM, Javier wrote: > > > > > > > On 9/19/20 9:48 PM, Javier via artix-general wrote: > > > > > > > > > Hi ! > > > > > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever booting, I get the message: > > > > > alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 > > > > > Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" > > > > > Hardware is initialized using a generic method > > > > > alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) > > > > > alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) > > > > > s6-rc: warning: unable to start service alsa: command exited 99 > > > > > Unfortunately, I have no sound on the laptop, and I really need audio to get into meetings and such. I don't use pulse, just plain alsa. Any help appreciated. > > > > > Thanks ! > > > > > > > > BTW, same happens with: > > > > % sudo s6-rc -d change alsa && sudo s6-rc -u change alsa > > > > > > BTW, this was not occurring on Arch, but particularly I was having no issues with audio on Arch... > > > > OK, found out I have no issues with audio, in the sense that I can listen and I can record audio. Great !!! My fault !!! > > However, I still have the issue with alsa on boot. What happens is that the alsa setting can't be recovered on boot, which is really annoying, given one really needs to remember resetting alsa, or deal with that resetting when urged to do so. > > Any help on preventing the alsa oneshot failure is appreciated ! > > Thanks ! > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Javier > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20200919/894ad217/attachment-0001.sig > > -- > > Message: 4 > Date: Sat, 19 Sep 2020 23:59:32 -0500 > From: Dudemanguy dudemanguy at artixlinux.org > To: artix-general at artixlinux.org > Subject: Re: [artix-general] [s6] alsa failing on boot for laptop > Message-ID: 3bf3479d-993b-47aa-6b85-2e3476c2a751 at artixlinux.org > Content-Type: text/plain; charset=utf-8; format=flowed > > On 9/19/20 11:35 PM, Javier via artix-general wrote: > > > However, I still have the issue with alsa on boot. What happens is that the alsa setting can't be recovered on boot, which is really annoying, given one really needs to remember resetting alsa, or deal with that resetting when urged to do so. > > Does running "alsactl restore" in the terminal work after boot up? > I assume that sound works normally otherwise. > > > -------------------------------------------------------------------------------------------------------------------- > > Message: 5 > Date: Sun, 20 Sep 2020 00:02:11 -0500 > From: Dudemanguy dudemanguy at artixlinux.org > To: artix-general at artixlinux.org > Subject: Re: [artix-general] [s6] not booting/rebooting laptop > Message-ID: e05fec98-a498-ec49-ce3f-6538d9e6f2ba at artixlinux.org > Content-Type: text/plain; charset=utf-8; format=flowed > > On 9/19/20 10:39 PM, Javier via artix-general wrote: > > > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever running "sudo poweroff", or "sudo reboot", the laptop actually kills several things, and sends the message on console saying something like "system shutting down" or similar. > > Well it's definitely s6 binaries that do init/shutdown. Does this happen > regularly? One thing you could attempt is to reinstall s6-linux-init > again. It would remake new init/poweroff/etc. binaries. Unsure if that > would actually fix your issue however. > > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Message: 6 > Date: Sun, 20 Sep 2020 02:10:37 -0600 > From: Javier je-vv at e.email > To: artix-general at artixlinux.org > Subject: Re: [artix-general] [s6] not booting/rebooting laptop > Message-ID: 35ba27c0-b278-100a-0b4e-0d27800e048a at e.email > Content-Type: text/plain; charset="utf-8" > > On 9/19/20 11:02 PM, Dudemanguy via artix-general wrote: > > > On 9/19/20 10:39 PM, Javier via artix-general wrote: > > > > > With Laptop "HP EliteBook 840 G3" with processor "Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz" (dual core), and using S6 (init + supervisor), whenever running "sudo poweroff", or "sudo reboot", the laptop actually kills several things, and sends the message on console saying something like "system shutting down" or similar. > > > > Well it's definitely s6 binaries that do init/shutdown. Does this happen > > regularly? One thing you could attempt is to reinstall s6-linux-init > > again. It would remake new init/poweroff/etc. binaries. Unsure if that > > would actually fix your issue however. > > Only once like in 20 times a reboot has succeeded, and no luck with poweroff at all. I'll try your suggestion Tomorrow. > > Thanks ! > > ------------------------------------------------------------------------------------------------------------------------------------ > > Javier > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20200920/8f4605e7/attachment.sig > > -- > > Subject: Digest Footer > > artix-general mailing list > artix-general at artixlinux.org > https://lists.artixlinux.org/listinfo/artix-general > > > --------------------------------------------------------------------------------------------------------------------------------------- > > End of artix-general Digest, Vol 19, Issue 3 From je-vv at e.email Sun Sep 20 11:33:41 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 03:33:41 -0600 Subject: [artix-general] artix-general Digest, Vol 19, Issue 3 In-Reply-To: <7ug4wZN0UyGbh2LoaAA_RyjoQUqxxh2PuG979QRn_nRR8DCYyR-f_NmSUBSBo7ndVI0CotcwwCJtpnHPQiPLmJJuouoSjiAYGtGvu2r0Fwk=@protonmail.com> References: <7ug4wZN0UyGbh2LoaAA_RyjoQUqxxh2PuG979QRn_nRR8DCYyR-f_NmSUBSBo7ndVI0CotcwwCJtpnHPQiPLmJJuouoSjiAYGtGvu2r0Fwk=@protonmail.com> Message-ID: On 9/20/20 2:37 AM, charliebrownau via artix-general wrote: > Gday > Does the OS pickup the audio chipset for the laptop ? What alsa complains about is an intel HDA sound card: ----------------- alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" Hardware is initialized using a generic method ----------------- And the linux module corresponds to the intel HDA sound card as well: ----------------- 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company EliteBook 840 G3 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Check using hardware info or lspci command > > HP EliteBook 840 G3 audio is using - Conexant ISST HD Audio Driver 2015 > ref - https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-840-g3-notebook-pc/7815294 > > I am using Artix with Presonus Audiobox USB (recording interface) It's possible to use an USB sound device, but I prefer to take advantage of the laptop sound card, and use a headset which I plug into the headset jack. > > Mine doesnt work with ALSA sound volume/mixer either Well, alsa sound works fine. What's wrong is that on boot, the alsa settings are not getting recovered. Not sure if you got that message I sent, where I clarified it was my bad to point out sound wasn't working. Not sure what's going on with the restore though... > > I recommend using > * LibreWolf for Browser Sound (works with ALSA) - > https://librewolf-community.gitlab.io/ Firefox also works fine with alsa (https://wiki.archlinux.org/index.php/Firefox/Tweaks#Get_ALSA_working_back). > * SMplayer for movies/media I've been using smplayer as well for quite a while. > * Strawberry for podcasts - https://www.strawberrymusicplayer.org/ I don't pay attention to podcasts, but for music player I use mpd + ncmpcpp > > Also try to get people to migrate from Skype+Zoom For work, I can't get rid of zoom and SFB one (Skype for Business), neither slack... > over to Jitsi meet - No program needed, its all via free https server > - https://meet.jit.si/ I have used Jitsi, but unfortunately barely since pretty much no contact of mine uses it. > > > Regards > Charliebrownau > Sent with ProtonMail Secure Email. I'm not sure what might be going on. Not sure if an issue from the init system (using S6), or if an issue with the alsa-utils package, or with some other alsa related package... Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 11:39:01 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 03:39:01 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> Message-ID: <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> On 9/20/20 2:18 AM, Javier via artix-general wrote: > On 9/19/20 10:59 PM, Dudemanguy via artix-general wrote: >> On 9/19/20 11:35 PM, Javier via artix-general wrote: >>> However, I still have the issue with alsa on boot.? What happens is that the alsa setting can't be recovered on boot, which is really annoying, given one really needs to remember resetting alsa, or deal with that resetting when urged to do so. >> >> Does running "alsactl restore" in the terminal work after boot up? >> I assume that sound works normally otherwise. > > Unfortunately not, it's the same as when as try the oneshot service, and as on boot: > >> % sudo alsactl restore >> [sudo] password for vasqueja: >> alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 >> Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" >> Hardware is initialized using a generic method >> alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #21 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #24 (No such file or directory) >> alsactl: set_control:1325: failed to obtain info for control #25 (No such file or directory) > > So no luck with "alsactl restore", :( And yes, sound is working fine, just that I have to set several things manually through alsactl after boot, particularly for the mic... Really weird. BTW, this happens with both linux versions, 5.8.8.artix1-1 and 5.8.10.artix1-1, and the linux module: > 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) > Subsystem: Hewlett-Packard Company EliteBook 840 G3 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 64 > Interrupt: pin A routed to IRQ 131 > IOMMU group: 8 > Region 0: Memory at e1244000 (64-bit, non-prefetchable) [size=16K] > Region 4: Memory at e1230000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Address: 00000000fee003b8 Data: 0000 > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel, snd_soc_skl As mentioned on a digest message answer, sound works (I apologize for given the wrong impression before), but what's not working is the alsa settings restore on boot, since "alsactl restore" just fails as indicated. Not sure if an alsa-utils package issue, or rather another alsa related package. As "alsactl restore" fails, perhaps this is not related with S6 neither the S6 related packages. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 11:40:57 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 03:40:57 -0600 Subject: [artix-general] artix-general Digest, Vol 19, Issue 3 In-Reply-To: References: <7ug4wZN0UyGbh2LoaAA_RyjoQUqxxh2PuG979QRn_nRR8DCYyR-f_NmSUBSBo7ndVI0CotcwwCJtpnHPQiPLmJJuouoSjiAYGtGvu2r0Fwk=@protonmail.com> Message-ID: <9ad17e8f-2296-aa01-512b-5416b3d061cf@e.email> On 9/20/20 3:33 AM, Javier via artix-general wrote: > On 9/20/20 2:37 AM, charliebrownau via artix-general wrote: >> Gday >> Does the OS pickup the audio chipset for the laptop ? > > What alsa complains about is an intel HDA sound card: > > ----------------- > alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 > Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" > Hardware is initialized using a generic method > ----------------- > > And the linux module corresponds to the intel HDA sound card as well: > > ----------------- > 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) > Subsystem: Hewlett-Packard Company EliteBook 840 G3 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Latency: 64 > Interrupt: pin A routed to IRQ 131 > IOMMU group: 8 > Region 0: Memory at e1244000 (64-bit, non-prefetchable) [size=16K] > Region 4: Memory at e1230000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Address: 00000000fee003b8 Data: 0000 > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel, snd_soc_skl > ----------------- > > I'm not sure about "conexant", since this is the 1st time I see that message from alsa. On Arch I never saw such message, and the alsa settings recovery was always successful. > >> Check using hardware info or lspci command >> >> HP EliteBook 840 G3 audio is using - Conexant ISST HD Audio Driver 2015 >> ref - https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-840-g3-notebook-pc/7815294 >> >> I am using Artix with Presonus Audiobox USB (recording interface) > > It's possible to use an USB sound device, but I prefer to take advantage of the laptop sound card, and use a headset which I plug into the headset jack. > >> >> Mine doesnt work with ALSA sound volume/mixer either > > Well, alsa sound works fine. What's wrong is that on boot, the alsa settings are not getting recovered. Not sure if you got that message I sent, where I clarified it was my bad to point out sound wasn't working. Not sure what's going on with the restore though... > >> >> I recommend using >> * LibreWolf for Browser Sound (works with ALSA) - >> https://librewolf-community.gitlab.io/ > > Firefox also works fine with alsa (https://wiki.archlinux.org/index.php/Firefox/Tweaks#Get_ALSA_working_back). > >> * SMplayer for movies/media > > I've been using smplayer as well for quite a while. > >> * Strawberry for podcasts - https://www.strawberrymusicplayer.org/ > > I don't pay attention to podcasts, but for music player I use mpd + ncmpcpp > >> >> Also try to get people to migrate from Skype+Zoom > > For work, I can't get rid of zoom and SFB one (Skype for Business), neither slack... > >> over to Jitsi meet - No program needed, its all via free https server >> - https://meet.jit.si/ > > I have used Jitsi, but unfortunately barely since pretty much no contact of mine uses it. > >> >> >> Regards >> Charliebrownau >> Sent with ProtonMail Secure Email. > > I'm not sure what might be going on. Not sure if an issue from the init system (using S6), or if an issue with the alsa-utils package, or with some other alsa related package... Sorry, rather I suspect not an init (S6) package related issue, given "alsactl restore" just fails, as shown in the original thread, and sound just works fine any ways. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Sun Sep 20 17:13:47 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 20 Sep 2020 10:13:47 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> Message-ID: <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> On 9/20/20 3:29 AM, Javier via artix-general wrote: > I decided to try it at once, and no luck, :(. After reinstalling s6-linux-init (pacman -S s6-linux-init), I tried rebooting 3 times, and reboot always hanged (had to force the power down with the power button)... Okay, I think this was my fault. I cleaned up the s6-linux-init package a little too much. The binaries need to be remade for every individual install (I accidentally removed that part). I pushed what should be a fixed version in testing. Give it and try and see how that goes. It might still fail once, but hopefully after that it'll work again. From dudemanguy at artixlinux.org Sun Sep 20 17:21:52 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 20 Sep 2020 10:21:52 -0500 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> Message-ID: On 9/20/20 4:39 AM, Javier via artix-general wrote: > As mentioned on a digest message answer, sound works (I apologize for given the wrong impression before), but what's not working is the alsa settings restore on boot, since "alsactl restore" just fails as indicated. Not sure if an alsa-utils package issue, or rather another alsa related package. As "alsactl restore" fails, perhaps this is not related with S6 neither the S6 related packages. So does "alsactl store" work without any issues then? It should create a /var/lib/alsa/asound.state file. From je-vv at e.email Sun Sep 20 19:37:03 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 11:37:03 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> Message-ID: <0cb559e8-b7b5-9b94-ab9f-eed843bd34fd@e.email> On 9/20/20 9:21 AM, Dudemanguy via artix-general wrote: > On 9/20/20 4:39 AM, Javier via artix-general wrote: >> As mentioned on a digest message answer, sound works (I apologize for given the wrong impression before), but what's not working is the alsa settings restore on boot, since "alsactl restore" just fails as indicated.? Not sure if an alsa-utils package issue, or rather another alsa related package.? As "alsactl restore" fails, perhaps this is not related with S6 neither the S6 related packages. > > So does "alsactl store" work without any issues then? It should create > a /var/lib/alsa/asound.state file. Ohh, as usual, your help is much appreciated. Yes "alsactl store" does work. And after manual execution of "alsactl store", "alsactl restore" does work as well. Actually I no longer get the boot message. But that means, on boot I get the state manually stored, not the final alsa state before boot. I believe the issue is the same as the poweroff and reset hanging. I think the issue is that when shutting down and hanging, the laptop never gets to store the alsa state... What do you think? Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 20:15:02 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 12:15:02 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> Message-ID: On 9/20/20 9:13 AM, Dudemanguy via artix-general wrote: > On 9/20/20 3:29 AM, Javier via artix-general wrote: >> I decided to try it at once, and no luck, :(.? After reinstalling s6-linux-init (pacman -S s6-linux-init), I tried rebooting 3 times, and reboot always hanged (had to force the power down with the power button)... > > Okay, I think this was my fault. I cleaned up the s6-linux-init package > a little too much. The binaries need to be remade for every individual > install (I accidentally removed that part). I pushed what should be a > fixed version in testing. Give it and try and see how that goes. It > might still fail once, but hopefully after that it'll work again. Well, I tried the current version in gremlins (1.0.4.1-3), as opposed to the current version in system (1.0.4.1-2), and that fixed the reboot and the poweroff issues, :). Unfortunately it broke S6 starting services and oneshots. On boot, only one tty gets enabled, it's not tty1, console-setup never gets started since I use a terminus font that never gets loaded as an example, and dhcpcd neither. Actually look at the error message when trying to start dhcpcd: % sudo s6-rc -u change dhcpcd s6-rc: fatal: unable to take locks: No such file or directory As another example fuse doesn't work either. So yes, s6-linux-init in gremlins does fix reboot/poweroff, but can't be used, since it sort of breaks S6... But I'm glad it seems it'll get fixed, :). Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Sun Sep 20 22:17:01 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 20 Sep 2020 15:17:01 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> Message-ID: <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> On 9/20/20 1:15 PM, Javier via artix-general wrote: > So yes, s6-linux-init in gremlins does fix reboot/poweroff, but can't be used, since it sort of breaks S6... But I'm glad it seems it'll get fixed, Argh, scripting error on my part. If you check your directories, there's a /etc/s6/current/scripts/scripts folder with a bunch of scripts in it. Just move those scripts out to /etc/s6/current/scripts and get rid of the /etc/s6/current/scripts/scripts folder. It should work again after a reboot. From je-vv at e.email Sun Sep 20 22:48:38 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 14:48:38 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> Message-ID: <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> On 9/20/20 2:17 PM, Dudemanguy via artix-general wrote: > On 9/20/20 1:15 PM, Javier via artix-general wrote: >> So yes, s6-linux-init in gremlins does fix reboot/poweroff, but can't be used, since it sort of breaks S6...? But I'm glad it seems it'll get fixed, > > Argh, scripting error on my part. If you check your directories, there's > a /etc/s6/current/scripts/scripts folder with a bunch of scripts in it. > Just move those scripts out to /etc/s6/current/scripts and get rid of > the /etc/s6/current/scripts/scripts folder. It should work again after a > reboot. OK, with that, S6 doesn't break, it boots normal. However though reboot started working back, poweroff still hangs. So it seems poweroff requires some more tuning? BTW, there was not only on scripts sub-directory inside scripts. There's another one inside that one: /etc/s6/current/scripts/scripts/scripts -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Sep 20 23:07:55 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 15:07:55 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> Message-ID: <946ee78f-4442-7add-471e-9de91c17c77f@e.email> On 9/20/20 2:48 PM, Javier via artix-general wrote: > On 9/20/20 2:17 PM, Dudemanguy via artix-general wrote: >> On 9/20/20 1:15 PM, Javier via artix-general wrote: >>> So yes, s6-linux-init in gremlins does fix reboot/poweroff, but can't be used, since it sort of breaks S6...? But I'm glad it seems it'll get fixed, >> >> Argh, scripting error on my part. If you check your directories, there's >> a /etc/s6/current/scripts/scripts folder with a bunch of scripts in it. >> Just move those scripts out to /etc/s6/current/scripts and get rid of >> the /etc/s6/current/scripts/scripts folder. It should work again after a >> reboot. > > OK, with that, S6 doesn't break, it boots normal. However though reboot started working back, poweroff still hangs. So it seems poweroff requires some more tuning? > > BTW, there was not only on scripts sub-directory inside scripts. There's another one inside that one: > > /etc/s6/current/scripts/scripts/scripts My bad, none is working, not "poweroff", neither "reboot". That was some sort of good luck on 1st trial I'd guess... BTW, I actually re-installed the gremlins package again, so that I started just from the 1st sub-dir, and not having 3 sub-dirs... So no luck, :(. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Mon Sep 21 00:00:38 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 16:00:38 -0600 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <0cb559e8-b7b5-9b94-ab9f-eed843bd34fd@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> <0cb559e8-b7b5-9b94-ab9f-eed843bd34fd@e.email> Message-ID: <73311ccc-8b1d-2d60-1dbe-661b91a56c91@e.email> On 9/20/20 11:37 AM, Javier via artix-general wrote: > On 9/20/20 9:21 AM, Dudemanguy via artix-general wrote: >> On 9/20/20 4:39 AM, Javier via artix-general wrote: >>> As mentioned on a digest message answer, sound works (I apologize for given the wrong impression before), but what's not working is the alsa settings restore on boot, since "alsactl restore" just fails as indicated.? Not sure if an alsa-utils package issue, or rather another alsa related package.? As "alsactl restore" fails, perhaps this is not related with S6 neither the S6 related packages. >> >> So does "alsactl store" work without any issues then? It should create >> a /var/lib/alsa/asound.state file. > > Ohh, as usual, your help is much appreciated. Yes "alsactl store" does work. And after manual execution of "alsactl store", "alsactl restore" does work as well. Actually I no longer get the boot message. But that means, on boot I get the state manually stored, not the final alsa state before boot. > > I believe the issue is the same as the poweroff and reset hanging. I think the issue is that when shutting down and hanging, the laptop never gets to store the alsa state... What do you think? > > Thanks ! I believe I've confirmed it... See, if I delete "/var/lib/alsa/asound.state", and then poweroff or reboot, then upon boot, "alsactl restore" fails, as well as executing it manually, since it doesn't find the stored state. But if I manually store the alsa state with "alsactl store", then "alsactl restore" succeeds both, on boot and manually. So I guess I need to try again once the "poweroff" and "reboot" issues with S6 get fixed... Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Mon Sep 21 00:06:31 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 16:06:31 -0600 Subject: [artix-general] artix-general Digest, Vol 19, Issue 3 In-Reply-To: <9ad17e8f-2296-aa01-512b-5416b3d061cf@e.email> References: <7ug4wZN0UyGbh2LoaAA_RyjoQUqxxh2PuG979QRn_nRR8DCYyR-f_NmSUBSBo7ndVI0CotcwwCJtpnHPQiPLmJJuouoSjiAYGtGvu2r0Fwk=@protonmail.com> <9ad17e8f-2296-aa01-512b-5416b3d061cf@e.email> Message-ID: On 9/20/20 3:40 AM, Javier via artix-general wrote: > On 9/20/20 3:33 AM, Javier via artix-general wrote: >> On 9/20/20 2:37 AM, charliebrownau via artix-general wrote: >>> Gday >>> Does the OS pickup the audio chipset for the laptop ? >> >> What alsa complains about is an intel HDA sound card: >> >> ----------------- >> alsa-lib main.c:983:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 >> Found hardware: "HDA-Intel" "Conexant CX20724" "HDA:14f150f4,103c8079,00100101 HDA:80862809,80860101,00100000" "0x103c" "0x8079" >> Hardware is initialized using a generic method >> ----------------- >> >> And the linux module corresponds to the intel HDA sound card as well: >> >> ----------------- >> 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) >> Subsystem: Hewlett-Packard Company EliteBook 840 G3 >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- > Latency: 64 >> Interrupt: pin A routed to IRQ 131 >> IOMMU group: 8 >> Region 0: Memory at e1244000 (64-bit, non-prefetchable) [size=16K] >> Region 4: Memory at e1230000 (64-bit, non-prefetchable) [size=64K] >> Capabilities: [50] Power Management version 3 >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+) >> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- >> Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ >> Address: 00000000fee003b8 Data: 0000 >> Kernel driver in use: snd_hda_intel >> Kernel modules: snd_hda_intel, snd_soc_skl >> ----------------- >> >> I'm not sure about "conexant", since this is the 1st time I see that message from alsa. On Arch I never saw such message, and the alsa settings recovery was always successful. >> >>> Check using hardware info or lspci command >>> >>> HP EliteBook 840 G3 audio is using - Conexant ISST HD Audio Driver 2015 >>> ref - https://support.hp.com/us-en/drivers/selfservice/hp-elitebook-840-g3-notebook-pc/7815294 >>> >>> I am using Artix with Presonus Audiobox USB (recording interface) >> >> It's possible to use an USB sound device, but I prefer to take advantage of the laptop sound card, and use a headset which I plug into the headset jack. >> >>> >>> Mine doesnt work with ALSA sound volume/mixer either >> >> Well, alsa sound works fine. What's wrong is that on boot, the alsa settings are not getting recovered. Not sure if you got that message I sent, where I clarified it was my bad to point out sound wasn't working. Not sure what's going on with the restore though... >> >>> >>> I recommend using >>> * LibreWolf for Browser Sound (works with ALSA) - >>> https://librewolf-community.gitlab.io/ >> >> Firefox also works fine with alsa (https://wiki.archlinux.org/index.php/Firefox/Tweaks#Get_ALSA_working_back). >> >>> * SMplayer for movies/media >> >> I've been using smplayer as well for quite a while. >> >>> * Strawberry for podcasts - https://www.strawberrymusicplayer.org/ >> >> I don't pay attention to podcasts, but for music player I use mpd + ncmpcpp >> >>> >>> Also try to get people to migrate from Skype+Zoom >> >> For work, I can't get rid of zoom and SFB one (Skype for Business), neither slack... >> >>> over to Jitsi meet - No program needed, its all via free https server >>> - https://meet.jit.si/ >> >> I have used Jitsi, but unfortunately barely since pretty much no contact of mine uses it. >> >>> >>> >>> Regards >>> Charliebrownau >>> Sent with ProtonMail Secure Email. >> >> I'm not sure what might be going on. Not sure if an issue from the init system (using S6), or if an issue with the alsa-utils package, or with some other alsa related package... > > Sorry, rather I suspect not an init (S6) package related issue, given "alsactl restore" just fails, as shown in the original thread, and sound just works fine any ways. > > Thanks ! After the help gotten on the original thread, "[artix-general] [s6] alsa failing on boot for laptop", it seems I was wrong about discarding S6 init. In the end, I can even store the alsa state, and the problem with my laptop is that poweroff and reboot hang, and therefore, most probably don't get to store the alsa state, so the alsa state restore fails both, on boot and manually attempted. IF I, at some point, store that state manually, then from the point on, whatever I last stored manually, is what moving forward gets restored, whether on boot or manually, and then I'm no longer experiencing the error on boot... However I still need to test once the "reboot" and "poweroff" S6 issues get solved. Greetings ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Mon Sep 21 00:30:21 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 20 Sep 2020 17:30:21 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <946ee78f-4442-7add-471e-9de91c17c77f@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> Message-ID: On 9/20/20 4:07 PM, Javier via artix-general wrote: > My bad, none is working, not "poweroff", neither "reboot". That was some sort of good luck on 1st trial I'd guess... BTW, I actually re-installed the gremlins package again, so that I started just from the 1st sub-dir, and not having 3 sub-dirs... So no luck,:(. Could you do a pacman -Sy, install the version from system, and then reinstall the gremlins one? I updated/pushed a new one and the main mirror synced. From dudemanguy at artixlinux.org Mon Sep 21 00:33:53 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 20 Sep 2020 17:33:53 -0500 Subject: [artix-general] [s6] alsa failing on boot for laptop In-Reply-To: <73311ccc-8b1d-2d60-1dbe-661b91a56c91@e.email> References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> <0cb559e8-b7b5-9b94-ab9f-eed843bd34fd@e.email> <73311ccc-8b1d-2d60-1dbe-661b91a56c91@e.email> Message-ID: On 9/20/20 5:00 PM, Javier via artix-general wrote: > I believe I've confirmed it... See, if I delete "/var/lib/alsa/asound.state", and then poweroff or reboot, then upon boot, "alsactl restore" fails, as well as executing it manually, since it doesn't find the stored state. But if I manually store the alsa state with "alsactl store", then "alsactl restore" succeeds both, on boot and manually. > > So I guess I need to try again once the "poweroff" and "reboot" issues with S6 get fixed... Well the latest alsa-utils-s6 script does check if /var/lib/alsa/asound.state exists before trying to run alsa restore, so you shouldn't be having this problem actually. Maybe the test is wrong. From je-vv at e.email Mon Sep 21 01:46:47 2020 From: je-vv at e.email (Javier) Date: Sun, 20 Sep 2020 17:46:47 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> Message-ID: <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> On 9/20/20 4:30 PM, Dudemanguy via artix-general wrote: > On 9/20/20 4:07 PM, Javier via artix-general wrote: >> My bad, none is working, not "poweroff", neither "reboot".? That was some sort of good luck on 1st trial I'd guess...? BTW, I actually re-installed the gremlins package again, so that I started just from the 1st sub-dir, and not having 3 sub-dirs...? So no luck,:(. > > Could you do a pacman -Sy, install the version from system, and then > reinstall the gremlins one? I updated/pushed a new one and the main > mirror synced. I did it already, with same results. The gremlins version kept being 1.0.4.1-3, but the package was different, since pacman complained, requesting to remove the old cached package. But no luck, :(, reboot and poweroff still hang. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From ruben at mrbrklyn.com Mon Sep 21 05:29:03 2020 From: ruben at mrbrklyn.com (Ruben Safir) Date: Sun, 20 Sep 2020 23:29:03 -0400 Subject: [artix-general] secondary DNS servers Message-ID: I am looking for some more secondary DNS servers, if someone wants to slave off my domains, and I can do vice versa. I have a half dozen domains I would like to spread out geographically. include nylxs.com and nylxs.org and mrbrklyn.com and brooklyn-living.com and brooklyn-fishing.com which I still need to set up. I want to consolidate my DNS registry and find new seconardies. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 From dudemanguy at artixlinux.org Wed Sep 23 23:21:44 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Wed, 23 Sep 2020 16:21:44 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> Message-ID: <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> On 9/20/20 6:46 PM, Javier via artix-general wrote: > I did it already, with same results. The gremlins version kept being 1.0.4.1-3, but the package was different, since pacman complained, requesting to remove the old cached package. But no luck, Apologies for the delay, but did 1.0.4.1-1 work fine on this laptop? I did discover one possible difference in the PKGBUILD that may be related (using mv instead of cp -a). Hopefully that will fix it for you since otherwise there isn't any difference between 1.0.4.1-1 and 1.0.4.1-3 when it comes to installing the binaries. I updated the gremlins package (no version change again) so give it a reinstall and hope for the best... From je-vv at e.email Thu Sep 24 00:19:51 2020 From: je-vv at e.email (Javier) Date: Wed, 23 Sep 2020 16:19:51 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> Message-ID: On 9/23/20 3:21 PM, Dudemanguy via artix-general wrote: > On 9/20/20 6:46 PM, Javier via artix-general wrote: >> I did it already, with same results.? The gremlins version kept being 1.0.4.1-3, but the package was different, since pacman complained, requesting to remove the old cached package.? But no luck, > > Apologies for the delay, but did 1.0.4.1-1 work fine on this laptop? > I did discover one possible difference in the PKGBUILD that may be > related (using mv instead of cp -a). Hopefully that will fix it for > you since otherwise there isn't any difference between 1.0.4.1-1 and > 1.0.4.1-3 when it comes to installing the binaries. I updated the > gremlins package (no version change again) so give it a reinstall and > hope for the best... Did you just upload it? I might need to wait for it, since I didn't get any pacman message about package corrupted, or anything like that, which should happen if the package (same version) changes... BTW, I don't know about 1.0.4.1-1, I'll have to get it from an archive repo. Greetings ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Thu Sep 24 01:02:59 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Wed, 23 Sep 2020 18:02:59 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> Message-ID: <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> On 9/23/20 5:19 PM, Javier via artix-general wrote: > Did you just upload it? I might need to wait for it, since I didn't get any pacman message about package corrupted, or anything like that, which should happen if the package (same version) changes... BTW, I don't know about 1.0.4.1-1, I'll have to get it from an archive repo. Yeah this was about an hour ago or so. I was under the impression that my s6-linux-init package cleanup broke your poweroff/reboot commands somehow, but perhaps it's not even related. If 1.0.4.1-1 has the same issue, it's quite probable you actually discovered a s6-linux-init bug. Well regardless, I was too vigorous in my cleanup and removed things I shouldn't have removed so at least something good came out of this. :) From je-vv at e.email Thu Sep 24 02:08:01 2020 From: je-vv at e.email (Javier) Date: Wed, 23 Sep 2020 18:08:01 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> Message-ID: <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> On 9/23/20 5:02 PM, Dudemanguy via artix-general wrote: > On 9/23/20 5:19 PM, Javier via artix-general wrote: >> Did you just upload it?? I might need to wait for it, since I didn't get any pacman message about package corrupted, or anything like that, which should happen if the package (same version) changes...? BTW, I don't know about 1.0.4.1-1, I'll have to get it from an archive repo. > > Yeah this was about an hour ago or so. I was under the impression that > my s6-linux-init package cleanup broke your poweroff/reboot commands > somehow, but perhaps it's not even related. If 1.0.4.1-1 has the same > issue, it's quite probable you actually discovered a s6-linux-init bug. > Well regardless, I was too vigorous in my cleanup and removed things I > shouldn't have removed so at least something good came out of this. :) The new 1.0.4.1-3 makes the linux kernel segfault on boot. So not much progress with it. BTW, installing it is weird, since it makes me overwrite the the files it owns any ways... Greetings ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Thu Sep 24 02:23:13 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Wed, 23 Sep 2020 19:23:13 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> Message-ID: <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> On 9/23/20 7:08 PM, Javier via artix-general wrote: >BTW, installing it is weird, since it makes me overwrite the the files it owns any ways.. Okay yeah, that definitely shouldn't have happened. My own machines changed to that one without any issues. Maybe the bad one I pushed messed up your machine in subtle ways. It definitely shouldn't have segfaulted either. Not sure what to say at this point. From je-vv at e.email Thu Sep 24 02:39:05 2020 From: je-vv at e.email (Javier) Date: Wed, 23 Sep 2020 18:39:05 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> Message-ID: <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> On 9/23/20 6:23 PM, Dudemanguy via artix-general wrote: > On 9/23/20 7:08 PM, Javier via artix-general wrote: >> BTW, installing it is weird, since it makes me overwrite the the files it owns any ways.. > > Okay yeah, that definitely shouldn't have happened. My own machines > changed to that one without any issues. Maybe the bad one I pushed > messed up your machine in subtle ways. It definitely shouldn't have > segfaulted either. Not sure what to say at this point. One thing is for sure, when you accidentally made the scripts install in sub-dirs, I could poweroff and reboot fine. The issue was that no servers/oneshots were triggered at boot, :). So, there's something about scripts making powerdown hang. About the installing, well, I have no idea, but once I install the package, I can re-install the exact same package several times without issues... Please don't give up just yet. Seems like there's still hope, or so I believe so, :) Is there a way I can turn logging on for s6-linux-init in general (including the scripts), that gets logged somewhere (hopefully not getting corrupted, sine the disks are not getting unmounted on powerdown, and at boot I'm always getting journal cleanups)... Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Thu Sep 24 02:49:19 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Wed, 23 Sep 2020 19:49:19 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> Message-ID: <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> On 9/23/20 7:39 PM, Javier via artix-general wrote: > One thing is for sure, when you accidentally made the scripts install in sub-dirs, I could poweroff and reboot fine. The issue was that no servers/oneshots were triggered at boot, :). So, there's something about scripts making powerdown hang. About the installing, well, I have no idea, but once I install the package, I can re-install the exact same package several times without issues... > > Please don't give up just yet. Seems like there's still hope, or so I believe so, :) > > Is there a way I can turn logging on for s6-linux-init in general (including the scripts), that gets logged somewhere (hopefully not getting corrupted, sine the disks are not getting unmounted on powerdown, and at boot I'm always getting journal cleanups)... > Not sure. Maybe your scripts in /etc/s6/current/scripts are all messed up somehow. The rc.shutdown should just be a call to single call to "exec s6-rc -bda change". This technically blocks (waits for every service to be killed of course), but shouldn't take forever. rc.shutdown.final should just be entirely comments and do nothing. As for logs, maybe you'll have something interesting in /run/uncaught-logs/current. That's where something would go if it's not caught by the usual s6-log log daemons (those are in /var/log). From dudemanguy at artixlinux.org Thu Sep 24 02:55:30 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Wed, 23 Sep 2020 19:55:30 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> Message-ID: <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> On 9/23/20 7:49 PM, Dudemanguy via artix-general wrote:> "exec s6-rc -bda change" Wait, on second thought. Maybe this is the problem after all? Checking the skarnet documentation: >-b : blocking lock. If the service database is currently being used by >another program, s6-rc will wait until that other program has released >its lock on the database, then proceed. By default, s6-rc fails with an >error message if the service database is currently in use. The default >is the safe behaviour: for instance, it will correctly detect and fail >nested s6-rc invocations (which are an admin error), whereas s6-rc -b >would deadlock in such a case. https://skarnet.org/software/s6-rc/s6-rc.html Perhaps you somehow have a nest s6-rc invocation causing a deadlock? That would explain it. From je-vv at e.email Thu Sep 24 03:30:38 2020 From: je-vv at e.email (Javier) Date: Wed, 23 Sep 2020 19:30:38 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> Message-ID: <7060c697-f79b-9dad-40ca-04105eb23584@e.email> On 9/23/20 6:55 PM, Dudemanguy via artix-general wrote: > On 9/23/20 7:49 PM, Dudemanguy via artix-general wrote:> "exec s6-rc -bda change" > > Wait, on second thought. Maybe this is the problem after all? > Checking the skarnet documentation: > >>-b : blocking lock. If the service database is currently being used by >>another program, s6-rc will wait until that other program has released >>its lock on the database, then proceed. By default, s6-rc fails with an >>error message if the service database is currently in use. The default >>is the safe behaviour: for instance, it will correctly detect and fail >>nested s6-rc invocations (which are an admin error), whereas s6-rc -b >>would deadlock in such a case. > https://skarnet.org/software/s6-rc/s6-rc.html > > Perhaps you somehow have a nest s6-rc invocation causing a deadlock? > That would explain it. How can I have a nest s6-rc? Please let me know. I don't call s6-rc manually at all, unless restarting a service, or installing a new one on the fly. And I don't have modified services/oneshots (the /etc/s6/* stuff is vanilla). But not sure if there might be some non able to shutdown services though. If there's one non dying service, perhaps that's it. But how could I know? BTW, I just run "sudo s6-rc -b -a list" to test if it got blocked waiting, and it didn't. In general, I have no issues restarting services, like "sudo s6-rc -d change autofs && sudo s6-rc -u change autofs", I just tried it and it was almost instant, and running "sudo s6-rc -b -d change autofs && sudo s6-rc -b -u change autofs" was almost instant as well... I also tried some I know safe to reboot on the fly: clamd, cronie, cupsd, freshclam, smbd, nmbd, sshd... BTW, I doubt the scripts are messed up, since upon a fresh install of the package, they shouldn't be corrupted or messed up, right? And I don't touch them at all... Is there a way to make s6-rc verbose, so that we can see what's it waiting for? Like making it print on the screen waiting for X service to go down, and when Y service is down, also indicating service Y already down... So somehow we can see 1st the last service waited for, and then see if all the ones waited for, were already down... As of now: % sudo s6-rc -a list s6rc-oneshot-runner s6rc-fdholder agetty-tty2 agetty-tty3 agetty-tty4 agetty-tty5 agetty-tty6 autofs-log autofs-srv clamd-log clamd-srv cronie-log cronie-srv cupsd-log cupsd-srv dbus-log dbus-srv dhcpcd-log dhcpcd-srv elogind-log elogind-srv freshclam-log freshclam-srv gpm-log gpm-srv lvmetad-log lvmetad-srv lvmpolld-log lvmpolld-srv mpd-log mpd-srv nmbd-log nmbd-srv ntpd-log ntpd-srv rngd-log rngd-srv smbd-log smbd-srv sshd-log sshd-srv thermald-log thermald-srv udevd-log udevd-srv wpa_supplicant-log wpa_supplicant-srv alsa binfmt cleanup console-setup cryptsetup dmesg hostname hwclock kmod-static-nodes lm_sensors lvm2-monitor lvm2-pvscan modules mount-cgroups mount-devfs mount-filesystems mount-net mount-procfs mount-sysfs net-lo random-seed rc-local swap sysctl sysuser tmpfiles-dev tmpfiles-setup udevadm I don't suspect of any getting stuck, but who knows. -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Thu Sep 24 03:42:14 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Wed, 23 Sep 2020 20:42:14 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <7060c697-f79b-9dad-40ca-04105eb23584@e.email> References: <35ba27c0-b278-100a-0b4e-0d27800e048a@e.email> <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> Message-ID: On 9/23/20 8:30 PM, Javier via artix-general wrote: > How can I have a nest s6-rc? Please let me know. I don't call s6-rc manually at all, unless restarting a service, or installing a new one on the fly. And I don't have modified services/oneshots (the /etc/s6/* stuff is vanilla). But not sure if there might be some non able to shutdown services though. If there's one non dying service, perhaps that's it. But how could I know? Just a thought. Since earlier you said that poweroff/reboot worked fine when I broke your s6-rc scripts, perhaps you are somehow having a deadlock on this machine (although I don't know how). One easy way to verify is to edit /etc/s6/current/scripts/rc.init and comment out the s6-rc-init and exec lines. Maybe shutdown/poweroff will work then. If so, at least we'd finally be on the right track. > BTW, I doubt the scripts are messed up, since upon a fresh install of the package, they shouldn't be corrupted or messed up, right? And I don't touch them at all... Well I mean you surely have a default bundle right? That's always executed on startup. > Is there a way to make s6-rc verbose, so that we can see what's it waiting for? Like making it print on the screen waiting for X service to go down, and when Y service is down, also indicating service Y already down... So somehow we can see 1st the last service waited for, and then see if all the ones waited for, were already down... Definitely, you can add a -v2 argument (or maybe increase the verbosity even more) to the s6-rc call in /etc/s6/current/script/rc.shutdown. It will spam a bunch of stuff on tty1. You should also be able to check /run/uncaught-logs/ later for that output. From je-vv at e.email Thu Sep 24 18:37:58 2020 From: je-vv at e.email (Javier) Date: Thu, 24 Sep 2020 10:37:58 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <2ca33016-ff38-0fc3-2084-b83fcad88360@e.email> <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> Message-ID: <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> On 9/23/20 7:42 PM, Dudemanguy via artix-general wrote: > Just a thought. Since earlier you said that poweroff/reboot worked fine > when I broke your s6-rc scripts, perhaps you are somehow having a > deadlock on this machine (although I don't know how). One easy way to > verify is to edit /etc/s6/current/scripts/rc.init and comment out the > s6-rc-init and exec lines. Maybe shutdown/poweroff will work then. If so, at least we'd finally be on the right track. Commenting that line out, makes poweroff and reboot work flawlessly. However it also means no services/oneshots at boot. Pretty much the same as when the scripts were missing in a sub-dir. I'm missing adding verbosity still... -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Thu Sep 24 18:54:27 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Thu, 24 Sep 2020 11:54:27 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> References: <1eec7324-4c6a-ef2d-1863-dfb668e9c4dd@artixlinux.org> <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> Message-ID: On 9/24/20 11:37 AM, Javier via artix-general wrote: > Commenting that line out, makes poweroff and reboot work flawlessly. However it also means no services/oneshots at boot. Pretty much the same as when the scripts were missing in a sub-dir. I'm missing adding verbosity still... Cool, that means s6-linux-init was a red herring all along. What's actually happening is that one of the services can't be brought down and is blocking your entire shutdown somehow. You can uncomment those lines again. If you did those verbosity edits earlier, maybe you can see which service is hanging for you. From je-vv at e.email Thu Sep 24 19:33:31 2020 From: je-vv at e.email (Javier) Date: Thu, 24 Sep 2020 11:33:31 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> Message-ID: On 9/23/20 7:42 PM, Dudemanguy via artix-general wrote:> Definitely, you can add a -v2 argument (or maybe increase the verbosity > even more) to the s6-rc call in /etc/s6/current/script/rc.shutdown. It > will spam a bunch of stuff on tty1. You should also be able to check > /run/uncaught-logs/ later for that output. On 9/24/20 10:54 AM, Dudemanguy via artix-general wrote: > On 9/24/20 11:37 AM, Javier via artix-general wrote: >> Commenting that line out, makes poweroff and reboot work flawlessly.? However it also means no services/oneshots at boot.? Pretty much the same as when the scripts were missing in a sub-dir.? I'm missing adding verbosity still... > Cool, that means s6-linux-init was a red herring all along. What's > actually happening is that one of the services can't be brought down > and is blocking your entire shutdown somehow. You can uncomment those > lines again. If you did those verbosity edits earlier, maybe you can > see which service is hanging for you. Well, not quite. I actually used -v4... Just by looking at the screen output, every "service/oneshot processing" message showing up, has its corresponding "service stopped successfully" message also showing up. So I can't easily identify if a service/oneshot is causing trouble. Are those log messages stored somewhere, surviving several boots in between? Perhaps some greps might help. You can look at the last messages fitting in the screen here: https://gist.github.com/je-vv/0ed889564b6b3fcc35b7d4c14c7b1ea8 BTW, I noticed something weird. When enabling verbosity with -v2, I could poweroff/reboot successfully like 4 rounds on a row, but beyond that point it was the same thing. Then I changed to -v4 (just thinking about some race condition), and I experienced the same, like 4 poweroff/reboots sucessfull in a row, but then all the same. I don't know if there might actually be some raise condition around the services, but I can't explain why all of sudden I only get hanging powerdowns... I have the same services working fine on other boxes, but with slower and older processors, so that made me suspect of a possible raise condition... -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From dudemanguy at artixlinux.org Thu Sep 24 20:23:06 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Thu, 24 Sep 2020 13:23:06 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <03844963-9149-0143-df70-b50c2c0ac482@artixlinux.org> <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> Message-ID: On 9/24/20 12:33 PM, Javier via artix-general wrote: > https://gist.github.com/je-vv/0ed889564b6b3fcc35b7d4c14c7b1ea8 Can't say I notice anything here. Well the only thing that seems a little odd to me is the s6-ipcclient message printing there but I'm not familiar with it so maybe that's just normal. The other thing you could try doing is bringing down services manually one by one before shutting down. In theory, if you do stop all of them before powering off, the poweroff should work just fine. Of course, it would be more helpful to figure which service (or maybe combination of services) causes the hang. >Are those log messages stored somewhere, surviving several boots in between? Perhaps some greps might help. Yeah, /run/uncaught-logs wouldn't survive across boots unfortunately. There's not really an easy way to go about saving those. From je-vv at e.email Sun Sep 27 06:33:30 2020 From: je-vv at e.email (Javier) Date: Sat, 26 Sep 2020 22:33:30 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: References: <8f26ccce-0fa2-11a5-61b6-18d20cf1b1ea@e.email> <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> Message-ID: <3d376484-4c18-b79f-413a-d7ec9cfab608@e.email> I believe I found the issue, and it's the order on which S6 shutdowns dhcpcd vs. wpa_supplicant. The reason I didn't have the reboot/poweroff issues on other boxes is that I didn't enabled wpa_supplicant on them. And in fact on another Toshiba laptop where I enabled wpa_supplicant, I found the same issue. See, if wpa_supplicant is not enabled, then I can shut dhcpcd down and turn it up, and then down and up again, as many times as I want. The bottom line is that dhcpcd just shutdowns fine. If I enable wpa_supplicant, then I can shut wpa_supplicant down and turn it up, and then down and up again, also as many times as I want. With wpa_supplicant enabled, if I 1st shut wpa_supplicant down, and then I shut dhcpcd down, and then turn dhcpcd up, and then I turn wpa_supplicant up, and then I can keep repeating that process without issues as many times as I want. However, with wpa_supplicant enabled, if I 1st shut dhcpcd down, 1st it automatically makes wpa_supplicant shut down, which makes sense, since wpa_supplicant depends on dhcpcd. But after wpa_supplicant shuts down, dhcpcd just hangs, and it never shuts down. Having wpa_supplicant enabled, I tried both, without dhcpcd being part of the default bundle, and with dhcpcd being part of the default bundle (I forced shutdowns in the middle, so that the system started with the default bundle I wanted to test, and then performed the tests). There's no difference on whether dhcpcd is part of the default bundle or not. This sounds fine since whether dhcpcd is part of the default bundle or not, it gets enabled any ways, whether by wpa_supplicant in one case, or by the same wpa_supplicant reason or by being part of the default bundle in the other (whatever gets turned up 1s by S6 in the last case). I think what happens is that "s6-rc -bda change" gets to shut dhcpcd down before or at the same time than wpa_supplicant (at the same time is possible if doing stuff in parallel), and that causes issues. It seems dhcpcd is handling fine being a dependency for wpa_supplicant, since it's shutting down wpa_supplicant before the dhcpcd shutting down is attempted, but it hangs afterwords, so there's an issue with dhcpcd and wpa_supplicant. BTW, I also noticed this with the recent upgrade of s6-scripts (20200918-1 -> 20200923-1), s6-linux-init (1.0.4.1-2 -> 1.0.4.2-1) and the removal of eudev-s6. The upgrade just hanged, and I had to break it (ctrl-c), and when doing so, there was a message on failing to shut the dhcpcd service, though the removal of udev-s6 succeeded after the break. I guess the removal of the eudev service caused other services depending on it, as the dhcpcd one, to shut down, to then be brought up back once s6-scripts got upgraded. So I had to upgrade again, and to make sure, I also installed all packages on that upgrade manually... So, what do you think @Dudemanguy? Any way to deal with this order of dhcpcd vs. wpa_supplicant getting shut down, or specify that particular order to S6? -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From prmarino1 at gmail.com Mon Sep 21 06:45:30 2020 From: prmarino1 at gmail.com (Paul Robert Marino) Date: Mon, 21 Sep 2020 00:45:30 -0400 Subject: [artix-general] [Hangout - NYLXS] [s6] alsa failing on boot for laptop In-Reply-To: References: <36948b64-7f0f-3cf4-ec98-269a308728da@e.email> <71000625-2676-1782-27ef-9b1368039142@e.email> <82dcbcfc-f977-99d4-b6a1-4b03daaba228@e.email> <2bb917f2-f043-0f45-1643-d424f7e5e08e@e.email> <3bf3479d-993b-47aa-6b85-2e3476c2a751@artixlinux.org> <9e2d6017-f8f7-a478-cc37-8a5e820181e8@e.email> <395a5d38-08a1-8053-ca66-c50ca8497e8e@e.email> <0cb559e8-b7b5-9b94-ab9f-eed843bd34fd@e.email> <73311ccc-8b1d-2d60-1dbe-661b91a56c91@e.email> Message-ID: it sounds like it may not be running the stop script on shutdown. try disabling it with chkconfig then reenabling it. On Sun, Sep 20, 2020 at 7:55 PM Dudemanguy via artix-general < artix-general at artixlinux.org> wrote: > On 9/20/20 5:00 PM, Javier via artix-general wrote: > > I believe I've confirmed it... See, if I delete > "/var/lib/alsa/asound.state", and then poweroff or reboot, then upon boot, > "alsactl restore" fails, as well as executing it manually, since it doesn't > find the stored state. But if I manually store the alsa state with > "alsactl store", then "alsactl restore" succeeds both, on boot and manually. > > > > So I guess I need to try again once the "poweroff" and "reboot" issues > with S6 get fixed... > > Well the latest alsa-utils-s6 script does check if > /var/lib/alsa/asound.state exists before trying to > run alsa restore, so you shouldn't be having this > problem actually. Maybe the test is wrong. > -- > artix-general mailing list > artix-general at artixlinux.org > https://lists.artixlinux.org/listinfo/artix-general > _______________________________________________ > Hangout mailing list > Hangout at nylxs.com > http://lists.mrbrklyn.com/mailman/listinfo/hangout > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dudemanguy at artixlinux.org Sun Sep 27 17:56:35 2020 From: dudemanguy at artixlinux.org (Dudemanguy) Date: Sun, 27 Sep 2020 10:56:35 -0500 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <3d376484-4c18-b79f-413a-d7ec9cfab608@e.email> References: <946ee78f-4442-7add-471e-9de91c17c77f@e.email> <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> <3d376484-4c18-b79f-413a-d7ec9cfab608@e.email> Message-ID: <630a6ffe-f693-e2e9-21ab-8705afbb50d1@artixlinux.org> First of all, thanks for all the investigative work! >But after wpa_supplicant shuts down, dhcpcd just hangs, and it never shuts down. Do the dhcpcd logs in /var/log/dhcpcd say anything interesting here? It should say something like "received SIGTERM, stopping" when it shuts down. > So, what do you think @Dudemanguy? Any way to deal with this order of dhcpcd vs. wpa_supplicant getting shut down, or specify that particular order to S6? One thought would be to remove the dhcpcd dependency from wpa_supplicant, but I would rather not do that because you do need dhcpcd running for wpa_supplicant to work correctly. It might be possible to add a finish script that will solve your problem. For example, "wpa_cli terminate" being run when wpa_supplicant gets brought down might possibly prevent dhcpcd from hanging for you. Alternatively, dhcpcd may need a finish script itself. From je-vv at e.email Sun Sep 27 23:35:25 2020 From: je-vv at e.email (Javier) Date: Sun, 27 Sep 2020 15:35:25 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <630a6ffe-f693-e2e9-21ab-8705afbb50d1@artixlinux.org> References: <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> <3d376484-4c18-b79f-413a-d7ec9cfab608@e.email> <630a6ffe-f693-e2e9-21ab-8705afbb50d1@artixlinux.org> Message-ID: <862f0679-fe6a-0ba4-bd3b-f8b1b6f3bf41@e.email> On 9/27/20 9:56 AM, Dudemanguy via artix-general wrote: > Do the dhcpcd logs in /var/log/dhcpcd say anything interesting here? It > should say something like "received SIGTERM, stopping" when it shuts > down. The dhcpcd service actually receives the SIGTERM, and actually does exits. So that part is good, but as soon as it does, then it starts again. I believe the issue is not on the dhcpcd side though, since it seems to do things fine. What makes it start again is what's faulting. Please remember when there's no wpa_supplicant, dhcpcd dies fine. On the console: > % sudo s6-rc -d -v2 change dhcpcd > [sudo] password for vasqueja: > s6-rc: info: service wpa_supplicant-srv: stopping > s6-rc: info: service wpa_supplicant-srv successfully stopped > s6-rc: info: service dhcpcd-srv: stopping There the dhcpcd service just hangs. The corresponding /var/log/dhcpcd/current (including its start at boot): > 2020-09-27 14:36:36.037374263 dhcpcd-9.2.0 starting > 2020-09-27 14:36:36.048819381 dev: loaded udev > 2020-09-27 14:36:36.050056676 DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19 > 2020-09-27 14:36:36.152177882 no interfaces have a carrier > 2020-09-27 14:36:36.565768987 in-wired-0: waiting for carrier > 2020-09-27 14:36:36.565775437 in-wireless-0: waiting for carrier > 2020-09-27 14:36:36.565777742 in-wireless-0: carrier acquired > 2020-09-27 14:36:36.574231978 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 14:36:36.580133950 in-wireless-0: adding address fe80::55a:5374:22a4:4ce2 > 2020-09-27 14:36:36.580142432 in-wireless-0: carrier lost > 2020-09-27 14:36:36.621093633 in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2 > 2020-09-27 14:36:40.125047310 in-wireless-0: carrier acquired > 2020-09-27 14:36:40.126338416 in-wireless-0: connected to Access Point `sanctuary' > 2020-09-27 14:36:40.131870236 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 14:36:40.131876653 in-wireless-0: adding address fe80::19db:fef7:609f:47ff > 2020-09-27 14:36:40.867502547 in-wireless-0: soliciting an IPv6 router > 2020-09-27 14:36:41.082659588 in-wireless-0: rebinding lease of 192.168.0.24 > 2020-09-27 14:36:42.097383244 in-wireless-0: Router Advertisement from fe80::1 > 2020-09-27 14:36:42.097784202 in-wireless-0: adding default route via fe80::1 > 2020-09-27 14:36:42.118390071 in-wireless-0: requesting DHCPv6 information > 2020-09-27 14:36:43.241524408 in-wireless-0: REPLY6 received from fe80::1 > 2020-09-27 14:36:43.241531694 in-wireless-0: refresh in 86400 seconds > 2020-09-27 14:36:45.167755509 in-wireless-0: probing address 192.168.0.24/24 > 2020-09-27 14:36:46.961029631 in-wired-0: carrier acquired > 2020-09-27 14:36:46.966393068 in-wired-0: IAID fd:a9:93:88 > 2020-09-27 14:36:46.966422087 in-wired-0: adding address fe80::ae2b:a054:4551:ee66 > 2020-09-27 14:36:47.807487628 in-wired-0: soliciting an IPv6 router > 2020-09-27 14:36:48.151709417 in-wired-0: rebinding lease of 192.168.0.16 > 2020-09-27 14:36:48.203744307 in-wired-0: probing address 192.168.0.16/24 > 2020-09-27 14:36:48.551086720 in-wired-0: Router Advertisement from fe80::1 > 2020-09-27 14:36:48.551094161 in-wired-0: adding default route via fe80::1 > 2020-09-27 14:36:48.578354631 in-wired-0: requesting DHCPv6 information > 2020-09-27 14:36:49.629098160 in-wired-0: REPLY6 received from fe80::1 > 2020-09-27 14:36:49.629111372 in-wired-0: refresh in 86400 seconds > 2020-09-27 14:36:50.042137747 in-wireless-0: leased 192.168.0.24 for 259200 seconds > 2020-09-27 14:36:50.043180344 in-wireless-0: adding route to 192.168.0.0/24 > 2020-09-27 14:36:50.043187700 in-wireless-0: adding default route via 192.168.0.1 > 2020-09-27 14:36:53.670796782 in-wired-0: leased 192.168.0.16 for 259200 seconds > 2020-09-27 14:36:53.670804843 in-wired-0: adding route to 192.168.0.0/24 > 2020-09-27 14:36:53.670806712 in-wired-0: adding default route via 192.168.0.1 > 2020-09-27 14:45:10.658332393 in-wireless-0: carrier lost > 2020-09-27 14:45:10.755923527 ps_bpf_recvbpf: Network is down > 2020-09-27 14:45:10.757974343 in-wireless-0: deleting default route via fe80::1 > 2020-09-27 14:45:10.781556944 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff > 2020-09-27 14:45:10.784978177 in-wireless-0: deleting route to 192.168.0.0/24 > 2020-09-27 14:45:10.785189038 in-wireless-0: deleting default route via 192.168.0.1 > 2020-09-27 14:47:16.819264626 received SIGTERM, stopping > 2020-09-27 14:47:16.819315805 in-wireless-0: removing interface > 2020-09-27 14:47:16.824369106 in-wired-0: removing interface > 2020-09-27 14:47:16.831387371 dhcpcd exited > 2020-09-27 14:48:50.220665342 dhcpcd-9.2.0 starting > 2020-09-27 14:48:50.235339511 dev: loaded udev > 2020-09-27 14:48:50.237413093 DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19 > 2020-09-27 14:48:50.634904515 no interfaces have a carrier > 2020-09-27 14:48:50.843336281 in-wired-0: waiting for carrier > 2020-09-27 14:48:50.843343025 in-wireless-0: waiting for carrier > 2020-09-27 14:48:50.843345737 in-wireless-0: carrier acquired > 2020-09-27 14:48:50.849938976 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 14:48:50.850530481 in-wireless-0: adding address fe80::55a:5374:22a4:4ce2 > 2020-09-27 14:48:50.850534593 in-wireless-0: carrier lost > 2020-09-27 14:48:50.886479451 in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2 > 2020-09-27 14:48:54.349958769 in-wireless-0: carrier acquired > 2020-09-27 14:48:54.351216664 in-wireless-0: connected to Access Point `sanctuary' > 2020-09-27 14:48:54.359568194 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 14:48:54.359574334 in-wireless-0: adding address fe80::19db:fef7:609f:47ff > 2020-09-27 14:48:54.500045235 in-wireless-0: rebinding lease of 192.168.0.24 > 2020-09-27 14:48:54.759697179 in-wireless-0: soliciting an IPv6 router > 2020-09-27 14:48:56.130927029 in-wireless-0: Router Advertisement from fe80::1 > 2020-09-27 14:48:56.131129536 in-wireless-0: adding default route via fe80::1 > 2020-09-27 14:48:56.144578620 in-wireless-0: requesting DHCPv6 information > 2020-09-27 14:48:57.260937736 in-wireless-0: REPLY6 received from fe80::1 > 2020-09-27 14:48:57.260945305 in-wireless-0: refresh in 86400 seconds > 2020-09-27 14:48:59.446024892 in-wireless-0: probing address 192.168.0.24/24 > 2020-09-27 14:49:01.106600972 in-wired-0: carrier acquired > 2020-09-27 14:49:01.110397758 in-wired-0: IAID fd:a9:93:88 > 2020-09-27 14:49:01.110405281 in-wired-0: adding address fe80::ae2b:a054:4551:ee66 > 2020-09-27 14:49:01.141445535 in-wired-0: rebinding lease of 192.168.0.16 > 2020-09-27 14:49:01.199099942 in-wired-0: probing address 192.168.0.16/24 > 2020-09-27 14:49:01.547882733 in-wired-0: soliciting an IPv6 router > 2020-09-27 14:49:03.034853761 in-wired-0: Router Advertisement from fe80::1 > 2020-09-27 14:49:03.035200754 in-wired-0: adding default route via fe80::1 > 2020-09-27 14:49:03.044935642 in-wired-0: requesting DHCPv6 information > 2020-09-27 14:49:04.092221763 in-wired-0: REPLY6 received from fe80::1 > 2020-09-27 14:49:04.092249974 in-wired-0: refresh in 86400 seconds > 2020-09-27 14:49:04.384681565 in-wireless-0: leased 192.168.0.24 for 259200 seconds > 2020-09-27 14:49:04.385289662 in-wireless-0: adding route to 192.168.0.0/24 > 2020-09-27 14:49:04.385411907 in-wireless-0: adding default route via 192.168.0.1 > 2020-09-27 14:49:06.745315169 in-wired-0: leased 192.168.0.16 for 259200 seconds > 2020-09-27 14:49:06.745964771 in-wired-0: adding route to 192.168.0.0/24 > 2020-09-27 14:49:06.745971033 in-wired-0: adding default route via 192.168.0.1 > 2020-09-27 14:50:31.666498911 in-wireless-0: carrier lost > 2020-09-27 14:50:31.694642076 in-wireless-0: deleting default route via fe80::1 > 2020-09-27 14:50:31.708662121 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff > 2020-09-27 14:50:31.734671244 in-wireless-0: deleting route to 192.168.0.0/24 > 2020-09-27 14:50:31.734760375 in-wireless-0: deleting default route via 192.168.0.1 > 2020-09-27 14:57:54.284007333 in-wireless-0: carrier acquired > 2020-09-27 14:57:54.308508721 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 14:57:54.308637041 in-wireless-0: adding address fe80::19db:fef7:609f:47ff > 2020-09-27 14:57:54.388030157 in-wireless-0: soliciting an IPv6 router > 2020-09-27 14:57:55.313265473 in-wireless-0: rebinding lease of 192.168.0.24 > 2020-09-27 14:57:55.500301187 in-wireless-0: Router Advertisement from fe80::1 > 2020-09-27 14:57:55.500718178 in-wireless-0: adding default route via fe80::1 > 2020-09-27 14:57:55.518591827 in-wireless-0: requesting DHCPv6 information > 2020-09-27 14:57:56.610665164 in-wireless-0: REPLY6 received from fe80::1 > 2020-09-27 14:57:56.610852349 in-wireless-0: refresh in 86400 seconds > 2020-09-27 14:57:59.665253280 in-wireless-0: probing address 192.168.0.24/24 > 2020-09-27 14:58:04.671481023 in-wireless-0: leased 192.168.0.24 for 259200 seconds > 2020-09-27 14:58:04.676816082 in-wireless-0: adding route to 192.168.0.0/24 > 2020-09-27 14:58:04.676852041 in-wireless-0: adding default route via 192.168.0.1 > 2020-09-27 14:59:26.705880261 in-wireless-0: carrier lost > 2020-09-27 14:59:26.730262529 in-wireless-0: deleting default route via fe80::1 > 2020-09-27 14:59:26.741923912 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff > 2020-09-27 14:59:26.747137774 in-wireless-0: deleting route to 192.168.0.0/24 > 2020-09-27 14:59:26.747151400 in-wireless-0: deleting default route via 192.168.0.1 > 2020-09-27 14:59:30.704560862 received SIGTERM, stopping > 2020-09-27 14:59:30.704568449 in-wireless-0: removing interface > 2020-09-27 14:59:30.711468054 in-wired-0: removing interface > 2020-09-27 14:59:30.721546523 dhcpcd exited > 2020-09-27 15:00:08.554239015 dhcpcd-9.2.0 starting > 2020-09-27 15:00:08.565005127 dev: loaded udev > 2020-09-27 15:00:08.565925381 DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19 > 2020-09-27 15:00:08.683340454 no interfaces have a carrier > 2020-09-27 15:00:09.081804702 in-wired-0: waiting for carrier > 2020-09-27 15:00:09.081810466 in-wireless-0: waiting for carrier > 2020-09-27 15:00:09.081812892 in-wireless-0: carrier acquired > 2020-09-27 15:00:09.086944245 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 15:00:09.087203079 in-wireless-0: adding address fe80::55a:5374:22a4:4ce2 > 2020-09-27 15:00:09.087208134 in-wireless-0: carrier lost > 2020-09-27 15:00:09.116553908 in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2 > 2020-09-27 15:00:12.616721111 in-wireless-0: carrier acquired > 2020-09-27 15:00:12.617974561 in-wireless-0: connected to Access Point `sanctuary' > 2020-09-27 15:00:12.625571903 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 15:00:12.625578571 in-wireless-0: adding address fe80::19db:fef7:609f:47ff > 2020-09-27 15:00:12.791590558 in-wireless-0: soliciting an IPv6 router > 2020-09-27 15:00:13.927112004 in-wireless-0: Router Advertisement from fe80::1 > 2020-09-27 15:00:13.927490413 in-wireless-0: adding default route via fe80::1 > 2020-09-27 15:00:13.944574191 in-wireless-0: requesting DHCPv6 information > 2020-09-27 15:00:14.028123094 in-wireless-0: rebinding lease of 192.168.0.24 > 2020-09-27 15:00:15.062150872 in-wireless-0: REPLY6 received from fe80::1 > 2020-09-27 15:00:15.062163229 in-wireless-0: refresh in 86400 seconds > 2020-09-27 15:00:18.645953696 in-wireless-0: probing address 192.168.0.24/24 > 2020-09-27 15:00:19.677716854 in-wired-0: carrier acquired > 2020-09-27 15:00:19.682969338 in-wired-0: IAID fd:a9:93:88 > 2020-09-27 15:00:19.683044595 in-wired-0: adding address fe80::ae2b:a054:4551:ee66 > 2020-09-27 15:00:20.062651977 in-wired-0: soliciting an IPv6 router > 2020-09-27 15:00:20.773309148 in-wired-0: rebinding lease of 192.168.0.16 > 2020-09-27 15:00:20.832364989 in-wired-0: probing address 192.168.0.16/24 > 2020-09-27 15:00:21.153244886 in-wired-0: Router Advertisement from fe80::1 > 2020-09-27 15:00:21.153516617 in-wired-0: adding default route via fe80::1 > 2020-09-27 15:00:21.169834594 in-wired-0: requesting DHCPv6 information > 2020-09-27 15:00:22.286498945 in-wired-0: REPLY6 received from fe80::1 > 2020-09-27 15:00:22.286533090 in-wired-0: refresh in 86400 seconds > 2020-09-27 15:00:23.837636173 in-wireless-0: leased 192.168.0.24 for 259200 seconds > 2020-09-27 15:00:23.841740790 in-wireless-0: adding route to 192.168.0.0/24 > 2020-09-27 15:00:23.841769460 in-wireless-0: adding default route via 192.168.0.1 > 2020-09-27 15:00:25.433243781 in-wired-0: leased 192.168.0.16 for 259200 seconds > 2020-09-27 15:00:25.434557803 in-wired-0: adding route to 192.168.0.0/24 > 2020-09-27 15:00:25.434565015 in-wired-0: adding default route via 192.168.0.1 The key part of the log is: > 2020-09-27 14:59:30.704560862 received SIGTERM, stopping > 2020-09-27 14:59:30.704568449 in-wireless-0: removing interface > 2020-09-27 14:59:30.711468054 in-wired-0: removing interface > 2020-09-27 14:59:30.721546523 dhcpcd exited > 2020-09-27 15:00:08.554239015 dhcpcd-9.2.0 starting > 2020-09-27 15:00:08.565005127 dev: loaded udev As you can see dhcpcd got shut down. It's weird that it was started up again, and of course, as it starts again, and remains enabled afterwords it seems, then the shutdown process hangs. > One thought would be to remove the dhcpcd dependency from > wpa_supplicant, but I would rather not do that because you do need > dhcpcd running for wpa_supplicant to work correctly. It might be > possible to add a finish script that will solve your problem. For > example, "wpa_cli terminate" being run when wpa_supplicant gets > brought down might possibly prevent dhcpcd from hanging for you. > Alternatively, dhcpcd may need a finish script itself. Perhaps you're right about adding something on the finish script. I can tell the wpa_supplicant service actually dies when the dhcpcd one shuts it down, since afterwords, the wireless interface is never brought up back, unless I manually start the wpa_supplicant service. But let me get the logs on the wpa_supplicant service later, just to confirm. BTW, to break the shut down hang, I do: > ^C > s6-rc: warning: received INT, aborting longrun transitions and exiting asap > s6-rc: warning: unable to stop service dhcpcd-srv: command crashed with signal 2 And then dhcp, as alive, tries to bring the wireless interfaces up, but as wpa_supplicant is down, it can't. On the log, we get additionally: > 2020-09-27 15:02:23.288184126 in-wireless-0: carrier lost > 2020-09-27 15:02:23.313193548 in-wireless-0: deleting default route via fe80::1 > 2020-09-27 15:02:23.325320899 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff > 2020-09-27 15:02:23.329582421 in-wireless-0: deleting route to 192.168.0.0/24 > 2020-09-27 15:02:23.329591237 in-wireless-0: deleting default route via 192.168.0.1 And the log doesn't move from there, even if I manually start the dhccpcd service, which for some reason can be done and doesn't fail, even though dhcp is up and running, perhaps because for S6 it should be dead already, and calling the dhcpcd daemon twice doesn't provoke any failure, just gets ignored, but I'm not sure... Let me get some logs from wpa_supplicant to complement all this. -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Mon Sep 28 00:04:46 2020 From: je-vv at e.email (Javier) Date: Sun, 27 Sep 2020 16:04:46 -0600 Subject: [artix-general] [s6] not booting/rebooting laptop In-Reply-To: <862f0679-fe6a-0ba4-bd3b-f8b1b6f3bf41@e.email> References: <08001b07-8db9-ecdc-4dd8-ca94a5fa805b@e.email> <535d00e0-3c60-19e1-6d3e-ff68d6e44409@artixlinux.org> <1d81e0f9-3edb-f403-6ac1-156b336b4b11@artixlinux.org> <20890cca-6653-3b0a-df5e-1d226d2df5e5@e.email> <9fe482cd-359b-22a6-96a7-61f96b0b1781@artixlinux.org> <9e5f33f3-8412-fab1-4483-dcf21ccbd5ae@e.email> <254d79a0-331d-8f5d-5aef-da63c7a07ca4@artixlinux.org> <90b70e1b-944d-3532-159f-f674ae826e1c@artixlinux.org> <7060c697-f79b-9dad-40ca-04105eb23584@e.email> <41e57dcb-2b2d-a202-31d8-24bec8e2aa01@e.email> <3d376484-4c18-b79f-413a-d7ec9cfab608@e.email> <630a6ffe-f693-e2e9-21ab-8705afbb50d1@artixlinux.org> <862f0679-fe6a-0ba4-bd3b-f8b1b6f3bf41@e.email> Message-ID: <08588c38-b364-abcc-b4ef-214f90271bca@e.email> On 9/27/20 3:35 PM, Javier via artix-general wrote: > On 9/27/20 9:56 AM, Dudemanguy via artix-general wrote: >> Do the dhcpcd logs in /var/log/dhcpcd say anything interesting here? It >> should say something like "received SIGTERM, stopping" when it shuts >> down. > > The dhcpcd service actually receives the SIGTERM, and actually does exits. So that part is good, but as soon as it does, then it starts again. I believe the issue is not on the dhcpcd side though, since it seems to do things fine. What makes it start again is what's faulting. Please remember when there's no wpa_supplicant, dhcpcd dies fine. On the console: > >> % sudo s6-rc -d -v2 change dhcpcd >> [sudo] password for vasqueja: >> s6-rc: info: service wpa_supplicant-srv: stopping >> s6-rc: info: service wpa_supplicant-srv successfully stopped >> s6-rc: info: service dhcpcd-srv: stopping > > There the dhcpcd service just hangs. The corresponding /var/log/dhcpcd/current (including its start at boot): > >> 2020-09-27 14:36:36.037374263 dhcpcd-9.2.0 starting >> 2020-09-27 14:36:36.048819381 dev: loaded udev >> 2020-09-27 14:36:36.050056676 DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19 >> 2020-09-27 14:36:36.152177882 no interfaces have a carrier >> 2020-09-27 14:36:36.565768987 in-wired-0: waiting for carrier >> 2020-09-27 14:36:36.565775437 in-wireless-0: waiting for carrier >> 2020-09-27 14:36:36.565777742 in-wireless-0: carrier acquired >> 2020-09-27 14:36:36.574231978 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 14:36:36.580133950 in-wireless-0: adding address fe80::55a:5374:22a4:4ce2 >> 2020-09-27 14:36:36.580142432 in-wireless-0: carrier lost >> 2020-09-27 14:36:36.621093633 in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2 >> 2020-09-27 14:36:40.125047310 in-wireless-0: carrier acquired >> 2020-09-27 14:36:40.126338416 in-wireless-0: connected to Access Point `sanctuary' >> 2020-09-27 14:36:40.131870236 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 14:36:40.131876653 in-wireless-0: adding address fe80::19db:fef7:609f:47ff >> 2020-09-27 14:36:40.867502547 in-wireless-0: soliciting an IPv6 router >> 2020-09-27 14:36:41.082659588 in-wireless-0: rebinding lease of 192.168.0.24 >> 2020-09-27 14:36:42.097383244 in-wireless-0: Router Advertisement from fe80::1 >> 2020-09-27 14:36:42.097784202 in-wireless-0: adding default route via fe80::1 >> 2020-09-27 14:36:42.118390071 in-wireless-0: requesting DHCPv6 information >> 2020-09-27 14:36:43.241524408 in-wireless-0: REPLY6 received from fe80::1 >> 2020-09-27 14:36:43.241531694 in-wireless-0: refresh in 86400 seconds >> 2020-09-27 14:36:45.167755509 in-wireless-0: probing address 192.168.0.24/24 >> 2020-09-27 14:36:46.961029631 in-wired-0: carrier acquired >> 2020-09-27 14:36:46.966393068 in-wired-0: IAID fd:a9:93:88 >> 2020-09-27 14:36:46.966422087 in-wired-0: adding address fe80::ae2b:a054:4551:ee66 >> 2020-09-27 14:36:47.807487628 in-wired-0: soliciting an IPv6 router >> 2020-09-27 14:36:48.151709417 in-wired-0: rebinding lease of 192.168.0.16 >> 2020-09-27 14:36:48.203744307 in-wired-0: probing address 192.168.0.16/24 >> 2020-09-27 14:36:48.551086720 in-wired-0: Router Advertisement from fe80::1 >> 2020-09-27 14:36:48.551094161 in-wired-0: adding default route via fe80::1 >> 2020-09-27 14:36:48.578354631 in-wired-0: requesting DHCPv6 information >> 2020-09-27 14:36:49.629098160 in-wired-0: REPLY6 received from fe80::1 >> 2020-09-27 14:36:49.629111372 in-wired-0: refresh in 86400 seconds >> 2020-09-27 14:36:50.042137747 in-wireless-0: leased 192.168.0.24 for 259200 seconds >> 2020-09-27 14:36:50.043180344 in-wireless-0: adding route to 192.168.0.0/24 >> 2020-09-27 14:36:50.043187700 in-wireless-0: adding default route via 192.168.0.1 >> 2020-09-27 14:36:53.670796782 in-wired-0: leased 192.168.0.16 for 259200 seconds >> 2020-09-27 14:36:53.670804843 in-wired-0: adding route to 192.168.0.0/24 >> 2020-09-27 14:36:53.670806712 in-wired-0: adding default route via 192.168.0.1 >> 2020-09-27 14:45:10.658332393 in-wireless-0: carrier lost >> 2020-09-27 14:45:10.755923527 ps_bpf_recvbpf: Network is down >> 2020-09-27 14:45:10.757974343 in-wireless-0: deleting default route via fe80::1 >> 2020-09-27 14:45:10.781556944 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff >> 2020-09-27 14:45:10.784978177 in-wireless-0: deleting route to 192.168.0.0/24 >> 2020-09-27 14:45:10.785189038 in-wireless-0: deleting default route via 192.168.0.1 >> 2020-09-27 14:47:16.819264626 received SIGTERM, stopping >> 2020-09-27 14:47:16.819315805 in-wireless-0: removing interface >> 2020-09-27 14:47:16.824369106 in-wired-0: removing interface >> 2020-09-27 14:47:16.831387371 dhcpcd exited >> 2020-09-27 14:48:50.220665342 dhcpcd-9.2.0 starting >> 2020-09-27 14:48:50.235339511 dev: loaded udev >> 2020-09-27 14:48:50.237413093 DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19 >> 2020-09-27 14:48:50.634904515 no interfaces have a carrier >> 2020-09-27 14:48:50.843336281 in-wired-0: waiting for carrier >> 2020-09-27 14:48:50.843343025 in-wireless-0: waiting for carrier >> 2020-09-27 14:48:50.843345737 in-wireless-0: carrier acquired >> 2020-09-27 14:48:50.849938976 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 14:48:50.850530481 in-wireless-0: adding address fe80::55a:5374:22a4:4ce2 >> 2020-09-27 14:48:50.850534593 in-wireless-0: carrier lost >> 2020-09-27 14:48:50.886479451 in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2 >> 2020-09-27 14:48:54.349958769 in-wireless-0: carrier acquired >> 2020-09-27 14:48:54.351216664 in-wireless-0: connected to Access Point `sanctuary' >> 2020-09-27 14:48:54.359568194 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 14:48:54.359574334 in-wireless-0: adding address fe80::19db:fef7:609f:47ff >> 2020-09-27 14:48:54.500045235 in-wireless-0: rebinding lease of 192.168.0.24 >> 2020-09-27 14:48:54.759697179 in-wireless-0: soliciting an IPv6 router >> 2020-09-27 14:48:56.130927029 in-wireless-0: Router Advertisement from fe80::1 >> 2020-09-27 14:48:56.131129536 in-wireless-0: adding default route via fe80::1 >> 2020-09-27 14:48:56.144578620 in-wireless-0: requesting DHCPv6 information >> 2020-09-27 14:48:57.260937736 in-wireless-0: REPLY6 received from fe80::1 >> 2020-09-27 14:48:57.260945305 in-wireless-0: refresh in 86400 seconds >> 2020-09-27 14:48:59.446024892 in-wireless-0: probing address 192.168.0.24/24 >> 2020-09-27 14:49:01.106600972 in-wired-0: carrier acquired >> 2020-09-27 14:49:01.110397758 in-wired-0: IAID fd:a9:93:88 >> 2020-09-27 14:49:01.110405281 in-wired-0: adding address fe80::ae2b:a054:4551:ee66 >> 2020-09-27 14:49:01.141445535 in-wired-0: rebinding lease of 192.168.0.16 >> 2020-09-27 14:49:01.199099942 in-wired-0: probing address 192.168.0.16/24 >> 2020-09-27 14:49:01.547882733 in-wired-0: soliciting an IPv6 router >> 2020-09-27 14:49:03.034853761 in-wired-0: Router Advertisement from fe80::1 >> 2020-09-27 14:49:03.035200754 in-wired-0: adding default route via fe80::1 >> 2020-09-27 14:49:03.044935642 in-wired-0: requesting DHCPv6 information >> 2020-09-27 14:49:04.092221763 in-wired-0: REPLY6 received from fe80::1 >> 2020-09-27 14:49:04.092249974 in-wired-0: refresh in 86400 seconds >> 2020-09-27 14:49:04.384681565 in-wireless-0: leased 192.168.0.24 for 259200 seconds >> 2020-09-27 14:49:04.385289662 in-wireless-0: adding route to 192.168.0.0/24 >> 2020-09-27 14:49:04.385411907 in-wireless-0: adding default route via 192.168.0.1 >> 2020-09-27 14:49:06.745315169 in-wired-0: leased 192.168.0.16 for 259200 seconds >> 2020-09-27 14:49:06.745964771 in-wired-0: adding route to 192.168.0.0/24 >> 2020-09-27 14:49:06.745971033 in-wired-0: adding default route via 192.168.0.1 >> 2020-09-27 14:50:31.666498911 in-wireless-0: carrier lost >> 2020-09-27 14:50:31.694642076 in-wireless-0: deleting default route via fe80::1 >> 2020-09-27 14:50:31.708662121 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff >> 2020-09-27 14:50:31.734671244 in-wireless-0: deleting route to 192.168.0.0/24 >> 2020-09-27 14:50:31.734760375 in-wireless-0: deleting default route via 192.168.0.1 >> 2020-09-27 14:57:54.284007333 in-wireless-0: carrier acquired >> 2020-09-27 14:57:54.308508721 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 14:57:54.308637041 in-wireless-0: adding address fe80::19db:fef7:609f:47ff >> 2020-09-27 14:57:54.388030157 in-wireless-0: soliciting an IPv6 router >> 2020-09-27 14:57:55.313265473 in-wireless-0: rebinding lease of 192.168.0.24 >> 2020-09-27 14:57:55.500301187 in-wireless-0: Router Advertisement from fe80::1 >> 2020-09-27 14:57:55.500718178 in-wireless-0: adding default route via fe80::1 >> 2020-09-27 14:57:55.518591827 in-wireless-0: requesting DHCPv6 information >> 2020-09-27 14:57:56.610665164 in-wireless-0: REPLY6 received from fe80::1 >> 2020-09-27 14:57:56.610852349 in-wireless-0: refresh in 86400 seconds >> 2020-09-27 14:57:59.665253280 in-wireless-0: probing address 192.168.0.24/24 >> 2020-09-27 14:58:04.671481023 in-wireless-0: leased 192.168.0.24 for 259200 seconds >> 2020-09-27 14:58:04.676816082 in-wireless-0: adding route to 192.168.0.0/24 >> 2020-09-27 14:58:04.676852041 in-wireless-0: adding default route via 192.168.0.1 >> 2020-09-27 14:59:26.705880261 in-wireless-0: carrier lost >> 2020-09-27 14:59:26.730262529 in-wireless-0: deleting default route via fe80::1 >> 2020-09-27 14:59:26.741923912 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff >> 2020-09-27 14:59:26.747137774 in-wireless-0: deleting route to 192.168.0.0/24 >> 2020-09-27 14:59:26.747151400 in-wireless-0: deleting default route via 192.168.0.1 >> 2020-09-27 14:59:30.704560862 received SIGTERM, stopping >> 2020-09-27 14:59:30.704568449 in-wireless-0: removing interface >> 2020-09-27 14:59:30.711468054 in-wired-0: removing interface >> 2020-09-27 14:59:30.721546523 dhcpcd exited >> 2020-09-27 15:00:08.554239015 dhcpcd-9.2.0 starting >> 2020-09-27 15:00:08.565005127 dev: loaded udev >> 2020-09-27 15:00:08.565925381 DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19 >> 2020-09-27 15:00:08.683340454 no interfaces have a carrier >> 2020-09-27 15:00:09.081804702 in-wired-0: waiting for carrier >> 2020-09-27 15:00:09.081810466 in-wireless-0: waiting for carrier >> 2020-09-27 15:00:09.081812892 in-wireless-0: carrier acquired >> 2020-09-27 15:00:09.086944245 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 15:00:09.087203079 in-wireless-0: adding address fe80::55a:5374:22a4:4ce2 >> 2020-09-27 15:00:09.087208134 in-wireless-0: carrier lost >> 2020-09-27 15:00:09.116553908 in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2 >> 2020-09-27 15:00:12.616721111 in-wireless-0: carrier acquired >> 2020-09-27 15:00:12.617974561 in-wireless-0: connected to Access Point `sanctuary' >> 2020-09-27 15:00:12.625571903 in-wireless-0: IAID 00:bb:a5:3f >> 2020-09-27 15:00:12.625578571 in-wireless-0: adding address fe80::19db:fef7:609f:47ff >> 2020-09-27 15:00:12.791590558 in-wireless-0: soliciting an IPv6 router >> 2020-09-27 15:00:13.927112004 in-wireless-0: Router Advertisement from fe80::1 >> 2020-09-27 15:00:13.927490413 in-wireless-0: adding default route via fe80::1 >> 2020-09-27 15:00:13.944574191 in-wireless-0: requesting DHCPv6 information >> 2020-09-27 15:00:14.028123094 in-wireless-0: rebinding lease of 192.168.0.24 >> 2020-09-27 15:00:15.062150872 in-wireless-0: REPLY6 received from fe80::1 >> 2020-09-27 15:00:15.062163229 in-wireless-0: refresh in 86400 seconds >> 2020-09-27 15:00:18.645953696 in-wireless-0: probing address 192.168.0.24/24 >> 2020-09-27 15:00:19.677716854 in-wired-0: carrier acquired >> 2020-09-27 15:00:19.682969338 in-wired-0: IAID fd:a9:93:88 >> 2020-09-27 15:00:19.683044595 in-wired-0: adding address fe80::ae2b:a054:4551:ee66 >> 2020-09-27 15:00:20.062651977 in-wired-0: soliciting an IPv6 router >> 2020-09-27 15:00:20.773309148 in-wired-0: rebinding lease of 192.168.0.16 >> 2020-09-27 15:00:20.832364989 in-wired-0: probing address 192.168.0.16/24 >> 2020-09-27 15:00:21.153244886 in-wired-0: Router Advertisement from fe80::1 >> 2020-09-27 15:00:21.153516617 in-wired-0: adding default route via fe80::1 >> 2020-09-27 15:00:21.169834594 in-wired-0: requesting DHCPv6 information >> 2020-09-27 15:00:22.286498945 in-wired-0: REPLY6 received from fe80::1 >> 2020-09-27 15:00:22.286533090 in-wired-0: refresh in 86400 seconds >> 2020-09-27 15:00:23.837636173 in-wireless-0: leased 192.168.0.24 for 259200 seconds >> 2020-09-27 15:00:23.841740790 in-wireless-0: adding route to 192.168.0.0/24 >> 2020-09-27 15:00:23.841769460 in-wireless-0: adding default route via 192.168.0.1 >> 2020-09-27 15:00:25.433243781 in-wired-0: leased 192.168.0.16 for 259200 seconds >> 2020-09-27 15:00:25.434557803 in-wired-0: adding route to 192.168.0.0/24 >> 2020-09-27 15:00:25.434565015 in-wired-0: adding default route via 192.168.0.1 > > The key part of the log is: > >> 2020-09-27 14:59:30.704560862 received SIGTERM, stopping >> 2020-09-27 14:59:30.704568449 in-wireless-0: removing interface >> 2020-09-27 14:59:30.711468054 in-wired-0: removing interface >> 2020-09-27 14:59:30.721546523 dhcpcd exited >> 2020-09-27 15:00:08.554239015 dhcpcd-9.2.0 starting >> 2020-09-27 15:00:08.565005127 dev: loaded udev > > As you can see dhcpcd got shut down. It's weird that it was started up again, and of course, as it starts again, and remains enabled afterwords it seems, then the shutdown process hangs. > >> One thought would be to remove the dhcpcd dependency from >> wpa_supplicant, but I would rather not do that because you do need >> dhcpcd running for wpa_supplicant to work correctly. It might be >> possible to add a finish script that will solve your problem. For >> example, "wpa_cli terminate" being run when wpa_supplicant gets >> brought down might possibly prevent dhcpcd from hanging for you. >> Alternatively, dhcpcd may need a finish script itself. > > Perhaps you're right about adding something on the finish script. I can tell the wpa_supplicant service actually dies when the dhcpcd one shuts it down, since afterwords, the wireless interface is never brought up back, unless I manually start the wpa_supplicant service. But let me get the logs on the wpa_supplicant service later, just to confirm. > > BTW, to break the shut down hang, I do: > >> ^C >> s6-rc: warning: received INT, aborting longrun transitions and exiting asap >> s6-rc: warning: unable to stop service dhcpcd-srv: command crashed with signal 2 > > And then dhcp, as alive, tries to bring the wireless interfaces up, but as wpa_supplicant is down, it can't. On the log, we get additionally: > >> 2020-09-27 15:02:23.288184126 in-wireless-0: carrier lost >> 2020-09-27 15:02:23.313193548 in-wireless-0: deleting default route via fe80::1 >> 2020-09-27 15:02:23.325320899 in-wireless-0: deleting address fe80::19db:fef7:609f:47ff >> 2020-09-27 15:02:23.329582421 in-wireless-0: deleting route to 192.168.0.0/24 >> 2020-09-27 15:02:23.329591237 in-wireless-0: deleting default route via 192.168.0.1 > > And the log doesn't move from there, even if I manually start the dhccpcd service, which for some reason can be done and doesn't fail, even though dhcp is up and running, perhaps because for S6 it should be dead already, and calling the dhcpcd daemon twice doesn't provoke any failure, just gets ignored, but I'm not sure... > > Let me get some logs from wpa_supplicant to complement all this. After looking into the wpa_supplicant log, I don't believe attempting to kill the wpa_supplicant daemon can help at all. It actually dies. See, on boot, and, before shutting the dhcpcd server down, on the log: > 2020-09-27 15:36:57.442124057 Successfully initialized wpa_supplicant > 2020-09-27 15:36:57.983004498 nl80211: kernel reports: Attribute failed policy validation > 2020-09-27 15:36:57.983013105 Failed to create interface p2p-dev-in-wireless-0: -22 (Invalid argument) > 2020-09-27 15:36:57.983015011 nl80211: Failed to create a P2P Device interface p2p-dev-in-wireless-0 > 2020-09-27 15:36:57.983016607 P2P: Failed to enable P2P Device interface > 2020-09-27 15:36:57.983018238 in-wireless-0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD > 2020-09-27 15:37:01.404758651 in-wireless-0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US > 2020-09-27 15:37:01.405830470 in-wireless-0: SME: Trying to authenticate with d8:eb:97:2a:5c:39 (SSID='sanctuary' freq=5180 MHz) > 2020-09-27 15:37:01.419654060 in-wireless-0: Trying to associate with d8:eb:97:2a:5c:39 (SSID='sanctuary' freq=5180 MHz) > 2020-09-27 15:37:01.429192118 in-wireless-0: Associated with d8:eb:97:2a:5c:39 > 2020-09-27 15:37:01.429200398 in-wireless-0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 > 2020-09-27 15:37:01.529282281 in-wireless-0: WPA: Key negotiation completed with d8:eb:97:2a:5c:39 [PTK=CCMP GTK=CCMP] > 2020-09-27 15:37:01.529292964 in-wireless-0: CTRL-EVENT-CONNECTED - Connection to d8:eb:97:2a:5c:39 completed [id=3 id_str=] And dhcpcd gets in charge of getting the dhcp lease and the IP for the interface... When shutting the dhcpcd server down: > % sudo s6-rc -d -v2 change dhcpcd > [sudo] password for vasqueja: > s6-rc: info: service wpa_supplicant-srv: stopping > s6-rc: info: service wpa_supplicant-srv successfully stopped > s6-rc: info: service dhcpcd-srv: stopping There the shut down process hangs, but on the wpa_supplicant service log: > 2020-09-27 15:40:29.279810697 in-wireless-0: CTRL-EVENT-DISCONNECTED bssid=d8:eb:97:2a:5c:39 reason=3 locally_generated=1 > 2020-09-27 15:40:29.309159972 nl80211: deinit ifname=in-wireless-0 disabled_11b_rates=0 > 2020-09-27 15:40:29.344121158 in-wireless-0: CTRL-EVENT-TERMINATING And from that point on, after breaking the hang with ^C, and even after starting the dhcpcd service up again (which doesn't really start the dhcpcd daemon, since it got somehow started when its shut down was attempted), there's no movement on the wpa_supplicant log, and on the dhcpcd log we saw before that there was no way to get a carrier for the wireless interface, meaning wpa_supplicant is really dead. And I don't believe trying to kill it, when it never gets restarted, doesn't help. Also, please notice I can start the wpa_supplicant service afterwords, and then the wireless interface starts working back: > % sudo s6-rc -u change wpa_supplicant That leads to the wpa_supplicant log: > 2020-09-27 15:55:56.697073328 Successfully initialized wpa_supplicant > 2020-09-27 15:55:57.038145036 nl80211: kernel reports: Attribute failed policy validation > 2020-09-27 15:55:57.038174195 Failed to create interface p2p-dev-in-wireless-0: -22 (Invalid argument) > 2020-09-27 15:55:57.038181640 nl80211: Failed to create a P2P Device interface p2p-dev-in-wireless-0 > 2020-09-27 15:55:57.038188256 P2P: Failed to enable P2P Device interface > 2020-09-27 15:55:57.038460579 in-wireless-0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD > 2020-09-27 15:56:00.483832434 in-wireless-0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US > 2020-09-27 15:56:00.486802655 in-wireless-0: SME: Trying to authenticate with d8:eb:97:2a:5c:39 (SSID='sanctuary' freq=5180 MHz) > 2020-09-27 15:56:00.503434311 in-wireless-0: Trying to associate with d8:eb:97:2a:5c:39 (SSID='sanctuary' freq=5180 MHz) > 2020-09-27 15:56:00.512004555 in-wireless-0: Associated with d8:eb:97:2a:5c:39 > 2020-09-27 15:56:00.512339053 in-wireless-0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 > 2020-09-27 15:56:00.525569599 in-wireless-0: WPA: Key negotiation completed with d8:eb:97:2a:5c:39 [PTK=CCMP GTK=CCMP] > 2020-09-27 15:56:00.525698941 in-wireless-0: CTRL-EVENT-CONNECTED - Connection to d8:eb:97:2a:5c:39 completed [id=3 id_str=] And the corresponding log on dhcpcd: > 2020-09-27 15:56:00.526577562 in-wireless-0: carrier acquired > 2020-09-27 15:56:00.551237006 in-wireless-0: IAID 00:bb:a5:3f > 2020-09-27 15:56:00.551264680 in-wireless-0: adding address fe80::19db:fef7:609f:47ff > 2020-09-27 15:56:00.830301813 in-wireless-0: soliciting an IPv6 router > 2020-09-27 15:56:01.868272052 in-wireless-0: Router Advertisement from fe80::1 > 2020-09-27 15:56:01.869373085 in-wireless-0: adding default route via fe80::1 > 2020-09-27 15:56:01.888599901 in-wireless-0: requesting DHCPv6 information > 2020-09-27 15:56:02.146206350 in-wireless-0: rebinding lease of 192.168.0.24 > 2020-09-27 15:56:02.986700192 in-wireless-0: REPLY6 received from fe80::1 > 2020-09-27 15:56:02.986798581 in-wireless-0: refresh in 86400 seconds Bottom line, I don't know what's needed, but it seems something is waking dhcpcd back, and it doesn't seem it's the wpa_supplicant daemon. Perhaps the S6 supervisor, as it did not kill the wpa_supplicant service itself, still believes it's up, and that's the reason the dhcp daemon is restarted automatically. I honestly have no clue. @Dudemanguy, perhaps after reading all these logs, you can make more sense of what's going on, and then, you can identify what's making dhcpcd come up again when shutting down, and then maybe you can identify a work around, or a fix... Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From moody at posixcafe.org Wed Sep 30 23:46:58 2020 From: moody at posixcafe.org (Jacob Moody) Date: Wed, 30 Sep 2020 16:46:58 -0500 Subject: [artix-general] [Artix] [RFC] s6-dns and s6-networking packages Message-ID: Hello, I've included PKGBUILD files for both s6-dns and s6-networking. I think it would be a great addition to add them to the packages that are offered in Artix. This is my first time writing PKGBUILD files so feedback is much appreciated. Thanks, Moody # s6-dns # Maintainer: Jacob Moody pkgname=s6-dns pkgver=2.3.2.0 pkgrel=1 epoch=0 pkgdesc="A suite of DNS client programs and libraries for UNIX systems" arch=('x86_64') url="https://skarnet.org/software/s6-dns/" license=('ISC') groups=() depends=() makedepends=('gcc' 'glibc' 'skalibs' 'make') checkdepends=() optdepends=() provides=() conflicts=() replaces=() backup=() options=() install= changelog= source=("https://codeload.github.com/skarnet/$pkgname/tar.gz/v$pkgver") noextract=() sha256sums=('75e7c06d296f81360b5cf0273253d905e9439ab31d93cdb0aff79d4e3fe91607') validpgpkeys=() build() { cd "$pkgname-$pkgver" ./configure --prefix=/usr make } package() { cd "$pkgname-$pkgver" make DESTDIR="$pkgdir/" install } # s6-networking # Maintainer: Jacob Moody pkgname=s6-networking pkgver=2.3.1.2 pkgrel=1 epoch=0 pkgdesc="A suite of small networking tools for UNIX systems." arch=('x86_64') url="https://skarnet.org/software/s6-networking/" license=('ISC') groups=() depends=('s6' 'libressl' 'execline') makedepends=('gcc' 'glibc' 'skalibs' 'make' 's6-dns') checkdepends=() optdepends=() provides=() conflicts=() replaces=() backup=() options=() install= changelog= source=("https://codeload.github.com/skarnet/$pkgname/tar.gz/v$pkgver") noextract=() sha256sums=('6c6886bf594805c23c893e42c77a96f8a0d9bad302985387795f2b6f00b761c4') validpgpkeys=() build() { cd "$pkgname-$pkgver" ./configure --prefix=/usr --with-lib=/usr/lib/s6-dns/ make } package() { cd "$pkgname-$pkgver" make DESTDIR="$pkgdir/" install }