Re: NetworkManager CVS detects bcm43xx as wired
Nope, since it turns out that your bcm43xx driver isn't advertising itself as a wireless device. At least, it certainly doesn't have any /sys/class/net/eth1/wireless directory. Which it should. So something with the driver seems broken. Ok, well it's already been established that the bcm43xx driver is pretty dodgy. I suppose I should be looking more in that direction then. If you "cat /sys/class/net/eth1/type", what do you get? It outputs: 1 Are there any bcm43xx messages in the output of 'dmesg'? running "dmesg | grep bcm43xx" gives me: bcm43xx driver bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled bcm43xx: PHY connected bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off bcm43xx: set security called bcm43xx:.level = 0 bcm43xx:.enabled = 0 bcm43xx:.encrypt = 0 bcm43xx: PHY connected bcm43xx: Radio turned on bcm43xx: Chip initialized bcm43xx: DMA initialized bcm43xx: 80211 cores initialized bcm43xx: Keys cleared bcm43xx: Radio turned off bcm43xx: DMA 0x0200 (RX) max used slots: 1/64 bcm43xx: DMA 0x0260 (TX) max used slots: 0/512 bcm43xx: DMA 0x0240 (TX) max used slots: 0/512 bcm43xx: DMA 0x0220 (TX) max used slots: 2/512 bcm43xx: DMA 0x0200 (TX) max used slots: 0/512 bcm43xx: PHY connected bcm43xx: Radio turned on bcm43xx: Chip initialized bcm43xx: DMA initialized bcm43xx: 80211 cores initialized bcm43xx: Keys cleared Just to make sure I don't get caught not including the right information again, I've included the full output of dmesg as an attachment. The card itself is working. Like I said, if I turn all encryption on the network off, it connects just fine. So I guess in that sense, NetworkManager is working fine. It's being told it's a wired card and if it doesn't have to deal with anything specific to wireless networks, then it runs the connect scripts like it's supposed to. Weird. So it's sounding more and more like a udev thing then. Good, I was beginning to think this was going to be easy. :-) dmesg.out Description: Binary data ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
On Mon, 2006-05-15 at 23:09 -0400, Dan Williams wrote: > Nope, since it turns out that your bcm43xx driver isn't advertising > itself as a wireless device. At least, it certainly doesn't have > any /sys/class/net/eth1/wireless directory. Which it should. So > something with the driver seems broken. > > If you "cat /sys/class/net/eth1/type", what do you get? Are there any > bcm43xx messages in the output of 'dmesg'? OK, I've changed the component on Fedora bug 191557 "hal identifies bcm43xx device as wired 802.3 device" from hal to kernel. (Red Hat guys: let me know if changing the component like this is against Bugzilla etiquette and I'll close it and file a new one.) James -- James Ettle[EMAIL PROTECTED] Southampton High Energy Physics School of Physics and Astronomy University of Southampton, SO17 1BJ PGP key ID: 03F94B5D --- signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
On Tue, 2006-05-16 at 00:25 +0100, Steven Cote wrote: > > > Actually, it doesn't, in the standardized manner NM expects it: > > > net.80211 set in info.category. > > Ah, well then, shows what I know. Ok, I went back and looked at the > output again, and I see what you're describing, I just didn't copy the > right part in. The entry right after what I had pasted goes on to > describe eth1 (my wireless card) and the info.category was set to > net.80203 > > > Can you attach the output of "tree /sys" to an email (don't paste it in) > > and send it to this list? > > Sure thing. Would the output of lshal be useful at all? Nope, since it turns out that your bcm43xx driver isn't advertising itself as a wireless device. At least, it certainly doesn't have any /sys/class/net/eth1/wireless directory. Which it should. So something with the driver seems broken. If you "cat /sys/class/net/eth1/type", what do you get? Are there any bcm43xx messages in the output of 'dmesg'? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
On Mon, 2006-05-15 at 14:24 -0400, Robert Love wrote: > On Mon, 2006-05-15 at 19:17 +0100, Steven Cote wrote: > > > It does say that it is a wireless card, here's the relevenat output that I > > get: > > Actually, it doesn't, in the standardized manner NM expects it: > net.80211 set in info.category. > > But I don't see net.8023 set, either, which is odd. > Might be initscripts+udev strangeness. I hear a new initscripts in updates might fix the issue of device renaming, which could be what this is. Can you attach the output of "tree /sys" to an email (don't paste it in) and send it to this list? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
On Mon, 2006-05-15 at 19:17 +0100, Steven Cote wrote: > It does say that it is a wireless card, here's the relevenat output that I > get: Actually, it doesn't, in the standardized manner NM expects it: net.80211 set in info.category. But I don't see net.8023 set, either, which is odd. Robert Love ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
I'm having the same problem. I'm using NetworkManager 0.6.2-2.fc5 and the bcm43xx driver from kernel 2.6.16-1.2111_FC5. Does 'lshal' show the device as having net.80211 capabilities? It does say that it is a wireless card, here's the relevenat output that I get: udi = '/org/freedesktop/Hal/devices/pci_14e4_4320' info.linux.driver = 'bcm43xx' (string) info.udi = '/org/freedesktop/Hal/devices/pci_14e4_4320' (string) linux.subsystem = 'pci' (string) linux.hotplug_type = 1 (0x1) (int) pci.subsys_product = 'Belkin F5D7001 High-Speed Mode Wireless G Network Card' (string) pci.subsys_vendor = 'Belkin' (string) info.product = 'BCM4306 802.11b/g Wireless LAN Controller' (string) pci.product = 'BCM4306 802.11b/g Wireless LAN Controller' (string) info.vendor = 'Broadcom Corporation' (string) pci.vendor = 'Broadcom Corporation' (string) pci.device_protocol = 0 (0x0) (int) pci.device_subclass = 128 (0x80) (int) pci.device_class = 2 (0x2) (int) pci.subsys_vendor_id = 6041 (0x1799) (int) pci.subsys_product_id = 28673 (0x7001) (int) pci.vendor_id = 5348 (0x14e4) (int) pci.product_id = 17184 (0x4320) (int) pci.linux.sysfs_path = '/sys/devices/pci:00/:00:10.0' (string) info.parent = '/org/freedesktop/Hal/devices/computer' (string) info.bus = 'pci' (string) linux.sysfs_path_device = '/sys/devices/pci:00/:00:10.0' (string) linux.sysfs_path = '/sys/devices/pci:00/:00:10.0' (string) Given that, do we know why it might be coming up as a wired card? I had the previous version of NetworkManager installed and it worked fine. Also, it will work now if I turn all encryption off on my wireless network. I'm not sure if that information helps, but there it is. If there's any other information you'd like me get for you, I'd be glad to do it. I'd love to see this bug fixed. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
On Fri, 2006-05-12 at 13:33 +0100, James Ettle wrote: > Dan, > > > Does 'lshal' show the device as having net.80211 capabilities? If not, > > then it's a udev+hal+driver issue that needs to get fixed. Sometimes > > the device name gets changed by udev, and hal doesn't quite know about > > it, so hal can't "connect the dots" in sysfs and figure out that the > > device is wireless. > > I don't have that notebook with me at the moment so I can't run lshal > (I'll post it later), but I do know that NM 0.6.2 from fedora-devel > works OK. I just pushed much the same version from fc5-updates-testing -> fc5-updates yesterday. Try that out, let us know how it works. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
Dan, > Does 'lshal' show the device as having net.80211 capabilities? If not, > then it's a udev+hal+driver issue that needs to get fixed. Sometimes > the device name gets changed by udev, and hal doesn't quite know about > it, so hal can't "connect the dots" in sysfs and figure out that the > device is wireless. I don't have that notebook with me at the moment so I can't run lshal (I'll post it later), but I do know that NM 0.6.2 from fedora-devel works OK. James -- James Ettle[EMAIL PROTECTED] Southampton High Energy Physics School of Physics and Astronomy University of Southampton, SO17 1BJ PGP key ID: 03F94B5D --- signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager CVS detects bcm43xx as wired
On Thu, 2006-05-11 at 22:44 +0100, James Ettle wrote: > Hi, > > I'm using the NM from CVS with bcm43xx from Fedora kernel > 2.6.16-1.2111_FC5. For some reason, it picks up the Broadcom wireless > card as a wired connection (see attached screenshot). Does 'lshal' show the device as having net.80211 capabilities? If not, then it's a udev+hal+driver issue that needs to get fixed. Sometimes the device name gets changed by udev, and hal doesn't quite know about it, so hal can't "connect the dots" in sysfs and figure out that the device is wireless. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
