Cannot "startx" in SuSE 9.3
Jess Jackson
I am running SuSE Pro 9.3. It is a fresh install on a vintage Dell
400-MHz system. Everything appeared to install just fine. I can boot to
the command prompt and login and do any normal terminal activities. But
when I try "startx" it tries to start but will not and returns to the
command prompt. The Xorg.0.log file is 350+ lines long, so I am
including the first and last parts to avoid making this too long. I get
a couple of terminal messages. The ones that seem significant are as
follows...
INPUT_METHOD is not set or empty
...
There is no default input method for the current locale
...
DCOP aborting call from...
kded: ERROR: Communication problem with kded, it probbaly crashed
...
I am fairly new at Linux and brand new at SuSE. Any help would be
greatly appreciated.
Thanks,
Jess
---------------
Xorg.0.log as follows...
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux Dell400 2.6.11.4-20a-default #1 Wed Mar
23 21:52:37 UTC 2005 i686
Build Date: 22 March 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 24 06:27:42 2005
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout[all]"
(**) |-->Screen "Screen[fbdev]" (0)
(**) | |-->Monitor "Monitor[0]"
(**) | |-->Device "Device[fbdev]"
(**) |-->Input Device "Keyboard[0]"
(**) |-->Input Device "Mouse[1]"
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/truetype/,/usr/X11R6/lib/X11/fonts/URW/,/usr/X11R6/lib/X11/fonts/uni/,/usr/X11R6/lib/X11/fonts/misc/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(**) Input device list set to
"/dev/ttyS0,/dev/ttyS1,/dev/ttyS2,/dev/ttyS3,/dev/ttyS4,/dev/ttyS5,/dev/ttyS6,/dev/ttyS7,/dev/ttyS8,/dev/psaux,/dev/logibm,/dev/sunmouse,/dev/atibm,/dev/amigamouse,/dev/atarimouse,/dev/inportbm,/dev/gpmdata,/dev/usbmouse,/dev/adbmouse,/dev/input/mice,/dev/input/event0"
(**) ModulePath set to "/usr/X11R6/lib/modules"
(**) Option "AllowMouseOpenFail"
(**) Option "BlankTime" "0"
(**) Option "Xinerama" "off"
(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.7
X.Org XInput driver : 0.4
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(--) using VT number 7
.... LOTS OF OMITTED LINES ......
(EE) FBDEV(0): FBIOBLANK: Invalid argument
(EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument
(==) FBDEV(0): Backing store disabled
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "CoreKeyboard"
(**) Keyboard[0]: Core Keyboard
(**) Option "Protocol" "Standard"
(**) Keyboard[0]: Protocol: Standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) Keyboard[0]: XkbRules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) Keyboard[0]: XkbModel: "pc104"
(**) Option "XkbLayout" "us"
(**) Keyboard[0]: XkbLayout: "us"
(**) Option "XkbKeycodes" "xfree86"
(**) Keyboard[0]: XkbKeycodes: "xfree86"
(**) Option "CustomKeycodes" "off"
(**) Keyboard[0]: CustomKeycodes disabled
(**) Option "Protocol" "explorerps/2"
(**) Mouse[1]: Device: "/dev/input/mice"
(**) Mouse[1]: Protocol: "explorerps/2"
(**) Option "CorePointer"
(**) Mouse[1]: Core Pointer
(**) Option "Device" "/dev/input/mice"
(==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse[1]: Buttons: 3
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD)
(II) Mouse[1]: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/truetype/,
removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/URW/, removing
from list!
(EE) FBDEV(0): FBIOBLANK: Invalid argument
robbie chen
> Could not init font path element /usr/X11R6/lib/X11/fonts/truetype/,
> removing from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/URW/, removing
> from list!
According to my experience, the abover two lines tells the reason. X
server couldn't init font path which is configed in /etc/X11/xorg.conf
for SuSe 9.3.
To solve that problem temperatory, edit /etc/X11/xorg.conf, comment the
two lines with path /usr/X11R6/lib/X11/fonts/truetype/ &
/usr/X11R6/lib/X11/fonts/URW/. Then startx again. Hope this help:)
NunYa Bidness
us:
Another thing to try is
sax2 -m 0=vesa
That is a zero.
This will start sax and attempt to bring up a vesa driven xwindow.
If it succeeds, he can accept it and try startx again.
Reinhard Gimbel
> Hi:
>
> I am running SuSE Pro 9.3. It is a fresh install on a vintage Dell
> 400-MHz system. Everything appeared to install just fine. I can boot to
> the command prompt and login and do any normal terminal activities. But
> when I try "startx" it tries to start but will not and returns to the
> command prompt. The Xorg.0.log file is 350+ lines long, so I am
> including the first and last parts to avoid making this too long. I get
> a couple of terminal messages. The ones that seem significant are as
> follows...
>
> INPUT_METHOD is not set or empty
> ...
> There is no default input method for the current locale
> ...
> DCOP aborting call from...
> kded: ERROR: Communication problem with kded, it probbaly crashed
> ...
>
> I am fairly new at Linux and brand new at SuSE. Any help would be
> greatly appreciated.
>
> Thanks,
> Jess
For me it looks that your graphics controller is not supported from the
X servers available in SuSE 9.3 ...
Has the X server ever run ? As you maybe know the initial graphical
installation system of SuSE 9.3 is running on a X environment.
The question is: Have you had graphical installation screens or have you
had just terminal output during the installation process ?
How about the graphics controller used in your "vintage" system ?
"lspci" might help to find the controller type used in your system.
/sbin/lspci -n | grep 0300
You should have a look into SuSE's hardware database http://cdb.suse.de
for more information.
What "sax2 -p" states about the available graphics hardware ?
What happens when "sax2 -f" is issued ?
What is shown after "hwinfo --framebuffer" is called ?
Another idea is to call sax2 with either
sax2 -m 0=fbdev
or
sax2 -m 0=vesa
You might find some more information in SuSE's support database
http://portal.suse.com/sdb (E.g.
http://portal.suse.com/sdb/en/2002/11/wessels_sax247.html and
http://portal.suse.com/sdb/de/2001/04/wessels_problematic_chipsets.html;
Sorry the 2nd link points to german language article; these information
should be available as english language articles as well, but I couldn't
find it right now ...)
Sorry, lots of information ...
Best regards,
Reinhard.
TokaMundo
<rein...@dragonfly7.de> Gave us:
>Another idea is to call sax2 with either
>
>sax2 -m 0=fbdev
>
>or
If you had read his post, you would find that he IS attempting
startup with the fbdev in place.
Reinhard Gimbel
I might believe or not: I read that he is using fbdev !
But there might be an inconsistency within the /etc/X11/xorg.conf which
will be overwritten when using sax2. If sax2 fails as well that trace
migth be wrong.
Than other traces like using hwinfo, lspci, and the like might be more
useful.
Apropos hwinfo: the option "--gfxcard" is also worth a try ...
You should read my post completely and try to understand what I would
like to gain: I would like to help Jess in getting his system running.
Reinhard.
Jess Jackson
I have tried most all the combinations you suggested. I ran yast and
redetected my ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c) video
card and my Gateway VX900 monitor.
But most of the time sax2 with any options starts, I get a blue screen
with a penguin in the lower right and back to a command prompt.
Now startx gives me a logon screen (looks 640x480) but entering username
and password (regular user or root) brings back the same login screen.
Here is the screen output from startx (perhaps this will help??)...
xauth: (stdin):1: bad "add" command line
xauth: (stdin):2: bad "add" command line
xauth: (stdin):3: bad "add" command line
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux Dell400 2.6.11.4-20a-default #1 Wed Mar
23 21:52:37 UTC 2005 i686
Build Date: 22 March 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 31 03:14:54 2005
(==) Using config file: "/etc/X11/xorg.conf"
Could not init font path element /usr/X11R6/lib/X11/fonts/local,
removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing
from list!
/etc/X11/xim: Checking wether an input method should be started.
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
startkde: Starting up...
mkdir: Owner of /tmp/.ICE-unix should be set to root
DCOP aborting call from 'anonymous-17418' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
Warning: connect() failed: : Connection refused
/usr/X11R6/bin/kde: line 257: 17420 Segmentation fault kwrapper
ksmserver $KDEWM
startkde: Shutting down...
Warning: connect() failed: : Connection refused
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done.
waiting for X server to shut down
Jess Jackson
Since this was a freshly installed system on which I had already put a
couple of hours with this problem, I wiped the Linux partitions and
re-installed from scratch. Good news — it runs X just fine. So I perhaps
lost a learning opportunity but my time, in this case, was more valuable.
I would like to have "solved" this but time was more valuable right now.
Regards,
Jess
Kevin Nathan
Jess Jackson <jessj...@cox.net> wrote:
> I would like to have "solved" this but time was more valuable right
> now.
The next time you have display problems in X, and SaX2 and the other
ideas don't help, do the following:
1. Gather specs for monitor (horiz/vert freqs are most important), video
card (chipset and amount of memory), mouse and keyboard (connection
types and such).
2. Shut down the X server -- logout of KDE or whatever DM/WM you are
using. If you're booting straight into runlevel 5 (KDM/GDM/XDM come up
automatically), then press Ctrl-Alt-F1 (or F2) and log in as root.
3. Enter:
init 3
4. Run:
xf86config
or
xorgconfig
(They are the same program, at least right now.) Do *not* run
'xorgcfg'! This is graphical and probably won't work if you're having X
problems.
5. While answering the questions from xorgconfig, be sure to enter very
conservative values for any of which you are unsure.
6. After this is finished, do:
startx
This has never failed to get me a working X server. It might not be the
best you can get, but once you finally have a running version (save
the /etc/X11/xorg.conf or /etc/X11/XF86Config file in a safe
place/name) you can continue tweaking -- and you always have a working
configuration to which you can return . . .
--
Kevin Nathan (Arizona, USA)
Linux Potpourri and a.o.l.s. FAQ -- http://www.project54.com/linux/
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.8-24.17-default
7:08pm up 21 days 23:59, 15 users, load average: 0.06, 0.10, 0.17