Bug 578965
| Summary: | [NV4e] nouveau driver does not work with geforce 6100 | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | shmuel siegel <fedora> | ||||||||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 14 | CC: | airlied, awilliam, bskeggs, fdor6, gasmith, mcepl | ||||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | [cat:modesetting] | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | 525905 | Environment: | |||||||||||||
| Last Closed: | 2012-08-16 17:37:12 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 507684 | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
shmuel siegel
2010-04-01 22:02:20 UTC
GPU lockup is being detected with f13 beta rc3 with a minimal install (no X) 2.6.33.1-24 still has this problem. In addition, after switching to text mode, udev hangs. Using athlon 3800+ and geforce 6100 Can we get your kernel and X logs? Can you also test with the latest kernel - http://koji.fedoraproject.org/koji/buildinfo?buildID=166151 ? Thanks. As I said, minimal install (no X, therefore no X logs). Is there a way for me to get logs from a system that hangs in udev? not particularly easily. i'm still not entirely clear what the bug is here? it's titled 'nouveau driver does not work', then you talk about 'GPU lockup', then udev hang 'after switching to text mode' (but if this is a minimal install it's *always* text mode)? confused. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 407321 [details]
xorg log file for pure noise on screen
failure for kernel 2.6.33.2-41.fc13.x86_64
xorg-x11-drv-nouveau-0.0.16-3.20100305git6b8b157.fc13.x86_64
xorg-x11-server-Xorg-1.8.0-4.fc13.x86_64
My laptop with the nvidia GPU died, I'm going to remove myself from this bug, I can no longer help. I am receiving this message many times in dmesg when started with nomodeset. Is it relevant to my failure to bring up x on geforce 6100? [drm] nouveau 0000:00:05.0: called without init nomodeset is not intended to work any longer in F13. now i am getting these dnesg messages over and over [drm] nouveau 0000:00:05.0: PFIFO_DMA_PUSHER - Ch 0 [drm] nouveau 0000:00:05.0: PFIFO_DMA_PUSHER - Ch 1 [drm] nouveau 0000:00:05.0: PFIFO_DMA_PUSHER - Ch 2 for kernel 2.6.33.2-57.fc13.x86_64 x server xorg-x11-server 1.8.0-6.fc13 [ 20.353] (--) PCI:*(0:0:5:0) 10de:0242:1462:7252 nVidia Corporation C51G [GeForce 6100] rev 162, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfc000000/16777216, BIOS @ 0x????????/131072 [ 20.398] (II) LoadModule: "nouveau" [ 20.400] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 20.400] (II) Module nouveau: vendor="X.Org Foundation" [ 20.400] compiled for 1.7.99.901, module version = 0.0.15 [ 20.401] Module class: X.Org Video Driver [ 20.401] ABI class: X.Org Video Driver, version 7.0 kernel 73 and the april 28 version of the nouveau driver do not solve this problem. Is there anything that I can provide to help debugging this? This machine work in f12 prior to march. This bug was discussed at the 2010/04/30 blocker review meeting. It looks like this is a single-system (may be single-adapter) bug; there's no duplicate reports we can find. We don't usually consider such issues blockers, unfortunately, as it's not really possible to fix every single such issue and still stick to a plausible release schedule. Sorry about this. If Ben does manage to get a fairly safe fix available by Tuesday, we can consider taking it for the final release. Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers nomodeset is working now. I have a working X nomodeset is causing you to get the vesa driver instead in all likelihood, nouveau no longer supports nomodeset. The bug is still in fedora 14. I've tested 3 ways: 1) Without xorg.conf: Vesa driver is automatically selected. Works, but video is slow. I can't change to my prefered hand-made resolution (tested with "xrandr" command). 2) With nouveau driver forced: Doesn't work (X doesn't start). 3) With nv driver forced: Works, but video is even worse than with the first way (vesa driver). Video slow. I can't change to my prefered hand-made resolution. For 2) and 3) ways, I've used a minimal xorg.conf file. For 2) way: Section "Device" Identifier "n" Driver "nouveau" EndSection For 3) way: Section "Device" Identifier "n" Driver "nv" EndSection I'm attaching xorg log files for every way. I had to add "nomodeset" to kernel booting parameters. Without "nomodeset", the kernel doesn't boot (it just hangs up). Am I doing something wrong? Or is this bug still unfixed? (P.S. Please change the bug Status from "NEW" to "CONFIRMED" or something. Also, update bug Version from "13" to "14") Created attachment 502492 [details]
Xorg.log - No xorg.conf
Created attachment 502493 [details]
Xorg.log - Nouveau forced
Created attachment 502494 [details]
Xorg.log - nv forced
Created attachment 502496 [details]
Xorg.log - No xorg.conf
Oops, I atached the log file for other graphic card.
This is the good one.
Thanks for the update. If the vesa driver is selected by default, it sounds like the X devs are aware of this problem and blacklisting the adapter to avoid it... Have you had a chance to test with F15 yet? This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I'll probably upgrade to F15 next days, I'll tell you. Thanks. Fixed in Fedora 15. I've: - upgraded to Fedora 15. - removed "nomodeset" from kernel booting parameters. - forced "nouveau" driver in xorg conf. A minor problem: - While booting, the graphical boot is shown for some seconds (~2 sec.). - Then, the screen goes into black (my monitor goes into power saving mode) until the end of the booting process. - Then, the screen is changed from black to the graphical login (gdm). - Finally, I enter username and password, kde is loaded correctly (screen doesn't change its mode nor goes into black), and I can work perfectly with all apps. I know the graphical booting is complex, so I consider the black screen problem as minor. Hope it will be fixed. Thanks Reporter, could you please confirm the comment 23. Has this been fixed in F15? Thank you Sorry, I no longer have the relevant hardware. It seems that the only other person who was bothered by this problem is happy now. So feel free to close the bug. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |