Got my HAL working even with CONCURRENCY in /etc/init.d/rc set to shell.
Here are the steps I took. (All are included above in previous posts and Bug #149881 link https://bugs.launchpad.net/ubuntu/+source/hal/+bug/149881 .)
Changed the CONCURRENCY setting by:
sudo gedit /etc/init.d/rc and editing CONCURRENCY=none to CONCURRENCY=shell. Then saving.
Compared my /etc/rc2.d filenames to those posted above. My rc2.d was S50dbus instead of S12dbus. Changed that by:
sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus
Saw in another thread that hal should be set to 13 so that it starts after dbus is started. My HAL was 12. Fixed that by:
sudo mv /etc/rc2.d/S12hal /etc/rc2.d/13hal
Another post said to change the Hal cache. Did that by:
sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache
Restarted PC and all seems fine.
Thanks to the Ubuntu posters for your help. Gutsy still starts up awlfully slow compared to Feisty.
Any other ideas are appreciated.
Got my HAL working even with CONCURRENCY in /etc/init.d/rc set to shell.
Here are the steps I took. (All are included above in previous posts and Bug #149881 link https:/ /bugs.launchpad .net/ubuntu/ +source/ hal/+bug/ 149881 .)
Changed the CONCURRENCY setting by:
sudo gedit /etc/init.d/rc and editing CONCURRENCY=none to CONCURRENCY=shell. Then saving.
Compared my /etc/rc2.d filenames to those posted above. My rc2.d was S50dbus instead of S12dbus. Changed that by:
sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus
Saw in another thread that hal should be set to 13 so that it starts after dbus is started. My HAL was 12. Fixed that by:
sudo mv /etc/rc2.d/S12hal /etc/rc2.d/13hal
Another post said to change the Hal cache. Did that by:
sudo mv /var/cache/ hald/fdi- cache~ /var/cache/ hald/fdi- cache
Restarted PC and all seems fine.
Thanks to the Ubuntu posters for your help. Gutsy still starts up awlfully slow compared to Feisty.
Any other ideas are appreciated.