Click to See Complete Forum and Search --> : HAL died
soulestream
08-25-2005, 01:53 AM
so i installed slack 10.1 the other day and everything has been going well. (got my wireless fixed), but i rebooted and the computer wouldnt boot. it would get to login, the hal would finish loading and lock up. so i turned off hal to get it to boot, but i need to know how to "fix" hal. I havent messed with hald.conf. I did try to uninstall/reinstall hal. that didnt help.
any ideas?
soule
grep -rl hal /var/log/*
look for errors
soulestream
08-25-2005, 01:31 PM
sorry i thought i posted that.
Code:
Aug 25 09:36:52 localhost hal.hotplug[2284]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2318]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2352]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2386]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2420]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2454]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2488]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2522]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2556]: DEVPATH is not set
Aug 25 09:36:52 localhost hal.hotplug[2590]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2624]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2658]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2692]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2726]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2760]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2794]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2828]: DEVPATH is not set
Aug 25 09:36:53 localhost hal.hotplug[2862]: DEVPATH is not set
this was in /var/log/syslog. i also noticed a coulple of entries had been put in fstab.
one was for my ipod, the othe was a second entry for my cdrw
#/dev/hdc /mnt/cdrecorder auto user,exec,noauto 0 0
#/dev/sdb1 /mnt/KEITHS_MUSI vfat user,exec,noauto,iocharset=utf8,noatime,sync 0 0
I commented them out, just in case but no luck.
soulestream
08-26-2005, 02:34 AM
well for future reference if any body runs across this..
after googling and asking my tail off
it seems that kernel 2.6, HAL, and ipw2200 cards can have a bug. it depends on the driver, kernel config, and HAL. but i did a complete reinstall and as soon as in installed the firmware for my card, the next reboot the computer locked up.
soule
psych-major
08-26-2005, 01:17 PM
That's really weird, that you had the exact combination to produce a failure. You could stick with the 2.4 kernel that ships with 10.1... :rolleyes:
soulestream
08-26-2005, 04:41 PM
need 2.6 kernel for ipw2200 drivers. Think im going to turn off HAL.
and just order a cheap wireless card.
When it comes in I will just turn HAL back on
What were you using in your other post?
soule
psych-major
08-26-2005, 05:32 PM
They are NEC Warpstar, Atheros-based. They were at www.geeks.com for $10.99!!
When I called Monday, they had over 900 in stock, now they are sold out!
I also found them here (http://tekgems.com/Products/et-17451-nwl-pa-wl54ag.htm) for $25.00 and here (http://shop.store.yahoo.com/justdeals/pawl54ag.html) for $19.99.
soulestream
08-26-2005, 10:28 PM
well i just ordered own of those. Hopefully it will work. If I have any problems I will repost.
as a note.
1. I have tried a couple different kernels and configs and the computers locks everytime I install firmware so beware.
2. I would like to give thanks to the guys at bestbuy/geek sqaud. While I dont think they knew why I wanted the info, they were nice enough to google the chipsets for the cards I was looking at. ;)
3. thanks for the help
soule
psych-major
08-27-2005, 08:30 AM
FYI. I just installed madwifi for one of these new cards on a ThinkPad, and some saint has gone and made a package out of the madwifi driver! You can download it here (http://sox.homeip.net/slackware/slackbuilds/madwifi/pkg/). I had mine downloaded, installed, and working within about 2 minutes! Definitely easier than last time!
soulestream
08-27-2005, 02:31 PM
im assuming part of that model # is the kernel they are compliled against.
soule
psych-major
08-28-2005, 12:48 AM
That is correct, and they are kernel-specific.