This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release (9.10 stable or
10.04 beta)? Thank
The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains
** Changed in: debian-installer (Ubuntu)
Status: New => Invalid
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-source-2.6.22 (Ubuntu)
Stat
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Network Team
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
The driver is now properly loading, but the signal is slow, and I'm not able
to connect to any network, it seems that I get no Ip address from the dhcp...
The driver is probably no working correctly...
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notificati
installing the bcm43xx-fwcutter solve the problem, as it asked if I want
to install the firmware automatically...
In order to make this device working directly after install, maybe the
installer should install automatically the bcm43xx-fwcutter if bcm43xx
device is present ?
** Also affects: deb
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
uname -a
Linux utopia 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load
failed.
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notification because you are a member of Ub
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/8698450/lspci-vvnn.log
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
I experience the same problem in Gutsy tribe3
The card was installed, but is not usable.
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "dmesg"
http://launchpadlibrarian.net/8698446/dmesg.log
--
BCM4306 not working
https://bugs.
I was under the impression that this was a bug concerning the BCM4306
Wireless LAN Controller in that it didn't work after the upgrade from
fiesty. I had the exact same card and problem so I assumed it was the
same bug. Also, the default driver did not work either, but the
ndiswrapper did ... so
This bug report is about something different, namely the bcm43xx driver.
Your ndiswrapper problem is not related to this problem.
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Update, I have not thoroughly tested it yet, but it appears that I fixed
the problem.
Steps:
1 - Download ndiswrapper (attachment included), stick it on a flash drive or cd
and then bring it to the computer with no internet. Transfer it over, un tar
it , cd to the directory created, run "make u
** Attachment added: "bcm4318.all.tar.gz"
http://launchpadlibrarian.net/7928734/bcm4318.all.tar.gz
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Just another confirmation. Before upgrade to fiesty I had ndiswrapper
set up and everything was going fine, then I upgraded and it no longer
detects my card (lspci sees it, just no wireless devices). Exact same
symptoms.
--
BCM4306 not working
https://bugs.launchpad.net/bugs/93342
You received
What drivers did you use? Try fwcutter on broadcom-wl-4.80.53.0 with
bcm43xx-mac80211. It works fine for me except limited range problem.
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
I have the same problems. Dell Latitude d800, Broadcom Corporation
BCM4309 802.11a/b/g (rev 02).
tried fwcutter with normal and v4.80.53 drivers.
tried bcm43xx and bcm43xx-mac80211
Loading bcm43xx-mac80211 genereates a weird wmaster0 device and eth1
The card appears to be up, but i cannot scan
During tests I noticed that new firmware and new driver works fine but
is very limited by range. Wireless card works in one room, but if I move
my laptop to another no ping can pass through (signal monitor shows
100%). It does not disconnect from network or drops packets (according
to ifconfig) but
I downloaded broadcom-wl-4.80.53.0 drivers and extracted firmware.
Wireless card works flawlessly with bcm43xx-mac80211. Will check
stability and speed issues and report. Thx for help.
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
See /usr/share/doc/bcm43xx-fwcutter/README.gz for download links of v4
firmwares.
Download one and run bcm43xx-fwcutter against it (bcm43xx-fwcutter
wl_apsta.o for example) . After, move the *.fw s generated to
/lib/firmware (sudo mv *.fw /lib/firmware) and reboot or remodprobe
bcm43xx.
--
BCM43
Apparently I've got old firmware. How can I upgrade it?
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
If you upgrade to 2.6.20-12 in feisty, you can try:
sudo modprobe -r bcm43xx
sudo modprobe bcm43xx-mac80211
See if that helps, but it will probably require you to get v4 firmware.
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu
** Attachment added: "uname -a"
http://librarian.launchpad.net/6850851/uname-a.log
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Martin Jürgens => (unassigned)
Status: Needs Info => Unconfirmed
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
lspci -vvnn and dmesg included
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/6850801/dmesg.log
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
uname -a
Linux jojo-laptop 2.6.20-11-386 #2 Thu Mar 15 07:58:11 UTC 2007 i686
GNU/Linux
** Tags removed: dmesg
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/6850794/lspci-vvnn.log
--
BCM4306 not working
https://launchpad.net/bugs/93342
--
ubuntu-bugs mailing list
ubuntu
Works nice for me.
Though, thanks for taking the time to report this bug. Unfortunately we
can't fix it, because your description doesn't yet have enough
information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional
** Description changed:
- My WiFi card based on BCM4306 chip is still not working properly. During
- upgrade from Edgy to Fiesty it was recognized and I was informed about
- extracting microcode from chip. Everything went smoothly and WiFi status
- led started to blink. Unfortunately I'm not able
29 matches
Mail list logo
