LVDSBiosNativeMode must be turned off on Radeon 7500 Mobile (regression)

Broken xorg.conf.

Same happened to me (also on Mobility Radeon 7500) on my Dell Inspiron 5100 (i was just about to file a bug report). This is what I updated last night (in case someone can figure out it has something to do with another package upgrade than xserver-xorg-video-ati but it's the only one I can come out with too. I'll attach my xorg.0.log too (where I can't find any errors explaining the problem).

I have the same problem with ATI Radeon 9800 Pro (ie desktop not laptop)

Since upgrade of ATI drivers yesterday (15 August), get a black screen when X Starts.

ctrl-alt-backspace is broken, can't get back to command line.

Ran today's update ( 16 Aug ) which updated fglrx driver and xorg and the problem is still there.

My xorg.conf is dated July4, so I'm not sure providing this is going to help as the the system was working fine until the latest updates.

If any more information is needed, please ask

I guess my bug is related to this one. I have a dualhead setup using Radeon 7500 and my right screen (connected to VGA) went blank after my todays update in Gutsy, but the left screen (connected to DVI) still works. Well it actually works when using my single screen setup, since on dualhead the left screen is totally messed up. (Windows are drawn only partly and so on.)

My last upgrade did this:
upgrade xserver-xorg-video-ati 1:6.6.3-2ubuntu6 1:6.6.193-1ubuntu1

I also had this bug with Radeon 9700 mobile. I resolved the problem removing my xorg.conf.

Did you just delete the xorg.conf, or did you need to reconfigure it as well?

I get screen distortions on a radeon 9250 since the latest updates,

Same problem (Ati 9600). I had to disable agpfastwrite for X to work.

disabling agpfastwrite worked for me too (radeon 9800 pro)

Disabling AGPFastWrite didn't fix my dualhead setup. (Tried to disable it on both devices and also only for the VGA device.) One note: when I use my original single screen setup, the desktop gets correctly cloned to both screens.

Here is my log on dualhead setup from start to KDM's login screen. This time the login screen was a mess too. The user list wasn't loaded and it missed other components too... Like said before, the right screen connected to VGA (called "Extra Screen" in log) is blank. The screen "is there" though, I can move the mouse cursor there, but that doesn't help much... :(

Could someone at least mark this bug as confirmed?

A lot of you seem to be playing with various radeon-options.. please don't do that. If it works for you without the xorg.conf, maybe it's the options that broke it.

To the ones with the same bug as the original reporter; try playing around with the MonitorLayout -option, or disable DRI.

This is my xorg.conf for the dualhead setup. DRI is always disabled by X itself since it's not working with xinerama. I tried to play around with the MonitorLayout option, but it didn't make any difference...

Confirmed with Mobility Radeon M24. Works with Vesa-driver.

I have clean install of Kubuntu Gutsy Tribe 5 and first boot after install ends with black screen and a system freeze. Removing xorg.conf causes my screen to be white and a system freeze.

My display adapter is Mobility Radeon M6 LY not Mobility Radeon M24 as i wrote above.

Latest updates to Xorg seemed to resolve issue for me.

It seems to be still broken. My display adapter doesn't work if power supply is connected. I used my laptop with battery and thought this issue was resolved. If I connect power supply my screen fills with carbage. Gutsy tribe 5 livecd works fine though with power supply connected.

Can somebody else test this with battery only.

I can confirm that my desktop's dualhead setup is still broken with the latest updates (Tribe 5).

Is anyone else still having problems with this bug? Since this starts to be quite irritating. Imagine being able to use only the left half of your desktop...

I am still having this problem (sorry, was out of the country for a couple of days, I actually hoped it would be fixed by now but doesn't seem so). I did a full upgrade without any effect.

- I tried to work on battery only but I don't see any difference
- I tried to play around with the MonitorLayout option, but this doesn't solve anything either. I don't have an external screen to attach to my laptop, so I still don't have anything but a black screen.
- I uncommented all additional options that I've added, without any result
- I backed up my xorg.conf and then did a reconfigure, but also without any result.

Thus far, I don't see any solution coming up to see my X on a single screen setup on my laptop.

Still broken for me with latest updates. Running on battery or on AC power makes absolutely no difference -- perhaps the person experiencing that has an unrelated ACPI bug?

Downgrading to 6.6.3-2ubuntu6 fixes the problem in its entirety, so there's definitely an issue with the upgrade.

Hallo,

My system is updated to todays state (ie 1/Sept). I still have this problem. By the way this means I have to do a hard restart, I cant get out of it with ctrl-alt-backspace.

I followed the advice from Timo Aaltonen above:

1. Re-enable AGPFASTREWRITE and restart X.
Result: black screen
Reboot machine into recoverz mode

2. Disable loading of DRI module and start X
Result: black screen
Reboot machine into recoverz mode

3. Rename xorg.conf as xorg.bak and start X
Result: X starts successfullz but Gnome gives an error message on trzing to set some properties.

Of course now mz German kezboard is a US kezboard and mz lefthanded mouse is a righthanded mouse ...

4. I don|t know what to do about MonitorLayout, maybe you can give some more instructions here

Please try this driver:

http://people.ubuntu.com/~bryce/Testing/ati/

we will (hopefully) upload it to gutsy, since it seems to fix more than it breaks, so far :)

Thanks for the update, but unfortunately, same behavior observed here. I've attached a new Xorg.log to see if anything might be more helpful. I can only hope. :)

Same here, it didn't fix my problem. The xserver-xorg-video-ati_6.7.192-1ubuntu1_i386.deb downloaded from http://people.ubuntu.com/~bryce/Testing/ati/ worked actually even worse with my dualhead setup: even the left screen connected to DVI was blank. It seems that X crashed completely with this setup. On single monitor setup this driver worked like the "real" Gutsy's driver.

How about going back to the old driver If this can't be fixed before Gutsy is released... ?

see this my bug report at #LP 137396 that seems duplicate of this bug
https://bugs.launchpad.net/compizsettings/+bug/137396

there is some logs that i I hope can help.

If duplicate , can I assign that bug as duplicate to this

I agree that 137396 may be a duplicate, and I don't think it's a compiz bug, so probably more appropriate here. I'll leave it to your discretion.

Tuxfan, I think your dual-head crash is the same as in https://bugs.freedesktop.org/show_bug.cgi?id=12295

please try the latest driver (only x86 binary available):

http://users.tkk.fi/~tjaalton/dpkg/ati

also, run "dpkg-reconfigure -phigh xserver-xorg" to get a clean xorg.conf. It doesn't generate a Modules-section anymore, and that could help here.

I tried all previous suggested options, still without any change: the screen remains black (even after getting the clean xorg.conf).

I tried use driver from

 http://people.ubuntu.com/~bryce/Testing/ati/
with version xserver-xorg-video-ati_6.7.192-1ubuntu1_i386.deb 28-Aug-2007 18:46 389K

and have the result of screen blank with errors like the picture attached.
and stop there. with alt-f2 I have access from terminal

the logs

Xorg.0.log
xorg.conf

XORG.0.log

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu2)
Current Operating System: Linux instavel-laptop 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686
Build Date: 26 August 2007
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 6 12:22:13 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "ATI Technologies Inc RC410 [Radeon Xpress 200M]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "stylus"
(**) |-->Input Device "cursor"
(**) |-->Input Device "eraser"
(**) |-->Input Device "Synaptics Touchpad"
(**) Option "NoTrapSignals" "true"
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
 Entry deleted from font path.
(WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
(**) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/cyrillic,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81e8500
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.3
 X.Org Video Driver: 1.2
 X.Org XInput driver : 0.7
 X.Org Server Extension : 0.3
 X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 1.3.0, module version = 1.0.0
 ABI class: X.Org Video Driver, version 1.2
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1002,5a31 card 1025,0109 rev 01 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1002,5a3f...

Tormod: could be. Do you think it's related to this bug?

Timo: no luck. Dual head still crashes with xserver-xorg-video-ati_6.7.192-1ubuntu2_i386.deb from http://users.tkk.fi/~tjaalton/dpkg/ati

I made a new dual head config after the suggested "dpkg-reconfigure -phigh xserver-xorg", it's attached in this comment. I'll post the log in a minute.

I tried use too the driver from

 http://users.tkk.fi/~tjaalton/dpkg/ati/
with version xserver-xorg-video-ati_6.7.192-1ubuntu2_i386.deb 06-Sep-2007 14:47 389K

and have the result of screen not blank but with wallpaper :) but with errors yet :( like the picture attached.
and stop there. with alt-f2 I have access from terminal too

I see that is better atached long logs in the other posts ;)

I will attached the xorg logs

This is the log with the new dual head config. Still crashing like the old one. Note that DefaultDepth was 24 in the new config after the suggested "dpkg-reconfigure -phigh xserver-xorg".

The new driver (xserver-xorg-video-ati_6.7.192-1ubuntu2_i386.deb) worked like the previous one when using the single monitor setup: the desktop gets correctly cloned to both screens.

I'm getting the same behavior even with ubuntu2. Still black screen. Tried attaching an external monitor, no output there either. Xorg.0.log attached, xorg.conf is next.

Tuxfan, zaphod mode does not work anymore, and as it seems, you are getting cloned mode working out of the box. So this bug is not for you ;)

