Jump to content
Compatible Support Forums
Sign in to follow this  
the_bard

Radeon 9000 Pro Driver Seg Fault

Recommended Posts

Can anybody out there offer me any help?

 

I've upgraded my video card to a "Built-By-ATI" Radeon 9000 Pro. Using ATI's 2.5.1 drivers, I consistently receive segmentation faults in both Unreal Tournament and FlightGear.

 

In Unreal Tournament, I could load the game without a problem... however, on the first turn to the left on the introductory movie, the ATI driver would segfault. If I skipped the movie, I could play the game for a seemingly random amount of time before it segfaulted.

 

I managed to work around the UT problem by changing the renderer from

SDL to OpenGL.

 

However, I can't seem to get around the issue with FlightGear. Whenever I fly at night, the driver immediately segfaults, causing FG to die. During the day, the driver seems to handle it fine... in fact, I'm quite pleased with its performance.

 

I managed to run gdb on it, backtrace it... and receive the following output.

 

... *Lots of Loading going on*...

Loading tile /usr/games/lib/FlightGear/Scenery/w130n30/w123n37/942034

token = OBJECT_BASE name = 942034.btg

(no debugging symbols found)...

Program received signal SIGSEGV, Segmentation fault.

[switching to Thread 16384 (LWP 11386)]

0x47da6a0f in s12896 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so

(gdb) bt

#0 0x47da6a0f in s12896 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so

#1 0x3e8bd554 in ?? ()

 

I have absolutely no clue what this means, or what I can do about it... or if I simply have to wait until ATI releases a fix (there seems to be no official ATI support forum... just their bug report system). A week or so of searching on google/linux didn't help at all... seems like nobody else is running into this problem.

 

I've tried upgrading to XFree 4.2.99, but upon starting x, or automatically configuring it, it seems like my character set becomes corrupted... suddenly the screen is filled with odd characters that look like random dots more than anything else. The system still responds, however... I can type in commands, watch the characters change on the screen, and my commands execute correctly. I don't know how to fix that can of worms...

so I returned to 4.2.1

 

I've also tried installing the GATOS drivers, with no go...

 

By the way, I'm running Gentoo, upgraded to 1.4rc2, with the vanilla-linux-2.4.20 kernel (stock 2.4.20 kernel sources).

 

Can anybody offer any advice?

 

Update: ;( :x

I ran 'strace' on it too... set the output to a log file. The tail end of it is here:

open("/usr/games/lib/FlightGear/Scenery/w130n30/w123n37/942034.btg", O_RDONLY) = -1 ENOENT (No such file or directory)

open("/usr/games/lib/FlightGear/Scenery/w130n30/w123n37/942034.btg.gz", O_RDONLY) = 10

fstat64(10, {st_mode=S_IFREG|0640, st_size=8298, ...}) = 0

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x52195000

read(10, "\37\213\10\0\0\0\0\0\0\3]Y\t\\\216\313\367?\317C\310\232"..., 16384) = 8298

read(10, "", 4096) = 0

_llseek(10, 0, [8298], SEEK_CUR) = 0

read(10, "", 16384) = 0

close(10) = 0

munmap(0x52195000, 4096) = 0

close(9) = 0

munmap(0x52194000, 4096) = 0

ioctl(4, 0x4008642a, 0xbffff188) = 0

ioctl(4, 0x4008642a, 0xbffff038) = 0

--- SIGSEGV (Segmentation fault) ---

+++ killed by SIGSEGV +++

 

Once again, I have very little clue what's going on... and what I do know is probably wrong laugh . I have the entire log file, but it's rather large... if you need it, drop me an address, and I'll email it to you.

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×