There's a quirk in radeon_atombios.c in RADEONApplyATOMQuirks() for my particular card and laptop (begins "Falcon NW"). While testing the Linux Kernel Modesetting, I discovered that the quirk wasn't quite enough to ensure smooth functioning. At present, the driver identifies the LVDS-connected panel with the VGA output and blanks the panel when there is no VGA connected. There's a patch at bugzilla.kernel.org (http://bugzilla.kernel.org/show_bug.cgi?id=13720) which forces the multiplexer for the LVDS Connector to be a higher number than that of the VGA, which has resolved the issue for me. Is this patch applicable -- I notice that there's some similarity in the shape and configuration of both codebases -- and can I supply any more information to help resolve this issue?
The fix from the kms code shouldn't be needed for the ddx. Are you actually having problems with the ddx when not using kms? If so, please re-open and attach your xorg.conf
Created attachment 27446 [details] Xorg.0.log file Ubuntu's X.org setup has a blank Xorg.conf file and automatically detects the system's outputs. I'm sorry for the confusion, but whether I'm running a KMS kernel or not, the version of the driver on my Kubuntu system presents a black screen instead of X.
Bug reopened because problem occurs both mode-setting and non-modesetting.
(In reply to comment #2) > Created an attachment (id=27446) [details] > Xorg.0.log file > > Ubuntu's X.org setup has a blank Xorg.conf file and automatically detects the > system's outputs. > > I'm sorry for the confusion, but whether I'm running a KMS kernel or not, the > version of the driver on my Kubuntu system presents a black screen instead of > X. > Are you running a kms enabled xorg radeon driver? If not, running a non-kms radeon driver with kms active may cause problems as both drivers will be attempting to drive the hw. Make sure kms is not active if your xorg radeon driver does not support kms. if you still have a blank screen in that case, try this option (put it in the device section of your xorg config): Option "R4xxATOM" "TRUE"
(In reply to comment #4) > (In reply to comment #2) > > I'm sorry for the confusion, but whether I'm running a KMS kernel or not, the > > version of the driver on my Kubuntu system presents a black screen instead of > > X. > > Are you running a kms enabled xorg radeon driver? If not, running a non-kms > radeon driver with kms active may cause problems as both drivers will be > attempting to drive the hw. Make sure kms is not active if your xorg radeon > driver does not support kms. if you still have a blank screen in that case, > try this option (put it in the device section of your xorg config): > Option "R4xxATOM" "TRUE" I wouldn't be surprised if the kernel is enabled for KMS but the userland isn't quite there. I'll check with Ubuntu and my installation, and also try out the R4XXATOM option.
Created attachment 27464 [details] [review] Don't use fixed ref div on r4xx If you are still having problems with the xorg radeon driver when kms is disabled, please try this patch both with and without the R4xxATOM option.
Created attachment 27482 [details] Xorg.0.log file with R4xxATOM option This didn't seem to make a difference.
Created attachment 27483 [details] Xorg.0.log file with R4xxATOM option and KMS Again no change. Still a blank screen.
With kms enabled, the ddx no longer touches the hw, so if you are getting a blank screen with X on KMS, then it's a drm problem. Any modesetting related patches (like the one I attached here) will only have an affect when kms is disabled.
I've changed to an updated version of the driver being tested in Ubuntu Karmic and the issue has resolved itself. Status now to 'notourbug'. Thanks for your help, Alex.
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.