On Fri, 2006-11-10 at 23:03 -0500, Andrew Robinson wrote: > After upgrading my laptop from FC4 to FC6, I'm trying to configure > bcm43xx. So far, no luck. I'm hoping someone can help me figure out what > I'm doing wrong. > > Thanks! > > Andrew Robinson > > > bcm43xx-cutter -w /lib/firmware bcmwl564.sys > > ls /lib/firmware > bcm43xx_initval01.fw bcm43xx_initval04.fw bcm43xx_initval07.fw > bcm43xx_initval10.fw bcm43xx_microcode5.fw bcm43xx_initval02.fw > bcm43xx_initval05.fw bcm43xx_initval08.fw bcm43xx_microcode2.fw > bcm43xx_pcm4.fw bcm43xx_initval03.fw bcm43xx_initval06.fw > bcm43xx_initval09.fw bcm43xx_microcode4.fw bcm43xx_pcm5.fw > > >> from modprobe.conf << > alias eth1 bcm43xx > > >> from /var/log/messages << > kernel: bcm43xx: Radio turned off > kernel: bcm43xx: DMA-32 0x0200 (RX) max used slots: 0/64 > kernel: bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 > kernel: bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 > kernel: bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 > kernel: bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 > kernel: bcm43xx: DMA-32 0x0220 (TX) max used slots: 2/512 > kernel: bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 > kernel: ACPI: PCI interrupt for device 0000:00:0c.0 disabled > kernel: bcm43xx driver > kernel: PCI: Enabling device 0000:00:0c.0 (0000 -> 0002) > kernel: ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 18 (level, low) -> > IRQ 201 > kernel: bcm43xx: Chip ID 0x4306, rev 0x3 > kernel: bcm43xx: Number of cores: 5 > kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled > kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled > kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled > kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled > kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled > kernel: bcm43xx: PHY connected > kernel: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 > kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) > kernel: bcm43xx: Radio turned off > kernel: bcm43xx: Radio turned off > kernel: SoftMAC: ASSERTION FAILED (0) at: > net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate() > kernel: bcm43xx: set security called, .active_key = 0, .level = 1, > .enabled = 1, .encrypt = 1 > kernel: SoftMAC: Associate: Scanning for networks first. > kernel: SoftMAC: Associate: failed to initiate scan. Is device up? > kernel: bcm43xx: PHY connected > kernel: bcm43xx: Microcode rev 0x118, pl 0x17 (2004-05-06 21:34:00) > kernel: bcm43xx: Radio turned on > kernel: bcm43xx: Chip initialized > kernel: bcm43xx: 32-bit DMA initialized > kernel: bcm43xx: Keys cleared > kernel: bcm43xx: Selected 802.11 core (phytype 2) > kernel: SoftMAC: Associate: Scanning for networks first. > kernel: SoftMAC: Start scanning with channel: 1 > kernel: SoftMAC: Scanning 14 channels > kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready > kernel: SoftMAC: Scanning finished > kernel: SoftMAC: Associate: Scanning for networks first. > kernel: SoftMAC: Start scanning with channel: 1 > kernel: SoftMAC: Scanning 14 channels > kernel: SoftMAC: Unable to find matching network after scan! > kernel: SoftMAC: Scanning finished > kernel: SoftMAC: Associate: Scanning for networks first. > kernel: SoftMAC: Start scanning with channel: 1 > kernel: SoftMAC: Scanning 14 channels > kernel: SoftMAC: Scanning finished > kernel: SoftMAC: Associate: Scanning for networks first. > kernel: SoftMAC: Start scanning with channel: 1 > kernel: SoftMAC: Scanning 14 channels > kernel: SoftMAC: Scanning finished > kernel: SoftMAC: Associate: Scanning for networks first. > kernel: SoftMAC: Start scanning with channel: 1 > kernel: SoftMAC: Scanning 14 channels > kernel: SoftMAC: Scanning finished > kernel: SoftMAC: Unable to find matching network after scan! > avahi-daemon[2513]: New relevant interface eth1.IPv4 for mDNS. > avahi-daemon[2513]: Joining mDNS multicast group on interface eth1.IPv4 > with address 192.168.1.101. > avahi-daemon[2513]: Registering new address record for 192.168.1.101 on > eth1. > > > iwlist eth1 scan > eth1 No scan results > > > Why dont you try ndiswrapper and windows driver. It works great for me. I can give you full how-to (How I did) if you need. Or otherwise you can try it yourself. its quite easy. -- Thanx Pritam Ghanghas