To the 7500 owners; try putting "MonitorLayout" "LVDS,CRT" to the Device-section. It seems that the driver thinks the panel is a TMDS-device, while laptop panels are LVDS...

Okey... Didn't even know what a zaphod mode was. :/ But I got my dual head working after little searching and playing around with the configs.

All I had to do was add a "Virtual 2580 1024" to the new single monitor xorg.conf under Screen section's subsection "Display" and then use "xrandr --output VGA-0 --right-of DVI-0". So it works now (with the driver version 1:6.7.192-1ubuntu2 at least), except that the monitors are identified in different order than with xinerama... Now the VGA is screen 1 and DVI screen 2, but I can live with that if I can't find out how to change the order.

I think it should be mentioned somewhere in the release notes that dual head system has changed so that people upgrading with old configs would know what to do when they end up with a broken X.

(Sorry for being off-topic, but since we discuss dual-head already) After what I have learned today, zaphod is when you have two "Screen" sections in xorg.conf on one card. Xinerama then combines these two screens. The new xrandr 1.2 can do dual-head with one "screen", like what TuxFan explains. So should displayconfig-gtk be fixed to use xrandr 1.2 when possible/needed, like when using the new ati driver?

I hope you didn't ask that from me Tormod, since I don't even use Ubuntu. I use Kubuntu. :)

But I found out that it's still possible to have a static setting for dual head in xorg.conf. Otherwise you'd have to put the xrandr command somewhere where it's runned after boot for KDM (or GDM). Here's a good howto that I found: http://www.intellinuxgraphics.org/dualhead.html

I still haven't found out how to change the order of the detected ports in the graphic card since the current order makes the login screen to go to the "wrong" monitor and KDE's desktop settings also say that monitor 2 is the left one and monitor 1 the right one for me...

