<PotentialUser-94>I'm having trouble installing Guix system 1.1.0 I downloaded the iso file and verified the autenticity of the file. burned it to usb stick and got selected boot device failed error. Since usb didn't work, I burned it on a cd and get the same error. What am I doing wring? Thank you for your help in advance
<marusich>Where did the error come from? Depending on your BIOS (or UEFI), you might have to adjust some settings in your BIOS (or UEFI) to be able to boot that image.
<PotentialUser-94>I could't finish installing Guix system. I'm using graphical interface for installation, it asks me please select a disk (my hdd and dvd+ appears on the list) I select the hdd. and on the next screen I select everything in one partition option. Once I click ok, it start over. What am I doing wrong?
<PotentialUser-94>I didn't select a desktop environment assuming Guix system comes with it's own desktop environment, and the ones on the list are additional ones. Might that be the reason?
<PotentialUser-94>Another question not directly related to the problem I'm having, should I select openssh?
<kelsoo1>What about upstream systemd'd applications? does guix handle them. ignore, fork, replace, other?
<kelsoo1>What about upstream systemd'd applications? How does guix handle them. ignore, fork, replace, other?
<marusich>PotentialUser-94, my guess is you probably aren't doing anything wrong, and the GUI installer has a bug. To work around the issue, it sucks but I suggest starting over and being careful to only traverse the "happy path" of the GUI installer, by not making mistakes as you go.
<marusich>For example, if you do something, and then you think, "huh I wish I had selected something else," so you go back to some previous section of the GUI installer and change it, it *should* be no problem at all, but in practice it might be buggy, I guess.
<marusich>At the same time, although I'm sure you're probably tired from just going through the installation routine, if you know what the exact steps were which produced the looping behavior, you might consider sending a bug report to email@example.com.
<marusich>I haven't used the GUI installer for a long time, but I recall it having such bugs.
<PotentialUser-94>I mostly selected recommended options. My only guess it failed because it didn't like me not choosing a desktop envitonment or my hdd is not compatible or something.
<marusich>I mean, it shouldn't leave you in a dead end state, regardless. Does it not print any error messages at all?
<PotentialUser-94>No, nothing, it just goes back to the beginning where it asks about the locale keyboard language and such
<marusich>That sucks. What happens if you try starting over fresh? Without an indication as to why it's looping, I really don't have anything better to suggest.
<PotentialUser-94>It just loops. I don't know why. I wish I had an error code at least. Spent some time to decide on a linux distro now it doesn't work -,-
<guixy>* Slots of services:: What a <service> object consists of.
<lafrenierejm>Ah. That makes sense. Thank you for explaining that insight.
<lafrenierejm>Separate question: What is the proper way to start user-level shepherd services? Just invoking `shepherd` in a shell concludes with "Exiting shepherd...".
<guixy>I got it going a year ago, but had to reinstall.
<guixy>Make sure shepherd is installed to a user profile
<guixy>Try shepherd -c FILE where FILE is where you define all your services.
<guixy>Process 1 in guix is essentially /gnu/store/...-guile-3.0.2/bin/guile --no-auto-compile /gnu/store/...-shepherd-0.8.1/bin/shepherd --config /gnu/store/...shepherd.conf so that should work
<guixy>If you don't have anything that launches a login script, you can always put that in your .bash_profile
<guixy>And if you sometimes log out and log back in, you should call herd stop root in .bash_logout
<guixy>But if you use virtual terminals at all, you need to do something smarter. I'm still trying to figure it out.
<guixy>'users | xargs -n1 | grep $USER | wc -l' prints the number of times you are logged in. When it is 1, launch (or stop) shepherd (after you source your guix profile).
<guixy>lol, That should work for any user other than root. root can't have a personal shepherd.
<guixy>Or rather, root's personal shepherd is process 1 on guix
<lafrenierejm>Hm. Even with shepherd installed to my user profile, only having a single login, and specifying the full path to the init file, shepherd still prints that its exiting and there's no surviving process for the service (syncthing).
<guixy>I'm going to try it on my end. If it doesn't work, we'll know there's a bug.
<PotentialUser-94>I reinitiated the installation but it didn't work. I choose a desktop environment thinking that maybe that might be the reason but the same problem happened. After choosing partition thing, it just goes back to the beginning.
<guixy>Check to see if herd is running. `herd status`
<guixy>If it is running, it lists the services. Else, it says it is not running.
<guixy>The documentation says if you want it in interactive mode, use --socket=none
<fnstudio>- is it possible to `sudo apt remove cron` from my foreign distro and then `guix install mcron` (as a user)? would that allow me to schedule tasks (as that same user)?
<fnstudio>- if not, would it make any difference if i guix-installed mcron as root? i'd tend to think that that would also fall short of launching a demo... as how can guix know of and interact with my system's service management?
<bdju>anyone know how to check if my hardware is supported by intel-vaapi-driver?
<leoprikler>fnstudio: I think you should be able to start a user mcron using systemd or even shepherd
<leoprikler>you'd have to write the service file yourself though
<fnstudio>leoprikler: uh, interesting, thanks - so it might be possible to install shepherd next to my system's systemd?
<leoprikler>you can install shepherd as a user program through guix and start it in your bash_profile
<alextee[m]>PotentialUser-29: i think you email <bug id>-done@<whatever the domain was>
<PotentialUser-29>Is it going to delete it from the bug tracker tho? I noticed my submission is listed online. I thought I was mailing to a bug help team or something. I didn't mean to publish it online
<terpri>maybe the docs should emphasize it somehow, but it's obvious if you click on any link in (info "(guix) Tracking Bugs and Patches") that bug reports are published online; dunno how one could conclude one was submitting a bug report to some kind of private support team from the current docs
<leoprikler>I doubt our mailing lists are the primary target of Nigerian princes.
<terpri>yeah, the gnu project is not exactly known for its wealth, ostentatiousness and gullibility
***hji- is now known as hji
<greenrd>How can I use a channel with a locally-modified guix?
<greenrd>I tried using ./pre-inst-env guix pull -p /tmp/my-guix but I get a warning that compilation of the file that I changed failed
<greenrd>also I think that is only going to be used for that instance of guix, not the instance of guix that guix pull is building?
<zimoun>greenrd: did you do make before ./pre-inst-env?
<HappyEnt[m]>str1ngs: Yes, should be the 2GB version. Ah didn't know there was upstream support for the soc of the pinephone.
<HappyEnt[m]>str1ngs: Problem is my version is the one with the usb bug, so I kinda have to rely on the kernel fix from the pine64 kernel to get usb otg working.
<str1ngs>HappyEnt[m]: maybe we can start with linux-libre and layer some patches on top.
<str1ngs>also I don't know about blob and firmware. so it's going to take some research to get this working with mainline guix.
<greenrd>ah, I think I've figured it out. I think I need to replace the default guix channel in channels.scm with a file:/// url pointing to my local guix fork.
<greenrd>not sure whether I need pre-inst-env any more if I'm doing that
<str1ngs>HappyEnt[m]: what distro do you normally use with your pinephone?
<HappyEnt[m]>str1ngs: https://xff.cz/kernels/5.9/README megi has done a lot of work on making mainline linux work on the pinephone. Blob wise it seems like that camera, everything related wireless and hdmi out would not be able to work with libre linux.
<HappyEnt[m]>str1ngs: currently i am not using the pinephone a lot, but most of the time i have run mobian
<str1ngs>HappyEnt[m]: okay I use mobian too. right now I'm using stub u-boot-loader that does nothing. and then I used mobian to write a bootloader if I need it. but mostly that's because of specifics to the 3GB model I have. and I think I can eventually automate the bootloader just using normal guix and u-boot packages.