View previous topic :: View next topic |
Author |
Message |
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Tue Sep 10, 2002 5:55 pm Post subject: Starting XFree86 4.2.1 fails with unresolved symbols... |
|
|
Hi All!
I have just finished emerging X 4.2.1 on my Dell with an ATI 3D Rage Pro card and when I try to start X after rebooting, I get the following errors:
(II) ATI(0): Using Block 0 MMIO aperture at 0xFCFFF400.
(II) ATI(0): Using Block 1 MMIO aperture at 0xFCFFF000.
(==) ATI(0): Write-combining range (0xfd000000,0x400000)
(II) ATI(0): MMIO write caching enabled.
(--) ATI(0): 4096 kB of SGRAM (1:1) detected (using 4095 kB).
(WW) ATI(0): Cannot shadow an accelerated frame buffer.
(--) ATI(0): Internal programmable clock generator detected.
(--) ATI(0): Reference clock 157.5/11 (14.318) MHz.
(II) ATI(0): My Monitor: Using hsync range of 31.50-79.00 kHz
(II) ATI(0): My Monitor: Using vrefresh range of 50.00-100.00 Hz
(II) ATI(0): Maximum clock: 230.00 MHz
Symbol XAAInit from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol XAADestroyInfoRec from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol XAACreateInfoRec from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol xf86CreateCursorInfoRec from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol xf86DestroyCursorInfoRec from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol xf86InitCursor from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol xf1bppScreenInit from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol ShadowFBInit from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol xf4bppScreenInit from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol fbScreenInit from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol xf86DestroyCursorInfoRec from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Symbol XAADestroyInfoRec from module /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
Fatal server error:
Caught signal 4. Server aborting
So, needless to say, I can not start my X back up after emerging the new version, and I have to work on this stupid Windows box...
HELP!!!!
Erik |
|
Back to top |
|
|
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Tue Sep 10, 2002 7:34 pm Post subject: |
|
|
Ok, so I figured it out myself....
At least, I'm not getting these errors anymore.
I had to add sections to the "Module" section of the XF86Config file:
Load "xaa"
Load "ramdac"
Load "xf1bpp"
Load "xf4bpp"
Load "fb"
Load "shadowfb"
When I try to start X, I don't get any errors when parsing the XF86Config file, but it terminates as follows:
Fatal server error:
Caught signal 4. Server aborting
Ideas anyone?
Erik |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Tue Sep 10, 2002 7:43 pm Post subject: |
|
|
Most relevant Google so far has been this, then this. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Tue Sep 10, 2002 11:14 pm Post subject: |
|
|
kanuslupus wrote: | Most relevant Google so far has been this, then this. |
Unfortunately, they didn't give me much at all.
Here is part of the strace log from where it fails:
write(0, "Cannot shadow an accelerated fra"..., 43) = 43
write(0, "(--) ", 5) = 5
write(0, "ATI(0): ", = 8
write(0, "Internal programmable clock gene"..., 4 = 48
write(0, "(--) ", 5) = 5
write(0, "ATI(0): ", = 8
write(0, "Reference clock 157.5/11 (14.318"..., 39) = 39
--- SIGILL (Illegal instruction) ---
rt_sigaction(SIGILL, {SIG_IGN}, {0x8082a90, [ILL], SA_RESTART|0x4000000}, = 0
write(2, "\nFatal server error:\n", 21) = 21
write(0, "\nFatal server error:\n", 21) = 21
write(2, "Caught signal 4. Server abortin"..., 34) = 34
write(0, "Caught signal 4. Server abortin"..., 34) = 34
write(2, "\n", 1) = 1
write(0, "\n", 1) = 1
As you can see, there is no reference from strace to what actually happened. I also tried running it under gdb, but that just locks up and I have to reboot. Not much help there, I'm afraid.
I tried to remove all ati related object modules and recompile them with different CFLAGS. I use gcc 3.1.1 btw. The same result here.
I have no problems using VESA/VGA drivers, but it just looks horrible.
So I'm currently backing down to 4.2.0 in an attempt to get my system back up and running.
Erik |
|
Back to top |
|
|
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Wed Sep 11, 2002 1:27 am Post subject: |
|
|
Ok folks...
The story is over.
I have re-emerged 4.2.0 and it is now back to normal.
Bottom line is:
If you are using any ATI graphics card, don't upgrade to 4.2.1 yet.
I'm sure the problem will get fixed, but I have been to busy at work today to do anything else than get my machine back to functional state.
Erik |
|
Back to top |
|
|
theneopro Tux's lil' helper
Joined: 08 Aug 2002 Posts: 90
|
Posted: Wed Sep 11, 2002 3:47 pm Post subject: Xfree86 4.2.1 |
|
|
2 weekends ago when i first installed Gentoo for the firsat time, I went for Xfree86 4.2.1 and I had errors as well. So I stepped back too 4.2.0
I am using the NVdriver. But it is not card specfic. Its the build. Im sure someone who wants to stick with it can figure it out, but I was more intrested in getting gentoo up for the first time and using X.
I can honestly say Gentoo is my favorite linux distrobution. Even tho I am currently working out some minor detials. I am still able to use my desktop. Unlike the other distro's i've used.
peace out
-Mykey _________________ ___________________________________
- The Rain Forest,
That sounds wet!!!! |
|
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
|
|