On Thu, 13 Dec 2007 18:09:26 -0800 Larry Finger <[EMAIL PROTECTED]> wrote:
> Michael Buesch wrote: > > On Friday 14 December 2007 01:05:00 Ray Lee wrote: > >> Okay, I had to modprobe rfkill-input and rfkill by hand, didn't > >> realize that. Hopefully that'll be automatic soon. Regardless, upon > >> doing so, and loading ssb and b43, it sees my card, but is still not > >> fully functional. iwconfig sees: > >> > >> lo no wireless extensions. > >> eth0 no wireless extensions. > >> tun0 no wireless extensions. > >> eth1 no wireless extensions. > >> 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 > >> 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 > >> > >> (eth0 is ethernet, eth1 doesn't exist -- usually it's the wireless.) > >> > >> `ifconfig` doesn't see eth1 or wlan0_rename. > >> > >> What else might I be doing wrong? > > Your udev rules are screwed up. In /etc/udev/rules.d/70-persistent-net.rules, > you should have a line > that looks like > > SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1a:73:6b:28:5a", > ATTR{type}=="1", NAME="eth1" > > with the MAC address for your device. You probably have the ATTR{type}=="1" > clause missing. I have a 4318, which I've been using for some time with ndiswrapper (bcm43xx doesn't work very well with it, you know and as I've reported on this list). I finally decided to take the plunge and try b43, so I installed 2.6.24-rc4 (vanilla from kernel.org), and began getting chaos, similar to the OP's. I pretty much gave up, when I saw your suggestion that the problem is broken udev rules. Sure enough, here is (was) my persistent-net.rules: # This file was automatically generated by the /lib/udev/write_net_rules # program, probably run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # MAC addresses must be written in lowercase. # PCI device 0x14e4:0x4318 (bcm43xx) SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:19:7d:06:a5:44", NAME="eth0" # PCI device 0x14e4:0x170c (b44) SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:16:d4:5e:1e:9c", NAME="eth1" # PCI device 0x168c:0x0013 (ath_pci) SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:40:f4:e5:07:7e", ATTRS{type}=="1", NAME="ath0" The two Broadcom lines (wired and wireless cards builtin to my Acer Aspire 3690-2672 laptop) don't contain the 'ATTRS{type}=="1"' clause, while the Atheros line (for a PCMCIA card) does. Adding the clause to the Broadcom wireless line fixed the problem, and it now seems to be working perfectly (no screen flicker, which I had seen with bcm43xx), so thanks. My questions: A) I have only a very basic understanding of udev; what does that clause mean? I couldn't figure it out by googling or looking in the basic udev docs. B) I'm running Debian Sid; I assume the installer wrote the builtin cards' lines and the running system the subsequently inserted PCMCIA line. Is this a bug? Do you know where I should report it? I have never (until my addition of your clause) touched the ruls file. C) I wasn't seeing this device naming problem with my old kernels (2.6.18 - 2.6.22) and bcm43xx / ndiswrapper. Is this a 2.6.24 thing, or a b43 thing, or some combination thereof, or something else entirely? Thanks to you and all the devs for all your Broadcom work! > Larry Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev