Bug 468505 - X not working with ATI Radeon XPRESS 200M on newer kernels
Summary: X not working with ATI Radeon XPRESS 200M on newer kernels
Keywords:
Status: CLOSED DUPLICATE of bug 468294
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-25 11:50 UTC by Jeff Layton
Modified: 2014-06-18 07:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-26 14:49:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg.conf file (1.21 KB, text/plain)
2008-10-25 11:51 UTC, Jeff Layton
no flags Details

Description Jeff Layton 2008-10-25 11:50:36 UTC
My laptop has an ATI Radeon XPRESS 200M. Everything was working correctly on it with kernel-2.6.27.3-30.rc1.fc10.i686. With every kernel since then (I've tried -34 and -39), I've not been able to start X. When I boot with no extra kernel parameters, I just get a garbage pattern of horizontal lines on the screen when X starts. When I boot with "nomodeset", I get a black screen when X starts.

It seems that aside from the display, everything is working correctly. The laptop boots, I see the wireless light come on, when I hit the power button, I see the disk work for a bit and eventually the machine shuts down.

So it looks like just the display isn't working right.

lspci -vvv info for the display chip:

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) (prog-if 00 [VGA controller])
	Subsystem: Hewlett-Packard Company Device 30ae
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 66 (2000ns min), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at c8000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at 9000 [size=256]
	Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at c0120000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel modules: radeonfb, radeon

...other info available upon request. I may even be able to set it up so that I can ssh in while the display is in this state if it'll be helpful.

Some other (possibly unrelated) facts:

- on much earlier kernels, the display would be stuck at 640x480 unless I booted with "nomodeset". This seems to be fixed with -30 kernel. Possibly earlier ones, but I haven't tested this to determine when it was fixed.

- on the -30 kernel, while I can start X at the native screen resolution without using nomodeset, I can't hibernate the laptop. It writes data to the disk for a bit and then never actually powers off. When I boot with nomodeset, I can hibernate and resume it without any problem.

Comment 1 Jeff Layton 2008-10-25 11:51:32 UTC
Created attachment 321501 [details]
xorg.conf file

Comment 2 Pete Zaitcev 2008-10-25 18:57:46 UTC
This may be a duplicate of bug 468294.

Comment 3 Jeff Layton 2008-10-26 14:49:52 UTC
Thanks Pete...

Sure looks like it, I'll close this as a duplicate of that one for now and plan to reopen it if the fix for that doesn't also fix this.

*** This bug has been marked as a duplicate of bug 468294 ***


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