You are not logged in.
Pages: 1
I have added dbus and hal to the DAEMONS line in my rc.conf. Howeve,r on bootup they are not starting, as denoted by the red [FAIL] on the right by them. It goes by really fast, and I cannot find it in one of my log files either . However, i think I have caught it and it says something about the UUID...I know i am not giving much to work with, but its all I can find, any help would be great, thanks.
I didn't configure these in any way, so if that is needed then I just need to know how.
Last edited by psilo357 (2008-11-12 02:29:10)
Offline
I have added dbus and hal to the DAEMONS line in my rc.conf. Howeve,r on bootup they are not starting, as denoted by the red [FAIL] on the right by them. It goes by really fast, and I cannot find it in one of my log files either
. However, i think I have caught it and it says something about the UUID...
To read the boot message:
http://wiki.archlinux.org/index.php/Pos … ot_Process
You DON'T need to start dbus manually as it is loaded automatically by hal. That means dbus shouldn't be in the DAEMONS line if hal is.
Offline
alright, i took dbus out of the DAEMONS list in my rc.conf.
I also added the line to my rc.local it said to make it pause, however, it did not work.
I am still having problems getting hal to start. While booting it says
Starting Hardware Abstraction Layer [FAIL]
and thats all it really gives me, and other tips would be great. Also, why can that stuff not be logged to a normal log file? Everything from the kernel startup is, just not the autostart daemons and stuff...odd
Offline
You can run:
# hald --verbose=yes --daemon=no
That will give you some output and hopefully the reason its failing to start.
Offline
01:09:50.665 [i] hald.c:669: hal 0.5.11
01:09:50.665 [i] hald.c:734: Will not daemonize
01:09:50.665 [i] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-hI6oBHBXRI,guid=f89b864a243267b4bdfc2954490ff53e
01:09:50.665 [E] hald_dbus.c:5747: dbus_bus_get(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
that is what the command output. I'm guessing the line with the [E] means error, and its right, there is nothing inside the /var/run/dbus/ directory. All the way up to dbus is there, but its empty...
Any idea what system_bus_socket is supposed to consist of or even if its a directory or file?
Offline
Some people from other distros have reported that reinstalling dbus clears the missing system_bus_socket problem. I suppose its worth a try.
Offline
Alright, well, i reinstalled DBUS, and to no avail, it still fails at boot, causing hal to fail. anyone with any other suggestions?
thanks
Offline
What happens when you try to start the services manually from a command prompt (without booting into X at all)?
see here:
http://wiki.archlinux.org/index.php/Beg … DE_DAEMONS
Seems to me you do it in this order:
1) install or make sure you have hal and fam installed
2) manually turn them on from the command line
3) Edit your /etc/rc.conf to add hal and fam to the line
DAEMONS=(syslog-ng network crond alsa hal fam)
then reboot and see if it fixes your problem
Offline
I am still having problems getting hal to start. While booting it says
Starting Hardware Abstraction Layer [FAIL]
Same failure here, but only on my KDE4 box. HAL starts fine on the Gnome box.
Hopefully, the fact that it works fine under Gnome and not under KDE4 might provide a clue about a fix.
Edit: ok, it turns out that it was portmap not starting for me, and it was because I had inadvertently added it to rc.conf "after" fam, whereas it should have been entered "before" fam. Since then, I've found that neither portmap or fam are dependencies to KDE4 so I've removed both of them from the system and removed them from the daemons listing in rc.conf and my system is running great.
Last edited by ozar (2008-12-03 05:18:49)
oz
Offline
alright, I didn't even have fam in there, and when added, it also fails. Both rely on dbus to run, and since my dbus won't start, they fail as well.
I am also on kde4 so that could very well be the problem.
peace
Offline
well, never got this to work, did a reinstall though, and did not pick dbus-core as one of the packages to install from the get-go. Then installed kdemod instead of kde4, and it was smooth. Now dbus works fine, don't know if it was installing it during arch install or what, but it works now.
peace
Offline
Pages: 1