Bug 812964
Summary: | nouveau driver is unable to provide acceleration on GeForce GTX 460 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | joshua | ||||||||||||
Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 16 | CC: | airlied, ajax, bskeggs, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, maxamillion, otaylor, samkraju, walters | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | Unspecified | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2013-02-13 20:30:53 UTC | Type: | Bug | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
joshua
2012-04-16 16:44:58 UTC
There is a newer version of Nvidia Geforce GTX 460 based on GF114 (same branch of GTX 560). nouveau driver did not recognize this videocard leading to a black screen while attempting to use the installer. I first had to use vesa driver then nvidia binary from rpmfusion to check the name: $ cat /proc/driver/nvidia/gpus/0/information Model: GeForce GTX 460 v2 IRQ: 19 GPU UUID: GPU-f8a89220-46be-f68c-51c9-180b628a4bcf Video BIOS: 70.24.25.00.62 Bus Type: PCI-E DMA Size: 40 bits DMA Mask: 0xffffffffff Bus Location: 0000:02.00.0 Would this info be helpful for my card, or is the lspci output that I provided enough? It should be (In reply to comment #2) > Would this info be helpful for my card, or is the lspci output that I provided > enough? Yes it should be enough. Your card is from GF104 family. I'd like to see dmesg output from trying to use nouveau on this board please. Created attachment 577926 [details]
Xorg.9.log
Here is attached Xorg.log. Attempting to run with Nouveau driver resulted a black screen. Only way to run Nvidia Geforce GTX 460 v2 is either VESA or binary Nvidia provided by rpmfusion which I use.
lspci gives this result:
02:00.0 VGA compatible controller: nVidia Corporation Device 1205 (rev a1)
It looks like nouveau was confused with this newer GTX 460 v2 based on GTX 560.
Created attachment 578088 [details]
output from 'dmesg | egrep -i "vga|nouveau|drm|nvidia"'
Note that my video card is exactly this: EVGA 02G-P3-1387-KR GeForce GTX 460 2Win (Fermi) 2GB 512-bit GDDR5 PCI Express 2.0 x16 HDCP Ready Video Card or more succinctly: http://www.newegg.com/Product/Product.aspx?Item=N82E16814130626 (In reply to comment #7) > Note that my video card is exactly this: > > EVGA 02G-P3-1387-KR GeForce GTX 460 2Win (Fermi) 2GB 512-bit GDDR5 PCI Express > 2.0 x16 HDCP Ready Video Card > > or more succinctly: > > http://www.newegg.com/Product/Product.aspx?Item=N82E16814130626 Basically a dual Geforce GTX 460 designed by EVGA. Ben, should I open another bug report? Although the title mention Geforce GTX 460 and I have similar problem, the architectures are different from GF104 to GF114. (In reply to comment #6) > Created attachment 578088 [details] > output from 'dmesg | egrep -i "vga|nouveau|drm|nvidia"' My immediate (strong) suspicion is there's not enough memory bandwidth available at default clocks to run the 2560x1600 display, hence the black screen. Ok, but my screen isn't going blank. Luya's is per comment #1, but mine isn't doing that whatsoever. The output works just fine... but Gnome reports that not enough acceleration exists to use it's "full experience" desktop. When I install the kmod-nvidia drivers, Gnome is happy... when I use nouveau, it isn't. (In reply to comment #11) > Ok, but my screen isn't going blank. Luya's is per comment #1, but mine isn't > doing that whatsoever. The output works just fine... but Gnome reports that > not enough acceleration exists to use it's "full experience" desktop. > > When I install the kmod-nvidia drivers, Gnome is happy... when I use nouveau, > it isn't. Okay, right. I got a bit confused. These are two completely different issues. Nouveau *should* be able to manage acceleration just fine on this chipset. Can you post me your X log, glxinfo output, and your "LIBGL_DEBUG=verbose glxgears" output too please? Interestingly I see output in your dmesg that would indicate that something's used the 3D driver (the PMFB_SUBP messages are a different, mostly harmless, "bug" triggered by it)... So I really don't know why gnome-shell would be bitching about it.. Created attachment 579682 [details]
output from "LIBGL_DEBUG=verbose glxgears"
Created attachment 579683 [details]
glxinfo
Created attachment 579684 [details]
Xorg log
Requested info attached Thanks! Okay, I'm still not seeing whatsoever why gnome-shell is giving you fallback mode.. The 3D driver appears to be functioning correctly to me. From fallback mode, what do you see if you run "gnome-shell --replace" from a terminal? Wow... just that command takes me to the full-experience version of the GNOME3 desktop. Here is the output: $ gnome-shell --replace Window manager warning: GConf key '/apps/metacity/general/action_double_click_titlebar' is set to an invalid value Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. (gnome-shell:10417): folks-DEBUG: individual-aggregator.vala:310: Setting primary store IDs to defaults. (gnome-shell:10417): folks-DEBUG: individual-aggregator.vala:338: Primary store IDs are 'eds' and 'system'. JS LOG: ibus-daemon is not running JS ERROR: !!! WARNING: 'assignment to undeclared variable type' JS ERROR: !!! WARNING: file '/usr/share/gnome-shell/extensions/temperature@xtranophilist/extension.js' line 213 exception 0 number 156 JS ERROR: !!! WARNING: 'assignment to undeclared variable r' JS ERROR: !!! WARNING: file '/usr/share/gnome-shell/extensions/temperature@xtranophilist/extension.js' line 325 exception 0 number 156 Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject Window manager warning: Log level 16: Error registering polkit authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject (polkit-error-quark 0) JS LOG: GNOME Shell started at Wed Apr 25 2012 17:16:07 GMT-0400 (EDT) (gnome-shell:10417): libebook-WARNING **: e_book_client_new: Cannot get book from factory: Invalid source (gnome-shell:10417): libebook-WARNING **: e_book_client_new: Cannot get book from factory: Invalid source (gnome-shell:10417): folks-WARNING **: Error preparing persona store 'eds:1320795985.15241.1@f16-laptop': Couldn't open address book ‘1320795985.15241.1@f16-laptop’: Invalid source (gnome-shell:10417): folks-WARNING **: Error preparing persona store 'eds:1320795985.15241.4@f16-laptop': Couldn't open address book ‘1320795985.15241.4@f16-laptop’: Invalid source Window manager warning: Log level 16: fetch_connections_done: error fetching connections: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.. Window manager warning: Log level 16: _nm_remote_settings_ensure_inited: (NMRemoteSettings) error initializing: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details. JS LOG: NetworkManager is not running, hiding... I assume this means that this is a Gnome bug, and not a kernel/video bug? Either that, or a configuration issue of some kind on your end. Either way, this isn't a Nouveau bug. What does: $ /usr/libexec/gnome-session-check-accelerated-helper && echo "acceleration found" show? Yes, it seems to think I have acceleration, both before and after I do a "gnome-shell --replace". What could cause gnome to start in deprecated mode like it does for me? This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" 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 Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |