Hi Saifi, The firmware was installed. However when I boot the machine it still tries to bring up net.eth0. (This happens even if the cable is not connected)
Namita On Thursday 24 July 2008 08:47:49 Saifi Khan wrote: > Hi Namita: > > b43-fwcutter needs to work with a blob like > broadcom-wl-4.80.53.0 > wl_apsta-3.130.20.0.o > bcmwl5.sys (cabextract from sp34152.exe) > > The dmesg log should like this: > > $dmesg | grep bcm43xx > > kobject bcm43xx: registering. parent: <NULL>, set: module > kobject holders: registering. parent: bcm43xx, set: <NULL> > fill_kobj_path: path = '/module/bcm43xx' > kobject notes: registering. parent: bcm43xx, set: <NULL> > bcm43xx driver > bus pci: add driver bcm43xx > kobject bcm43xx: registering. parent: <NULL>, set: drivers > fill_kobj_path: path = '/bus/pci/drivers/bcm43xx' > pci: Matched Device 0000:06:00.0 with Driver bcm43xx > pci: Probing driver bcm43xx with device 0000:06:00.0 > bcm43xx: Chip ID 0x4311, rev 0x1 > bcm43xx: Number of cores: 4 > bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243 > bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243 > bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243 > bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243 > bcm43xx: PHY connected > bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 8 > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) > bcm43xx: Radio initialized > bcm43xx: Radio initialized > bound device '0000:06:00.0' to driver 'bcm43xx' > pci: Bound Device 0000:06:00.0 to Driver bcm43xx > kobject drivers: registering. parent: bcm43xx, set: <NULL> > > After the log shows pci device bound to driver bcm43xx, > again we need to check the log and it should show. > > bcm43xx: PHY connected > bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) > bcm43xx: Radio turned on > bcm43xx: Radio enabled by hardware > bcm43xx: Chip initialized > bcm43xx: 32-bit DMA initialized > bcm43xx: Keys cleared > bcm43xx: Selected 802.11 core (phytype 2) > bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = > 0 > > I think that in most of the cases, the above set of lines > are not seen in the log, in which case the second command > below will give error like: > > # iwconfig eth1 essid "NETGEAR" > # iwconfig eth1 txpower on > > Error for wireless request "Set Tx Power" (8B27) : > GET failed on device eth1 ; No such device. > > In short, the firmware blob did not work :-( > > Let's troubleshoot this. > > thanks > Saifi. >
