GNU bug report logs -
#44925
gdm boot up failure
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44925 in the body.
You can then email your comments to 44925 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#44925
; Package
guix
.
(Sat, 28 Nov 2020 17:54:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Christopher Howard <christopher <at> librehacker.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sat, 28 Nov 2020 17:54:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Boot up process continues mostly like normal, but instead of going to
gdm login screen, screen gets stuck on a black screen with a flashing
cursor. I recall seeing a message in the virtual console about the "c1"
session being removed, though I can't find the text in the logs. The
messages log has messages about failing to activate an Accounts
service, and also some entries about dead gdm processes.
$ guix describe
Generation 10 Sep 03 2018 17:32:44 (current)
guix e0fa68c
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: e0fa68c7718fffd33d81af415279d6ddb518f727
My messages log, and also my system description file, is attached. The
system was built using the above commit. My user profile is somewhat
behind the system but only because I could not successfully build my
user profile do to the gnutls-dane build failure. (But I hadn't even
logged in to my user at this point.)
christopher <at> nightshade ~$ neofetch --stdout
christopher <at> nightshade
----------------------
OS: Guix System 9e2669690c80dc00973859edf732964f0a514d7b x86_64
Host: GA-880GM-UD2H
Kernel: 5.7.15-gnu
Uptime: 13 mins
Packages: 103 (guix-system), 84 (guix-user)
Shell: bash 5.0.16
Resolution: 1920x1200
DE: GNOME 3.34.2
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: kitty
CPU: AMD Athlon II X3 455 (3) @ 3.300GHz
GPU: AMD ATI Radeon HD 4250
Memory: 1139MiB / 7456MiB
--
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)
[messages (text/plain, attachment)]
[nightshade-system.scm (text/x-scheme, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44925
; Package
guix
.
(Mon, 30 Nov 2020 03:04:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 44925 <at> debbugs.gnu.org (full text, mbox):
In case it is helpful, I wanted to note that commit
b618c1512b9086199ce0496dbbcc4f4f587a826d from five days ago does not
have this problem. That commit uses the 5.9 kernel, so that shows also
this is not a kernel problem.
Christopher
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44925
; Package
guix
.
(Wed, 02 Dec 2020 19:26:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 44925 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I had a similar problem today.
I booted with a system configured with Guix at
275fcffc9b5f4deb516c510b26b07c13d6e47307 and everything worked fine.
Then I reconfigured with Guix at commit
04b83678653fda3c66e600e88f54f5108290ec1c, removed a few dozen old
generations and did a 'guix gc'.
At the next reboot, gdm didn't work anymore. I rebooted and launched the
previous system generation, but gdm still didn't work, which is strange.
After some investigation, I found that gdm was failing because the
kernel driver for the GPU was not loaded (the 'nouveau' driver in my
case). I tried to load it by hand with
'insmod /run/booted-system/kernel/lib/modules/5.9.11/.../nouveau.ko.gz',
and it failed with the error 'unknown symbol in module'.
I'm not sure what was going on here... The only way I got everything to
work again is by reconfiguring the system to compile and use the 5.9.12
kernel.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44925
; Package
guix
.
(Mon, 11 Jan 2021 03:02:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 44925 <at> debbugs.gnu.org (full text, mbox):
Hi Christopher,
Guillaume Le Vaillant <glv <at> posteo.net> writes:
> I had a similar problem today.
>
> I booted with a system configured with Guix at
> 275fcffc9b5f4deb516c510b26b07c13d6e47307 and everything worked fine.
>
> Then I reconfigured with Guix at commit
> 04b83678653fda3c66e600e88f54f5108290ec1c, removed a few dozen old
> generations and did a 'guix gc'.
>
> At the next reboot, gdm didn't work anymore. I rebooted and launched the
> previous system generation, but gdm still didn't work, which is strange.
>
> After some investigation, I found that gdm was failing because the
> kernel driver for the GPU was not loaded (the 'nouveau' driver in my
> case). I tried to load it by hand with
> 'insmod /run/booted-system/kernel/lib/modules/5.9.11/.../nouveau.ko.gz',
> and it failed with the error 'unknown symbol in module'.
>
> I'm not sure what was going on here... The only way I got everything to
> work again is by reconfiguring the system to compile and use the 5.9.12
> kernel.
Could you confirm that the problem has resolved itself with the current
Linux kernel version packaged in Guix?
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#44925
; Package
guix
.
(Mon, 11 Jan 2021 06:10:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 44925 <at> debbugs.gnu.org (full text, mbox):
Hi, I'm not having this problem currently under commit
223d8fb4a0e31957c85ef42ef501c8ed038a7259, kernel version 5.10.4-gnu.
So, I'm satisfied. However, I should note, for the record, that I did
change my graphics card in the interm from the original reported AMD
ATI Radeon HD 4250 (integrated GPU) to an external NVIDIA GeForce 8400
GS Rev. 3.
--
Christopher Howard
p: +1 (907) 374-0257 (no texting)
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)
On Sun, 2021-01-10 at 22:01 -0500, Maxim Cournoyer wrote:
> Hi Christopher,
>
> Guillaume Le Vaillant <glv <at> posteo.net> writes:
>
> > I had a similar problem today.
> >
> > I booted with a system configured with Guix at
> > 275fcffc9b5f4deb516c510b26b07c13d6e47307 and everything worked
> > fine.
> >
> > Then I reconfigured with Guix at commit
> > 04b83678653fda3c66e600e88f54f5108290ec1c, removed a few dozen old
> > generations and did a 'guix gc'.
> >
> > At the next reboot, gdm didn't work anymore. I rebooted and
> > launched the
> > previous system generation, but gdm still didn't work, which is
> > strange.
> >
> > After some investigation, I found that gdm was failing because the
> > kernel driver for the GPU was not loaded (the 'nouveau' driver in
> > my
> > case). I tried to load it by hand with
> > 'insmod /run/booted-
> > system/kernel/lib/modules/5.9.11/.../nouveau.ko.gz',
> > and it failed with the error 'unknown symbol in module'.
> >
> > I'm not sure what was going on here... The only way I got
> > everything to
> > work again is by reconfiguring the system to compile and use the
> > 5.9.12
> > kernel.
>
> Could you confirm that the problem has resolved itself with the
> current
> Linux kernel version packaged in Guix?
>
> Thanks,
>
> Maxim
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Mon, 11 Jan 2021 13:19:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Christopher Howard <christopher <at> librehacker.com>
:
bug acknowledged by developer.
(Mon, 11 Jan 2021 13:19:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 44925-done <at> debbugs.gnu.org (full text, mbox):
Hello Christopher,
Christopher Howard <christopher <at> librehacker.com> writes:
> Hi, I'm not having this problem currently under commit
> 223d8fb4a0e31957c85ef42ef501c8ed038a7259, kernel version 5.10.4-gnu.
> So, I'm satisfied. However, I should note, for the record, that I did
> change my graphics card in the interm from the original reported AMD
> ATI Radeon HD 4250 (integrated GPU) to an external NVIDIA GeForce 8400
> GS Rev. 3.
Thank you for the follow up. Good to know your system is back in
working order. I'll close this bug now, but feel free to reopen a new
one should the issue re-appear.
Thanks,
Maxim
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 09 Feb 2021 12:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 48 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.