You are not logged in.
Pages: 1
So, when I turn on my computer HAL normally takes about 20 seconds to start up. Once I have booted up I can restart it in 0.1 seconds.
Here is my daemon line:
DAEMONS=(syslog-ng hal @network @mpd !btnx !netfs slim)
Now making changes to this line will allow HAL to start up quickly once, but then it goes back to taking a long time. For example someone on the Arch IRC recommended that I add dbus before hal because it could not be starting fast enough or something. I did that and my next boot was super quick. I thought it was fixed but the next time it was back to slow. After a couple more slow starts I removed dbus from my daemons line and I got another fast startup. Again this only lasted once. Disabling btnx also gave me one fast startup.
Here is my bootchart:
Also on another note I don't know why btnx is still on my boot chart when it is disabled...
Last edited by Dethredic (2009-05-29 15:56:55)
Offline
same here.
dont know why.
Offline
ohh weird. No one I have really talked to has even heard of this problem
Offline
Hmm you can try hal-easy from AUR
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
Using it now. It is no faster. Its even slower on startup.
Offline
ammon, do you use btnx by any chance? Someone I talked to had the same problem and said btnx caused it. He was able to fix it but it was a while ago and he didn't remember how.
Offline
No. My sistem is very minimal. XFCE and tilda are only things I have on startup.
It takes 4-5 secs to reach deamon startup. And more 5-6 sec to xinit. I know that hal is to be blamed.
But i dont know how to fix it.
Offline
Ok, I guess so.
Is there a way to reconfigure it or clear it's config?
Offline
In hal-easy (in aur) ther is section i pkgbuild where is hal config. Dont know how could that help...
Offline
In hal-easy (in aur) ther is section i pkgbuild where is hal config. Dont know how could that help...
hmm, it won't let me instal hal-easy because hal is installed and it won't let me remove hal because lots of things depend on it.
Offline
sudo pacman -Rd hal
then try.
Offline
Well, Hal-easy only took like 15 seconds relative to the normal 20. Better, but still not a good solution.
Last edited by Dethredic (2009-06-06 19:54:12)
Offline
Ok, I wanted to see if Hal was giving any errors so I edited /etc/rc.d/hal
Inside that file you find a line that says "/usr/sbin/hald"
I changed that line to "/usr/sbin/hald --verbose yes --use-syslog" I restarted and hal didn't take forever. I checked the log and didn't find anything.
I tried again to be sure, and again hal started instantly and didn't give any errors.
I changed the line back to "/usr/sbin/hald". I rebooted and hal decided to take 20 seconds again. >.<
I am just going to leave it on "/usr/sbin/hald --verbose yes --use-syslog" and enjoy a quick startup.
EDIT: nvm, with "/usr/sbin/hald --verbose yes --use-syslog" I just got a long startup. =[
Here is the log: http://gunnewiek.com/up/everything.txt
I can't really see any errors, but someone else might be able to.
Last edited by Dethredic (2009-06-07 12:55:13)
Offline
Offline
Tried that --verbose yes --use-syslog and got same thing. Maybe a bit slower.
It's a long log, and I dont understand it. Look for [W] marks, they mean error.
Someone with more experience should see this.
Offline
Ok, I sent an e-mail to the hal mailing list because their IRC channel is not responsive. I will keep you updated.
Last edited by Dethredic (2009-06-10 20:18:45)
Offline
Pages: 1