Comment 7 for bug 202567
Revision history for this message
| tatojo (manuel-mlmateos) wrote Re: [Bug 202567] Re: restricted manager in hardy fails to install correct firmware b43-fwcutter - solution | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
You are right el es!
I just ran, from directory
/root/broadcom-
The command
sudo /usr/bin/
and worked fine.
This message is wireless going with the new b43 driver in a bcm4318 [Air
Force One 54g] 802.11g in a Acer-Ferrari-4000, Hardy-server-86_64.
Manuel
el es wrote:
> tatojo: Don't build a new fwcutter - the one from Hardy is OK
> Whenever you have the distupgrade ready, the b43-fwcutter package is installed (at least it was on my Acer 3023WLMi)
>
> It is enough to just run it as I stated above. (by means it worked for
> me OK)
>
> The problem is only I don't know exactly where the firmware should be
> extracted - so I did the above both for /lib/firmware and
> /lib/firmware/
>
> Ah. One thing : use the 2.6.24 kernel that comes with hardy. b43 is only
> there.
>
> (it was frankly the reason I went on to Hardy instead of staying with
> Gutsy)
>
> ** Description changed:
>
> Ubuntu Hardy 8.04 latest beta just after upgrade from Gutsy.
>
> The Broadcom firmware is wrong for the used b43 driver.
>
> http://
>
> - As the b43-fwcutter version is correct (011)
> + As the b43-fwcutter *package* version is correct (011) you don't need to
> + build it again!
>
> To make the b43 driver running you need to do
>
> - export FIRMWARE_
> - /lib/firmware/
> + export FIRMWARE_
> + -r`
>
> (i have actually done it on both paths, don't know where it should
> really go)
>
> wget http://
> tar xjf broadcom-
> cd broadcom-
>
> # as the b43-fwcutter package is installed, this
> - b43-fwcutter-
> + b43-fwcutter -w "$FIRMWARE_
> + has just worked.
>
> - I have an Acer 3023WLMi and from the previous Gutsy installation, it has the acer-acpi package.
> - I do it in recovery mode, and when leaving it, going into normal X session, the card just starts working normally.
> + I have an Acer 3023WLMi and from the previous Gutsy installation, it has
> + the acer-acpi package.
>
> - (in recovery mode, because I need to fix the sudo, but that is a topic
> - for different bug actually...)
> + Whenever you have the sudo fixed, might be that if you do it, your
> + Network Manager daemon will just modprobe the b43 module and everything
> + starts working. If not, a reboot will be needed.
> +
> + I did it in recovery mode, and when leaving it, going into normal X
> + session, the card just started working normally.
>
> ** Description changed:
>
> Ubuntu Hardy 8.04 latest beta just after upgrade from Gutsy.
>
> The Broadcom firmware is wrong for the used b43 driver.
> + For Hardy's 2.6.24.x kernel we need to use the 'non-bleeding-edge' firmware.
>
> + The solution is here :
> http://
>
> - As the b43-fwcutter *package* version is correct (011) you don't need to
> - build it again!
> + As the b43-fwcutter *from*package* version is correct (011) you don't need to build it again as described.
> + There is no need to compile anything.
>
> To make the b43 driver running you need to do
>
> export FIRMWARE_
> -r`
>
> - (i have actually done it on both paths, don't know where it should
> - really go)
> + (FIXME!!! i have actually done it on both paths, don't know where it
> + should really go)
>
> wget http://
> tar xjf broadcom-
> cd broadcom-
>
> # as the b43-fwcutter package is installed, this
> - b43-fwcutter -w "$FIRMWARE_
> - has just worked.
> + sudo b43-fwcutter -w "$FIRMWARE_
> + has just worked.[1]
>
> I have an Acer 3023WLMi and from the previous Gutsy installation, it has
> the acer-acpi package.
>
> Whenever you have the sudo fixed, might be that if you do it, your
> Network Manager daemon will just modprobe the b43 module and everything
> starts working. If not, a reboot will be needed.
>
> - I did it in recovery mode, and when leaving it, going into normal X
> - session, the card just started working normally.
> + [1] I did it in recovery mode, without sudo, and when leaving it, going
> + into normal X session, the card just started working normally.
>
>