Re: [radeonhd] 0x9442:0x174B:0xE810: HD4850 Sapphire Toxic 512Mb
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'.
- The Gnome screen res applet doesn't seem to want to give me options other than:
1280x800 1280x768 1024x768 800x600 640x480
What does 'xrandr -q --verbose' report?
Attached.
OK, these are the only modes you have.
1280x800 (0x48) 83.5MHz h: width 1280 start 1344 end 1480 total 1680 skew 0 clock 49.7KHz v: height 800 start 801 end 804 total 828 clock 60.0Hz 1280x768 (0x49) 80.1MHz h: width 1280 start 1344 end 1480 total 1680 skew 0 clock 47.7KHz v: height 768 start 769 end 772 total 795 clock 60.0Hz 1024x768 (0x4a) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x4b) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 640x480 (0x4c) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz
DDC isn't working and we need to find out why.
Can you please run 'rhd_conntest
Egbert Eich wrote:
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'.
Will do tonight when I get home.
DDC isn't working and we need to find out why.
Can you please run 'rhd_conntest
' for me?
Yep. n -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
[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?
Nigel Rantor wrote:
Okay, we have some progress.
When I booted up I had many many modes available to me. Weird.
Further progress, of sorts. I boot today and I have the same problem with modes again. I had coem from windows, so I rebooted. Didn't help. I powered the machine off and disconnected the power cable for 20 seconds. Reboot and still no modes. So, my assumption about windows setting something that doesn't get wiped on a warm boot is probably incorrect.
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?
I have just run this, output inline below: ------------- root@ferret:/home/wiggly/build/xf86-video-radeonhd/utils/conntest# ./rhd_conntest 01:00.0 rhd_conntest: v1.2.3, git branch master, commit 3f558efc Checking connectors on 0x9442, 0x174B, 0xE810 (@01:00:00): Load Detection: RHD_OUTPUT_NONE HotPlug: RHD_HPD_1 RHD_HPD_2 DDC: RHD_DDC_NONE ------------- Hope that helps somewhat. I am also about to test using the other connector on the board, although I don't see why that would change anything. (but you never know) n -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
participants (2)
-
Egbert Eich -
Nigel Rantor