Red Hat Bugzilla – Bug 251087
GeForce 8400M PCI setup bug
Last modified: 2008-05-17 11:19:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20070718 Fedora/22.214.171.124-1.fc7 Firefox/126.96.36.199
Description of problem:
With the nv driver enabled X will lock up, when this happens normally the display is gray but has also displayed a "negative 8 color image." the lock ups happen when starting the system in runlevel 5, changing to runlevel 5 or using the startx command. Currently I am using all F7 bits other than the nv driver (xorg-x11-drv-nv-2.1.2-1.fc8).
lspci shows the graphics card as "01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0428 (rev a1)" The card is marketed as a "GeForce 8400m G"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Change Driver entry in xorg.conf from vesa to nv
2. attempt to start the X server
X gets stuck, Lock up, ssh and networking still works.
Much GUI goodness.
Created attachment 160785 [details]
Xorg.0.log of failed startx
Can you attach output of 'lspci -vnn' and the content of /proc/iomem please?
The allocation thing is weird even though I don't think it's causing this
Created attachment 187741 [details]
output of 'lspci -vnn'
Created attachment 187751 [details]
content of /proc/iomem
Created attachment 187781 [details]
Log for the running vesa driver
Okay, this is just weird. I don't see sufficient bridge setup in lspci to see
how the 0x1_40000000 map can ever get to the VGA device. But vesa's not using
that range anyway:
Clearly I need to double-check what BARs on G80 correspond to what features, but
I suspect the mismapped one is just registers not memory, which would explain
why unaccelerated vesa works.
Does the nv driver work if you add
to the nv Driver section of xorg.conf?
Created attachment 187871 [details]
nv driver w/ NoAccel conf
Created attachment 187881 [details]
Log from nv driver w/ NoAccel
Just tested this issue with the kernel-188.8.131.52-8.fc7 build from koji, same results.
I'm told this is a system BIOS bug. IIRC the affected machine is a laptop, so
it sounds suspiciously like:
There's a patch in the latter thread but it's _really_ sketchy. Is there a BIOS
update for this machine?
Yeah it is a laptop, ASUS A8Sc.
I updated my BIOS using a biosdisk util from Dell that mdomsch gave me link to
so my bios is now v205 was 202.
Still no nv love... reading the links you provided now.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
My laptop was sent out for repairs, they updated the BIOS and this issue does
not exist in F9 now that it is back.
Thank you for helping me track it down, this bug was included as a reference
when the hardware was sent to ASuS.