Further tests and reading the nvidia 310 and 313 file that was patched for 304.6x shows that nvidia has updated the paths to include the uapi alternative, along with the old ones.
Actually the patch for 304 was not well done, since it only supports a single scenario, user with 3.7 kernel, whereas the nvidia fix supports all the kernels, including the 3.7. I'm not actually at all clear on what the issue was, but sgfxi now does look for a missing file and will link to it if it's actually gone. Note that this only runs with a full new driver install, ie, if you already had 304.64 running on an older kernel, sgfxi will just make a module and bypass the patch, so run: sgfxi -f to force it to recreate the driver install, this will also remove the driver from the other kernels but it does work. My conclusion is that actually no patch is required at all for kernel 3.7 and 310/313 drivers. 173 is not handled, and 304 works with a simple patch. :: Code :: System: Host: systest Kernel: 3.7-0.towo-siduction-686-pae i686 (32 bit) Desktop: KDE 4.8.4 Distro: sidux-20070102-d:1
Machine: Mobo: ASRock model: A770DE+ Bios: American Megatrends version: P1.70 date: 09/07/2010 CPU: Dual core AMD Athlon 64 X2 5000+ (-MCP-) clocked at 2600.00 MHz Graphics: Card: NVIDIA G86 [GeForce 8400 GS] X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@75.0hz, 1280x1024@60.0hz GLX Renderer: GeForce 8400 GS/PCIe/SSE2/3DNOW! GLX Version: 3.3.0 NVIDIA 313.09 Network: Card: Intel 82574L Gigabit Network Connection driver: e1000e Drives: HDD Total Size: 810.2GB (75.1% used) Info: Processes: 247 Uptime: 2:32 Memory: 2853.7/4047.9MB Client: Shell (bash) inxi: 1.8.24 however, depending on how kernel maintainers create their packages, that link patch may be required, and sgfxi will create it automatically. If you run sgfxi and it just builds the module, skipping the patch/extraction process, just run with -f and it should work. Back to top |
All times are GMT - 8 Hours |