unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Christopher Howard <christopher@librehacker.com>
Cc: 44925@debbugs.gnu.org
Subject: bug#44925: gdm boot up failure
Date: Wed, 02 Dec 2020 20:24:53 +0100	[thread overview]
Message-ID: <87o8jcdn96.fsf@yamatai> (raw)
In-Reply-To: <f57756b994aa51cd9451b393aed341d47d728f73.camel@librehacker.com>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]


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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-12-02 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 17:53 bug#44925: gdm boot up failure Christopher Howard
2020-11-30  3:03 ` Christopher Howard
2020-12-02 19:24   ` Guillaume Le Vaillant [this message]
2021-01-11  3:01     ` Maxim Cournoyer
2021-01-11  6:08       ` Christopher Howard
2021-01-11 13:18         ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8jcdn96.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=44925@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).