Testing the latest (rather large) changed GIT drivers seems to reveal that something is broken for an X1400 (mobile) in an Thinkpad T60 (2007) model. Starting X with the new driver results in a framebuffer that's blanked but nothing happens afterwards (RadeonHD doesn't change the resolution nor does anything else after starting up the initalisation process). Please find attached the log file with logverbose set to 7,8,99,999,9999 - I wasn't able to get more details about what wrong. I think it has something to do with a wrong setup of registers or something similar. Most likly it's related to the memory controller again. After changing the driver back to the latest working version (the one week old git one) results in a working X. But you can see some interesting behavior: Switching from X to the console shows a corrupted contentof the last shown screen content before it finally shows the correct framebuffer console after about 10 seconds(?). This does not happen if I do not try to start X with the latest git driver. This seems to be similar to the original description of bug #13605.
Created attachment 15085 [details] Log file for the new git driver
Created attachment 15086 [details] Log file for switching to vt with the older git driver after running (and killing) the new git driver.
Just to confuse the issue, I'm also running these latest updates on a T60 (X1400, 2007 model) and all is working fine so far here..
Argh, yes, I've created an endless loop in a piece of code that isn't supposed to be used yet. This was triggered thru a second bug. You had set "RROutputOrder" in your config file, right? Thanks for reporting, fix already pushed. 00f182d6c9f026ac05969cc1304e02e6483cae90 and 98d328b04500dda5030eb612f1fa899ee0fb5a95
Yes you are right and the latest git code works as expected (at least so far) :) Thanks for your work!
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.