Red Hat Bugzilla – Bug 480541
nv driver fails to start X on GeForce 7025/7050/7150
Last modified: 2018-04-11 04:15:10 EDT
Description of problem:
x fails to start on a system with Geforce 7025 integrated chipset. Nouveau works fine.
Version-Release number of selected component (if applicable):
Everytime you try to use the nv driver.
Steps to Reproduce:
1. Boot live CD or change driver setting on installed system.
x to start as normal.
Nouveau works fine. Looking at the log, it says that the device is unsupported by the driver, so maybe Fedora should default to Nouveau for this chipset?
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
And could we get the same set when using nouveau driver as well, please?
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 329441 [details]
xorg.conf with nouveau driver
Created attachment 329442 [details]
xorg.log with nouveau driver
Created attachment 329443 [details]
xorg.log with nv driver
Attached requested files. I presume no xorg.conf for nv driver as it occurred after first installation, which no longer uses that file? I could generate one using the system-config-display utility if that would be useful.
I'd be interested to know if nv simply works on this chipset by adding a case for 0x0530 to the list in nv_driver.c function NVIsSupported().
As far as I'm aware we didn't need to change anything in nouveau (aside from some chipset-specific code that is irrelevant to nv) to support this series of chips, so it could simple be a case of missing pciids for this series.
Are you able to test a new RPM for me? This contains a patch to nv which tells it about all the cards of your series, hopefully this'll be all that's required to get nv running on these chips.
The RPM is here:
Could you give me some advice on how to install the RPM? When I try, it conflicts with the currently installed package, and if I try to remove it fails because xorg-x11-drivers depends on it.
Simple question, I'm sure, but will be more than happy to help when I know how :)
Thanks for your work so far,
It should install with "rpm -ivh --force <rpm filename>".
Tried the new RPM, it didn't work :(
When I changed the driver setting and reset X, it failed to come back at all - couldn't even switch virtual terminals and there was no blinking cursor. Had to do a hard reboot to get anything back, and then boot to run level 3 (apparently xdriver= on the grub boot doesn't work any more?)
I've attached the xorg.log from the failed attempt.
Created attachment 329787 [details]
Patched RPM xorg.log
Ok, i know where that problem is and have came up with a fix. Unfortunately i won't have a real net connection until i get back to brisbane on monday, so won't be able to build you a new rpm until then. Thanks for testing :)
New RPM is available here: http://koji.fedoraproject.org/scratch/bskeggs/task_1082067/xorg-x11-drv-nv-2.1.12-6.fc10.i386.rpm
Just tested the latest RPM and although it didn't leave me with just a blank screen, my monitor displayed a sign saying "out of range" and the virtual terminals were extremely garbled with white marks all over - couldn't actually make out the text but they were functional. Had to reboot into run level 3 again and this time edit xorg.conf by hand because system-config-display wouldn't work (it tried to start with nv I think).
Attaching the log again.
Hope it helps,
Created attachment 329980 [details]
Second new RPM xorg.log
You definitely installed the new RPM? The crash is identical to the previous one. It's possible the crash was in a different place to where I suspected however. If you're sure you used the new RPM I'll come up with a patch to provide more info as to where the crash is happening. Thanks again!
Well, I just re-installed, and provided the link is correct I'm certain I installed the new RPM. Got the same results as before. The crash actually performs a little differently to the old one from a user perspective. I suppose it's possible I attached the wrong xorg.log... I just grabbed Xorg.1.log the next time I booted up with a running X - looked to me like Xorg.0.log was the log for the most recent successful attempt.
(In reply to comment #19)
> next time I booted up with a running X - looked to me like Xorg.0.log was the
> log for the most recent successful attempt.
Check their timestamps with ls -l /var/log/Xorg.*.log, but you don't do anything bad when you attach all of them.
*** Bug 478527 has been marked as a duplicate of this bug. ***
*** Bug 465634 has been marked as a duplicate of this bug. ***
*** Bug 471365 has been marked as a duplicate of this bug. ***
*** Bug 468278 has been marked as a duplicate of this bug. ***
*** Bug 473301 has been marked as a duplicate of this bug. ***
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. 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 '11'.
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 11'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 11 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 to the applicable version. 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.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.