Hi maro:
I tried your suggestion: using b43 driver instead.
I used a vanilla installation, where firmware-openfwwf.tcz is default.
Unfortunately, it still does not work.
Not even the wi-fi led is on!
Dmesg | tail -20 tells us why:
EXT4-fs (sdb1): mounting ext2 file system using the ext4 subsystem
EXT4-fs (sdb1): mounted filesystem without journal. Opts: (null)
Adding 2931824k swap on /dev/sda5. Priority:-2 extents:1 across:2931824k
cfg80211: Calling CRDA to update world regulatory domain
intel_rng: FWH not detected
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
intel_rng: FWH not detected
intel_rng: FWH not detected
intel_rng: FWH not detected
usb 3-2: new low speed USB device number 2 using uhci_hcd
input: Microsoft Microsoft Wireless Optical MouseĀ® 1.00 as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input8
generic-usb 0003:045E:00E1.0001: input: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical MouseĀ® 1.00] on usb-0000:00:1d.1-2/input0
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
]b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website .
I'm a little confused, so let me set the record straight:
- I thought that this firmware-openfwwf.tcz was the info obtained by the b43-fwcutter.tcz, right?
- If not so, then do I need to fetch additional info with b43-fwcutter-tools.tcz?
I've noticed, that there is another firmware-broadcom.tcz in the repos. Could that be used instead.? Are they mutually exclusive?
Your help will be highly appreciated.
cefcom.