![](https://seccdn.libravatar.org/avatar/f5d4b91d909b11578fdc7969f8bc422e.jpg?s=120&d=mm&r=g)
[re-sending with compressed attachments...mail list server rejected the first one for being too large] Egbert Eich wrote:
Nigel Rantor writes:
Egbert Eich wrote:
Nigel Rantor writes:
- I cannot use my VTs once the radonhd driver is loaded.
Before then,
during boot, I can see VT's fine, once GDM starts up X I can no longer see anything. My monitor reports "signal out of range" when I switch to a VT.
Can you please try with:
Option "UseAtomBIOS" "off" ?
With this option I can still not see the VT when I use Ctrl-Alt-<n>, but interestingly, when I switch back to X I *do* see brief glimpse of a black screen with a unix login prompt.
This does not take up the whole of the screen, it is merely a rectangle within the redrawn X display, and only for a moment.
OK. There is an indication in the log file you've sent in that something may have gone wrong. Please remove the option line in your config file and run X with '-logverbose 7'.
Okay, we have some progress. When I booted up I had many many modes available to me. Weird. So, I turned up logging and turned off atom bios just to check. Attached are four log files. 1 - cold_boot1 - first boot of this machine today - lots of modes available, no VTs 2 - cold_boot2 - second boot atom bios off - lots of modes available, no VTs 3 - cold boot 3 - third boot atom bios back on - lots of modes available, no VTs 4 - warm boot - booted up from windows without fully powering off. - very few modes available, no VTs So, it looks like windows is setting something that is interfering with the way the radeonhd driver works. either firmware or just some setting that radeonhd isn't able/attempting to clear out. Either way, I know how to get more modes now, which is good. Still no VTs.
DDC isn't working and we need to find out why.
Can you please run 'rhd_conntest
' for me?
I can't run this without doing some more work to download/install things. If this was just in relation to modes then shall I skip it or would you still find it useful? Regards, n p.s. I also echo the sentiment of JP Fournier - I make software for a living but I've no idea where to start with driver development, even though I could probably spare some time. Any tasks that someone who knows nothing about the internals could usefully do?