David, did you try without an xorg.conf? Does the machine freeze or just the screen or not at all (hard disk activity? switch console?)

I have not tried without any .conf, only with the one produced by dpkg-reconfigure. I will try without an xorg.conf shortly. The machine does not freeze under any version of the driver, only a blank screen on X. I can still hit Ctrl+Alt+F1 to get to a console and swap back to VESA driver and restart X. I suspect, based on the lack of obvious errors and the fact that the machine continues to run, that the driver is just not sending output or not sending it to the right place.

Same behavior occurs with no xorg.conf. Only a bare minimum vesa config works to get X running.

I hate to triple-post like this, but given the 3 duplicate bugs and the number of users who have reported a me too, I feel compelled to request that someone from ubuntu-qa please mark this bug as Importance High because (per the Bug Importance Guidelines): "A problem with an essential hardware component (disk controller, laptop built-in wireless, video card, keyboard, mouse)" as well as a "severe impact" on users (probably not even a small proportion, so might be critical).

Did you try MonitorLayout as Timo suggested?

I did try a couple of MonitorLayout options, but perhaps I'm missing the critical one:
"LVDS,AUTO"
"LVDS,NONE"
"LVDS,CRT"
"AUTO,AUTO"

Any suggestions on other combinations to try?

Can you report this upstream? https://bugs.freedesktop.org/enter_bug.cgi Add your Xorg.0.log from without xorg.conf.

Timo, David's log has:
(II) RADEON(0): Output VGA-0 disconnected
(II) RADEON(0): Output LVDS connected
(II) RADEON(0): Output S-video disconnected
(II) RADEON(0): Output LVDS using initial mode 1024x768

Does that mean it sees the connected built-in screen? But fails to drive it correctly?

Just a shot in the dark: can you run "xrandr -q -d :0" on a virtual console?

I just used restricted drivers manager to uninstall then again to reinstall fixed problem.Didnt even have to restart after the uninstall only after reinstall.

I installed latest driver and then generated a new xorg.conf as described above. I note that previously the monitor had been defined as "default" but now is correctly identified with model number, (This is a desktop system withRadeon 9800 Pro with external TFT screen). MonitorLayout option is DPMS.

Restarted X without problem.

I attach the new xorg conf.

Timestamp of conf file is incorrect, it was generated at 10:40 but timestamp is 11:40 ??

I don't know if this helps anyone, but I tried to downgrade back to current Gutsy's version 6.6.193-1ubuntu1, but that version didn't understand my new dual head setup and I ended up in cloned single monitor mode. I then went to the 6.7.192-1ubuntu1 from http://people.ubuntu.com/~bryce/Testing/ati/ and it's working like was the Timo's 6.7.192-1ubuntu2.

Attached is xrandr -q -d :0

I have the sam behavior like David, without xorg , with xorg generated by dpkg-reconfigure

the shoot in the dark lcd :) using fglrx driver

root@instavel-laptop:/home# xrandr -q -d :0
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 800
default connected 1280x800+0+0 0mm x 0mm
   1280x800 60.0*
   1024x768 60.0
   848x480 60.0
   800x600 60.0
   720x576 60.0
   720x480 60.0
   640x480 60.0
   640x400 60.0
   640x350 60.0
   512x384 60.0
   400x300 60.0
   320x240 60.0
   320x200 60.0
root@instavel-laptop:/home#

root@instavel-laptop:/home# xrandr --verbose -q -d :0
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 800
default connected 1280x800+0+0 (0x7d) normal (normal) 0mm x 0mm
        Identifier: 0x7c
        Timestamp: -415821373
        Subpixel: horizontal rgb
        Clones:
        CRTC: 0
        CRTCs: 0
  1280x800 (0x7d) 61.4MHz
        h: width 1280 start 0 end 0 total 1280 skew 0 clock 48.0KHz
        v: height 800 start 0 end 0 total 800 clock 60.0Hz
  1024x768 (0x7e) 47.2MHz
        h: width 1024 start 0 end 0 total 1024 skew 0 clock 46.1KHz
        v: height 768 start 0 end 0 total 768 clock 60.0Hz
  848x480 (0x7f) 24.4MHz
        h: width 848 start 0 end 0 total 848 skew 0 clock 28.8KHz
        v: height 480 start 0 end 0 total 480 clock 60.0Hz
  800x600 (0x80) 28.8MHz
        h: width 800 start 0 end 0 total 800 skew 0 clock 36.0KHz
        v: height 600 start 0 end 0 total 600 clock 60.0Hz
  720x576 (0x81) 24.9MHz
        h: width 720 start 0 end 0 total 720 skew 0 clock 34.6KHz
        v: height 576 start 0 end 0 total 576 clock 60.0Hz
  720x480 (0x82) 20.7MHz
        h: width 720 start 0 end 0 total 720 skew 0 clock 28.8KHz
        v: height 480 start 0 end 0 total 480 clock 60.0Hz
  640x480 (0x83) 18.4MHz
        h: width 640 start 0 end 0 total 640 skew 0 clock 28.8KHz
        v: height 480 start 0 end 0 total 480 clock 60.0Hz
  640x400 (0x84) 15.4MHz
        h: width 640 start 0 end 0 total 640 skew 0 clock 24.0KHz
        v: height 400 start 0 end 0 total 400 clock 60.0Hz
  640x350 (0x85) 13.4MHz
        h: width 640 start 0 end 0 total 640 skew 0 clock 21.0KHz
        v: height 350 start 0 end 0 total 350 clock 60.0Hz
  512x384 (0x86) 11.8MHz
        h: width 512 start 0 end 0 total 512 skew 0 clock 23.0KHz
        v: height 384 start 0 end 0 total 384 clock 60.0Hz
  400x300 (0x87) 7.2MHz
        h: width 400 start 0 end 0 total 400 skew 0 clock 18.0KHz
        v: height 300 start 0 end 0 total 300 clock 60.0Hz
  320x240 (0x88) 4.6MHz
        h: width 320 start 0 end 0 total 320 skew 0 clock 14.4KHz
        v: height 240 start 0 end 0 total 240 ...

