Created an attachment (id=34657)
Xorg.0.log from KMS boot on 2.6.34-rc3
Just tried kernel 2.6.34-rc3 (not from mainline, self compiled, no source changes).
Same result as before.
Software is fine, not complaining about anything. But there are some things that I noticed when booting with KMS enabled:
- no EDID detection of the monitor (driver does that in UMS)
- outputs get swapped finally:
(II) RADEON(0): Output DVI-0 using monitor section Dell 3007WFPHC
(II) RADEON(0): Output DIN has no monitor section
(II) RADEON(0): Output DVI-1 has no monitor section
(II) RADEON(0): Output DVI-0 disconnected
(II) RADEON(0): Output DIN disconnected
(II) RADEON(0): Output DVI-1 connected
(II) RADEON(0): Using exact sizes for initial modes
(II) RADEON(0): Output DVI-1 using initial mode 2560x1600
With UMS this results in DVI-0 becoming connected. The log says previously that the driver detected the monitor on DVI-1 which is incorrect so the final swapping corrects the output. With KMS however the initial detection is correct and the output swapping seems to make it wrong.
Created an attachment (id=34657)
Xorg.0.log from KMS boot on 2.6.34-rc3
Just tried kernel 2.6.34-rc3 (not from mainline, self compiled, no source changes).
Same result as before.
Software is fine, not complaining about anything. But there are some things that I noticed when booting with KMS enabled:
- no EDID detection of the monitor (driver does that in UMS)
- outputs get swapped finally:
(II) RADEON(0): Output DVI-0 using monitor section Dell 3007WFPHC
(II) RADEON(0): Output DIN has no monitor section
(II) RADEON(0): Output DVI-1 has no monitor section
(II) RADEON(0): Output DVI-0 disconnected
(II) RADEON(0): Output DIN disconnected
(II) RADEON(0): Output DVI-1 connected
(II) RADEON(0): Using exact sizes for initial modes
(II) RADEON(0): Output DVI-1 using initial mode 2560x1600
With UMS this results in DVI-0 becoming connected. The log says previously that the driver detected the monitor on DVI-1 which is incorrect so the final swapping corrects the output. With KMS however the initial detection is correct and the output swapping seems to make it wrong.