The problem was resolved with the release 8.04 Hardy... On Tue, Apr 29, 2008 at 1:02 AM, Luke Hoersten <[EMAIL PROTECTED]> wrote: > Apr 28 09:18:21 mcclaike-laptop firmware_helper[7590]: main: error loading > '/lib/firmware/b43legacy/ucode4.fw' for device > '/devices/pci0000:00/0000:00:1e.0/0000:02:02.0/ssb0:0/firmware/ssb0:0' with > driver '(unknown)' > Apr 28 09:18:21 mcclaike-laptop kernel: [ 1812.558893] b43legacy-phy0 ERROR: > Firmware file "b43legacy/ucode4.fw" not found or load failed. > Apr 28 09:18:21 mcclaike-laptop kernel: [ 1812.558903] b43legacy-phy0 ERROR: > You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware > and download the correct firmware (version 3). > Apr 28 09:18:23 mcclaike-laptop NetworkManager: <WARN> > nm_device_802_11_wireless_scan(): (eth1): could not trigger wireless scan: > Network is down > > My friend is having this same problem even after updating today. She > doesn't know how to use the advanced package manager and she's hours > away so I can't help her with it. Will this just be fixed automatically > at any point? Otherwise, I'm going to need a super easy fix to tell her > over the phone. > > ** Attachment added: "syslog" > http://launchpadlibrarian.net/14005480/syslog > > > > -- > [Hardy]b43-fwcutter install script fails to fetch firmware in first run > https://bugs.launchpad.net/bugs/197819 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in Source Package "b43-fwcutter" in Ubuntu: Invalid > Status in Source Package "jockey" in Ubuntu: Fix Released > Status in b43-fwcutter in Ubuntu Hardy: Invalid > Status in jockey in Ubuntu Hardy: Fix Released > > Bug description: > [EMAIL PROTECTED]:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=8.04 > DISTRIB_CODENAME=hardy > DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" > [EMAIL PROTECTED]:~$ uname -a > Linux lil-spooky 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 > x86_64 GNU/Linux > > ------------------------------------------------------------------------------------------------- > [EMAIL PROTECTED]:~$ apt-cache policy b43-fwcutter > b43-fwcutter: > Installed: 1:008-2 > Candidate: 1:008-2 > Version table: > *** 1:008-2 0 > 500 http://us.archive.ubuntu.com hardy/universe Packages > 100 /var/lib/dpkg/status > > ---------------------------------------------------------------------------------------------------------------------------- > what I expected to happen : after doing a fresh install of Hardy Alpha 5, I > started the Restricted Driver Manager to install the broadcom firmware to get > my wireless working, just like I did in Gutsy. I expected the fwcutter > package to download and install the correct firmware, which is what happened > under Gutsy. In Gutsy, the little orange light turned blue right away ( my > machine is an HP dv6000 series laptop ) indicating that wireless is up and > running. > > ------------------------------------------------------------------------------------------------------------------------------ > what happened instead : started the Restricted Driver manager now called > "Hardware Drivers" under System-->Administration, clicked the checkbox for > the Broadcom firmware to be downloaded and installed. The Hardware Driver > manager told me it had downloaded and installed the firmware, however, the > orange light did not turn blue. I tried rebooting to see if that would make a > difference. It did not make a difference. No working wireless. This page : > http://linuxwireless.org/en/users/Drivers/b43 seems to indicate that various > kernel versions need not just different versions of the firmware, but > different versions of the fwcutter program/package itself, as well. Would be > great if that could be integrated into Hardy before final release. > > ---------------------------------------------------------------------------------------------------------------------------------- >
-- [Hardy]b43-fwcutter install script fails to fetch firmware in first run 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
