Hal starting failure

skyraider · 2007-04-11 08:33:57

Hi,

Since the last Hal update, hal is unable to start. I have no errors about in /var/log... My kernel is a custom 2.6.18.8 release I have compiled myself (because of some bad things about my RT61 wifi driver, which does not want to compile with kernels above 2.6.18). Before hal update, it works fine, but now... it works only with the official kernel, but with a such kernel, there is no wifi.

Any idea ?
Thanks.

klixon · 2007-04-11 09:36:26

I have no solution for your hal issue, but i have a PKGBUILD for serialmonkey's rt61 driver. It's a CVS version, but works flawless on my custom 2.6.20.6.

I can post it here when i come home tonight, if you're interested. It gets you back on the track of new kernel-releases

If you don't want the CVS version and don't mind a ton more compiler warnings, you can also try the rt61 package in AUR. It has a patch with it that allows it to compile for a > 2.6.19.3 kernel

If you're unsure about how to use ABS, there's a nice wiki page about it
http://wiki.archlinux.org/index.php/ABS

skyraider · 2007-04-11 09:57:13

Ok... I think I'll try the rt61 package provided on AUR because I had a bad experience with the serialmonkey's driver (like freezes). Thanks for this idea - the last time I have search the rt61 driver on AUR, it was not "2.6.20 ready", but today it seems to be up to date.

klixon · 2007-04-11 10:08:25

If you're referring to the rt2x00 driver, you could be right. I've never tried that one...
I'm referring to the rt61 driver, which is a cleaned up version of the original ralink-driver. Anyway, either will work.

Hope you get it working!

skyraider · 2007-04-11 10:11:18

By the way, I think there is a bug in the /usr/bin/netcfg script about wifi.
When I use network profiles, when network starts, I get an error about "ra0" (my wifi card) because when netcfg try to do an iwconfig, the network interface is down. In other words, no "ifconfig ra0 up" is done. The only solution I found is to change the "ifconfig" position directly into the netcfg script ("ifconfig" is in an "if" condition which tests whether the wpa mode is required or not, by I don't use wpa so ifconfig is never done).

Is it a know bug ?

klixon · 2007-04-11 10:27:08

I have no idea. I never use network-profiles or the netcfg-script.
I just add

ra0="ra0 xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast xxx.xxx.xxx.255"

to /etc/rc.conf
I do all my wireless configuration (wpapsk 2 with AES encryption) in /etc/Wireless/RT61STA/rt61sta.dat

easy as hell and works like a charm... but then, I only ever connect my box to 1 AP

skyraider · 2007-04-11 10:35:10

In my case I connect my laptop to different networks (adhoc, ap), and always with dhcp. So, network profiles are very useful !

mangus · 2007-04-13 08:57:03

skyraider wrote:

Hi,
Since the last Hal update, hal is unable to start. I have no errors about in /var/log... My kernel is a custom 2.6.18.8 release I have compiled myself (because of some bad things about my RT61 wifi driver, which does not want to compile with kernels above 2.6.18). Before hal update, it works fine, but now... it works only with the official kernel, but with a such kernel, there is no wifi.
Any idea ?
Thanks.

For the hal issue You may want to try to recompile your kernel including inotify support that is requested by hal 0.5.9.
This solved my hal issue with my custom kernel..
HTH cheers
Fede

skyraider · 2007-04-13 12:07:29

Ok, I'll try this method. Yesterday, I tried the rt61 AUR package, which works as well as klixon said, except with iwconfig (however it is possible to do same things with iwpriv). But for an unknown reason, when my PC lose the connection (eg. I was too far from the AP), the kernel freezes. The only way I found to solve this mistake is to compile my own kernel directly from kernel.org (a 2.6.18, because even with a custom 2.6.20 I have the problem). I don't know why it works with a vanilla 2.6.18, and why not with a vanilla 2.6.20... but it works !

And it would be better if hal works too...

Last edited by skyraider (2007-04-13 12:10:22)

klixon · 2007-04-13 13:34:20

I'll put my rt61_cvs into AUR when i get home tonight, so you can check that. It's essentially a cleaned-up version of the original ralink drivers.
You should realy give it a spin... if you don't like it, you can alway pacman -R it

skyraider · 2007-04-16 09:36:09

Ok, thanks, I'll try it.

klixon · 2007-04-16 09:43:44

Sorry man, had some emergencies this weekend... Will post tomorrow

klixon · 2007-04-17 21:07:12

ok... if you want to give it a try, i just uploaded "rt61-cvs" to AUR
Just remember to re-makepkg it on every kernel-update, but i guess you're already familiar with that procedure

Arch Linux

#1 2007-04-11 08:33:57

Hal starting failure

#2 2007-04-11 09:36:26

Re: Hal starting failure

#3 2007-04-11 09:57:13

Re: Hal starting failure

#4 2007-04-11 10:08:25

Re: Hal starting failure

#5 2007-04-11 10:11:18

Re: Hal starting failure

#6 2007-04-11 10:27:08

Re: Hal starting failure

#7 2007-04-11 10:35:10

Re: Hal starting failure

#8 2007-04-13 08:57:03

Re: Hal starting failure

#9 2007-04-13 12:07:29

Re: Hal starting failure

#10 2007-04-13 13:34:20

Re: Hal starting failure

#11 2007-04-16 09:36:09

Re: Hal starting failure

#12 2007-04-16 09:43:44

Re: Hal starting failure

#13 2007-04-17 21:07:12

Re: Hal starting failure

Board footer