ATI crashes and changes resolution

Screen resolution, 3D Acceleration, nVidia, ATI
Forum rules
Before you post please read this
Post Reply
nesredep
Level 1
Level 1
Posts: 8
Joined: Tue Dec 28, 2010 6:48 am

ATI crashes and changes resolution

Post by nesredep »

I tend to use Tux Racer (or whatever name it goes by) as a quick test of video. Ran into a strange thing on LMDE.

Hardware is T30 Thinkpad, Radeon 7500, screen resolution is 1024x768.

When I start Tux Racer, everything looks fine, music plays, menu works. However, when I initiate a race, it crashes, blank screen for a moment, and suddenly my system is now set to 800x600.

If I run in a terminal, I see this:

%%% etracer warning: Attempt to bind to Texture unloaded texture: `b-herring_run_icon'

drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info.

Checking dmesg doesn't tell me anything:

[ 193.838254] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

Not a huge issue for me, but if anybody knows what's going on, or if there's an easy fix, I'd appreciate it.

John

nesredep
Level 1
Level 1
Posts: 8
Joined: Tue Dec 28, 2010 6:48 am

Re: ATI crashes and changes resolution

Post by nesredep »

nesredep wrote:I tend to use Tux Racer (or whatever name it goes by) as a quick test of video. Ran into a strange thing on LMDE.

Hardware is T30 Thinkpad, Radeon 7500, screen resolution is 1024x768.

When I start Tux Racer, everything looks fine, music plays, menu works. However, when I initiate a race, it crashes, blank screen for a moment, and suddenly my system is now set to 800x600.

If I run in a terminal, I see this:

%%% etracer warning: Attempt to bind to Texture unloaded texture: `b-herring_run_icon'

drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info.

Checking dmesg doesn't tell me anything:

[ 193.838254] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

Not a huge issue for me, but if anybody knows what's going on, or if there's an easy fix, I'd appreciate it.

John
If anybody is interested, bumping the kernel up to 2.6.37 fixed the problem.

Post Reply

Return to “Graphics Cards & Monitors”