lxdm.log Fatal server error:Server is already active for display 0

Flavio · 2021-12-09 19:02:54

you are right: nouveau was blacklisted in /etc/modprobe.d/blacklist.conf
Now i can load it with modprobe nouveau.

seth · 2021-12-09 20:07:36

Well, and how's te impact on starting X11?

Flavio · 2021-12-09 20:21:14

Startx gives :
No screens found
Xinit: giving up
Xinit: unable to Connect to x server: connection refused
Xinit: server error

seth · 2021-12-09 20:22:17

Do you think the xorg log might be a bit more informative?

Flavio · 2021-12-09 20:36:32

When i reboot maybe it cannot load nouveau as reported by Xorg.0.log: http://ix.io/3HvX
but if i load it manually it work as i verify with lsmod.

Flavio · 2021-12-09 21:46:48

How can i load nouveau at boot?
I've added nouveau.config=NvBios=PRAMIN in the kernel parameters in grub. conf but without luck.

seth · 2021-12-09 21:49:03

See https://wiki.archlinux.org/title/Kernel … _KMS_start and in any event rebuild the initramfs - the blacklist config is likely copied there as well.

Flavio · 2021-12-09 22:04:42

OK i've added the nouveau module in /etc/mkinitcpio.conf and mkinitcpio -p linux-lts give at last image generation successful
rebooted but nouveau still noto presente in lsmod

Flavio · 2021-12-10 07:51:41

Maybe is a bug as reported by bugzilla (i have same type of laptop):
https://bugs.freedesktop.org/show_bug.cgi?id=111853

seth · 2021-12-10 08:10:41

It's also from 2019 and has

It came to me to repair because of video corruption in Windows 7 that appeared only after warmup.

lspci -k
modprobe -c | grep nouveau
sudo modprobe -v nouveau
lspci -k

Flavio · 2021-12-10 09:52:12

So as i've done before need to install nvidia-340xx driver, right?
I have tested that it works

seth · 2021-12-10 10:53:37

The 340xx driver seems to fail w/ the 1.21 server ABI - what's not unlikely given the time since it receied the last update.
It's gonna be nouveau or pinning the xorg server at 1.20 what means you'll have to maintain xorg and possibly xlib from the AUR or at some point have to stop updating the system entirely (or use some longterm distro like debian stable)

Please post the outputs of the commands in #35

Flavio · 2021-12-10 18:44:39

lspci -k
http://ix.io/3HCw

modprobe -c | grep nouveau
http://ix.io/3HCx

sudo modprobe -v nouveau
http://ix.io/3HCy

lspci -k
http://ix.io/3HCw

seth · 2021-12-10 22:31:03

blacklist nouveau
options nouveau modeset=0

It's still blacklisted and has modesetting disabled… which is likely because

Kernel modules: nouveau, nvidia

The some nvidia driver seems to be installed (again?)

and the lspci outputs are the same file (I wanted to see whether loading nouveau w/ modprobe assigns it to the device)

Flavio · 2021-12-11 09:43:01

I've unistalled nvidia driver with command "nvidia-installer --unistall"
but as can see is still in kernel modules.
If i do "plocate nvidia" i get: http://ix.io/3HGk
So there are some libs anywhere; NB /NVIDIA directory contains the nvidia driver insteller (don't want remove it)
About lspci -k i don't know why after load nouveau not show assigned device.(i've retried)

seth · 2021-12-11 12:45:49

I've unistalled nvidia driver with command "nvidia-installer --unistall"

This is why you're not supposed to bypass the package manager.

pacman -Qs nvidia

About lspci -k i don't know why after load nouveau not show assigned device.(i've retried)

Because the two ix.io links for lspci in #38 are the same…

This isn't going anywhere.

Flavio · 2021-12-11 14:23:06

pacman -Qs nvidia
gives only libvdpau package installed.
ix.io have recognized that file content is the same giving the same url
lspci give about nouveau the same string:
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GT] (rev a1)
Subsystem: Sony Corporation Device 902d
Kernel modules: nouveau, nvidia

seth · 2021-12-11 14:40:07

stat /usr/lib/xorg/modules/drivers/nvidia_drv.so /usr/lib/modules/5.10.75-1-lts/kernel/drivers/video/nvidia.ko /usr/lib/modprobe.d/nvidia-installer-disable-nouveau.conf

