Florian Kulzer schrieb:
On Mon, May 14, 2007 at 22:20:58 +0200, Kristian Lampen wrote:Florian Kulzer wrote:My MD5 is the same, but I recognised that HAL works if I use the standard-kernel-image 2.6-686 (2.6.18+6), or the standart 2.6.20 kernel. Usually I use a selfcompiled 2.6.18. I did´t change this kernel in the last month, so the problem must be, that a updated version of hal needs some other kernel options or modules to be active.On Sun, May 13, 2007 at 13:44:10 +0200, Kristian Lampen wrote:Hi,I use the recent sid installation, kernel 2.6.18 (update almost everyday). As I tried to use my USB-Stick yesterday, I recognised that kde does not mount it automatically (the same with cdrom). The last time before two weeks all worked well.I found out, that the hal daemon crashes on startup: sid:~# /etc/init.d/dbus restart Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon. Stopping Hardware abstraction layer: hald. Stopping system message bus: dbus. Starting system message bus: dbus.Starting Hardware abstraction layer: haldrun-parts: /etc/dbus-1/event.d/20hal exited with return code 1Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.I didn´t change the hal configuration, so maybe the reason is a update of the hal system?sid:~# apt-cache policy hal dbus udev hal: Installiert:0.5.9-2[...]dbus: Installiert:1.0.2-5[...]udev: Installiert:0.105-4That combination works for me. Let's check if we have the exact same version of /etc/dbus-1/event.d/20hal. You can just compare the MD5sum: $ md5sum /etc/dbus-1/event.d/20hal 3f1321d3006e133c789494981569d198 /etc/dbus-1/event.d/20hal (I am not sure if this script is architecture-dependent. The MD5sum seems to be the same for i386 and amd64.)Does anyone know which options/modules have to be enabled for HAL?You can try to edit /etc/dbus-1/event.d/20hal and change the line set -e to set -xe Then you can restart dbus and all commands in that script will be echoed to STDOUT as they are run. Maybe that will give you a clue where things go wrong. (A quick look in /usr/share/doc/hal did not tell me anything. NEWS.gz states that a kernel >= 2.6.17 is needed but I did not notice any specific modules being mentioned.)
This is the output: sid:~# /etc/init.d/dbus restart Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon. + case "$1" in + do_stop + log_daemon_msg 'Stopping Hardware abstraction layer' hald + '[' -z 'Stopping Hardware abstraction layer' ']' + '[' -z hald ']' + echo -n 'Stopping Hardware abstraction layer: hald'Stopping Hardware abstraction layer: hald+ start-stop-daemon --stop --oknodo --quiet --pidfile /var/run/hal/hald.pid --exec /usr/sbin/hald
+ log_end_msg 0 + '[' -z 0 ']' + log_use_fancy_output + TPUT=/usr/bin/tput + EXPR=/usr/bin/expr + '[' xxterm '!=' xdumb ']' + '[' -x /usr/bin/tput ']' + '[' -x /usr/bin/expr ']' + /usr/bin/tput hpa 60 + /usr/bin/tput setaf 1 + '[' -z ']' + FANCYTTY=1 + case "$FANCYTTY" in + true ++ /usr/bin/tput setaf 1 + RED='' ++ /usr/bin/tput op + NORMAL='' + '[' 0 -eq 0 ']' + echo . . + return 0 + exit 0 Stopping system message bus: dbus. Starting system message bus: dbus. + case "$1" in + do_start + '[' '!' -d /var/run/hal ']' + log_daemon_msg 'Starting Hardware abstraction layer' hald + '[' -z 'Starting Hardware abstraction layer' ']' + '[' -z hald ']' + echo -n 'Starting Hardware abstraction layer: hald'Starting Hardware abstraction layer: hald+ start-stop-daemon --start --pidfile /var/run/hal/hald.pid --exec /usr/sbin/hald --
run-parts: /etc/dbus-1/event.d/20hal exited with return code 1 Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.Nothing I can get from this output, just that the hald programm crashes directly.
Kristian