Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 2849

Graphical Environments & Desktops • xserver failure (no gdm) after migrating from debian 11 to debian 12

$
0
0
Hello,

After upgrading to debian 12 (bookworm), I have no display manager running. Black screen and only with console available after ctrl-alt-F4

Here is my config:

Code:

System:  Kernel: 4.19.0-27-amd64 arch: x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: N/A dm: GDM3    Distro: Debian GNU/Linux 12 (bookworm)Graphics:  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: ASUSTeK driver: nouveau v: kernel arch: Maxwell    pcie: speed: 2.5 GT/s lanes: 16 ports: active: DVI-I-1 empty: DP-1, DP-2, DP-3, HDMI-A-1    bus-ID: 01:00.0 chip-ID: 10de:1401 temp: 36.0 C  Display: server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:    loaded: fbdev,modesetting,vesa gpu: nouveau  Monitor-1: DVI-I-1 model: Philips 241SL res: 1920x1080 dpi: 92 diag: 609mm (24")  API: OpenGL Message: No GL data found on this system.
Here is what I did
==================

I upgraded from debian 10 (buster) to debian 11 (bullseye), using this procedure:
https://linuxize.com/post/how-to-upgrad ... debian-11/
(summary: change /etc/apt/sources.list, then apt update, apt upgrade and apt full-upgrade)

Everything was ok, very easy. I could reboot and boot in debian 11 and login after that. I had a graphical desktop, all my programs, mail etc.

So a few minutes later, next step was to migrate from debian 11 to debian 12 (bookworm), just using a similar procedure from:
https://linuxize.com/post/how-to-upgrad ... debian-12/

The upgrade seemed ok, but when I boot, there is no graphical manager.

First I get this:

Code:

[1.207813] nouveau 0000:01:00.0: firmware: failed to load nvidia/gm206/gr/sw_nonctx.bin (-2)
(but I think that I already had that in buster, and this file exists!)

Then after some 30 seconds, this message disapears and there is no graphical environment. Im stuck on a black screen. I can force switch to console with ctrl-alt-f4 and use of character mode is perfectly ok. It's debian 12:

Code:

lsb_release -aNo LSB modules are available.Distributor ID: DebianDescription: Debian GNU/Linux 12 (bookworm)Codename : bookworm
Starting xserver manually gives an error, but for me the cause is unclear:
it finishes with a "(EE) Caught signal 11 (Segmentation fault). Server aborting".
I may be wrong but I think that it's not relevant, it's probably caused by this previous cause.

The log seems ok until arriving to those 3 lines:

Code:

[   165.365] (II) Module glamoregl: vendor="X.Org Foundation"[   165.365] compiled for 1.21.1.7, module version = 1.0.1[   165.365] ABI class: X.Org ANSI C Emulation, version 0.4
After these lines, I think we should see this:

Code:

(II) modeset(0): glamor X acceleration enabled on NV126(II) modeset(0): glamor initialized
But instead of that, there is a backtrace appearing:

Code:

[   165.384] (EE) Backtrace:[   165.384] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55f843be7f79][   165.385] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f9d6a25b050][ more lines here in the log (see attached file). then:]Fatal server error:[   165.387] (EE) Caught signal 11 (Segmentation fault). Server aborting
I tried many actions to solve this, without success:
  • start xserver (failed, see the 3 blocks of code here above and attached log file)
  • sudo start xserver (failed, even worse: unable to connect to x server: connection refused)
  • played with /etc/apt/sources.list, adding or removing non-free and/or non-free-firmware and redoing update and upgrade
  • tried "sudo tasksel", adding or removing some distributions (gnome, gnome flashback, kde, etc).
  • tried to play with systemctl set-default (currently graphical.target).
  • also tried to remove or reinstall packages which seemed involved in a graphical context (like xserver-xorg-core or xserver-xorg-video-nouveau
  • As Nvidia has always been several days or weeks of hard work to make it run under linux, I also purged "*nvidia*" packages, just in case...
I don't know what to do next. Any idea, someone, please? I would be very grateful, thank you in advance!
Xorg.0.log

Statistics: Posted by debianero — 2025-02-10 09:19



Viewing all articles
Browse latest Browse all 2849

Trending Articles