[RC410] Xpress 200m with pci id 1002:5a62 and Linux 2.6.22 - X will not start

Binary package hint: xserver-xorg-video-ati

When booting up Ubuntu Gutsy on a Toshiba Satellite L35-S2316 laptop with an ATI Radeon Xpress 200m the laptop goes to start X, however the screen goes blank, and when I say blank, I mean blank, no power, straight black! This only occurs with the 2.6.22 kernels and not the 2.6.20 kernels.

How this was fixed:

I removed the radeon.ko from /lib/modules/2.6.22-12-generic/kernel/drivers/char/drm/, rebooted and it worked (thanks to mj59). I am attaching a before and after Xorg.0.log file below.

Is this an installed system? If so did this just start happening after you updated to 2.6.22 or did it happen after an incremental update? Thanks in advance.

Brian,

Yes this is an installed system. He started out with Feisty and dist-upgraded a month ago and has been working with Canonical tech-support on the issue since then. After the dist-upgrade when it installed the new kernels (2.6.22-11) it started killing the radeon/X start up.

The output of 'lspci -vvnn' on the system would be helpful also. Thanks in advance.

Hello, everyone.

I have a Toshiba Satellite L35-SP4116 laptop, with an ATI chipset and the same problem as Richard Johnson.

I have two kernels, the lastest for Feisty and the latest for Gutsy. Just like Richard did, I dist-upgraded Feisty, but only Feisty's kernel is now working with Gutsy.

I've attached the output of 'lspci -vvnn'.

HTW. Cheers!

* Sorry, I meant "HTH".

I'm sorry once again: I forgot to add that the workaround worked for me.

By chance, did those experiencing the bug have fglrx installed at any point when you had Feisty installed? If so, one thing to try is to reinstall mesa.

The reporter in the duplicate bug report indicates that they are experiencing the issue in the live desktop environment.

Hi, I am the reporter of the duplicate bug.
What I tested so far on the laptop I have.

--- proprietary driver
Start live session 7.04 + install to harddisk + INSTALL proprietary driver => work fine
Start live session 7.04 + install to harddisk + INSTALL proprietary driver + full distro upgrade to 7.10 beta=> work fine
No upgrade problem here.

--- NO proprietary driver
Start live session 7.04 + install to harddisk + no proprietary driver => work fine
Start live session 7.04 + install to harddisk + no proprietary driver + full distro upgrade to 7.10 beta => blank screen
after distro upgrade start with the 2.6.22-12 => blank screen
after distro upgrade start with the 2.6.20-16 => work fine

2 posible work around fix for upgrade user with no proprietary driver:
1)boot with 2.6.20-16 + remove radeon.ko+ restart with 2.6.22-12 => work fine
2)boot with 2.6.20-16 + install proprietary ATI driver via system => Administration => restricted driver manager
 + restart with 2.6.22-12 => work fine

---- tribe test
Start live session 7.10 tribe 4 + install to harddisk + no proprietary driver => work fine
Start live session 7.10 tribe 5 => blank screen
The problem/regresion start with Tribe 5

---- beta cd test
fresh install 7.10 beta alternate + reboot => blank screen
live session 7.10 beta live cd => "Start or install Ubuntu" will give blank screen.

------- The work around 'fix' for fresh install 7.10 beta live CD
Must select "start Ubuntu in save graphics mode"
This will start live Ubuntu CD in 1024*768 resolution
Install Ubuntu to harddisk
restart computer
resolution in still 1024*768

Must install proprietary ATI driver via system => Administration => restricted driver manager
Restart computer
resolution is now the correct 1280*800
No blank screen any more.
-------- end 'fix'

I think this is duplicates of Bug #132716
ATI Driver Gets Black Screen on Radeon 7500 Mobile (Regression)
No problem in tribe 4
Tribe 4 after upgrade => blank screen

Here is another duplicate. ATI radeon 200m again.

Bug #138084

The DRI support for this card has been disabled in upstream git: "rc410: disable DRI by default due to it not working "

I guess the reason X worked with 2.6.20 is that the kernel didn't enable DRI for this card?

Workaround until this lands in Ubuntu: Add: Option "DRI" "off" to the Device section of /etc/X11/xorg.conf

http://bugs.freedesktop.org/show_bug.cgi?id=12048
So this is not the same as Bug #132716
I have done 2 test with success.
---fresh install 7.04 with default "ATI" non propertary driver
Add: Option "DRI" "off" to the Device section of /etc/X11/xorg.conf
remove load "dri"
Distro upgrade to 7.10 beta
No blank screen after the upgrade as the previous test.
--- fresh install 7.10 beta alternate CD
Add: Option "DRI" "off" to the Device section of /etc/X11/xorg.conf
reboot
No blank screen any more.

Gerry, thanks for the upstream link. Yes, 132716 is another issue (radeon 7500 cards).

