Summary: | [NVF0] Kernel/Driver fails to initialize acceleration on GTX Titan | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Vladimir <bobahu4> | ||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | ||||||||
Version: | unspecified | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Vladimir
2013-10-09 18:12:53 UTC
You need to mmiotrace the blob and get the graph firmware. See http://nouveau.freedesktop.org/wiki/NVC0_Firmware/ (up to "Video Firmware", which you don't need to worry about). Once you get that, stick the files in /lib/firmware/nouveau and boot with nouveau.config=NvGrUseFW=1,PGRAPH=1 . Built-in firmware is being worked on, afaik, but currently incomplete. There is preliminary support you could use if you like, see drivers/gpu/drm/nouveau/core/engine/graph/nvf0.c: .fecs.ucode = 0 ? &nvf0_graph_fecs_ucode : NULL, Just change that to 1 ? instead of 0 ?, but I have no idea if it's even expected to work. I'm going to leave this bug open until NVF0 is supported with open firmware. Thanks, I did that, and after news about gtx780 being supported back in july I hoped it will work. But it seems textures coordinates are messed up, at least in kde. https://www.dropbox.com/s/wyvyaiklbi5jqhn/2013-10-19%2000.06.53.jpg Unity is much worse https://www.dropbox.com/s/vxxk8gxlvcqzlz2/2013-10-19%2000.04.46.jpg Which "that" did you do? BTW, the news item on the page about NVF0 support might be a bit misleading. It does presently still require mmiotrace'd firmware. Created attachment 87845 [details]
glxgears
Created attachment 87846 [details]
cube2
Sorry it wasn't clear. I've used mmiotrace. without composited enviroment it looks better. glxgears has same bug as with gtx650. cube2 has same bug as kde sshot above, texture coordinates are wrong. I assume you're running mesa 9.2 or later? Looks like preliminary support went in with commit c29c6b2b2e65f73c75c70daae1d2d32e53964120 Author: Ben Skeggs <bskeggs@redhat.com> Date: Fri May 17 14:48:15 2013 +1000 nvc0: enable very initial support for nvf0 (GK110) Shaders need a lot of work still. Basic stuff generally works, so this is basically just fine for gnome-shell, OA etc at this point. Signed-off-by: Ben Skeggs <bskeggs@redhat.com> Just glanced at nv50_ir_emit_gk110.cpp, it's got TODO's all over, esp in the texture stuff. If you're interested in helping fix this, find piglit tests that exercise the relevant functionality, and run them with the blob and valgrind-mmt. This should provide the data required to fill in some of the blanks. Join in on #nouveau @ freenode if you want to help out/get some pointers/etc. Long story short, don't expect 3d to work correctly on gk110. 2d accel with the mmiotrace'd firmware is all that's supported right now, it seems. I have a branch where I've started fixing some stuff for gk110/gk208... it's largely untested, feel free to give it a shot: https://github.com/imirkin/mesa/commits/gk110 Among other things, a floating point subtract was treated as an add, which couldn't have helped. The latest kernel (3.14-rcX) should provide nouveau firmware for nvf0, so you shouldn't need the blob fw anymore. I've checked in a bunch of fixes for GK110, should be available now in mesa 10.2-rc1. Also, 3.14+ supply firmware, so you don't have to use the blob one. I'm closing this bug. If you have further issues, feel free to create a new bug with specifics. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.