server, drm, xf86-video-ati from git. Current xf86-video-ati seems to be detecting a secondary monitor(inexistant in my setup) and trying MergedFB by default. That leads to a lower resolution mode than usual(and than specified in xorg.conf). When issued the config setting Option "MergedFB" "off", server segfaults.
Created attachment 9334 [details] xorg.conf with mergedfb forced off
Created attachment 9335 [details] log with server backtrace
hmmm... looks like mergedfb is not actually getting forced off.
*** Bug 10405 has been marked as a duplicate of this bug. ***
I'm having the same problem with MergedFB, and had it disabled for the same reason, the driver seems to detect a nonexistant second monitor and thus I get no Xv for video playback. As a work around I set "MonitorLayout" "NONE, TDMS", but this only gave me a blank screen. My TFT monitor (connected to the VGA port) is detected as CRT. Should I file a separate bug about this? I'm using a ATI Radeon 9100 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QM [Radeon 9100] My backtrace of the crash, log file and configuration is available in the Debian bug I originally filed. Just ask and I will add any additional information needed. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413463
(In reply to comment #5) > I'm having the same problem with MergedFB, and had it disabled for the same > reason, the driver seems to detect a nonexistant second monitor and thus I get > no Xv for video playback. See bug 5623 which also explains how to work around the Xv problem. > As a work around I set "MonitorLayout" "NONE, TDMS", but this only gave me a > blank screen. My TFT monitor (connected to the VGA port) is detected as CRT. > Should I file a separate bug about this? There's no bug, the VGA port implies CRT from the driver POV.
Created attachment 9340 [details] [review] Stab in the dark Does this happen to help at all? Dave or Alex would probably have better ideas. Alternatively, does Option "MonitorLayout" "CRT,NONE" avoid the problem?
> There's no bug, the VGA port implies CRT from the driver POV. I see, thanks for the explanation. This does not seem to be mentioned in the radeon man page. > Created an attachment (id=9340) [details] > Stab in the dark > > Does this happen to help at all? Dave or Alex would probably have better ideas That seems to work great, no crash anymore, wonderful! :) > Alternatively, does Option "MonitorLayout" "CRT,NONE" avoid the problem? Yes, setting both Option "MergedFB" "false" and Option "MonitorLayout" "CRT, NONE" does avoid the crash.
(In reply to comment #7) > Created an attachment (id=9340) [details] > Stab in the dark > > Does this happen to help at all? Dave or Alex would probably have better ideas. > > Alternatively, does Option "MonitorLayout" "CRT,NONE" avoid the problem? > Patch looks good to me. I won't have time to test or debug this until this weekend. If it works for Sven, I'd say commit it.
Fix pushed to git, thanks for testing.
*** Bug 10503 has been marked as a duplicate of this bug. ***
The segfault is fixed with option mergedfb off, but now I get a blank("turned off") display with MergeFB Off or MonitorLayout CRT,NONE (or even NONE, CRT). Leaving it closed since it's mainly about the segfault?
(In reply to comment #12) > The segfault is fixed with option mergedfb off, but now I get a blank("turned > off") display with MergeFB Off or MonitorLayout CRT,NONE (or even NONE, CRT). > Leaving it closed since it's mainly about the segfault? Right. Can you try current git without either option? It should no longer artificially limit the resolution. If you still have issues with that, please file a separate bug.
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.