The xserver starts without errors but nothing is displayed. I have to add the
kernel boot option "vga=792" to get it to work correctly.
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x
(rev 64) (prog-if 00 [VGA])
Subsystem: Dell: Unknown device 009e
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: 66 (2000ns min), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd000000 (32-bit, non-prefetchable)
Region 1: I/O ports at 2000 [size=256]
Region 2: Memory at fc100000 (32-bit, non-prefetchable) [size=4K]
Capabilities:  AGP version 1.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans-
64bit- FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [5c] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Created attachment 659 [details]
Log file when system displays nothing
Created attachment 660 [details]
Log when "vga=792" is added to kernel command line so that display works
Adding to release blocker for consideration for 6.8.0 release.
With the 220.127.116.113 release, it still doesn't work.
Created attachment 766 [details]
log with 903 when nothing is displayed
Created attachment 767 [details]
log with 903 and kernel cmdline arg vga=792
This was discussed on today's release wranglers call. The decision was that
since it is so late in the release process and we do not have access to the
hardware, we won't have time fix this problem in this release; however, since
there is a workaround, we want to document it so that anyone else experiencing
this problem will know what to do.
Moving this to the release notes bug 999 and will keep it open so that it can be
investigated after the release.
at least, I'm pretty sure this is the problem
*** This bug has been marked as a duplicate of 1881 ***
This affects at least FreeBSD and OpenBSD as well.
the workaround obviously doen't work for them (at least not directly)
If this has been fixed soemwhere then add a link to the fixed file in CVS.
It is not a duplicate of 1881 as that is for the radeon friver and this is the
Good point, my bad.
This has been fixed by patch from Marc Aurele La France in this message:
and commited to XFree86:
It has also been confirmed that the patch fixes Xorg. FreeBSD ports include this
If someone attaches the actual patch to bugzilla as a file attachment,
we can nominate it for inclusion in 6.8.3.
Created attachment 2446 [details] [review]
patch from the freebsd site listed above
Since I'd like to see this fixed, I've attached the patch as downloaded from
the freebsd site. It seems to apply cleanly and I'm currently rebuilding the
Fedora 6.8.2-23 RPM to see if it works on my laptop.
My rebuilt RPMs with the patch applied seem to work fine. I no longer have to
use vga=792 to get the LCD to display X.
So is there any chance of this fix getting into 6.8.3?
I've reviewed the patch, and I don't see anything obviously bad about it.
There seems to be enough evidence pointed to in this bug report that it
fixes the problem, so I'm nominating it for 6.8.3.
do we have this in HEAD? it's marked as blocking 6.9/7.0.
(In reply to comment #17)
> do we have this in HEAD? it's marked as blocking 6.9/7.0.
we do now. fixed in HEAD.