View previous topic :: View next topic |
Author |
Message |
Tamerz Apprentice
Joined: 29 Apr 2003 Posts: 232 Location: Chicago IL, USA
|
Posted: Thu Oct 21, 2004 1:42 am Post subject: Problems starting X [SOLVED] |
|
|
I have X compiled along with the ati-drivers installed for my Radeon 9800 Pro. I followed all the directions and when I start X you it tries to start and you even get a glimpse of the hourglass. Then it crashes with:
Code: | Symbol drmGetClient from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved!
Could not init font path element /usr/share/fonts/Speedo/, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list!
xterm: error while loading shared libraries: libXaw.so.8: cannot open shared object file: No such file or directory
xterm: error while loading shared libraries: libXaw.so.8: cannot open shared object file: No such file or directory
xterm: error while loading shared libraries: libXaw.so.8: cannot open shared object file: No such file or directory |
Why would it be doing this? Thanks.
Last edited by Tamerz on Sat Oct 23, 2004 3:24 pm; edited 1 time in total |
|
Back to top |
|
|
bunsen Tux's lil' helper
Joined: 10 Aug 2003 Posts: 105
|
Posted: Thu Oct 21, 2004 9:57 am Post subject: |
|
|
At a guess, the libXaw.so.8 which is reported to be missing won't be built and installed without the Xaw3d USE flag set. |
|
Back to top |
|
|
Tamerz Apprentice
Joined: 29 Apr 2003 Posts: 232 Location: Chicago IL, USA
|
Posted: Thu Oct 21, 2004 12:40 pm Post subject: |
|
|
So what would I do? Add the Xaw3d flag, and then what do I have to emerge again? Thanks. |
|
Back to top |
|
|
BlueNoteMKVI n00b
Joined: 07 Jul 2004 Posts: 65
|
Posted: Thu Oct 21, 2004 6:32 pm Post subject: |
|
|
I'm having exactly the same error messages - can anyone shed some light on a solution? |
|
Back to top |
|
|
BlueNoteMKVI n00b
Joined: 07 Jul 2004 Posts: 65
|
Posted: Thu Oct 21, 2004 9:44 pm Post subject: |
|
|
I just bit the bullet and recompiled X with the proper USE flag (see above). KDE starts up just fine now. Unfortunately last night's upgrade nuked a lot of my config files. I'm rather annoyed at losing a day's work because my computer was compiling all day...but c'est la vie. |
|
Back to top |
|
|
Tamerz Apprentice
Joined: 29 Apr 2003 Posts: 232 Location: Chicago IL, USA
|
Posted: Thu Oct 21, 2004 10:06 pm Post subject: |
|
|
Did you just "emerge x11-org"? |
|
Back to top |
|
|
Tamerz Apprentice
Joined: 29 Apr 2003 Posts: 232 Location: Chicago IL, USA
|
Posted: Sat Oct 23, 2004 5:29 am Post subject: |
|
|
Ok so I added that flag and emerged x11-org again. Now X starts up but just the plain X (not KDE). If I change XSESSION in rc.conf to kde it starts up just a blank screen with an X for the mouse cursor. What else do I need to change? Or do I have to emerge KDE over again? |
|
Back to top |
|
|
Tamerz Apprentice
Joined: 29 Apr 2003 Posts: 232 Location: Chicago IL, USA
|
Posted: Sat Oct 23, 2004 3:24 pm Post subject: |
|
|
Fixed. I put the Code: | echo "exec startkde" > ~/.xinitrc | line in wrong. |
|
Back to top |
|
|
melteye n00b
Joined: 28 Feb 2004 Posts: 36
|
Posted: Sat Oct 30, 2004 3:44 am Post subject: |
|
|
I'm getting these same errors. Since I don't want the new xorg to install the only method I could think of was unmerging xorg-x11 then emerging ati-drivers again (which reinstalls the old xorg).... I added "Xaw3d" to my USE flags but I am still getting the same errors...
When I installed froma Stage 2 I experienced no difficulties with Gentoo, since installing froma Stage 3 Gentoo has been a real pain.
I followed the EXACT same steps I took to get X working and now I'm getting these errors.
Code: | (WW) fglrx: No matching Device section for instance (BusID PCI:2:0:1) found |
As well as the libXaw errors previously stated. Any ideas? Knowing how to rebuild only the old xorg or how to mask the new one would help. |
|
Back to top |
|
|
melteye n00b
Joined: 28 Feb 2004 Posts: 36
|
Posted: Sat Oct 30, 2004 3:53 am Post subject: |
|
|
FIXED: I emerged xterm and it fixed the problem... But information on masking only the new xorg or emerging only the current version (no update) would still be appreciated. |
|
Back to top |
|
|
januszt n00b
Joined: 16 Jul 2003 Posts: 19
|
Posted: Mon Nov 15, 2004 4:05 pm Post subject: |
|
|
Hi
Having exactly the same problem.
Code: | emerge -pv =x11-base/xorg-x11-6.7.0-r2 |
would not show Xaw3d as a valid USE flag then I read your post about xterm.
Code: | emerge -pv --newuse xterm |
shows -Xawd3
I put flag into make.conf reemerged xterm and got my Xorg working
Thanks |
|
Back to top |
|
|
|