Flavio · 2021-12-11 15:32:57

nvidia_drv.so and nvidia.ko are no more present
stat /usr/lib/modprobe.d/nvidia-installer-disable-nouveau.conf gives:
http://ix.io/3HIq

seth · 2021-12-11 15:39:35

remove that file…

Flavio · 2021-12-11 16:11:03

removed /usr/lib/modprobe.d/nvidia-installer-disable-nouveau.conf
Now if i do lspci -k | grep nouveau i get: http://ix.io/3HIK
And dmesg | grep nouveau gives: http://ix.io/3HIP

Flavio · 2021-12-11 19:13:10

Also interesting the Xorg.0.log more verbose with kernel parameters drm.debug=14 and log_buf_len=16M
http://ix.io/3HJM

seth · 2021-12-11 19:53:37

Please don't bump. Edit your posts if nobody has replied yet.

The new xorg log is more verbose because the server now actually starts, but rapidly crashes in glx - perhaps because you invalidated the GL installation w/ your nvidia driver installation.

pacman -Qikk xorg-server libglvnd mesa

Flavio · 2021-12-11 22:03:42

pacman -Qikk xorg-server libglvnd mesa
http://ix.io/3HKL
Moreover dmesg | grep error gives
http://ix.io/3HKN

seth · 2021-12-12 07:18:35

xorg-server: 49 file totali, 2 file alterati
libglvnd: 58 file totali, 6 file alterati

But the output doesn't include stderr, so we can't see which exactly those are.
However, from the context it's safe to assume that those are the nvidia GL libraries.

So update your system and make sure to re-install those packages to sanitize the situation.

Arch Linux

#26 2021-12-09 19:02:54

Re: lxdm.log Fatal server error:Server is already active for display 0

#27 2021-12-09 20:07:36

Re: lxdm.log Fatal server error:Server is already active for display 0

#28 2021-12-09 20:21:14

Re: lxdm.log Fatal server error:Server is already active for display 0

#29 2021-12-09 20:22:17

Re: lxdm.log Fatal server error:Server is already active for display 0

#30 2021-12-09 20:36:32

Re: lxdm.log Fatal server error:Server is already active for display 0

#31 2021-12-09 21:46:48

Re: lxdm.log Fatal server error:Server is already active for display 0

#32 2021-12-09 21:49:03

Re: lxdm.log Fatal server error:Server is already active for display 0

#33 2021-12-09 22:04:42

Re: lxdm.log Fatal server error:Server is already active for display 0

#34 2021-12-10 07:51:41

Re: lxdm.log Fatal server error:Server is already active for display 0

#35 2021-12-10 08:10:41

Re: lxdm.log Fatal server error:Server is already active for display 0

#36 2021-12-10 09:52:12

Re: lxdm.log Fatal server error:Server is already active for display 0

#37 2021-12-10 10:53:37

Re: lxdm.log Fatal server error:Server is already active for display 0

#38 2021-12-10 18:44:39

Re: lxdm.log Fatal server error:Server is already active for display 0

#39 2021-12-10 22:31:03

Re: lxdm.log Fatal server error:Server is already active for display 0

#40 2021-12-11 09:43:01

Re: lxdm.log Fatal server error:Server is already active for display 0

#41 2021-12-11 12:45:49

Re: lxdm.log Fatal server error:Server is already active for display 0

#42 2021-12-11 14:23:06

Re: lxdm.log Fatal server error:Server is already active for display 0

#43 2021-12-11 14:40:07

Re: lxdm.log Fatal server error:Server is already active for display 0

#44 2021-12-11 15:32:57

Re: lxdm.log Fatal server error:Server is already active for display 0

#45 2021-12-11 15:39:35

Re: lxdm.log Fatal server error:Server is already active for display 0

#46 2021-12-11 16:11:03

Re: lxdm.log Fatal server error:Server is already active for display 0

#47 2021-12-11 19:13:10

Re: lxdm.log Fatal server error:Server is already active for display 0

#48 2021-12-11 19:53:37

Re: lxdm.log Fatal server error:Server is already active for display 0

#49 2021-12-11 22:03:42

Re: lxdm.log Fatal server error:Server is already active for display 0

#50 2021-12-12 07:18:35

Re: lxdm.log Fatal server error:Server is already active for display 0

Board footer