Quake 3 OpenGL subsystem error, Wolf:ET runs fine (same engine...)
Got Fedora Core 2 installed today, with all of the available updates on up2date, latest kernel, and latest Nvidia drivers. Video card is Geforce4 ti4400 (128MB DDR). Wolfenstein: Enemy Territory is installed and running fine, Quake 3, I copied the.
Got Fedora Core 2 installed today, with all of the available updates on up2date, latest kernel, and latest Nvidia drivers.
Video card is Geforce4 ti4400 (128MB DDR). Wolfenstein: Enemy Territory is installed and running fine, Quake 3, I copied the .pk3 files accordingly, and installed the 1.32 point release as per ID instructions.
Upon running either the quake3.sh or quake3.x86 I get an OpenGL subsystem error.
Any ideas?
Thanks in advance
Edit:
Kernel version: 2.6.8-1.521
Nvidia driver version: 1.0-6111
Edit 2:
Should have googled some more; found plenty of other users talking about this too.
Some links:
http://www.nvnews.net/vbulletin/showthread.php?t=35702&page=2&pp=15
http://www.fedoraforum.org/forum/showpost.php?p=97895&postcount=6
Off to reboot now, to try it; I'll post back with results.
[Edited by adamvjackson on 2004-10-30 19:31:11]
Video card is Geforce4 ti4400 (128MB DDR). Wolfenstein: Enemy Territory is installed and running fine, Quake 3, I copied the .pk3 files accordingly, and installed the 1.32 point release as per ID instructions.
Upon running either the quake3.sh or quake3.x86 I get an OpenGL subsystem error.
Any ideas?
Thanks in advance
Edit:
Kernel version: 2.6.8-1.521
Nvidia driver version: 1.0-6111
Edit 2:
Should have googled some more; found plenty of other users talking about this too.
Some links:
http://www.nvnews.net/vbulletin/showthread.php?t=35702&page=2&pp=15
http://www.fedoraforum.org/forum/showpost.php?p=97895&postcount=6
Off to reboot now, to try it; I'll post back with results.
[Edited by adamvjackson on 2004-10-30 19:31:11]
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
OK, the fix posted above at http://wwww.nvnews.net works.
Here's the fix, thanks to LordMorgul @ nV News Forums:
Quote:Examine the file /etc/sysctl.conf
Append:
vm.legacy_va_layout =1
Here's the fix, thanks to LordMorgul @ nV News Forums:
Quote:Examine the file /etc/sysctl.conf
Append:
vm.legacy_va_layout =1
Hi adamvjackson! Sure wish I had a few fingers of good ol' Asheville "shine" right about now!
Anyway, thanks for posting the solution!
Anyway, thanks for posting the solution!