ports/54209: FBSD-1.0-4365 nVidia driver (port) locks up in Wolfenstein Enemy Territory

[jimd_NOSPAM at siu.edu]

>Number:         54209
>Category:       ports
>Synopsis:       FBSD-1.0-4365 nVidia driver (port) locks up in Wolfenstein Enemy Territory
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 08 01:30:09 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     none
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
System: FreeBSD 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Tue Jun 24 22:44:46 CDT 2003 x at freebsd2.localnet10:/usr/src/sys/i386/compile/XSYSTEM i386

XFree86-Server-4.3.0_8
XFree86-clients-4.3.0_2
XFree86-libraries-4.3.0_5
linux_base-7.1_5

ET 2.55 linux-i386 May 27 2003 (under FreeBSD-1.0-3203 nvidia driver):
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: GeForce4 Ti 4600/PCI/SSE2
GL_VERSION: 1.3.1 NVIDIA 32.03


/etc/sysctl.conf:
hw.nvidia.registry.EnableAGPSBA=1
hw.nvidia.registry.EnableAGPFW=1

	
>Description:
	Using the FreeBSD-1.0-4265 nvidia driver.

	Normal video operations don't present any problems, so far. Wolfenstien Enemy
	Territory basic video operations don't present any problems. When playing a
	game and the player's character is killed, the screen locks up for at least
	as long as the "kill recycle time" - sometimes longer. The screen graphic is
	frozen but the sound may be repeating through a small segment (such as beeping).

	In most cases, game action and video operation is restored once the character
	has been "restored". Sometimes the game action and video display does not
	"reset" and X-windows must be aborted. Occassionally, the system will have to
	be "cold-booted" when you cannot "break out of" X.

	Restoring the previous FreeBSD-1.0-3203 nvidia driver restores normal Enemy
	Territory function when the character is "killed". Only one video lockup was
	encountered after going from 3203 to 4265 and back to 3203.

	Previous usage of Enemy Territory under 3203 did not exhibit any such behaviour.
	
>How-To-Repeat:
	
>Fix:

	



>Release-Note:
>Audit-Trail:
>Unformatted: