[SOLVED] Xorg strange behaviour, dri3 not loaded

TheCreeL · 2015-11-10 19:31:22

Hello,

I'm trying to set up my radeon system to hopefully have some decend framerates for future gaming sessions. I have a amd r280x, with mesa-git and xf86-video-ati-git installed.
One strange behaviour is that although working flawlessly the Xorg server doesn't seem able to load the driver.
Here's the log:

  2224.912] 
X.Org X Server 1.17.4
Release Date: 2015-10-28
[  2224.915] X Protocol Version 11, Revision 0
[  2224.916] Build Operating System: Linux 4.2.5-1-ARCH x86_64 
[  2224.917] Current Operating System: Linux Toybox 4.2.5-1-ARCH #1 SMP PREEMPT Tue Oct 27 08:13:28 CET 2015 x86_64
[  2224.917] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=61b5e446-7de5-4c23-8144-ecee674ab42c rw quiet
[  2224.918] Build Date: 01 November 2015  10:36:50AM
[  2224.919]  
[  2224.920] Current version of pixman: 0.32.8
[  2224.922] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  2224.922] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2224.925] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 11 00:59:59 2015
[  2224.925] (II) Loader magic: 0x817d60
[  2224.925] (II) Module ABI versions:
[  2224.925] 	X.Org ANSI C Emulation: 0.4
[  2224.925] 	X.Org Video Driver: 19.0
[  2224.925] 	X.Org XInput driver : 21.1
[  2224.925] 	X.Org Server Extension : 9.0
[  2224.927] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
[  2224.928] (II) xfree86: Adding drm device (/dev/dri/card0)
[  2224.928] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[  2224.929] (--) PCI:*(0:2:0:0) 1002:6798:1043:3006 rev 0, Mem @ 0xc0000000/268435456, 0xfea00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
[  2224.930] List of video drivers:
[  2224.930] 	nouveau
[  2224.930] 	neomagic
[  2224.930] 	mach64
[  2224.930] 	radeon
[  2224.930] 	tdfx
[  2224.930] 	ati
[  2224.930] 	trident
[  2224.930] 	voodoo
[  2224.930] 	intel
[  2224.930] 	ark
[  2224.930] 	glint
[  2224.930] 	nv
[  2224.930] 	r128
[  2224.930] 	siliconmotion
[  2224.930] 	sis
[  2224.930] 	vmware
[  2224.930] 	dummy
[  2224.930] 	i128
[  2224.930] 	savage
[  2224.930] 	openchrome
[  2224.930] 	vesa
[  2224.930] 	fbdev
[  2224.930] 	modesetting
[  2224.930] (II) LoadModule: "nouveau"
[  2224.930] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[  2224.930] (II) Module nouveau: vendor="X.Org Foundation"
[  2224.930] 	compiled for 1.17.0, module version = 1.0.11
[  2224.930] 	Module class: X.Org Video Driver
[  2224.930] 	ABI class: X.Org Video Driver, version 19.0
[  2224.930] (II) LoadModule: "neomagic"
[  2224.930] (II) Loading /usr/lib/xorg/modules/drivers/neomagic_drv.so
[  2224.930] (II) Module neomagic: vendor="X.Org Foundation"
[  2224.930] 	compiled for 1.17.1, module version = 1.2.9
[  2224.930] 	Module class: X.Org Video Driver
[  2224.930] 	ABI class: X.Org Video Driver, version 19.0
[  2224.930] (II) LoadModule: "mach64"
[  2224.930] (II) Loading /usr/lib/xorg/modules/drivers/mach64_drv.so
[  2224.930] (II) Module mach64: vendor="X.Org Foundation"
[  2224.930] 	compiled for 1.17.1, module version = 6.9.5
[  2224.930] 	Module class: X.Org Video Driver
[  2224.930] 	ABI class: X.Org Video Driver, version 19.0
[  2224.930] (II) LoadModule: "radeon"
[  2224.930] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[  2224.931] (II) Module radeon: vendor="X.Org Foundation"
[  2224.931] 	compiled for 1.17.4, module version = 7.5.99
[  2224.931] 	Module class: X.Org Video Driver
[  2224.931] 	ABI class: X.Org Video Driver, version 19.0

                      ... ETC ... it goes like this for all the drivers listed above

