[Solved] Fresh install; HAL won't start?

initbox · 2011-07-04 22:30:58

So I just finished a fresh installation and now I can't start X because HAL won't start up at all.

I haven't messed around with anything except for installing everything and fixing up my config files.

Seems like HAL is crashing because of permissions but I even checked the paths and they seem to be fine:

hald --daemon=no --verbose=yes

01:08:41.090 [i] hald.c:673: hal 0.5.14
01:08:41.090 [i] hald.c:674: using child timeout 250s
01:08:41.090 [i] hald.c:739: Will not daemonize
01:08:41.090 [i] hald_dbus.c:5444: local server is listening at unix:abstract=/var/run/hald/dbus-uBDySnOMjt,guid=33e68e9ab5cc00ac1ce4ba92000008c1
01:08:41.091 [i] hald_runner.c:304: Runner has pid 1695
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
01:08:41.093 [i] hald_runner.c:184: runner connection is 0x17da830
01:08:41.097 [W] osspec.c:393: Unable to open /proc/mdstat: No such file or directory

** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/preprobe': Permission denied

** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/preprobe': Permission denied

** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/information': Permission denied

** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/information': Permission denied

** (process:1694): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/policy': Permission denied

** (process:1694): WARNING **: Failed to add monitor on '/etc/hal/fdi/policy': Permission denied
22:08:41.098 [i] mmap_cache.c:126: Regenerating fdi cache..
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

22:08:41.099 [E] hald_runner.c:888: Error running 'hald-generate-fdi-cache': org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
22:08:41.099 [i] mmap_cache.c:104: In regen_cache_cb exit_type=2, return_code=0
22:08:41.099 [E] mmap_cache.c:153: fdi cache regeneration failed!
22:08:41.099 [i] mmap_cache.c:156: fdi cache generation done
22:08:41.099 [i] mmap_cache.c:278: cache mtime is 0
*** [DIE] osspec.c:osspec_init():449 : Unable to read /proc/mounts

Can't find anything worthwhile in logs etc., and I can't think of anything that could be causing this?

I checked that the HAL user exists and has been added to the default groups, but that "???"-part is alarming.
DBus starts up normally.
Networking and "lo" seem to be working fine as well, and I don't have iptables up.

Last edited by initbox (2011-07-05 16:59:36)

tomk · 2011-07-04 22:42:09

Update your system - xorg does not depend on hal anymore. hal is obsolete.

linuxer0203 · 2011-07-05 08:29:02

try using gdm to startx . did u add your user to video groups ?

initbox · 2011-07-05 16:57:42

tomk wrote:

Update your system - xorg does not depend on hal anymore. hal is obsolete.

Ah, haven't been up to date on all the changes, it seems...

In the past I've had problems with the nvidia driver + Xorg without HAL, I think?

Anyhow, contrary to the Xorg page, I had no 20-nvidia.conf. I created that and now I'm able to startx without HAL but KDM doesn't work, the screen flickers when it attempts to start Xorg but then it crashes. Strange. Nothing in the Xorg logs either.

I'll have to see about that next, but it's nice to be able to get rid of HAL at least.

mandog · 2011-07-05 20:44:37

use # nvidia-xconfig to create a new xorg.conf file nvidia looks for this 1st and will keep your settings people seem to write off hard faced settings for auto conf which does not always work as with my lcd monitor it only keeps its correct settings when using the xorg.conf file. as for hal you don't need it for a basic system a lot of programs still use hal and it does no harm running in the background. This is only some of the failings with Linux trying to make Linux more like MS but then forget to include manual over-ride settings just in case

Last edited by mandog (2011-07-05 20:46:08)

Arch Linux

#1 2011-07-04 22:30:58

[Solved] Fresh install; HAL won't start?

#2 2011-07-04 22:42:09

Re: [Solved] Fresh install; HAL won't start?

#3 2011-07-05 08:29:02

Re: [Solved] Fresh install; HAL won't start?

#4 2011-07-05 16:57:42

Re: [Solved] Fresh install; HAL won't start?

#5 2011-07-05 20:44:37

Re: [Solved] Fresh install; HAL won't start?

Board footer