DRI will automatically be off for the Xpress 200m in the next ati driver 6.7.195. Until then we might need to backport that change into the Gutsy 6.7.194 version.

For interest & instruction:

For ATI Radeon 200m but type RS482 [Radeon Xpress 200M] [1002:5975],
See Bug #144760
Symptoms similar but notably different - ie. gets to a login screen.

I've also seen this bug, on a Gateway ML-3109 laptop.

I found one more interesting thing in my testing: if I start the X server alone, with no startup script, it eventually displays normally (traditional "grey" background, X cursor) after about 8-10 minutes. It also stops eating CPU at this point. I've tried starting clients against it when it reaches this state, but they seem to fail.

The driver is:

xserver-xorg-video-ati 1:6.7.194-1ubuntu1

xrandr -q returns this:

Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1200
VGA-0 disconnected (normal left inverted right)
LVDS connected 1280x800+0+0 (normal left inverted right) 303mm x 190mm
   1280x800 60.0*+ 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9

More attachments follow-- an xorg.conf and an Xorg.0.log from this server started with a Feisty 2.6.20 kernel (this system was a fresh Feisty install, upgraded, then upgraded to Gutsy). The xorg.conf was autogenerated by "X :0 -configure", apart from the added and currently commented Option "dri" line.

One could argue that disabling DRI is more a workaround than a fix, anyway, this has been done upstream:
git commit d808781d48adf01e80b5bb476bae2d2f599030f1 "rc410: disable DRI by default due to it not working"

> I found one more interesting thing in my testing: if I start the X server alone, with no startup script, it eventually displays normally (traditional "grey" background, X cursor) after about 8-10 minutes. It also stops eating CPU at this point. I've tried starting clients against it when it reaches this state, but they seem to fail.

John, that's interesting. If you're curious you could maybe do some debugging from another computer a la https://wiki.ubuntu.com/DebuggingXorg to see what's going on?

Confirm fix with xserver-xorg-video-ati_6.7.194-1ubuntu1tv6_i386.deb on beta alternate 7.10
Thanks.

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

Tormod, I've been unable to get any useful debug info out of my gets-to-startup-screen behavior. strace loses control before getting to the point in question, I've been unable to get gdb to attach, the X server seems not to get to the startup screen if any debugging perturbs its behavior, and the machine often loses network on X startup. Sorry I can't contribute anything useful here.

John, thanks for trying, yes, these are typical issues when trying to debug Xorg.

I have something which seems like the same problem. I was using 7.04 successfully with the ATI binary drivers. Since upgrading to gutsy it doesn't work. At the moment I get 1280x1024, but there are screen display errors on occasion (localized, e.g. the 'show desktop' button is garbled.) I tried using kernel -20-16 instead of -22-13, but without success.
I am attaching lspci -vvnn and /etc/X11/xorg.conf.
Incidentally, running fglrxinfo crashes X.
If there's anything else that would help I'd be glad to give it.

This is the lspci output.

I'm Jadd, author of one the duplicate bugs.
Gutsy Beta Live CD still gave me the blank black screen, but when I chose safe graphics mode, it didn't, and it installed alright. I can now boot to Gutsy and log in on GNOME correctly, it seems to me.

To Jadd: Yes, the latest xserver-xorg-video-ati with this bug fix is integrated in the present live CD(20071008). I can also boot directly to gnome.
To Haran:Thank you for taking time to report the bug. But it seems to me that you have different kind of bug. This bug is blank screen at startup. You have 'garbled' button problem. You must find or filled a new bug report for your issue. This bug report 144297 is going to be close soon.

Hi, I have an ATI Xpress 200M 1002:5955 , and none of these workarounds worked for me. I had no problems with feisty, but with gutsy I get this error: PCI: cannot allocate resource region 0 after grub loading, and then blak screen, and I can do nothing. BUT,if I boot in recovery mode, and then I do init 3, I can get to GDM and everything works fine (until reboot). Same problem with restricted drivers enabled and fglrx, same workaround, same black screen after rebooting.

I've attached the output of 'lspci -vvnn'.

And I forgot to say that I had this problem only after Gutsy RC installation from the live CD, cause the live CD itself could boot and install with no problems (except the PCI: cannot allocate resource region 0 error after grub loading, but no black screen after that) ..

Hello, I have a Packard Bell R series with a

Radeon XPRESS 200M 5955 (PCIE) [1002:5955]

and none of the workarounds seems to work for me.
actually the same problem persists even with the Vesa driver on instead of the restricted one.

this is the output of my lspci -vvnn:
-----------------------------
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) [1002:5955] (prog-if 00 [VGA])
 Subsystem: Unknown device [1631:c00e]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (2000ns min), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 11
 Region 0: Memory at 90000000 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at c000 [size=256]
 Region 2: Memory at c0000000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at 98000000 [disabled] [size=128K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

---------------

in attachment i placed the log.

Please file new bug reports for other cards (or other drivers).

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Closing this against the linxu (Ubuntu) kernel package.