[  2224.949] (II) LoadModule: "vesa"
[  2224.949] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  2224.949] (II) Module vesa: vendor="X.Org Foundation"
[  2224.949] 	compiled for 1.17.2, module version = 2.3.4
[  2224.949] 	Module class: X.Org Video Driver
[  2224.949] 	ABI class: X.Org Video Driver, version 19.0
[  2224.949] (II) LoadModule: "fbdev"
[  2224.949] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  2224.949] (II) Module fbdev: vendor="X.Org Foundation"
[  2224.949] 	compiled for 1.17.0, module version = 0.4.4
[  2224.949] 	Module class: X.Org Video Driver
[  2224.949] 	ABI class: X.Org Video Driver, version 19.0
[  2224.949] (II) LoadModule: "modesetting"
[  2224.949] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  2224.949] (II) Module modesetting: vendor="X.Org Foundation"
[  2224.949] 	compiled for 1.17.4, module version = 1.17.4
[  2224.949] 	Module class: X.Org Video Driver
[  2224.949] 	ABI class: X.Org Video Driver, version 19.0
[  2224.949] (WW) Falling back to old probe method for neomagic
[  2224.949] (II) [KMS] Kernel modesetting enabled.
[  2224.949] (II) RADEON: Driver for ATI Radeon chipsets:
	ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
	ATI Radeon Mobility X300 (M24) 3152 (PCIE),
	ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
	ATI Radeon X600 (RV380) 3E50 (PCIE),
	ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
	ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),

        ... ETC ...

	BONAIRE, BONAIRE, BONAIRE, KABINI, KABINI, KABINI, KABINI, KABINI,
	KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
	KABINI, KABINI, KABINI, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
	MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
	MULLINS, MULLINS, MULLINS, MULLINS, KAVERI, KAVERI, KAVERI, KAVERI,
	KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
	KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
	KAVERI, KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
	HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
[  2224.952] (WW) Falling back to old probe method for trident
[  2224.952] (WW) Falling back to old probe method for voodoo
[  2224.952] (WW) Falling back to old probe method for ark
[  2224.952] (WW) Falling back to old probe method for glint
[  2224.952] (WW) Falling back to old probe method for siliconmotion
[  2224.952] (WW) Falling back to old probe method for sis
[  2224.952] (WW) Falling back to old probe method for dummy
[  2224.952] (WW) Falling back to old probe method for i128
[  2224.952] (WW) Falling back to old probe method for vesa
[  2224.952] (WW) Falling back to old probe method for fbdev
[  2224.952] (WW) Falling back to old probe method for modesetting
[  2224.952] No devices to configure.  Configuration failed.

It lists all the drivers just fine but then "no devices to configure. Configuration failed." This same error happens if i run

Xorg :0 -configure

.
Strangely enough if i start with a simple startx after login everything loads up and works flawlessly.

Now my doubt is that the 20-radeon.conf moduel in

/etc/X11/xorg.conf.d

is loaded at all. I modified it adding

Option "DRI3"   "on"

first with stock video-ati drivers and mesa and then with git versions but nothing changed in the xorg.log with both of them.
What's going on here?

Last edited by TheCreeL (2015-11-17 00:56:30)

spacelander · 2015-11-10 23:16:41

As I can make out from your Xorg log, you seam to have a laptop with switchable graphics. Xorg works, maybe because it uses the integrated graphics (eg. Intel), not the AMD card. To check if that is the cage, please post the output of

 lspci | grep VGA

Also check if your AMD/ATI card isn't disabled from the BIOS/UEFI.
If you have switchable graphics, then you need to use PRIME
https://wiki.archlinux.org/index.php/PRIME

Last edited by spacelander (2015-11-10 23:17:41)

TheCreeL · 2015-11-11 00:26:00

All i have is a desktop unit with an AMD R9 280x as stated before.
The Bios is fine. I'll post anyway some dumps to help figure this out.
If you need something specific just ask

lspci -k | grep -i radeon

02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
	Subsystem: ASUSTeK Computer Inc. Tahiti XTL [Radeon R9 280X DirectCU II TOP]
	Kernel driver in use: radeon
	Kernel modules: radeon

