Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 231359 (radeon-none-none) - Radeon driver doesn't get BIOS data correctly
Summary: Radeon driver doesn't get BIOS data correctly
Alias: radeon-none-none
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
: 186119 187821 208712 212762 229136 232496 233727 235403 238689 244777 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-07 20:52 UTC by Adam Tkac
Modified: 2018-04-11 12:51 UTC (History)
13 users (show)

Fixed In Version: 6.7.192
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-08-29 12:03:15 UTC

Attachments (Terms of Use)
(In reply to comment #18) (deleted)
2007-05-10 13:02 UTC, Adam Tkac
no flags Details
X log from Acer laptop with the patched driver (deleted)
2007-05-17 18:17 UTC, Daniel Qarras
no flags Details
Generated X config on Acer laptop with the patched driver (deleted)
2007-05-17 18:18 UTC, Daniel Qarras
no flags Details
lspci -vvv says this about my card (deleted)
2007-05-22 11:59 UTC, Adam Tkac
no flags Details

Description Adam Tkac 2007-03-07 20:52:01 UTC
Description of problem:
I have mobility radeon x700 graphics card in my notebook. When I try start Xorg
with default configuration I could see nice output - nothing

Version-Release number of selected component (if applicable):
rpm -q xorg-x11-drv-ati

How reproducible:
always when X has default configuration

Steps to Reproduce:
For all developers
 - 1. steal one ATI's mobility radeon x700
   2. try start Xorg with default configuration
   3. see output (black screen)

For ajax :)
 - 1. beg from me to access to my notebook
   2. beg again because first begging wasn't successful
   3. see steps to reproduce for all developers
Actual results:
black screen

Expected results:
working X

Additional info:
 - after ajax's investigations my bios lies to driver about monitor - says NONE
 - could be hacked when I add <Option "MonitorLayout" "LVDS,NONE"> to driver section

Comment 1 Adam Jackson 2007-04-02 21:51:17 UTC
*** Bug 233727 has been marked as a duplicate of this bug. ***

Comment 2 Adam Jackson 2007-04-02 21:52:40 UTC
*** Bug 229136 has been marked as a duplicate of this bug. ***

Comment 3 Adam Jackson 2007-04-02 22:03:50 UTC
*** Bug 208712 has been marked as a duplicate of this bug. ***

Comment 4 Adam Jackson 2007-04-02 22:14:50 UTC
*** Bug 187821 has been marked as a duplicate of this bug. ***

Comment 5 Adam Jackson 2007-04-06 17:55:42 UTC
*** Bug 212762 has been marked as a duplicate of this bug. ***

Comment 6 Adam Jackson 2007-04-09 15:27:33 UTC
*** Bug 232496 has been marked as a duplicate of this bug. ***

Comment 7 Adam Jackson 2007-04-10 20:31:11 UTC
*** Bug 186119 has been marked as a duplicate of this bug. ***

Comment 8 Daniel Qarras 2007-04-14 16:15:03 UTC
This problem still exists with Fedora 7 Test 3: tried the live CD and when the
system startup was finished all I saw was a blank screen. Switching to runlevel
3 and running system-config-display resulted also just a blank screen.

Bug 187821 has details about my system.

Comment 9 Daniel Qarras 2007-04-21 13:23:08 UTC
FWIW, Ubuntu 7.04 works perfectly on my laptop where both FC6/F7T3 fail.

Comment 10 Daniel Qarras 2007-04-29 11:45:16 UTC
This is still broken with Fedora 7 Test 4 (6.93) but works all ok with Ubuntu 7.04.

Comment 11 Adam Jackson 2007-05-08 19:53:01 UTC
*** Bug 235403 has been marked as a duplicate of this bug. ***

Comment 12 Adam Jackson 2007-05-08 20:51:30 UTC
Checking over 7.04 I see one patch that might be relevant.

Test rpm build with that patch applied:

Pick the one appropriate for your arch and test please.

Comment 13 Bruno Wolff III 2007-05-08 22:25:31 UTC
Can we just do an update and log out and back in (to restart the X server) to
test this? Or do we need to do a new install of F7?

Comment 14 John Reiser 2007-05-08 23:01:53 UTC
Bug #208712 (video out of range on graphical install from rescue CD on PowerPC),
which is marked as a duplicate of this bug #231359, is already fixed in the
FC-development Rescue CD-ROM for PowerPC of 2007-05-08, 131104768 bytes, sha1sum
f4098ed0db0965a2346b05df4da7160ce77ad8b0, even without trying those .rpm
mentioned in Comment #12 (and those do not include ppc [32-bit PowerPC] anyway.)

Comment 15 Bruno Wolff III 2007-05-09 03:47:50 UTC
I tested this by booting into F7, installing the i386 rpm above, removed
/etc/X11/xorg.conf and rebooted back into F7. My monitor was not detected, same
as previuosly.
I can still fix things by manually setting the monitor to NEC LCD2010X, logging
out, then changing the resolution to the native 1280x1024 for the monitor. For
some reason when I first change the monitor type, I can't also increase the
resolution (it is at 800x600), but after the first login it changes to 1920x1280
which doesn't make sense to me. Either it should stay at 800x600 or one would
think the monitor definition would have the prefered resolution (or at least
aspect ratio) and not just blindly pick the highest resolution supported by both
the video card and the monitor or whatever method it uses to pick the new

