Re: [Bcm43xx-dev] Link LED not working on cardbus Linksys WPC54G
Larry Finger wrote: > Mike, > > The driver I'm running is bcmwl5.sys, version 3.100.64.0. As our > hardware is identical, this one should work for you. > > Larry > Ok...I got a driver matching this version from the list posted on the ndiswrapper website. I still get pretty much the same results. Should I take this back to the fedora list?: Feb 11 01:47:58 localhost kernel: pccard: card ejected from slot 0 Feb 11 01:47:58 localhost kernel: bcm43xx: unable to switch to core 0, retried 12 times Feb 11 01:48:07 localhost kernel: pccard: CardBus card inserted into slot 0 Feb 11 01:48:07 localhost kernel: PCI: Enabling device :03:00.0 ( -> 0002) Feb 11 01:48:07 localhost kernel: ACPI: PCI Interrupt :03:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 Feb 11 01:48:07 localhost kernel: bcm43xx: Chip ID 0x4306, rev 0x2 Feb 11 01:48:07 localhost kernel: bcm43xx: Number of cores: 6 Feb 11 01:48:07 localhost kernel: bcm43xx: Core 0: ID 0x800, rev 0x2, vendor 0x4243, enabled Feb 11 01:48:07 localhost kernel: bcm43xx: Core 1: ID 0x812, rev 0x4, vendor 0x4243, disabled Feb 11 01:48:07 localhost kernel: bcm43xx: Core 2: ID 0x80d, rev 0x1, vendor 0x4243, enabled Feb 11 01:48:07 localhost kernel: bcm43xx: Core 3: ID 0x807, rev 0x1, vendor 0x4243, disabled Feb 11 01:48:07 localhost kernel: bcm43xx: Core 4: ID 0x804, rev 0x7, vendor 0x4243, enabled Feb 11 01:48:07 localhost kernel: bcm43xx: Core 5: ID 0x812, rev 0x4, vendor 0x4243, disabled Feb 11 01:48:07 localhost kernel: bcm43xx: Ignoring additional 802.11 core. Feb 11 01:48:07 localhost kernel: bcm43xx: PHY connected Feb 11 01:48:07 localhost kernel: bcm43xx: Detected PHY: Version: 1, Type 2, Revision 1 Feb 11 01:48:07 localhost kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) Feb 11 01:48:07 localhost kernel: bcm43xx: Radio turned off Feb 11 01:48:07 localhost kernel: bcm43xx: Radio turned off Feb 11 01:48:07 localhost kernel: bcm43xx: set security called Feb 11 01:48:07 localhost kernel: bcm43xx:.level = 0 Feb 11 01:48:07 localhost kernel: bcm43xx:.enabled = 0 Feb 11 01:48:07 localhost kernel: bcm43xx:.encrypt = 0 Feb 11 01:48:07 localhost kernel: SoftMAC: Associate: Scanning for networks first. Feb 11 01:48:07 localhost kernel: SoftMAC: Associate: failed to initiate scan. Is device up? Feb 11 01:48:07 localhost kernel: bcm43xx: PHY connected Feb 11 01:48:07 localhost kernel: bcm43xx: PHY disconnected Feb 11 01:48:07 localhost kernel: bcm43xx: PHY connected Feb 11 01:48:07 localhost kernel: bcm43xx: Radio turned on Feb 11 01:48:07 localhost kernel: bcm43xx: Chip initialized Feb 11 01:48:08 localhost kernel: bcm43xx: DMA initialized Feb 11 01:48:08 localhost kernel: bcm43xx: 80211 cores initialized Feb 11 01:48:08 localhost kernel: bcm43xx: TODO: Incomplete code in keymac_write() at drivers/net/wireless/bcm43xx/bcm43xx_main.c:1265 Feb 11 01:48:08 localhost last message repeated 7 times Feb 11 01:48:08 localhost kernel: bcm43xx: TODO: Incomplete code in keymac_write() at drivers/net/wireless/bcm43xx/bcm43xx_main.c:1267 Feb 11 01:48:08 localhost last message repeated 3 times Feb 11 01:48:08 localhost kernel: bcm43xx: Keys cleared Feb 11 01:48:08 localhost kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready Feb 11 01:48:08 localhost kernel: bcm43xx: set security called Feb 11 01:48:08 localhost kernel: bcm43xx:.level = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.enabled = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.encrypt = 0 Feb 11 01:48:08 localhost kernel: bcm43xx: set security called Feb 11 01:48:08 localhost kernel: bcm43xx:.level = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.enabled = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.encrypt = 0 Feb 11 01:48:08 localhost kernel: bcm43xx: set security called Feb 11 01:48:08 localhost kernel: bcm43xx:.level = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.enabled = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.encrypt = 0 Feb 11 01:48:08 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 Feb 11 01:48:08 localhost kernel: bcm43xx: set security called Feb 11 01:48:08 localhost kernel: bcm43xx:.level = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.enabled = 0 Feb 11 01:48:08 localhost kernel: bcm43xx:.encrypt = 0 Feb 11 01:48:08 localhost kernel: slab error in cache_free_debugcheck(): cache `size-512': double free, or memory outside object was overwritten Feb 11 01:48:08 localhost kernel: [] cache_free_debugcheck+0xc5/0x198 [] wireless_process_ioctl+0x543/0x5bd Feb 11 01:48:08 localhost kernel: [] kfree+0x49/0x79 [] wireless_process_ioctl+0x543/0x5bd Feb 11 01:48:08 localhost kernel: [] bcm43xx_wx_sprom_write+0x0/0x39a [bcm43xx] [] dev_ioctl+0x472/0x4ab Feb 11 01:48:08 localhost kernel: [] __handle_mm_fault+0x41d/0x7c3 [] sock_map_file+0x8b/0xf9 Feb 11 01:48:08 localhost kernel: [] sock_ioctl+0x0/0x232 [] do_ioctl+0x16/0x48 Feb 11 01:4
Re: [Bcm43xx-dev] Link LED not working on cardbus Linksys WPC54G
I'm still a no-go with this driver. I'm now using the kernel build #1928 released today for FC5, and I can only get as far as scanning. Larry suggested to me that I run a memory test...that's done (3 passes), and no errors were found. So, we're hoping someone on this list can add further insight - maybe somebody can explain the slab error, or messages related to 'sprom' in the kernel output... Among other things, I also notice that the LED indicator stays on while trying to connect, and turns off when not trying to connect - so I guess that's to be expected (given the topic that I chose to join-in on). Could it also be a problem with the firmware drivers that I installed using the fwcutter tool? The instructions for ndiswrapper indicated not to use the actual drivers distributed with the hardware, but find some drivers online that match the chipset. Should I instead turn to the default linksys-brand drivers? I guess I'll give that a try next... Here's what I get with ifconfig: eth1 Link encap:Ethernet HWaddr 00:06:25:40:4C:53 inet6 addr: fe80::206:25ff:fe40:4c53/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:151 errors:0 dropped:129 overruns:0 frame:0 TX packets:167 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9862 (9.6 KiB) TX bytes:9372 (9.1 KiB) Interrupt:10 Base address:0x4000 And with iwconfig: eth1 IEEE 802.11b/g ESSID:"mgl2" Nickname:"localhost.localdomain" Mode:Master Frequency=2.437 GHz Access Point: 00:0F:66:36:80:07 Bit Rate=54 Mb/s RTS thr:off Fragment thr:off Encryption key:off and the info for my router from iwlist: Cell 03 - Address: 00:0F:66:36:80:07 ESSID:"mgl2" Protocol:IEEE 802.11bg Mode:Master Channel:6 Encryption key:off Bit Rate:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Quality=100/100 Signal level=-31 dBm Extra: Last beacon: 276ms ago I'm getting a bunch of other routers detected, but all have weak signals, and since mine isn't even encrypted now, it shouldn't be an issue. All the info looks correct. I had originally been using WPA-PSK encryption, so I turned that off. Now, here are the system logs I'm getting when I unplug the card, then plug it back in, and run the following commands: sudo /sbin/ifconfig eth1 down sudo /sbin/ifconfig eth1 up sudo /sbin/iwlist scan sudo /sbin/iwconfig eth1 essid mgl2 key off mode master txpower auto ap 00:0F:66:36:80:07 Feb 11 00:26:15 localhost kernel: pccard: card ejected from slot 0 Feb 11 00:26:15 localhost kernel: bcm43xx: unable to switch to core 0, retried 12 times Feb 11 00:26:29 localhost kernel: pccard: CardBus card inserted into slot 0 Feb 11 00:26:29 localhost kernel: PCI: Enabling device :03:00.0 ( -> 0002) Feb 11 00:26:29 localhost kernel: ACPI: PCI Interrupt :03:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 Feb 11 00:26:29 localhost kernel: bcm43xx: Chip ID 0x4306, rev 0x2 Feb 11 00:26:29 localhost kernel: bcm43xx: Number of cores: 6 Feb 11 00:26:29 localhost kernel: bcm43xx: Core 0: ID 0x800, rev 0x2, vendor 0x4243, enabled Feb 11 00:26:29 localhost kernel: bcm43xx: Core 1: ID 0x812, rev 0x4, vendor 0x4243, disabled Feb 11 00:26:29 localhost kernel: bcm43xx: Core 2: ID 0x80d, rev 0x1, vendor 0x4243, enabled Feb 11 00:26:29 localhost kernel: bcm43xx: Core 3: ID 0x807, rev 0x1, vendor 0x4243, disabled Feb 11 00:26:29 localhost kernel: bcm43xx: Core 4: ID 0x804, rev 0x7, vendor 0x4243, enabled Feb 11 00:26:29 localhost kernel: bcm43xx: Core 5: ID 0x812, rev 0x4, vendor 0x4243, disabled Feb 11 00:26:29 localhost kernel: bcm43xx: Ignoring additional 802.11 core. Feb 11 00:26:29 localhost kernel: bcm43xx: PHY connected Feb 11 00:26:29 localhost kernel: bcm43xx: Detected PHY: Version: 1, Type 2, Revision 1 Feb 11 00:26:29 localhost kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) Feb 11 00:26:29 localhost kernel: bcm43xx: Radio turned off Feb 11 00:26:29 localhost kernel: bcm43xx: Radio turned off Feb 11 00:26:29 localhost kernel: bcm43xx: set security called Feb 11 00:26:29 localhost kernel: bcm43xx:.level = 0 Feb 11 00:26:29 localhost kernel: bcm43xx:.enabled = 0 Feb 11 00:26:29 localhost kernel: bcm43xx:.encrypt = 0 Feb 11 00:26:29 localhost kernel: SoftMAC: Associate: Scanning for networks first. Feb 11 00:26:29 localhost kernel: SoftMAC: Associate: failed to initiate scan. Is device up? Feb 11 00:26:29 localhost kernel: bcm43xx: PHY connected Feb 11 00:26:29 localhost kernel: bcm43xx: PHY disconnected Feb 11 00:26:29 localhost kernel: bcm43xx: PHY connected Feb 11 00:26:29 localhost kernel: bcm43xx: Radio turned on Feb 11 00:2
Re: [Bcm43xx-dev] Link LED not working on cardbus Linksys WPC54G
Mike Leahy wrote: List, Is there something I need to do after installing the kernel with the driver? See below. When I run iwconfig, I get this: eth1 IEEE 802.11b/g ESSID:"Auto" Nickname:"localhost.localdomain" Mode:Managed Frequency=2.437 GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate=1 Mb/s RTS thr:off Fragment thr:off Encryption key:off When I try to set the txpower: sudo /sbin/iwconfig eth1 txpower auto Error for wireless request "Set Tx Power" (8B26) : SET failed on device eth1 ; No such device. This is the message you get if the interface is down. Have you done an 'ifup eth1'? Check ifconfig for UP in the flags. If I try to scan with iwlist: eth1 Interface doesn't support scanning : No such device Same problem. The interface is not up. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Failed to suspend mac
On Wed, 2006-02-08 at 18:35 +0100, Michael Buesch wrote: > Johannes, what is your opinion on that. Does the original driver also > implement a mutex here? Not as far as I can see. johannes signature.asc Description: This is a digitally signed message part
