upgrade problems : x server

Archived topics about LMDE 1 and LMDE 2
Locked
pampelmoose

upgrade problems : x server

Post by pampelmoose »

Running LMDE. Mint-update just told me that there were a lot of upgrades (service pack 3 coming in?), so I upgraded ; about 900 new packages installed.

And now my x-server does not work. It doesn't matter whether I use the new kernel or the old one. I can boot using recovery mode, but then everything hangs if I run the command "startx".
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
pampelmoose

Re: upgrade problems : x server

Post by pampelmoose »

Some more info :

in my /var/log/syslog file, a lot of lines like the following :

Sep 29 16:08:35 gatonegro gdm3[2362]: WARNING: GdmDisplay: display lasted 0.401913 seconds
Sep 29 16:08:35 gatonegro acpid: client 3451[0:0] has disconnected
Sep 29 16:08:35 gatonegro acpid: client connected from 3455[0:0]
Sep 29 16:08:35 gatonegro acpid: 1 client rule loaded
Sep 29 16:08:35 gatonegro gdm3[2362]: WARNING: GdmDisplay: display lasted 0.518556 seconds
Sep 29 16:08:35 gatonegro acpid: client 3455[0:0] has disconnected
Sep 29 16:08:35 gatonegro acpid: client connected from 3459[0:0]
Sep 29 16:08:35 gatonegro acpid: 1 client rule loaded
Sep 29 16:08:36 gatonegro gdm3[2362]: WARNING: GdmDisplay: display lasted 0.518406 seconds
Sep 29 16:08:36 gatonegro acpid: client 3459[0:0] has disconnected
Sep 29 16:08:36 gatonegro acpid: client connected from 3463[0:0]
Sep 29 16:08:36 gatonegro acpid: 1 client rule loaded
Sep 29 16:08:36 gatonegro gdm3[2362]: WARNING: GdmDisplay: display lasted 0.523743 seconds
Sep 29 16:08:36 gatonegro acpid: client 3463[0:0] has disconnected
Sep 29 16:08:36 gatonegro acpid: client connected from 3467[0:0]
Sep 29 16:08:36 gatonegro acpid: 1 client rule loaded

and in my /var/log/Xorg.0.log file :

[ 26.424] (==) fglrx(0): NoDRI = NO
[ 26.425] (==) fglrx(0): Capabilities: 0x00000000
[ 26.425] (==) fglrx(0): CapabilitiesEx: 0x00000000
[ 26.425] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
[ 26.425] (==) fglrx(0): UseFastTLS=0
[ 26.425] (==) fglrx(0): BlockSignalsOnLock=1
[ 26.425] (--) Depth 24 pixmap format is 32 bpp
[ 26.425] (EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
[ 26.425] (WW) fglrx(0): ***********************************************************
[ 26.425] (WW) fglrx(0): * DRI initialization failed *
[ 26.425] (WW) fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible *
[ 26.425] (WW) fglrx(0): * 2D and 3D acceleration disabled *
[ 26.425] (WW) fglrx(0): ***********************************************************
pampelmoose

Re: upgrade problems : x server

Post by pampelmoose »

And another problem!

When I boot in recovery mode, and don't try to start X, I can't get connected to the network.

If I type "ifconfig eth0", I get a message that eth0 is not detected. The computer has an ethernet connection, with a realtek controller, which should use the R8168 module. With the new kernel (3.0.0-1), that module is not getting loaded. But even with the old kernel (2.6.39-2), the correct R8168 module is loaded, and it still can't detect eth0.

So no graphics, no internet connection : great upgrade!
User avatar
Roken
Level 5
Level 5
Posts: 737
Joined: Fri Nov 19, 2010 4:55 pm
Location: Newport, S Wales

Re: upgrade problems : x server

Post by Roken »

The good news is you can get back to a desktop. The bad news is fglrx won't work.

To get to the desktop, boot recovery mode and issue the command:

Code: Select all

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak
Then reboot.

Edit: normal boot should restore your network, too.
Kernel Linux Tex 5.12.14-zen1-1-zen, XFCE
Arch
Dual GTX1070 8Gb
AMD Ryzen 1800X
32Gb RAM
pampelmoose

Re: upgrade problems : x server

Post by pampelmoose »

Thanks Roken.

I think that I have stumbled into a not-too-weird setup. I installed the r8168 module into the 3.0.0-1 kernel. For some reason, that made my internet connection eth1, not eth0. But I was able to get the connection up, and then re-install the fglrx driver using the sgfxi script. And that seems to have solved my x-server problems.

Still some minor problems. The "update-initramfs -u" command seems not to work ; I have to reload the r8168 module each time I boot. And the network-manager applet insists that I'm not connected, even once I've got eth1 working. And boot time seems longer with the new kernel.
Locked

Return to “LMDE Archive”