Comment 16 Adam Tkac 2007-05-09 11:49:02 UTC
(In reply to comment #12)
still badly broken on my x86_64. I dug around and found interesting comment. See

Regards, -A-

Comment 17 Adam Jackson 2007-05-09 14:17:43 UTC
(In reply to comment #16)
> (In reply to comment #12)
> still badly broken on my x86_64. I dug around and found interesting comment. See
> Regards, -A-

Yeah, that's the patch I added.  Bleh.  Need to figure this one out.

Comment 18 Adam Jackson 2007-05-09 14:25:47 UTC
Also, if someone could attach an X log from running the patched driver, that'd help.

Comment 19 Adam Tkac 2007-05-10 13:02:42 UTC
Created attachment 154468 [details]
(In reply to comment #18)

Comment 20 Adam Tkac 2007-05-10 13:06:46 UTC
(In reply to comment #18)
You've got it. But it looks that there's nothing interesting in log.

rpm -q xorg-x11-drv-ati


Comment 21 Adam Jackson 2007-05-11 21:15:52 UTC
*** Bug 238689 has been marked as a duplicate of this bug. ***

Comment 22 Daniel Qarras 2007-05-17 18:13:55 UTC
Great news! The x86 RPM mentioned in Comment #12 solves the problem most on my
Acer laptop! Running Fedora 6.93 with following updates system-config-display
works and identifies my laptop display and also X works. Bug 187821 has details
about my system. Please consider pushing this fix to F7!


However, with those updates I still see following hickups:

- system-config-display offers resolutions 640x400 and 800x600 although Windows
XP reports using 1200x800 which I also believe being correct
- X seems to be using ideal resolution but when closing GNOME/X, display freezes
with last view showed and I need to do Alt-Ctrl-F1 to get back to console.
Starting X again works all ok, though.

Otherwise no problems.

Comment 23 Daniel Qarras 2007-05-17 18:17:08 UTC
Created attachment 154946 [details]
X log from Acer laptop with the patched driver

Comment 24 Daniel Qarras 2007-05-17 18:18:15 UTC
Created attachment 154947 [details]
Generated X config on Acer laptop with the patched driver

Comment 25 Adam Tkac 2007-05-22 11:58:32 UTC
(In reply to comment #22)
I've created i386 livecd with patched driver (i386 version) and this also
doesn't work in my case. Looks that you've got different version of graphics


Comment 26 Adam Tkac 2007-05-22 11:59:51 UTC
Created attachment 155157 [details]
lspci -vvv says this about my card

Comment 27 Daniel Qarras 2007-05-31 20:57:27 UTC
FWIW, this is still broken with Fedora 7 (but still works all ok with Ubuntu 7.04).

Comment 28 Jacek Piskozub 2007-06-22 09:02:01 UTC
The patched rpm from comment 12 saved the day on my Acer Travelmate 4100 with X700

Comment 30 Jacek Piskozub 2007-06-22 10:28:38 UTC
I'll add that I lost graphics completely after a yum update to f7 (dark screen,
no possibility of setting up the graphics with either radeon or vesa). Comment
12 rpm  was the solution.

Comment 31 Matěj Cepl 2007-06-29 14:26:20 UTC
After being one of the most duplicate bugs in Red Hat bugzilla, it may be time
to make this bug ASSIGNED, right? ;-)

Comment 32 Adam Jackson 2007-08-27 20:55:32 UTC
The radeon output detection code has been dramatically overhauled in 6.7.192,
which is currently headed to rawhide.  Anyone affected by this bug please test
it and report any failures here.

Comment 33 Daniel Qarras 2007-08-28 15:09:13 UTC
Oh, dear God, tears are coming from my eyes, it works finally! Thank you!

Seriously, though, a bit more complete report below including a way to get a
hang every time:

1) running system-config-display now finally works and if I just use the default
config created also the driver works perfectly. Config looks sane, no anything
especial there. So far so good.

2) however, when running system-config-display only resolution 800x600 can be
selected. So I was tempted to change monitor from autoconfigured to a 1200x800
LCD display and selecting 1200x800 resolution. With that xorg.conf I get almost
immediate system hangs after starting X and few applications.

In case 2) there's both new Monitor section and Modes setting under Display
section, also option "dpms" in the Monitor section. Commenting only "dpms" out
still hangs. When commenting out only Modes line I get only blank screen when
starting X. But when both "dpms" and Modes lines are commented out, everything
is working all ok again.

So clear progress here but for an unsuspecting user a great chance to get hanging X.

For details about my system please see Bug 187821.


Comment 34 Matěj Cepl 2007-08-28 16:54:43 UTC
Reporter, could you confirm please, that this is really resolved?

Comment 35 Adam Tkac 2007-08-29 06:41:02 UTC
Nice work, monitor detection is now correct

Comment 36 Adam Jackson 2007-10-01 20:21:53 UTC
*** Bug 244777 has been marked as a duplicate of this bug. ***

Comment 37 Jens Petersen 2007-10-03 08:01:12 UTC
Would it make sense to clone a bug of this for F7?

Comment 38 Dave Airlie 2007-10-04 00:15:48 UTC
I acutally don't think we can fix this in F7 in any reasonable fashion.

The reason this is fixed in F8 is a brand new ATI driver which drops support for
some of the older features like mergedfb/dual-head, so shipping the new driver
in F7 updates would break peoples existing setups..

We can't backport the fix either as the older driver is limited by its own

Comment 39 Bruno Wolff III 2007-10-04 04:20:59 UTC
For the problems I was having, there isn't any point to fixing F7. I only had a
problem on first boot and once I manually set up the xorg configuration I didn't
have to futz with it again. I don't plan on doing any more F7 installs, so just
having a fix in F8 is OK with me.

Comment 40 Jens Petersen 2007-10-04 05:10:28 UTC
Agreed - I just asked since there was talk of an update earlier
and this bug is already closed rawhide. :)

Note You need to log in before you can comment on or make changes to this bug.