• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 787
  • Last Modified:

X Server or other startup issues

Novice -- I'm having issues at startup... Failsafe X Windows is working, "regular" mode X Windows is not.

Not being sure which logs were significant, I copied all /var/log/*.* contents to an archive, then rebooted. On first boot, I started in "regular" mode, and allowed the system to fail. Having little choice, I then do a power off/reboot. On second boot, I started in failsafe mode.

I'm assuming:
1) /var/log/boot.omsg and /var/log/boot.msg are the previous and current boot logs, respectively.
2) /var/log/Xlog.0.log.old and /var/log/Xlog.0.log are the previous and current XWindows logs, respectively
3) All other logs in /var/log/ are appended on each reboot.

Searching the newly generated logs for significant entries, I find:

/var/log/boot.omsg ends with
      "Kernel logging (ksyslog) stopped."
      "Kernel log daemon terminating."

/var/log/boot.msg (failsafe mode?), continues beyond the previous lines with:
      "Boot logging started on /dev/char/../tty1(/dev/console)"
 and it continues with the fschk of the volumes (powered off previously)


/var/log/kdm.log has 2 reboot attempts:
where first has lines:
      "Setting master"
      "(EE) config/hal: couldn't initialise context: unknown error (null)"
      "Could not initialise connection to hald."
      "Normally this means the HAL daemon (hald) is not running or not ready."
      "Could not initialise connection to hald."
      "Normally this means the HAL daemon (hald) is not running or not ready."
      "Dropping master"

where second has only:
      "Setting master"


/var/log/messages has:
      (hint, next line for purpose of timestamp only)
      "09:55:09 linux-57kq kernel: [   46.660009] eth0: no IPv6 routers present"
      "09:55:44 linux-57kq kdm[1092]: X server startup timeout, terminating"
      "09:55:54 linux-57kq pm-profiler: Power Button pressed, executing /sbin/shutdown -h now"


So --  hald fails? causes X Server to fail?

Thnx in advance......


0
daveburrow
Asked:
daveburrow
2 Solutions
 
nociSoftware EngineerCommented:
The modern x-server indeed needs the hal to work for getting the devices available on the platform.

Any logging on the faith of the hal daemon?

For X there should be messages in /var/log/Xorg.0.log
0
 
elf_binCommented:
First of all you basically right about the logs.  The idea that entries are just appened forever is wrong though and are often controlled by a log roller application.
You need to start SuSE in runlevel 3 (networking without GUI)  append a 3 to the grub options.  Once you're up at level 3 (try level 1 if 3 won't boot) you need to try and restart the HAL daemon (/etc/init.d/haldaemon restart).  Also in /etc/init.d/haldaemon you could change:
HALDAEMON_PARA="--daemon=yes";
to:
HALDAEMON_PARA="--daemon=yes --verbose=yes --use-syslog";
This'll log using syslog (so generally, it'll go to the files in /var/log) and will log verbose messages.  This may give you a clue.
OpenSuSE has a HOWTO on HAL, please see: http://en.opensuse.org/HAL

You're X will not successfully start until you've got HAL sorted.

Hope this helps.

0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now