glxinfo | grep -i opengl

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD TAHITI (DRM 2.43.0, LLVM 3.8.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.1.0-devel (git-e06238c)
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.1.0-devel (git-e06238c)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.1.0-devel (git-e06238c)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

dmesg | grep -i radeon:

[    0.932341] [drm] radeon kernel modesetting enabled.
[    0.932941] fb: switching to radeondrmfb from VESA VGA
[    0.933241] radeon 0000:02:00.0: Invalid ROM contents
[    0.933330] radeon 0000:02:00.0: VRAM: 3072M 0x0000000000000000 - 0x00000000BFFFFFFF (3072M used)
[    0.933331] radeon 0000:02:00.0: GTT: 2048M 0x00000000C0000000 - 0x000000013FFFFFFF
[    0.933395] [drm] radeon: 3072M of VRAM memory ready
[    0.933396] [drm] radeon: 2048M of GTT memory ready.
[    0.938591] [drm] radeon: dpm initialized
[    0.946301] radeon 0000:02:00.0: WB enabled
[    0.946303] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff8802342abc00
[    0.946304] radeon 0000:02:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff8802342abc04
[    0.946306] radeon 0000:02:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff8802342abc08
[    0.946307] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff8802342abc0c
[    0.946309] radeon 0000:02:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff8802342abc10
[    0.947117] radeon 0000:02:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001c35a18
[    0.967303] radeon 0000:02:00.0: fence driver on ring 6 use gpu addr 0x00000000c0000c18 and cpu addr 0xffff8802342abc18
[    0.967304] radeon 0000:02:00.0: fence driver on ring 7 use gpu addr 0x00000000c0000c1c and cpu addr 0xffff8802342abc1c
[    0.967308] radeon 0000:02:00.0: radeon: MSI limited to 32-bit
[    0.967331] radeon 0000:02:00.0: radeon: using MSI.
[    0.967352] [drm] radeon: irq initialized.
[    3.100401] [drm] Radeon Display Connectors
[    3.180936] fbcon: radeondrmfb (fb0) is primary device
[    3.197879] radeon 0000:02:00.0: fb0: radeondrmfb frame buffer device
[    3.197880] radeon 0000:02:00.0: registered panic notifier
[    3.209986] [drm] Initialized radeon 2.43.0 20080528 for 0000:02:00.0 on minor 0

EDIT: edited the xorg.log because on last reboot even more drivers showed up...

What i don't understand is why it is loading all those other drivers when i esplicitly picked radeon, even if it's autodetecting.

Another quirk is that is i try to run

# Xorg -configure

it gives me error and then it keeps giving me error if i try startx, where if i just run startx just after login it runs fine.

Last edited by TheCreeL (2015-11-11 00:40:39)

john29 · 2015-11-11 07:53:54

Kernel 43

nano /etc/X11/xorg.conf.d/20-radeon.conf
Section "Device"
Identifier "HD7850"
Driver "radeon"
option "swapbufferwait" "0"
Option "ColorTiling" "on"
Option "DRI3" "1"
option "AccelMethod" "glamor"
Endsection

my work
mLIBGL_DEBUG=verbose glxinf

libGL: Using DRI3 for screen 0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:

Last edited by john29 (2016-01-23 11:19:50)

TheCreeL · 2015-11-11 14:48:00

What are you trying to say?

john29 · 2015-11-11 22:14:00

Try kernel 4.3 mainline rc7.1

20-radeon.conf
Option "DRI3" "1"

TheCreeL · 2015-11-12 01:19:25

I got that option already on my radeon.conf module.

For the kernel update i think i'll just wait until i get a proper pacman update, since i'm not too confortable with changing up kernels yet. And surely i'm not risking screwing up this setup while trying to learn it.
Thanks for the input tho, much appreciated.

I've ran the verbose glxinfo and got the same exact result as you except for that

libGL:Using DRI3 for screen 0

I'm really are at a loss here.

I've run some tests with Unigine Valley in wine using Direct3D 9 and it runs fairly well ( 23 fps with Native direct3d option and CSMT, still too low for the kind of card i have. In windows it hits the 85 cap), so some kind of driver must be running.
( the d3d9 green message of confirmation doesn't show up, but the yellow one does if i disable it, so it is installed and running fine i suppose )
Even stranger if i try to run the same benchmark with OpenGL instead, all i have is a 60fps white screen with music. ( waaat?)

I might ditch the open-source drivers all together for now and fallback to the propretary and see what happens, even if it's not really my ideal for the moment.

Last edited by TheCreeL (2015-11-12 01:20:06)

Lone_Wolf · 2015-11-12 12:49:01

Looks like you got way to many drivers installed and that may be confusing X .

Please post pacman -Qs xf86-video , and remove all drivers from it except those needed for your hardware.
(you prob only need one of them, xf86-video-ati ).

john29 · 2015-11-12 13:59:41

Have two kernels install is good you can change between them
pacman -S base-devel
nano /etc/pacman.conf
Add at end
[archlinuxfr]
Server = http://repo.archlinux.fr/$arch
pacman -S yaourt

yaourt -S linux-mainline

lone_wolf
pacman -Qs xf86-video
local/xf86-video-ati-git 3257.7186a87-1 (xorg-drivers xorg)
X.org ati video driver with Glamor acceleration (git version)

TheCreeL · 2015-11-12 14:42:43

@Lone_Wolf yeah you're right, i had way too many drivers installed and i don't know why. I already removed them while trying to clear up the mess ib my xorg.log file. I left untouched the following drivers:

xf86-video-ati (i believe it's for both ati and radeon entries)
xf86-video-vesa ( standard fallback, better leave it there)
xf86-video-modesetting ( not sure if removing KSM is a good idea so i left it there )

xf86-video-fbdev (this one i'm not sure what to do about it. I think is somewhat of a fallback driver too, later i explain why i left it there )

I got something sorted out meanwhile: i tried running

sudo X :1 -configure
( :0 was busy with my session X server)

and this time it successfully created an xorg.conf.new in /root.
( it autodetected fbdev as default driver that's why i didn't remove it)

I moved the xorg.conf autogenerated into /etc/X11, deleted the "Device" section ( already have the 20-radeon.conf module ) and added

BusID "PCI:2:0:0"

in case autodetection fails

Everything still loads with startx, and that's good news.

Now the problem is that i noticed xorg stopped writing log files in /var/log/.
In there i have the xorg.1.log from the configure command and xorg.0.log that still shows those drivers as installed ( just some of them ), plus the timestamp doesn't change between various reboots.

Now i have no way of knowing wether something changed or not.

I know xorg tells you the location of the log file everytime you start it but everytime is too quick and i can't see if it changed the default directory or just broke.

V1del · 2015-11-12 15:15:32

Since Xorg 1.16 it is started as an user process if you use startx and a free driver, new location would be ~/.local/share/xorg/[1]

[1] https://wiki.archlinux.org/index.php/Xorg#General

TheCreeL · 2015-11-12 21:36:02

Oh sweet, i totally missed that. I'll check on that as soon as i get my hands on it again.

I always used startx as user and i've always had the logs to var/log up until now...

Should i keep fbdev driver or can i delete it?

Lone_Wolf · 2015-11-13 16:52:23

xf86-video-modesetting was integrated in xorg-server a while ago (1.16 or 1.17) , so you no longer need that package.
(as it's no longer in repos, pacman -Qm and/or pacman -Qdt should list it).

Typical fallback order :
Xorg modesetting (requires Kernel Mode Setting,doesn't work with proprietary drivers )
vesa
fbdev

How many fallback drivers do you want ?

TheCreeL · 2015-11-14 10:33:54

Ah, well... You never know right?
Jokes aside, in fact i'm not even sure i actually installed modesetting explicitly, i'll check.

I've read fbdev uses framebuffer and is supported almost by every device, while vesa is less supported in general. But maybe that's not my case since i'll be using only newer cards from now and vesa would support them almost for sure. Thanks!

I guess i'll just keep vesa in case i installed the proprietary drivers then.

TheCreeL · 2015-11-17 00:56:08

Haven't had the chance to work on my computer in a while.
Found the xorg log in ~/.local/share/xorg/xorg.0.log with DRI3 actually loaded.

Thanks for the help.

Arch Linux

#1 2015-11-10 19:31:22

[SOLVED] Xorg strange behaviour, dri3 not loaded

#2 2015-11-10 23:16:41

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#3 2015-11-11 00:26:00

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#4 2015-11-11 07:53:54

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#5 2015-11-11 14:48:00

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#6 2015-11-11 22:14:00

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#7 2015-11-12 01:19:25

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#8 2015-11-12 12:49:01

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#9 2015-11-12 13:59:41

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#10 2015-11-12 14:42:43

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#11 2015-11-12 15:15:32

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#12 2015-11-12 21:36:02

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#13 2015-11-13 16:52:23

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#14 2015-11-14 10:33:54

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

#15 2015-11-17 00:56:08

Re: [SOLVED] Xorg strange behaviour, dri3 not loaded

Board footer