I have a g210 (nva8) and kms does not work at all/no signal. I am using the latest git as of 10/20/2009. I created an mmio trace and sent it to the mmio dumps account. I did make an attempt at the voodo/ctxvals but I am not sure it really matters for this.
Created attachment 30607 [details] dmesg
Awesome, I've been wondering when one of these'd appear :) Can I get a VBIOS image from your card too please. Just grab git://people.freedesktop.org/~stuart/vbtracetool, compile, then run "./vbtracetool -w 2>vbios.rom" Thanks!
Created attachment 30609 [details] vbios
Thanks for that. I haven't quite figured out the new PLL limits table version yet, there's one piece of info our PLL algorithms depend on that I can't yet fine. In the meantime, I've attached a patch that should hardcode the same values nv uses when version 4.0 limits table is found. Could you please apply to the DRM and see how things are for you? For acceleration, you'll need the latest DRM (for ctxprog etc) and DDX (the card uses a different 3D object than the others) git.
Created attachment 30621 [details] [review] Hardcode PLL limits when v4.0 limits table found
Created attachment 30623 [details] dmesg
I tried but still no go. I did have a minor complier error (should be limit_match instead of reg it seems).
Sorry about the compile issue, I just hacked it together very quickly!! Hmm, that's all the dmesg output you see? Any chance of getting another log with "modprobe drm debug=15; modprobe nouveau modeset=1;" Thanks
Created attachment 30711 [details] dmesg_monitor_at_init_no_load Monitor turned on and I see no signal at console init. I found that the console works if the monitor is off at init. I include a dmesg for that in the next attach.
Created attachment 30712 [details] dmesg_no_monitor_at_init_load The monitor isn't on and the console shows up once I power it on.
Created attachment 31326 [details] [review] Parse PLL limits table v4.0, adjust PLL calculations for new PLL type Are you able to apply the attached patch to current git master and see if anything improves, thanks!
No go. Did you want another log?
It appears I missed a couple of bits in the patch I attached. If you update to 6169057b2992862565c513ca432b35c4df33288a, the support is in there now. It appears to work fine on my NVA8, hopefully it will for you too :)
All good now.
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.