David, can you try this on the virtual console:
 sleep 10; xset -d :0 dpms force on
and quickly switch back to the X display (ctrl-alt-F7 normally) and wait ten seconds?

Tuxfan, let's discuss dual-head issues in another bug, so we don't hijack David's bug with other issues.

No such luck. The screen has been (powered) on the entire time... just black/blank. I also, in case it's helpful, dumped an xset query from xset -d :0 -q. It's attached.

This is an xorg.log with Tormod's ati driver that provides extra debug information. I wonder if it turning off both crtc 0 and crtc 1 could be related (not really sure, not a hardware guy).

Alex Deucher posted this in the upstream bug:

"(II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1040 1688 1344 768 771
777 806 (48.4 kHz)
(II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771
777 806 -hsync -vsync (48.4 kHz)

looks like you are getting two modes for 1024x768 on LVDS. Try switching to the
other one. you can use xrandr --verbose to list the modes."

Still nothing, assuming I'm doing this properly:

xrandr -d :0 --output 1 --mode 0x48

(I assume the 0x48 in parenthesis is the XID of the mode)

Honestly, I'm not at all familiar with xrandr and the man page is a bit on the spotty side.

Learning how to use xrandr helps. The following command fixed things substantially:

xrandr -d :0 --output LVDS --mode 0x48

I've attached the output of xrandr -d :0 -q --verbose to see if that helps create an underlying fix for the bug. (Or at least, reveals a way to avoid typing the xrandr command every start, AFTER fixing .Xauthority)

Any news on this? I'm still seeing problems after trying all suggestions.

ATI Radeon Mobility 9700

Thanks

I'm also having this problem. I'm more than happy to provide information on request.

My video card is: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
I'm using the auto-generated xorg.conf from "dpkg-reconfigure -phigh xserver-xorg" (and I just redid it to ensure it was clean).

If David's workaround doesn't work for you, you have another issue than him, so please file a new bug.

David, would you be able to follow up on Alex's questions in the upstream bug tracker?

Tormod: thanks, will do.

New bug created #141551

I am on a Dell Inspiron 5100 with the Radeon Mobility M7 [7500]. I have tried several of the suggestions listed to no avail. I get a black picture immediately upon starting xorg if the driver is set to ati. Having no xorg.conf, trying the various MonitorLayout Options, etc and all I get is the same black screen.
The xrandr commands all issue errors about the server refusing connection to screen 0.

Ok, I had to connect an external monitor to get x to start on the external monitor, then I could get a good xrandr output. See attached.

Now I can run:
xrandr -d :0 --output LVDS --mode 0x55

and get the display on the actual laptop to work. NOTE: The other 1024x768 mode didn't change anything. If someone can tell me what to do to get proper debugging info, I can post it, just me know.

According to upstream, this should be fixed in ATI git master. Any idea which ubuntu package version this will be? I assume it will make it into gutsy, right?

Alex is not very verbose about which upstream fix, but I guess it is the newer LVDS handling and mode fixes. They came after 6.7.193 which is in Gutsy, but they will be included in 6.7.194. Hopefully also the latter will be accepted in Gutsy since it has many bug fixes (and nothing else).

Please test the 6.7.194 test build from https://wiki.ubuntu.com/XorgOnTheEdge

Unfortunately, 6.7.194 does not fix the issue for me. I must still run the xrandr command to get video back.

Does not fix it for me either. I do have some more info though. After Xorg starts, I can login (blindly) and then run the xrandr commands from the console. It seems that the code for each mode is different when the external monitor is not connected. See attached output with 194 driver.

Same problem with Radeon xpress 200M (RC410)
Can't Install or try the new 7.10 beta.
This is also happening with the Mandriva beta and Fedora 8 test all of which worked fine in previous versions.

Same here with the latest update from 2.6.22-11 to 2.6.22-12 and fglrx 8.41.7. It seems x.org fails to start and freezes, because i'm not able to switch to the console with ctr alt f1, neither does ctr+alt_backspace work. (my numlock responds still).

Let us keep this bug for David's issue with the "ati" driver on 7500 cards. Please find/file other bugs for other issues.

Yea, I think the complete xorg freeze-up issues are different as I can still switch to a console and CTRL+ALT+BKSP just fine to kill the server (and it looks like the others with Mobility 7500s can too). Just to be clear for others, this bug is for the open 'ati' driver, not the proprietary 'fglrx' driver.

The -tv3 package from http://ppa.launchpad.net/tormodvolden/ubuntu/pool/main/x/xserver-xorg-video-ati/ (i386 still in build queue) will have all the relevant changes from current git upstream.

the tv3 package (i386) made everything worse. I couldn't use xrandr to switch anymore. I had to downgrade to get anything to work again. I am posting the xrandr output with the tv3 driver.

I prepared a -tv4 with the git changes from 3 hours ago. Unfortunately I uploaded them to the wrong pocket, and I am now far away from my keys. You can however download my sources and easily build it yourself (follow the Building Drivers instructions on https://wiki.ubuntu.com/XorgOnTheEdge). Or wait another ca 10 hours till I can upload again.

Please test the new -tv5 packages (available through https://wiki.ubuntu.com/XorgOnTheEdge)

tv5 still had issues. I can give the output of xrandr later, and I will test tv4 too.

Here is the output of xrandr for tv5. It is quite different. Note, that when I changed modes to try the 800x600 resolution, I lost the console as well.

I am dealing with the same bug as originally stated. I just tried the -tv5 package and am experiencing the same problem. xorg.conf attached.
According to the log, its correctly detecting the panel as the only output available and its correctly selecting it.

Let me know if there is anything else I can try.

Here is my log file

FYI: I have just helped the freedesktop.org developers test a new patch that should be fixing things. This has been committed to the freedesktop.org GIT and should (I would assume) be making to at least a -tv6 soon, if not into a new Gutsy package. I would really hope this gets out before release.

Yes, -tv6 is uploaded to my PPA and just waiting to be build.

Fixed upstream with these latest git commits (probably the first one):

597dffce9bdc200003d0be880235258386a0bdd7 RADEON: final fix for RMX/LVDS
bfede412b3a3cd11769a580b167c528734146096 RADEON: minor fixes for external TMDS
5f5c4e6ad61c45c24f1443b91b4bc5375efdebc0 RADEON: remove RADEONSaveMode()
b6bda79f72df5e5bf9c6b71fa3298e765da506bd RADEON: more fixes for single crtc chips
3a958ba136c3fae5a4ddd56373ac7cd47046f10e RADEON: remove some cruft

That seems to have done it. Xorg starts up to gdm now like it should.

Radeon 9600 RV350, tv6 package is doing well. The only problem noticed after installed it, Gutsy had been no sound. ?

I'm running tv6, sound works fine. I can't think of any reason the ati driver would affect sound.

Sound working fine for me too.

Just confirming that installing tv6 fixes the black screen problem for me on ThinkPad T41p with FireGL2, thanx

xserver-xorg-video-ati (1:6.7.194-1ubuntu2) gutsy; urgency=low

  [ Timo Aaltonen ]
  * Add some patches from git master which fix a number of important
    bugs. Also add a new patch (10) which has not yet been merged
    upstream.

  [ Tormod Volden ]
  * debian/patches/02_mode_code_cleanup.diff:
    - Prerequisite for patch 03.
    "RADEON: more clean up of mode code"
    (fd.o commit 21593d04d222b05dbba9abd31eaa3bfb91d999b6)
  * debian/patches/03_LVDS_mode_validation.diff:
    - Prerequisite for patch 07.
    "RADEON: more work on LVDS mode validation and fixups"
    (fd.o commit 99ceaefa18c6e07b55106cca0ea8996fa73667be)
  * debian/patches/04_remove_cruft.diff
    - Removes two unused functions.
    "RADEON: remove cruft"
    (fd.o commit dcc376e2d2a13329dd03f1bc4b471329757a6f5f)
  * debian/patches/05_ext_tdms_table.diff
    - Prerequisite for patch 09.
    "RADEON: add support for ext tmds table and ext tmds chip init"
    (fd.o commit 22519fde1e002f28d6036d448fcd18452d00f1bb)
  * debian/patches/06_initdispbandwidth.diff:
    "RADEON: fix RADEONInitDispBandwidth() on single crtc cards"
    (LP: #86072, #144011)
    (fd.o commit 0ca184c3c35032df39ea7ce5d2d4aba1a97b6426)
  * debian/patches/07_sort_out_LVDS_modes.diff:
    - Prerequisite for patch 09.
    "RADEON: Finally sort out LVDS modes"
    (fd.o commit cc0c2d8e61600652b1f9cb3dc49db2ef62b1e40d)
  * debian/patches/08_disable_dri_rc410.diff:
    "rc410: disable DRI by default due to it not working"
    (LP: #144297)
    (fd.o commit d808781d48adf01e80b5bb476bae2d2f599030f1)
  * debian/patches/09_mode_and_output_fixes.diff:
    "RADEON: final fix for RMX/LVDS"
    (LP: #132716)
    (fd.o commit 597dffce9bdc200003d0be880235258386a0bdd7)
    "RADEON: minor fixes for external TMDS"
    (fd.o commit bfede412b3a3cd11769a580b167c528734146096)
    "RADEON: remove RADEONSaveMode()"
    (fd.o commit 5f5c4e6ad61c45c24f1443b91b4bc5375efdebc0)
    "RADEON: more fixes for single crtc chips"
    (fd.o commit b6bda79f72df5e5bf9c6b71fa3298e765da506bd)
    "RADEON: remove some cruft"
    (fd.o commit 3a958ba136c3fae5a4ddd56373ac7cd47046f10e)
  * debian/patches/10_disable_dri_rs485.diff
    - disable DRI on RS485 (the driver mistakenly lists it as RS482)
      (LP: #139241)

 -- Timo Aaltonen <email address hidden> Sat, 6 Oct 2007 01:52:08 +0300

While 6.7.195-1ubuntu1 actually worked, 6.7.195-1ubuntu2 breaks things. It seems that the change SPECIFICALLY undid the changes made to fix things for the Radeon 7500. Please fix or advise: the driver is useless under autoconfiguration, even if there is an xorg.conf option to change it that MIGHT make things work (I haven't tried it).

Please do try that option. Unfortunately there is currently no method for automatically doing the right thing for all hardware :/

I'll reopen the upstream bug.

Option "LVDSBiosNativeMode" "FALSE" does work for me, but this seems likely to pose a problem for new installs unaware of the bug. Would it be possible to get some sort of autodetection based on lspci?

Just a "me too...". It worked for me the same as David stated, after adding the option... Thanks for the great efforts by the way to get things fixed so quickly.

Same for me. update breaks things... Option "LVDSBiosNativeMode" "FALSE" gets it working.

It might be useful if the me-tooers would add their exact hardware details, at least the output from: lspci -vvnn|grep "VGA comp"
Note: only for those who need the "LVDSBiosNativeMode" "false" option.

this is mine:

nokie@sergei:~$ lspci -vvnn|grep "VGA comp"
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA])

I have a Dell Inspiron 5100 Laptop

Here is mine:

maggie@PIXIE:~$ lspci -vvnn|grep "VGA comp"
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA])

I too have a Dell Inspiron 5100 laptop

Another Inspiron 5100:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA])

Ironically, I also have a Dell Inspiron 5100. Same lspci output:
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA])

