X won't start at boot, startx works fine though

TLV · 06-24-2004, 11:28 AM

I'm running Debian/Unstable on an IBM R40 laptop, kernel 2.6.6. Everything used to work fine, but after an update a while back (April/May), X won't start automatically when I boot. Instead I get kicked to a regular console login. After I've logged in I can do a startx (or a kdm as root) and X starts just fine.

XFree86.log looks good until when it's time for keyboard and mouse (there are some font warnings in the beginning, e.g. cryllic). Here's the last part of the log file when things start to go bad:

Code:

(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
(EE) xf86OpenSerial: Cannot open device /dev/psaux
        No such device.
(EE) Configured Mouse: cannot open input device
(EE) PreInit failed for input device "Configured Mouse"
(II) UnloadModule: "mouse"
(**) Option "Protocol" "ImPS/2"
(**) Generic Mouse: Protocol: "ImPS/2"
(**) Option "SendCoreEvents" "true"
(**) Generic Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(EE) xf86OpenSerial: Cannot open device /dev/input/mice
        No such device.
(EE) Generic Mouse: cannot open input device
(EE) PreInit failed for input device "Generic Mouse"
(II) UnloadModule: "mouse"
(WW) No core pointer registered
No core pointer

Fatal server error:
failed to initialize core devices

syslog tells me that:

Code:

Jun 24 17:02:46 milk kernel: PCI: Found IRQ 11 for device 0000:01:00.0
Jun 24 17:02:46 milk kernel: PCI: Sharing IRQ 11 with 0000:00:1d.0
Jun 24 17:02:46 milk kernel: PCI: Sharing IRQ 11 with 0000:02:07.0
Jun 24 17:02:46 milk input.agent[2262]:      evbug: blacklisted
Jun 24 17:02:46 milk kernel: input: PS/2 Generic Mouse on isa0060/serio1
Jun 24 17:02:46 milk input.agent[2262]:      evdev: already loaded
Jun 24 17:02:46 milk input.agent[2286]:      evbug: blacklisted
Jun 24 17:02:46 milk input.agent[2286]:      evdev: already loaded
Jun 24 17:02:46 milk input.agent[2336]:      evbug: blacklisted
Jun 24 17:02:46 milk input.agent[2336]:      evdev: already loaded
Jun 24 17:02:46 milk input.agent[2286]:      mousedev: loaded sucessfully
Jun 24 17:02:47 milk kernel: mice: PS/2 mouse device common for all mice
Jun 24 17:02:47 milk input.agent[2329]:      evbug: blacklisted
Jun 24 17:02:47 milk input.agent[2329]:      evdev: already loaded
Jun 24 17:02:47 milk input.agent[2404]:      evbug: blacklisted
Jun 24 17:02:47 milk input.agent[2404]:      evdev: already loaded
Jun 24 17:02:47 milk input.agent[2286]:      tsdev: loaded sucessfully
Jun 24 17:02:47 milk kernel: ts: Compaq touchscreen protocol output
Jun 24 17:02:49 milk kernel: eth0: no IPv6 routers present
Jun 24 17:02:49 milk kdm: :0[2226]: IO Error in XOpenDisplay
Jun 24 17:02:49 milk kdm[2160]: X server for display :0 terminated unexpectedly
Jun 24 17:02:49 milk kdm[2160]: Display :0 cannot be opened
Jun 24 17:02:49 milk kdm[2160]: Unable to fire up local display :0; disabling.

My XFConfig-4 looks like this for the input devices:

Code:

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "keyboard"
        Option          "CoreKeyboard"
        Option          "XkbRules"      "xfree86"
        Option          "XkbModel"      "pc101"
        Option          "XkbLayout"     "us"
EndSection

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/psaux"
        Option          "Protocol"              "PS/2"
        Option          "Emulate3Buttons"       "true"
        Option          "ZAxisMapping"          "4 5"
EndSection

Section "InputDevice"
        Identifier      "Generic Mouse"
        Driver          "mouse"
        Option          "SendCoreEvents"        "true"
        Option          "Device"                "/dev/input/mice"
        Option          "Protocol"              "ImPS/2"
        Option          "Emulate3Buttons"       "true"
        Option          "ZAxisMapping"          "4 5"
EndSection

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          "Default Screen"
        InputDevice     "Generic Keyboard"
        InputDevice     "Configured Mouse"
        InputDevice     "Generic Mouse"
EndSection

When I then do startx, the XFree86.log file look better...

Code:

(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 5
(**) Option "Protocol" "ImPS/2"
(**) Generic Mouse: Protocol: "ImPS/2"
(**) Option "SendCoreEvents" "true"
(**) Generic Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Generic Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Generic Mouse: ZAxisMapping: buttons 4 and 5
(**) Generic Mouse: Buttons: 5
(II) XINPUT: Adding extended input device "Generic Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Generic Mouse: ps2EnableDataReporting: succeeded
Warning: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0
Could not init font path element unix/:7101, removing from list!
SetClientVersion: 0 7

I've been working on this problem for a while now and I can't seem to find a solution. Any help is appreciated.

Thanks,
/TLV

sterrenkijker · 06-24-2004, 12:42 PM

Hmm, don't know about all the error messages, but maybe the symlink to start x isn't in the right rc-directory anymore?

There is a file /etc/inittab, which tells what is your default runlevel (probably 2). Take a look in the corresponding folder /etc/rc2.d (where the 2 must be your default runlevel). In that folder must be a symlink called S99kdm (or something similar) which points to /etc/init.d/kdm. (you can find that out by ls -l). If it doesn't exist, that must be your problem: then make such a symlink. If it exist, I hope anyone else can help you

.

I'll keep my fingers crossed

,

Corien

jsmarshall85 · 06-24-2004, 02:10 PM

i am having a similar problem. i boot to a command line and do startx always. it always worked until last week. now it wont load x

see this thread
http://www.linuxquestions.org/questi...hreadid=196504

TLV · 06-25-2004, 03:17 AM

sterrenkijker:
The symlinks exist (for KDM, GDM, XDM), and I know that the scripts are run because I edited them to add a delay before executing the main code. I did this temporarily as a troubleshooting tool because occasionally KDM started when I booted but most of the time not. I thought that perhaps the kernel needed some time to establish the devices (e.g., /dev/input/mice). But it didn't help.
Thanks for your input though.

jsmarshall85:
I'm not sure we have the same problem. I can do a startx (or even a kdm as root) and X starts flawlessly. My problem is that X/KDM won't start during the (end of the) boot process. I have to be logged in as a user to start X (KDM).

I am not an experienced Linux trouble shooter, jsmarshall85, but it seems as if you XFree86.log doesn't give any errors, just warnings. What does your /var/log/syslog (or /var/log/messages) say when X won't start? Please post that info in your thread, not this, and maybe that can give us a clue.

NB: My problem occurs no matter if I use KDM, GDM, or XDM. I just think KDM is prettier

/TLV

jsmarshall85 · 06-25-2004, 01:43 PM

i updated my other thread and found some info of interest in those files you said to look at
http://www.linuxquestions.org/questi...hreadid=196504

also i was able to get in by typing kdm at the prompt instead of startx and that worked, but the fonts looked kinda off, so i might just do that, set it up to load kdm at login, but thats the problem you are having right?

jsmarshall85 · 06-25-2004, 04:04 PM

ok, how do i get kdm to load after the system boots up?

sterrenkijker · 06-26-2004, 03:35 AM

I clearly underestimated your knowledge

.

macondo · 06-26-2004, 07:52 AM

http://www.linuks.mine.nu/debian-faq-wiki

Section 2.6.1

2.6.1. Getting PS/2 and USB mice to work with 2.6.x kernels

As root:

echo -e 'mousedev\npsmouse' >> /etc/modules
modprobe mousedev
modprobe psmouse

(You only need to do this once)

TLV · 06-26-2004, 10:05 AM

jsmarshall85:
Check out this link, http://sivut.koti.soon.fi/lindj/debian_problems.html, it probably have your answer. It also tells you how to remove and change it.

sterrenkijker:
Nah, I just like to research my problems and try to solve them myself before asking for help...

macondo:
Thanks a lot man. It finally works.

Question: I understand what the commands are doing - loading the modules. But why do they get loaded after I've logged in through the console (i.e., before the solution you cameup with) without them being specified in /etc/modules?

Thanks,
/TLV

macondo · 06-26-2004, 05:03 PM

"I know NOTHING, NOTHING!" -- Sgt Schultz (Hogan's Heroes)

jsmarshall85 · 06-29-2004, 08:52 AM

Quote:

Originally posted by sterrenkijker
I clearly underestimated your knowledge .

no no, i can do it, just not sure how on debian. the links others have provided only talk about removing kdm, xdm or whatever. in slackware for instance i can change the runlevel to 5 and that does it, but if i do that on debian it doesnt. i see that kdm does load but it kicks me back to a command prompt. i can run either kdm or startx and they work fine, but would just like kdm to start automatically. it isnt really that important, i kind of like starting at the command line and typing the commands i need.

TLV · 06-29-2004, 09:32 AM

Quote:

Originally posted by jsmarshall85
no no, i can do it, just not sure how on debian. the links others have provided only talk about removing kdm, xdm or whatever. in slackware for instance i can change the runlevel to 5 and that does it, but if i do that on debian it doesnt. i see that kdm does load but it kicks me back to a command prompt. i can run either kdm or startx and they work fine, but would just like kdm to start automatically. it isnt really that important, i kind of like starting at the command line and typing the commands i need.

See my post in your original thread.

Also, in my /etc/rc2.d I have a S99kdm. According to my logic, that would start kdm at the end of the boot. (But my logic has been known to falter

). Well, I think your first step should be to identify what is going wrong when you boot. The log files should give you some hints. When we know what's wrong, then we solve it.

Good luck,
/TLV

jsmarshall85 · 06-29-2004, 09:50 AM

well a little more on my systems. i have two machine i installed debina on using the beta installer using the sarge tree. then i switched it to sid to install firefox/thunderbird and did a dist-upgrade. both of my machines booted to a command prompt and i always did a startx to get into kde, that is until one of my machines stopped doing that. that is when i noticed that my other system actually loaded kdm (i always noticed and wondered why i got the nvidia splash screen first before i logged in)

so, i can live with it for now. i do appreciate everyones help. i'll probably chalk this one up to running sid and incompatabilities with the nvidia driver.

thanks again!

RavenLX · 06-24-2005, 10:37 AM

I'm having this exact same problem in Mandriva Limited Edition 2005. However, it was fine up until I did an update of packages (ie. live update thing or whatever). That's when the problems started. It will not boot into X, just into console, then it will work fine if I type 'startx'. inittab shows a run level of 5, so it SHOULD boot into X but doesn't.

Brief machine description: 2GHz Intel CPU, 512MB RAM, nVideo GeForce 5200FX 128-bit/128MB, 40G and 120G WD Caviar hard drives (linux on 40G drive, WinXP Pro SP2 on 120G drive), WinTV Go, US Robotic 5610B Modem, A-Bit IS-10 Motherboard and I have DSL via motherboard's LAN, SpeedStream modem and a LinkSys 4-port (non-wireless) router. Also have a DVD writer and 3.5" floppy drive. Mouse is a MS optical wheel mouse with a USB to PS/2 adapter and connected into the PS/2 port. I can't think of anything else that would be relevant here.

Here are some of the error codes in /var/log/messages which I was looking at. I removed the date and other numbers to save room here. Just captured the error messages alone:

xfs: xfs startup succeeded
xfs[7342]: ignoring font path element /usr/X11R6/lib/X11/fonts/drakfont/Type1 (unreadable)
xfs[7342]: ignoring font path element /usr/X11R6/lib/X11/fonts/drakfont/ttf (unreadable)
xfs[7342]: ignoring font path element /usr/X11R6/lib/X11/fonts/100dpi:unscaled (unreadable)

dm: Display manager startup succeeded
kdm_config[7763]: Unrecognized key 'ServerVTs' in section [General] at /usr/share/config/kdm/kdmrc:78
kdm_config[7763]: Unrecognized key 'GreeterPosFixed' in section [X-*-Greeter] at /usr/share/config/kdm/kdmrc:259
kdm_config[7763]: Unrecognized key 'GreeterPosX' in section [X-*-Greeter] at /usr/share/config/kdm/kdmrc:260
kdm_config[7763]: Unrecognized key 'GreeterPosY' in section [X-*-Greeter] at /usr/share/config/kdm/kdmrc:261
kdm_config[7763]: Invalid option value 'All' at /usr/share/config/kdm/kdmrc:293

kdm[7693]: X server for display :0 terminated unexpectedly
kdm: :0[7849]: IO Error in XOpenDisplay
kdm[7693]: Display :0 cannot be opened
kdm[7693]: Unable to fire up local display :0; disabling.

The top, I think I know what may cause that, but not sure. And not sure if it would be causing X not to boot. I think more than likely the 2nd and 3rd sets above are the problem. Seems like it's got keys in the config file that are not recognizable? Odd.

Last set it shows that it won't open the display :0 due to an IO Error in XOpenDisplay so it disabled it. THAT is the problem. Display :0 is where X would be put! Something is terminating the display on boot before X can take it over. Just prior to that it did a...

fstab-sync[7522]: removed all generated mount points

Now, display :0 can't possibly be a mount point as well, could it?

This does have me stumped. Unfortunately, my other machine is still in the process of being fixed up and upgraded, so Linux isn't installed on it yet. So I'm going to get out of WinXP here and look more into this. I'm hoping to track this error down. I can't promise though...

But since it looks like people with other distros than mine are also having problems, it might be some kind of bug in one of the programs or something that gets updated during a live update and changes one of the config files.

RavenLX · 06-24-2005, 12:27 PM

Problem solved; thank you to CAM_PIN in this post.