Hi Edwin,

This is the udev bug I discovered last night.  Use the following hack:

sed -i -e "s/ath/Ath/" /etc/udev/rules.d/z45_persistent-net-generator.rules

and remove /etc/udev/z25_persistent-net.rules, reboot

Please test with the latest voyage-current and voyage-0.3pre1 just released.

Regards,
Punky

Edwin Whitelaw wrote:
I've got a 233 MHz WRAP 2E running the 0.3 (Nov 16) release with 2 Atheros cards, 1 CM9 and 1 WLM54G.

Everything loads fine and both cards are detected w/o errors, the CM9 showing up as wifi0 and the WLM54G is wifi1.

The strangeness is that I cannot assign wifi0 to ath0 either through the interface file or running wlanconfig manually (wlanconfig returns ath0 when executed but iwconfig subsequently shows it created as ath1). If I map wifi0 to ath1 it loads perfectly. I've tried this with only the CM9 installed and also with the second card. Oddly enough, with the second card installed, I can now assign wifi1 to ath0.

Why can I not map wifi0 --> ath0 and wifi1 --> ath1?

Obviously, I can make the current arrangement work fine but would like to know why the "cross" assignment works and where this is determined. I do not have the problem in 0.2.

BTW, it now seems that the hostname in 0.3 is set by editing /etc/hostname directly rather than using /ro/etc/hostname as was the case for 0.2. Not a big deal, but different in any case.

Edwin

_______________________________________________
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux


--


P U N K N ! X  . c o m
Technology + Lifestyle
(http://www.punknix.com)

V O Y A G E . H K - http://www.voyage.hk
Linux - voyage-0.2 is released!
Store - New low price for Senao NMP-8602 Plus (400mW)!


_______________________________________________
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux

Reply via email to