My output of lspci -vvnn|grep "VGA comp":

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV280 [Radeon 9200 SE] [1002:5964] (rev 01) (prog-if 00 [VGA])

Sascha, did you need the LVDSBiosNativeMode option to make that card work? I have the same card in my desktop and did NOT need the LVDSBiosNativeMode option for 1280x1024. In fact, this bug should only affect laptops.... is yours one?

Hello David, no it is a desktop pc and no laptop. I don't know where the bug is exactly.

Cheers
Sascha

Alex Deucher says he has a fix in for LVDS related issues. I've done up a git snapshot of the current -ati head if anyone would like to test this:

 http://people.ubuntu.com/~bryce/Testing/ati/xserver-xorg-video-ati_6.7.195~git20071015_i386.deb

One caveat, I had to disable inclusion usr/share/pci/*, as those files weren't generated by the build process. I hope they're no longer needed, but it's possible I've omitted a step or something in the packaging process, in which case I apologize. So install this with care!

Bryce, those files are only needed by the experimental debian patches to automatically choose the right driver (without a Driver section in the xorg.conf), our server doesn't support that yet. So it's safe to not have those right now :)

When testing, remember to remove the "LVDSBiosNativeMode" option.

I have a Radeon 7000 (01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA])) and after upgrading from Feisty tu Gutsy I got a blank screen. I tried the latest git snapshot, switching modes with xrandr, with or without LVDSBiosNativeMode, using the default generic kernel instead of custom recompiled, nothing, my LCD screen still complains "no signal".
The same thing happened when I upgraded from openSuse 10.2 to 10.3, ironically that was the reason I switched to Kubuntu.

I noticed that now I don't get the message "agpgart: Device is in legacy mode, falling back to 1.x", while I've always had that in the past.

Brownout: if not even the Option helped, maybe you have another issue than what this bug is about.. Anyway, please test a new snapshot available here:

http://ppa.launchpad.net/tormodvolden/ubuntu/pool/main/x/xserver-xorg-video-ati/

same goes for the others too.

It crashed the system, cold reboot was needed.

I downgraded to 6.6.3 and works like a charm.

Hello,

I have the same problem... blank screen after upgrade to gutsy. I seem to have a newer ati card, though (ATI Technologies Inc M52 [Mobility Radeon X1300] ).
Adding the LVDSBios... option didn't help. Using the package linked by Timo didn't help. Every time, the log for x server shows a crash, in the fglrx driver. What can I do? :)
Brownout, how did you downgrade? Where can I find a deb with an older driver? And anyway, are the old driver compatible to the version of X used in Gutsy?

Thanks.

Andrei, for the X1300 you need to use the fglrx driver (file bugs on linux-restricted-modules-2.6.22) or the vesa driver.

The "LVDSBiosNativeMode" option is now obsolete in the newest upstream version and this should work automatically. Please try the newest version from https://wiki.ubuntu.com/XorgOnTheEdge

Hello Tormod, thanks for your answer. But I don't quite understand... Isn't everybody on this thread using the fglrx driver? Is there another ati driver? Are you implying that I'm not affected by this bug? :)

This bug is about the Open Source X.org ATI Driver supporting older Radeons, FIreGLs, etc. fglrx is a proprietary, closed-source driver for newer Radeons.

I had have the same problem. I use the instruction at the release notes:

-->
Blank screen with some ATI hardware

People with ATI display adapters may get a blank screen when loading X due to the driver being unable to initialize certain hardware. Upstream is working on it, and hopefully we'll be able to release an update for 7.10 soon after the release. In the meantime, add 'Option "LVDSBiosNativeMode" "false"' to the driver section of xorg.conf. Bug #132716
<--

After i change the xorg.conf i could start with a resolution of 800x600 pixels. Then i use the grafical tool to chance the resolution to 1280x1024 pixels, the normal resolution of my display.

cheers
Sascha

The Problem is that my solution is use the vesa driver. The new ATI driver at http://ppa.launchpad.net/tormodvolden/ubuntu/pool/main/x/xserver-xorg-video-ati/ don't works. Only get the *black screen of dead*.

Hoping for a solution.

Cheers
Sascha

I gots gutsy running on an ATI Radeon Mobility 7500 and no black screen... though, it does go black for a second or two during bootup.

However, everything I move something on the display my CPU usage skyrockets! The xorg.conf says the driver is "ati" not fglrx.

Sascha, I think you should open a new bug report. You have another card and probably another issue than David.

Same happened to me (also on Radeon 9200) on my Desktop. I only install with safety mode, but don't have all power, like i can't use compiz.

Hugs.

10202007 i386 driver seems to be working for me without the "LVDSBiosNativeMode" Option

10202007 amd64 driver works for me (ATI Radeon Xpress 200G; mobo integrated) after I blind logged in, Ctrl+F7, xrandr... and rebooted.
I also activated the ATI proprietary driver before installing Tormod's version which is recognized as the most recent.
No "LVDSBiosNativeMode" Option added to xorg.config either.

Although the 10202007 driver works to bypass the blank screen bug I'm struggling to get Ubuntu take into account my LCD resolution (1400*1050). Currently working with default 1280*1024...
Should I file for a new bug or wait for the official driver update?

As reported on this launchpad I can't figure out if bug is related only for mobility Radeon 7500 using opensource driver or not and if the main problem refers to "blank" or "black" screen. So I decided to open another bug report on https://bugs.edge.launchpad.net/ubuntu/+bug/154586.
If somebody conclude its a duplicate bug report, please feel free to change it.

victor, yes please open a new bug for the resolution issue.

David, could you please check if this bug is fixed in xserver-xorg-video-ati_6.7.195+git20071020tv ?

Yes, I can confirm, driver 6.7.195+git20071020tv solved the problem with dark screen on start up for Radeon 9600 RV350.

I have the same problem but I'm a complete newbie on all this.... How do I do to install the xserver-xorg-video-ati_6.7.195+git20071020tv in my Gutsy Gibbons?

> I have the same problem but I'm a complete newbie on all this...

Please read the previous comments to find the links, or wait for an official update.

Looking forward to an official update. How long will it propably take?

Hi Guys!

I'm still with Feisty Fawn. I have downloaded and ripped to CD Gutsy but I've heard about the bugs related to ATI's so I guess I will wait until the bugs get fixed.
Feisty works ok with Beryl and Compiz. Only when I have a video "running" and if I rotate the Cube the screen turns black:( I could never solve that. Maybe it's because of being an ATI. My Laptop runs ok, but has an Nvidia Geforce Go 7300.

Desktop: Intel i386, PIV, 3.4GHz, 1 GB RAM DDR 400, ATI 9200 Radeon.

Hope this can get solved!

Biber, we'll probably wait until 6.8 is released upstream. Maybe some weeks from now.

nunoribeiro, you can always check with the live CD if things work fine on your hardware.

And thanks to everybody testing the work-in-progress. Upstream is very grateful for your feedback, which helps to make an excellent final release.

Tormod, Live CD runs very well! I've tested! I changed the appearance for the very nitty effects and everything went ok. I was surprised because the cube didn't rotate but someone told me that I should download compiz-tools-config. That's why. I'm just afraid things get wrong:(
It's better a fresh install rather than an upgrade right?
Thanks!

Note that you can even install packages like compiz-tools-config inside the live session, if you have network and enough RAM. Yes, a clean install is always a bit safer than upgrading, but it adds the hassle of reinstalling what extra packages you use and any configuration you have done.

Yes I know:( And I have a lot of Packages so organized:) I use Gnome all the time, but I used Kopete as my preferred instant messenger, and a lot of other:) I will make backup up of everything and test either ways. I mean, first upgrade and see what's going on. If everything is ok I'll keep it!

Thank you very much for your support!

Keep up the Good Work!:)

Best Regards,

Nuno Ribeiro

Hello,

Here is a possible workaround, and clue. I too had no video when I installed 7.10. However I did have version 7.04 installed and did a full install of 7.10. Out of curiosity, I re-installed 7.04, then I did an UPGRADE from 7.04 to 7.10 Per the instructions for upgrading. I now have video!!

It would be interesting if others can do this too.

wb8erj, the most likely explanation would be that the xorg.conf generated in the 7.04 install works better than the one generated in the 7.10 install. Can you please compare them, or attach them here? On the other hand you maybe had a totally different issue than what this bug report is about.

Having something like that on a laptop with ATI 345M graphics with 128 megs of shared ram, 690 megs of ram, and an Intel Celeron M 1.80 GHz processor. When I start up the laptop, everything starts out fine, and then when the Ubuntu splash screen (that's what I call the screen with the Ubuntu logo and that progress bar) is supposed to come up, i just get this screen that changes colors from black to white and other light colors randomly. It starts up about a fifth of the time, and if i hold down the power button to turn it off, it just gets stuck on the BIOS screen. Then I have to restart the computer about ten times to get back to the damaged splashed screen. An Ubuntu memory scan says there are no errors in ram. What do I need to do to what? I'm not a linux noob.

I have an Asus a8v, athlon with an "ATI Technologies Inc M10 NQ [Radeon Mobility 9600]" and I'm experiencing the "black screen" on startup of the X server. I've done the "dpkg-reconfigure -phigh xserver.xorg", tried the xserver-xorg-video-ati_6.7.195+git20071020tv_i386.deb, and 'Option "LVDSBiosNativeMode" "false"', and I'm still getting the black screen. Here is a more detailed description:

Start with running system using vesa driver.

dpkg-query -W 'xserver*ati*'
xserver-xorg-driver-ati
xserver-xorg-video-ati 1:6.7.195+git20071020tv
xserver-xorg-video-ati-dbg
xserver-xorg-video-atimisc
dpkg-reconfigure -phigh xserver-xorg
Ctrl-Alt-Backspace

Result:
  Monitor goes into power save.
  Xorg starts consuming CPU, is not able to be killed (even with -9).

Reboot.
  Results unchanged.

ed xorg.conf s/"ati"/"vesa"
reboot.

  Works fine.

ed xorg.conf s/"vesa"/"ati"

apt-get install xserver-xorg-video-ati
dpkg-query -W 'xserver*ati*'
xserver-xorg-driver-ati
xserver-xorg-video-ati 1:6.7.195-1ubuntu2
xserver-xorg-video-ati-dbg
xserver-xorg-video-atimisc

Ctrl-Alt-Backspace
Result:
  black screen, xorg max cpu, unkillable.

Add Option "LVDSBiosNativeMode" "false"
reboot
Result:
  black screen, xorg max cpu, unkillable.

hi folks - have just d/led 7.10 and found that i cannot get video when trying to run from the CD. i have a Radeon X1300 graphics card and assume the issue is a variation on the above. how can this issue be worked around when running from the CD? (clearly, please - noob on board)

thanks!
hanna

This bug report is not the place to report other bugs even if they involve black screens. Basically only David's comments are wanted here, and once his bug is resolved, your other comments will be forgotten. Please read https://wiki.ubuntu.com/Bugs/AtiDriver

Tormod,

sorry for not being able to test the last version earlier. If i remember correct, I have the same configuration as David (inspiron 5100 and ATI Radeon 7500 Mobility), and i can confirm too that the latest version (xserver-xorg-video-ati_6.7.195+git20071020tv) is working without the LVDS-option.

Thanks a lot!

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/155954

I've just upgraded from Feisty to Gutsy fearing the evil black screen but it just works. This is my adapter:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA])

I didn't even have to insert the "LVDSBiosNativeMode" option. Everything fine.

Max

My adapter is:
ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]

My problem description is the following:
After Grub finishes I see "Starting..." string on the black screen, and the font of the string changes. But right after that the screen becomes completely black and I get a large underscore cursor blinking on the top left corner of the screen.

This black screen with cursor stays there for about 3 minutes (Feisty boots much faster on the same machine, I don't understand), and right after that (i.e. after X loads) I can see the famous Ubuntu login screen with brown background. Thereafter, I don't have any problems. This has been the case since fresh install.

Since my problem occurs before X loads and after that everything is fine, I wasn't too hopeful that new Xserver driver would solve my problem. But I've installed the latest driver from Tormod's page:
xserver-xorg-video-ati - 1:6.7.195+git20071026-0ubuntu0tv

Since it did not solve my problem, I've also added the following lines to xorg.conf later on:
Option "LVDSBiosNativeMode" "false"
Option "DRI" "off"

Nothing changed.

Since I don't have any problem after X loads, my situation is not so bad. But any suggestions are welcome.

Soner, that has obviously nothing to do with this bug report.

I'm experiencing problems with dual-head setup and xrandr 1.2 on a recent upgrade to Ubuntu 7.10 on my Dell Latitude D810 laptop with docking station. Previously this worked with the ati driver and it still functions when I change over to the "fglrx" driver (which rules out bad hardware).

I have a striped down configuration xorg.conf file (see below) with two identical Dell FP1905 monitors connected through a docking station, one via VGA-0 and the other via DVI-0. On startup the DVI-0 monitor functions as expected while the VGA-0 monitor displays "1: Analog Input Cannot Display This Video Mode". The "working" monitor shifts from DVI-0 to VGA-0 when I issue the following command:

xrandr --output DVI-0 --crtc 0 --output VGA-0 --crtc 1

At this point, my desktop is properly displayed on VGA-0 while DVI-0 displays "2: Digital Input Cannot Display This Video Mode". Is it possible that this bug is related to "crtc 0" on the ATI x600 (M24)?

The log of this session is attached. Here is my xorg.conf file:

*** BEGIN xorg.conf ***
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc104"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
 Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizEdgeScroll" "0"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "ATI Technologies Inc M24 1P [Radeon Mobility X600]"
 Driver "ati"
 BusID "PCI:1:0:0"
 Option "LVDSBiosNativeMode" "false"
EndSection

Section "Monitor"
 Identifier "Generic Monitor"
 Option "DPMS"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "ATI Technologies Inc M24 1P ...

Anthony, I don't think that you have the same problem for this bug. read the Gutsy Release notes about multi-screen setups: https://wiki.ubuntu.com/GutsyGibbon/ReleaseNotes

I had same kind of problem when tried 7.10 at Live-CD. X starts with black screen. Bug 153188, https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/153188

Cyberdork33,

I have read these release notes. That is why I posted my information to this bug report (it references people having problems with blank screens to this bug report). I created this configuration (and discovered how to move the problem from window to window) by following the steps at the sites referenced and by following Debian's guide to using xrandr:

http://wiki.debian.org/XStrikeForce/HowToRandR12

If the issues with "crtc 0" are not related to this bug, then what is the next step in trouble-shooting the issue?

Anthony

this is my first ubuntu installation

first I use a dell inspiron 5100 the blue Laptop

after booting from live cd the display was dead I e black screen

I choose the second option to install using safe drivers either on the live cd or the alternate insaller cd

how ever it worked installation was done using vesa driver

when I tried to change vesa to Ati driver using dkpg configuration

after saving xconfg....
it rebooted to black screen

after changing xorg.conf to what's given below the display appeared

i'm sure there is a problem here

xorg.conf

Section "Device"
  Identifier "ATI Technologies Inc M24 1P [Radeon Mobility X600]"
  Driver "ati"
  BusID "PCI:1:0:0"
  Option "LVDSBiosNativeMode" "false"
 EndSection

Now that the bug is fixed, a note should be added to the 7.10 release notes stating such.

Well, there's no official fix released for 7.10 users yet. There might be a backport later though. Anyway, the release notes link to this bug report.