Johannes Berg wrote: >>> wlan0_rename IEEE 802.11g ESSID:"" >>> Mode:Managed Channel:0 Access Point: Not-Associated >>> Tx-Power=0 dBm >>> Retry min limit:7 RTS thr:off Fragment thr=2346 B >>> Encryption key:off >>> Link Quality:0 Signal level:0 Noise level:0 >>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> That's a bug in your udev rules. Search the archives for this list, >> Larry recently posted a very long and detailed explanation. > > Meanwhile, you can of course use wlan0_rename just fine. Or rename it: > > ip link set eth1 name wmaster0 > ip link set wlan0_rename name eth1 > > johannes
Thanks to you all, this email is reaching you via my wireless interface :-) Johannes, I edited the udev rules and then realized I also need to have firmware :) Did that. Things good. But one problem still remains. When I boot in, the b43 modules does not load. It complains : [ 42.660654] ssb: Sonics Silicon Backplane found on PCI device 0000:0c:00.0 [ 53.325307] b43: disagrees about version of symbol ssb_device_is_enabled [ 53.325313] b43: Unknown symbol ssb_device_is_enabled [ 53.325466] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable [ 53.325468] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable [ 53.325553] b43: disagrees about version of symbol ssb_bus_may_powerdown [ 53.325555] b43: Unknown symbol ssb_bus_may_powerdown < and more similar lines....> So to load the module, I have to : [EMAIL PROTECTED]:/home/shouryas# rmmod ssb; modprobe b43 and then I get the wireless stuff fine. Any thoughts on why at boot time the module linking would fail but happen OK subsequently ? Anyway, thanks to Larry and you for your help. Shourya _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
