I can confirm that this does work :
Going under package manager, selecting completely remove the
b43-fwcutter package, and then installing it again does fix my wireless.
Looks like it's just the initial setup under System Administration
Hardware Drivers that somehow fails to get the firmware
I can confirm this bug on my laptop under hardy alpha 6. I have the
bcm4318 card. If i use the restricted hardware manager and enable the
driver it downloads and installs fine but does not work even after a
reboot. Going under package manager, selecting completely remove the
b43-fwcutter package,
And manually installing the firmware did not work either? Hm. What kind
of chip are you using? Looking at
http://linuxwireless.org/en/users/Drivers/b43/ shows, that not all
broadcom devices are supported. Could you please attach the output of
'lspci -vvnn'?
--
broadcom wireless not working fresh
Manual removal of the firmware supplied by Hardy's fwcutter package, and
then manual removal of Hardy's fwcutter package itself, followed by manual
installation of the fwcutter package referenced on the site I have listed in
my original post, followed by running that fwcutter package/program, DOES
Relevant output of lspci -vvnn :
03:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan
mini-PCI [14e4:4311] (rev 01)
Subsystem: Hewlett-Packard Company Unknown device [103c:1363]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+
Did you also try to perform these steps manually with the b43-fwcutter
package provided by Hardy (see my post above)? Trying this would give an
idea of it is a) a problem of the b43-fwcutter package in Hardy itself
not being able to extract the firmware or b) a problem of the
installation script
Thank you for the tips and suggestions, I'll do them tonight when I get home
from work, and will reply again with my results.
On Thu, Mar 6, 2008 at 8:04 AM, der_vegi [EMAIL PROTECTED] wrote:
Cory, what i your output of 'dmesg'? This would give an idea, if the
problem is the driver itself, or
Cory, what i your output of 'dmesg'? This would give an idea, if the
problem is the driver itself, or a problem of not loading the firmware.
A second aproach would be to do the steps, the install script shoud do,
manually (steps extracted from
Looks like the firmware version/fwcutter version issues I
mentioned/referenced in my first post.
Dmesg output attached.
On Thu, Mar 6, 2008 at 8:16 AM, Cory Flick [EMAIL PROTECTED] wrote:
Thank you for the tips and suggestions, I'll do them tonight when I get
home from work, and will reply
For whatever it's worth :
I tried a different approach. I did a clean install of Gutsy, got wireless
working that way, then upgraded to Hardy using update-manager -d.
Upon reboot, wireless does not work. Tried using Hardware Drivers under
System--Administration, it offered to download the
Hm, I wonder if this is an error of b43-fwcutter not installing the firmware
properly or the driver itself... Could you please give an output of typing
'dmesg' in your terminal? Is the b43 module loaded? 'lsmod | grep b43' tells
you this. If not, what happens, if you do 'sudo modprobe b43'?
I am running a Buffalo G PCMCIA wireless card which also uses the Broadcom
drivers. I, with a fresh install of Hardy, get the same behavior as the OP. The
output from dmesg is:
[ 390.486921] b43-phy0 ERROR: Firmware file b43/ucode5.fw not found or load
failed.
[ 390.486938] b43-phy0 ERROR: You
Update, I removed package b43-fwcutter (installed by Ubuntu) and
installed package bcm43xx-fcutter to no result; however, when I went to
the the hardware drivers page I noticed that the check box next to
enabled was off so I re-enabled it (note: it was enabled before I
removed b43). The driver
** Changed in: b43-fwcutter (Ubuntu)
Sourcepackagename: None = b43-fwcutter
--
broadcom wireless not working fresh install of hardy
https://bugs.launchpad.net/bugs/197819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
So it seems to be a problem of b43-fwcutter's install routine or the
restricted-driver-manager jockey? Cory Flick, what happens, if you try
to uninstall b43-fwcutter and then try enabling your wireless card over
the restricted manager again?
** Also affects: jockey (Ubuntu)
Importance:
Restricted Manager pops up the has to install firmware notice again. I
click ok, it installs/runs fwcutter again, which again does not result in
working wireless. On the web page I referenced in my original bug report,
there's talk of different kernels requiring different fwcutter versions as
well
16 matches
Mail list logo
