puredyne-team team mailing list archive

[Aymeric Mansoux <aymeric@xxxxxxxxxx>]

We are turning this bug into a question as it seems this is more related
to installation troubleshooting and process rather than reporting a
defect.

Please let us know if you need further help using the "Hardware Drivers"
feature, in the system menu.

** Changed in: puredyne-live
       Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/puredyne-live/+question/105394

-- 
broadcom wireless driver - b43-fwcutter
https://bugs.launchpad.net/bugs/510115
You received this bug notification because you are a member of puredyne
team, which is the registrant for Puredyne Live.

Status in Puredyne liveCD/DVD/USB/HD: Invalid

Bug description:
Hia, still a bit unclear, but someone reports on the IRC channel to have issues with:

10:11 < fubs> hey, has anyone tried to get a broadcom based wirless working?
10:12 < fubs> driver is loaded... don't see an eth name related to it tho when running dmesg
11:09 < fubs> hah it already says when starting
11:09 < fubs> found unsupported phy..bla b43
11:13 < fubs> b43-phy0 
11:13 < fubs> b43: probe of ssb0:0 failed with error -95
11:25 < fubs> i reinstalled b43-fwcutter
11:25 < fubs> it works with that in my ubuntu netbook version 
11:32 < fubs> just reinstalled network-manager too
11:33 < fubs> no complaining about firmware either
11:33 < fubs> and it's where it's supposed to be
11:34 < fubs> jeh it just comes when running the init stuff with .. ERROR found unsuppoerted blabla
11:39 < fubs> and also hardware drivers app says.. this driver is activated and currently in use

12:03 < fubs> i'll try to compile broadcom's driver
12:08 < fubs> that worked
12:11 < fubs> there was no wl.ko :D


Im reporting this cause i saw the broadcom card of a friend not being loaded also... will have to replicate the issue next time i meet him.