Hi Reza, Reza <[email protected]> writes:
> Hi Guixers > > After updating my system to the newest commit my system shows a black > screen after login. I booted the old generation #135 and had access to > my system again. This generation is still with linux 7.1, which I see in > the grub menu. Now I extracted the commit of the good generation with > > guix system describe /var/guix/profiles/system-135-link/profile > > and found the good commit 5c217ab1361758851ac89bc523015fcd965c0a83. I > reconfigured my system with this commit in channels.scm with > [...] > localhost linux: [ 0.286954] ACPI Error: AE_ALREADY_EXISTS, During > name lookup/catalog (20251212/psobject-220) > > localhost linux: [ 1.815475] init[1]: segfault at 3fff00 ip > 00000000004d5593 sp 00007ffdc591a7c0 error 4 in > guile[d5593,401000+202000] likely on CPU 16 (core 8, socket 0) The segfault at least is currently expected/known to not be critical [0]. [0] https://codeberg.org/guix/guix/issues/3333 > localhost linux: [ 2.979860] faux_driver regulatory: Direct firmware > load for regulatory.db failed with error -2 > > ntpd[958]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Not sure about this one; perhaps your hardware clock is way off? I don't think this would cause your boot problem though. > localhost gdm: Gdm: GdmLocalDisplayFactory: Failed to issue method call: > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.login1 was not provided by any .service files This one was caused by a regression in elogind; fixed (including fix-ups) in commit 14321bbbe38f1e3e26fae4d019468c5896e7bd18 ("services/elogind: Fix build for ungrafted elogind."). It wasn't critical to boot either, though, so wouldn't explain your black screen. -- Thanks, Maxim
