<davexunit>yeah one of the devs hangs out in #fsfsys and helps us out from time to time
<davexunit>I just want to talk to the sysadmins first because they know exactly how they configured and built this rom.
<davexunit>I'm going to bed now. between troubleshooting guix issues and the fsf.org problems that happened an hour or so ago, I'm exhausted.
<mark_weaver>davexunit: okay, thanks for all your work on this. good night!
<davexunit>night. thanks as always for your help and guidance.
<mark_weaver>looks like it might be important to list libahci.ko before ahci.ko
<svetlana>I tried to run guix in a tty on the host OS. It is an advantage: now I, with gdm, can select text there using mouse. However, I still can't scroll the output qemu and guix provide. On whose end is that problem?
<DusXMT>when doing guix system reconfigure, it works as expected with --no-grub, but without, I get a vague error that "failed to install GRUB on device '/dev/sda'", and increasing the verbosity level does nothing to it. Does guix keep any logs I could check about this?
<DusXMT>Temporary workaround: copy the generated grub.cfg from /gnu/store to /boot/grub
<mark_weaver>the same wpa_supplicant package works on my other machine (which is not pure guix).
<mark_weaver>I wonder if it's trying to call out to wireless-tools. I have that installed on the machine that works, but not on the machine that doesn't.
<davexunit>oh, give that a shot. if it works, would that mean we just have to add wireless-tools as a propagated input?
<mark_weaver>no time to try it now though. I'm going to be otherwise engaged for the next 24 hours or so.
<mark_weaver>davexunit: if wpa-supplicant does try to run executables from wireless-tools, then it should probably use the absolute pathname in /gnu/store/* to run them, in which case it wouldn't have to be a propagated input.