Re: Quake1/Quake3 on Sarge
Hey all, I am truly at a loss here, I am not sure where to go... I havent
hosed anything as of yet, but still can not get the nvidia module to build
and install.
I have pulled the kernel-source-2.4.27 with apt-get and installed it. Killed
the xserver(/etc/init.d/gdm stop) and tried build the module again, it still
fails looking for my kernel-source, so I hunted around and founda tar.bz2 of
it extracted it updatedb and reboot. I then used the
--kernel-source-path /path/to/kernel/source behind the sh NVIDIA.... and
still it fails looking for the kernel source.
What other info do you need?
On Sunday March 13 2005 9:21 am, Bill Day wrote:
> I am attempting to install quake1 & quake3 on my debian sarge system:
> 2.4.27-1-386
> nVidia eGeForce MX4000 64MB AGP 8X
> Cirrus Logic Crystal CS4281 PCI Audio
> XFree86 4.3.0.1
>
> I have working sound, I have seen my basic quakeforge install function(not
> used online as of yet). I began my quake3 install following the howto from
> http://www.mepislovers.com/guide/quake/Quake-3-Arena-Install-Part-1.html
> http://www.mepislovers.com/guide/quake/Quake-3-Arena-Install-Part-2.html
>
> On Part 2, I get to the point of running the shell script "sh quake3" from
> console or by clicking the icon from a file manager I get same results
> either way(konsole output):
>
> bill@beast:~/quake3$ sh quake3
> Q3 1.32b linux-i386 Nov 14 2002
> ----- FS_Startup -----
> Current search path:
> /home/bill/.q3a/baseq3
> /home/bill/quake3/baseq3/pak8.pk3 (9 files)
> /home/bill/quake3/baseq3/pak7.pk3 (4 files)
> /home/bill/quake3/baseq3/pak6.pk3 (64 files)
> /home/bill/quake3/baseq3/pak5.pk3 (7 files)
> /home/bill/quake3/baseq3/pak4.pk3 (272 files)
> /home/bill/quake3/baseq3/pak3.pk3 (4 files)
> /home/bill/quake3/baseq3/pak2.pk3 (148 files)
> /home/bill/quake3/baseq3/pak1.pk3 (26 files)
> /home/bill/quake3/baseq3/PAK0.PK3 (3539 files)
> /home/bill/quake3/baseq3
> ./quake3.x86/baseq3
>
> ----------------------
> 4073 files in pk3 files
> execing default.cfg
> couldn't exec q3config.cfg
> couldn't exec autoexec.cfg
> Hunk_Clear: reset the hunk ok
>
> ------- Input Initialization -------
> Joystick is not active.
> ------------------------------------
> ----- Client Initialization -----
> ----- Initializing Renderer ----
> -------------------------------
> ----- Client Initialization Complete -----
> ----- R_Init -----
> ...loading libGL.so.1: Initializing OpenGL display
> ...setting mode 3: 640 480
> Using XFree86-VidModeExtension Version 2.2
> XF86DGA Mouse (Version 2.0) initialized
> XFree86-VidModeExtension Activated at 640x480
> Using 8/8/8 Color bits, 16 depth, 0 stencil display.
> Xlib: extension "XFree86-DRI" missing on display ":0.0".
> GL_RENDERER: Mesa GLX Indirect
>
>
> ***********************************************************
> You are using software Mesa (no hardware acceleration)!
> Driver DLL used: libGL.so.1
> If this is intentional, add
> "+set r_allowSoftwareGL 1"
> to the command line when starting the game.
> ***********************************************************
> ...WARNING: could not set the given mode (3)
> ----- CL_Shutdown -----
> RE_Shutdown( 1 )
> -----------------------
> ----- CL_Shutdown -----
> -----------------------
> Sys_Error: GLimp_Init() - could not load OpenGL subsystem
>
> What happens here is the screen acts like it is opening up and changing
> video modes blanks and drops back to where I was. If I run the shell
> script with this line after it, "sh quake3 +set r_allowSoftwareGL 1" I end
> up seeing a a "blown" up corner of my desktop with nothing I can do except
> kill the xserver with CTRL + ALT + BKSPC
>
> Are there any suggestions at where I should start looking on this? I
> really need my Q3 Fortress sniper fix....
>
> TIA,
--
Bill Day
"A rich man isn't always wealthy, he just has all the love he can give and
ever wanted.."
http://counter.li.org #384146 284016
Reply to: