Running on an HD4350 card, with drm-next and git version of radeon, KMS works mostly fine, but does not identify the correct mode for my monitor; I'm attaching a running Xorg.0.log where the Modeline is forced by config file, xrandr reports Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 459mm x 296mm 1680x1050_60.00 60.0*+ 1680x1050 59.9 + 1280x1024 75.0 60.0 1280x960 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 If I don't force the modeline, both X and framebuffer gets out of range for the monitor that is unable to sync in with the received data. HTH, Diego
Created attachment 30039 [details] [review] Xorg.0.log
Does non-KMS X work ok or do you have to force the mode there as well? Can you also attach your dmesg and xorg.conf?
Sorry October was definitely a bad month. Non-KMS X works fine. I'll attach the xorg.conf right now… dmesg is a bit of a problem: I get so much stuff in it that the buffer is already saturated by runtime status. Looking for some block in particular?
Created attachment 31040 [details] xorg.conf
Does this still happen with the latest changes in Dave's drm-radeon-next branch? http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-next
Works like a charm now with drm-next :)
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.