Skip to main content ↑ ↓
Topic: fatal server error (EE) no screen found(EE)  (Read 507 times) previous topic - next topic
0 Members and 7 Guests are viewing this topic.

fatal server error (EE) no screen found(EE)

 Hello,

after the latest update xserver failed to load, this is frustrating because i just updating like usual and i didn't do any edit to my config/root file.

log-

Code: [Select]
[    11.166] 
X.Org X Server 1.21.1.11
X Protocol Version 11, Revision 0
[    11.166] Current Operating System: Linux ahloi 6.8.2-zen2-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 20:23:08 +0000 x86_64
[    11.166] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=ed0ed4fc-3f2e-4084-96ca-1ff9dd18fd7c rw loglevel=3 quiet
[    11.166]  
[    11.166] Current version of pixman: 0.43.4
[    11.166] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    11.166] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    11.166] (==) Log file: "/home/ahloi/.local/share/xorg/Xorg.0.log", Time: Wed Apr  3 13:59:48 2024
[    11.169] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    11.169] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    11.169] (==) No Layout section.  Using the first Screen section.
[    11.169] (==) No screen section available. Using defaults.
[    11.169] (**) |-->Screen "Default Screen Section" (0)
[    11.169] (**) |   |-->Monitor "<default monitor>"
[    11.170] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    11.170] (**) |   |-->Device "AMD Graphics"
[    11.170] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    11.170] (**) Option "DontZap" "false"
[    11.170] (==) Automatically adding devices
[    11.170] (==) Automatically enabling devices
[    11.170] (==) Automatically adding GPU devices
[    11.170] (==) Automatically binding GPU devices
[    11.170] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    11.170] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    11.170] 	Entry deleted from font path.
[    11.171] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    11.171] 	Entry deleted from font path.
[    11.171] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    11.171] 	Entry deleted from font path.
[    11.171] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    11.171] 	Entry deleted from font path.
[    11.171] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    11.171] 	Entry deleted from font path.
[    11.171] (==) FontPath set to:
	/usr/share/fonts/TTF
[    11.171] (==) ModulePath set to "/usr/lib/xorg/modules"
[    11.171] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    11.171] (II) Module ABI versions:
[    11.171] 	X.Org ANSI C Emulation: 0.4
[    11.171] 	X.Org Video Driver: 25.2
[    11.171] 	X.Org XInput driver : 24.4
[    11.171] 	X.Org Server Extension : 10.0
[    11.171] (++) using VT number 1

[    11.172] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    11.173] (II) xfree86: Adding drm device (/dev/dri/card1)
[    11.173] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:07:00.0/drm/card1
[    11.173] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0
[    11.176] (--) PCI:*(7@0:0:0) 1002:15d8:1002:15d8 rev 201, Mem @ 0xd0000000/268435456, 0xe0000000/2097152, 0xfcc00000/524288, I/O @ 0x0000e000/256
[    11.176] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    11.176] (II) LoadModule: "glx"
[    11.179] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    11.183] (II) Module glx: vendor="X.Org Foundation"
[    11.183] 	compiled for 1.21.1.11, module version = 1.0.0
[    11.183] 	ABI class: X.Org Server Extension, version 10.0
[    11.183] (II) LoadModule: "amdgpu"
[    11.183] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[    11.186] (EE) Failed to load /usr/lib/xorg/modules/drivers/amdgpu_drv.so: /usr/lib/xorg/modules/drivers/amdgpu_drv.so: undefined symbol: glamor_egl_init_textured_pixmap
[    11.186] (EE) Failed to load module "amdgpu" (loader failed, 0)
[    11.186] (EE) No drivers available.
[    11.186] (EE) 
Fatal server error:
[    11.186] (EE) no screens found(EE) 
[    11.186] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    11.186] (EE) Please also check the log file at "/home/ahloi/.local/share/xorg/Xorg.0.log" for additional information.
[    11.186] (EE) 
[    11.254] (EE) Server terminated with error (1). Closing log file


 it complained the amdgpu_drv.so,

i learn that included in linux kernel by default?
what is the problem here actually

Re: fatal server error (EE) no screen found(EE)

Reply #1 –
Kernel 6.8.2 is defective, at least on Artix. Try downgrading to 6.8.1

Re: fatal server error (EE) no screen found(EE)

Reply #3 –
Same issue here, solved by downgrading xf86-video-amdgpu to 23.0.0-1, downgrading the kernel didn't work. Here we are again with the usual Artix-only issues, I only post on this forum when they happen

Re: fatal server error (EE) no screen found(EE)

Reply #4 –
Quote from: Exentio – on
Same issue here, solved by downgrading xf86-video-amdgpu to 23.0.0-1, downgrading the kernel didn't work. Here we are again with the usual Artix-only issues, I only post on this forum when they happen
Omg thank you very much, i've been figuring this out for hours since this morning with no luck, i cannot thank you enough!
at first i suspect the xorg-server package because i was in under impression that it provide amdgpu_drv.so,  i downgrade it but same problem.
so the  xf86-video-amdgpu is the culprit, i wonder if the next version is going to replicate the same problem.
If you have a solution in a long terms please let me know, thank you so much.

Re: fatal server error (EE) no screen found(EE)

Reply #5 –
Quote from: Exentio – on
Same issue here, solved by downgrading xf86-video-amdgpu to 23.0.0-1, downgrading the kernel didn't work. Here we are again with the usual Artix-only issues, I only post on this forum when they happen
Use another distro then. Problem solved. All the other Distro's never have any issues at all.
Unless this is a second account you've only made one other post. part of which said:
Quote
I get that there aren't many maintainers and the ones working on the distro also have a life outside of this
I'd say you only get it up to a point.
Quote
I'm not angry or trying to be aggressive
"But I do like to have a little whine if I'm even slightly put out"
Quote
these recurring issues are what prevent me from actively recommending Artix
I wouldn't actively recommend Artix to anyone who wasn't already used to Linux (Which was originally how Arch was promoted), understood that Artix is a downstream version of Arch which makes significant changes to upstream packages on a reactive basis i.e. without warning or always time to fully test everything. (Hold things back too long and people moan their unsupported Arch repo packages don't work) and also had some ability to fix things for themselves. Like downgrading a package and adding an ignore entry to pacman.conf temporarily. And patience would also be a virtue.

Re: fatal server error (EE) no screen found(EE)

Reply #6 –
 

Re: fatal server error (EE) no screen found(EE)

Reply #8 –
It should work now with xf86-video-amdgpu-23.0.0-2.2. The newer makepkg default flags cause this symbol error. Evidently, arch doesn't build this package with their default flags in a clean chroot otherwise it should have the same problem.

Re: fatal server error (EE) no screen found(EE)

Reply #9 –
Quote from: Dudemanguy – on
It should work now with xf86-video-amdgpu-23.0.0-2.2. The newer makepkg default flags cause this symbol error. Evidently, arch doesn't build this package with their default flags in a clean chroot otherwise it should have the same problem.

Its been a long standing issue as fork  of arch devtools.
The default flags in devtools don't always seem to match the actual flags of their build chroot or container whatever used.
The latest pacman cleearly show that, pyalpm is still a mismatch, won't compile with default FORTIFY 3.
It leads from time to time time to problems on our end, which then needs exports or fixing flags in the PKGBUILD.