| View previous topic :: View next topic |
| Author |
Message |
Rork
n00b
Joined: 03 Aug 2004
Posts: 4
|
 Posted: Tue Aug 03, 2004 12:50 am Post subject: fglrx spamming the log |
 |
|
Hi,
I'm trying to get UT2004 to run but I'm having problems with fglrx.
My rig is a XP 2500+ on an nForce2 motherboard with a Radeon 9700 Pro and I'm using gentoo 2004.2, 2.6 kernel, xorg, and ati-drivers. Everything is setup according to this FAQ.
"glxinfo | grep direct" does report that hardware acceleration is enabled.
UT2004 does start and run, but at 5 FPS... Not really playable! I looked at my system log (/var/log/messages) and found out that fglrx is logging loads of messages there:
| Code: | Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] context 1 - use_count up to 1
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] got lock
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] switch context to 1...
Aug 3 02:27:30 sister-ray [fglrx:_r6x_switch_context] 0 => 1
Aug 3 02:27:30 sister-ray [fglrx:_r6x_switch_context] no context switch neccessary (b)
Aug 3 02:27:30 sister-ray [fglrx:_r6x_WaitNotBusy]
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] context 1 - use_count down to 0
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] context 1 has lock
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock] 0x00000001 got lock -> set lock.priv = 0xf5f7b980
Aug 3 02:27:30 sister-ray [fglrx:firegl_ioctl] ioctl finished, retcode = 0 |
And it goes on and on and on... They look more like debug messages rather than error messages, but they're annoying nonetheless because of their sheer amount (even when UT is not running).
Any help would be greatly appreciated. |
|
| Back to top |
|
 |
rickvernam
Guru
Joined: 09 Jul 2004
Posts: 313
|
| Posted: Tue Feb 07, 2006 4:30 pm Post subject: Re: fglrx spamming the log |
|
|
| Rork wrote: | Hi,
I'm trying to get UT2004 to run but I'm having problems with fglrx.
My rig is a XP 2500+ on an nForce2 motherboard with a Radeon 9700 Pro and I'm using gentoo 2004.2, 2.6 kernel, xorg, and ati-drivers. Everything is setup according to this FAQ.
"glxinfo | grep direct" does report that hardware acceleration is enabled.
UT2004 does start and run, but at 5 FPS... Not really playable! I looked at my system log (/var/log/messages) and found out that fglrx is logging loads of messages there:
| Code: | Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] context 1 - use_count up to 1
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] got lock
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] switch context to 1...
Aug 3 02:27:30 sister-ray [fglrx:_r6x_switch_context] 0 => 1
Aug 3 02:27:30 sister-ray [fglrx:_r6x_switch_context] no context switch neccessary (b)
Aug 3 02:27:30 sister-ray [fglrx:_r6x_WaitNotBusy]
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] context 1 - use_count down to 0
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock_device] context 1 has lock
Aug 3 02:27:30 sister-ray [fglrx:firegl_lock] 0x00000001 got lock -> set lock.priv = 0xf5f7b980
Aug 3 02:27:30 sister-ray [fglrx:firegl_ioctl] ioctl finished, retcode = 0 |
And it goes on and on and on... They look more like debug messages rather than error messages, but they're annoying nonetheless because of their sheer amount (even when UT is not running).
Any help would be greatly appreciated. |
ever get this to stop? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
