I experience the symptom on two systems (FirePro V4800 and FirePro M5950). xorg-server-1.17.1 runs fine: Upgrading to 1.17.2 results in blank screen. relevant log snippet: (II) modeset(G0): using drv /dev/dri/card0 (EE) No devices detected. while 1.17.1 show this: (WW) Falling back to old probe method for modesetting (II) [KMS] Kernel modesetting enabled. ...
I was asked to do a bisect in another bug by Michel Dänzer. 2ce54b81391d36856641c2691bcae8bd13daba4c is the first bad commit commit 2ce54b81391d36856641c2691bcae8bd13daba4c Author: Aaron Plattner <aplattner@nvidia.com> Date: Tue Dec 30 09:13:16 2014 -0800 xfree86: Add GPU screens even if there are no active GDevs xf86platformProbeDev creates GPU screens for any platform devices that were not matched by a GDev in the loop above, but only if there was at least one device. This means that it's impossible to configure a device as a GPU screen if there is only one platform device that matches that driver. Instead, create a GPU screen (if possible) for any platform device that was not claimed by the GDev loop. Signed-off-by: Aaron Plattner <aplattner@nvidia.com> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@ubuntu.com> Acked-by: Alex Deucher <alexander.deucher@amd.com> (cherry picked from commit e36236eade412dd3894f75f78a7b3d7c1037e6c3) :040000 040000 f5fbff105eb8dd75a0f8af3ec3f4072e9e2877d5 3d7f6e8225e0559ffe5e2bd69317f9dc521b3450 M hw
So the culprit commit looks like to be this: http://cgit.freedesktop.org/xorg/xserver/commit/?id=e36236eade412dd3894f75f78a7b3d7c1037e6c3 May it be a problem with my particular configuration? What should I do/test next? Thanks: Dwokfur
This is the place from where this new bug report diverged: https://bugs.freedesktop.org/show_bug.cgi?id=92168#c14
Attila, please attach the Xorg.0.log and xorg.conf files corresponding to the problem to this report. Aaron, any ideas?
Created attachment 118915 [details] working Xorg log file 1.17.1
Created attachment 118916 [details] failing Xorg log file 1.17.2
Created attachment 118917 [details] corresponding xorg.conf
(In reply to Michel Dänzer from comment #4) > Attila, please attach the Xorg.0.log and xorg.conf files corresponding to > the problem to this report. > > Aaron, any ideas? Please forgive me, that the config file may have some atavistic remnants from the last century, although I try to keep it as up to date as possible.
Does Xorg start up if you move the xorg.conf file away such that Xorg doesn't pick it up?
Hmm, yeah, that's strange. I don't know why the server would be picking up modesetting as a GPU screen before picking up radeon as a real screen here. I would also be curious to see if this reproduces without an xorg.conf file.
(In reply to Michel Dänzer from comment #9) > Does Xorg start up if you move the xorg.conf file away such that Xorg > doesn't pick it up? Xorg does start up after I move xorg.conf, so it doesn't pick it up. I'm curious to figure out why.
(In reply to Aaron Plattner from comment #10) > Hmm, yeah, that's strange. I don't know why the server would be picking up > modesetting as a GPU screen before picking up radeon as a real screen here. > I would also be curious to see if this reproduces without an xorg.conf file. It might be caused by the module loading section of my culprit xorg.conf. I try to figure that out. After moving xorg.conf so that the server doesn't pick it up the first loaded module is ati and then comes radeon. That is a difference compared to the hand-crafted config. Is there anything I may further test for you before somebody closes this bug?
This is some blind guess by a guest but you may try: Section "ServerFlags" Option "AutoAddGPU" "off" EndSection The AutoAddGPU function seems to add additional non-existing devices to existing ones while changing their interface type/number. But this may be completely wrong, don't rely on that!
(In reply to post from comment #13) > This is some blind guess by a guest but you may try: > > Section "ServerFlags" > Option "AutoAddGPU" "off" > EndSection > > The AutoAddGPU function seems to add additional non-existing devices to > existing ones while changing their interface type/number. But this may be > completely wrong, don't rely on that! Thanks for the tip. Since removing the Xorg config file solved the crashes I compared the logs and noticed the modules were loaded differently. It was disturbing, that although Xorg could figure out the hardware I have, it couldn't figure out how my displays are arranged. After I've modified my xorg.conf to reflect the proper module loading sequence it solved crashing problems and also ensured proper arrangement of my displays at the same time. BR: Dw.
The crashes were caused by a configuration file issue.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.