Have been having a problem getting a RivaTNT video card to work with newer kernels. Have tried gentoo-2.6.15 and vanilla-2.6.14 kernels. Because this is a legacy card, support has stopped on the newer drivers. So anyone using them will have to use older nvidia-kernels. Have tried 6629 and 7174 (which I believe is where support stops for RivaTNT). Errors get: nvidia: Unknown symbol register_ioctl32_conversion nvidia: Unknown symbol unregister_ioctl32_conversion Long story short. Zander's patch takes care of the problem. Working perfectly now. I have it up in the 2.6.14 vanilla kernel right now on the TNT card. Didn't even have to modify my kernel or xorg.conf from using my GeForce6800. Without this patch am not able to start X with the TNT card. Modified the ebuild to apply this patch and emerged fine. Without the patch get the errors listed above. Working on this for someone else still using the old video card on a amd64 system. Now I can put my 6800 back in. :)
Created attachment 76964 [details, diff] Zander's patch for the ioctl32_conversion problem.
Hmmm, it didn't take my additional comments when posting. Attached Zander's patch here, found it at http://www.nvnews.net/vbulletin/showthread.php?p=726656 2nd post on the thread. Please apply this patch.
Already done... *** This bug has been marked as a duplicate of 113466 ***
Sorry to disagree, but this isn't a duplicate of that bug. 1) I didn't see 6629-r5 and tried 6629-r4, r5 has the patch r4 doesn't. If I had tried r5 wouldn't have had the problem. But also wouldn't have found an error with the ebuilds. 2) The problem is the patch is only has only been applied to 6629-r5 and not 7174. Here is what found in 6629-r5 <snip> # Yes this is the wrong version but it's needed to fix problems with # 6629 and 7174 is no longer in portage. epatch ${FILESDIR}/${PV}/NVIDIA_kernel-1.0-7174-1296092.diff <snip> 7174 is still in portage. Still supports legacy cards (I am on a RivaTNT right now). Just to check it hadn't been slipped in on me. I emerge sync'd this morning and 7174's ebuild is still the same. And yes ebuild is still in portage and I just did a fetchonly on it to make sure. In conclusion the patch still needs to be applied to nvidia-kernel-1.0.7174 . Thanks
To be amiable I tried the nvidia-kernel-1.0.6629-r5 and glx 6629-r7. That did not work out at all. Thought my video card went bad. Login screen corrupted, but able to login. Desktop background and icons fine, but taskbar and any app started, was corrupted video,... So put back the Patched 7174 kernel and matching glx. Video card not bad. Back up and working. I did try some other stuff, but just couldn't get the patched 6629 to work right. 7174 is working fine with no changes. Just emerged it after editing the ebuild. The only other problem have with 7174 and had with 6629 was no nvidia devices created. Still working on the udev and baselayout didn't help. Have to mknod in local.start or do it manually. ?? Cause using a amd64 with an old card ?? Don't know. But do need 7174 patched. That is what the patch was created for: 7174
You need to reopen the bug, otherwise noone will probably ever notice again.
Sorry, didn't realize I had the authority to do so. Thanks.
Just applied the patch on another system using the 7174 cause was getting the same errors. Works like a charm now. I would correct the ebuild, but there are several ways to do it. Make a new FILES folder for 7174 and put the patch, or leave it where is and apply the patch. It would be easier to make a 7174 folder for it, but I can't do that with just an ebuild.
nvidia-kernel-1.0.7174-r1.ebuild now available. All patches from Zander included: http://www.nvnews.net/vbulletin/showthread.php?p=726656 http://www.nvnews.net/vbulletin/showthread.php?t=57990 Let me know how it works out for you.
Just tried the r2 version of the ebuild and worked perfect. Wasn't able to test the box out earlier. Thanks.
