I just upgraded to feisty and am having trouble with the wireless. I had
wireless working before the upgrade. The driver seems to load fine and I
can get a DHCP lease, but then can't get any packets through to
anything. A ping to my gateway gets 100% packet loss. There don't seem
to be any error
After installing the firmware cut from wl_apsta.o in 2.6.20-9 (as
described by Jeff), I now have wireless connectivity again without
resorting to booting the 2.6.20-6 kernel.
One glitch though: The wireless light on my laptop no longer lights up
as it does when using the 2.6.20-6 kernel.
Might I recommend opening a bug for that issue, then?
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No, this has been fixed post Herd 4. Wait for Herd 5 then.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have problem with feisty herd 4
i can not conecet to my wireless provider with my static ip adress they
are alway drop me i use D-Link -520 Atheros chipset
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
OK for me too.
bcm4306 rev03 working again. Thanks!
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This problem seems to be fixed in linux-image-2.6.20-9. After updating,
I added the firmware to /lib/firmware/2.6.20-9/. Once I restarted, I was
able to get wireless again. (Note: Remember to select the linux kernel
2.6.20-9 in grub.)
I have a Broadcom Corporation BCM4306 802.11b/g Wireless LAN
Sorry to add noise if it's unnecessary, but I can confirm; my
bcm43xx-based card is now working again, under feisty.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Confirmed fixed on powerpc, too. Thanks!
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: bcm43xx
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Michael Buesch is the bcm43xx upstream maintainer. Matthew is the Ubuntu
kernel maintainer.
The issue with the kernel tree has been ACK'ed.
No further comments are necessary.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
I am, of course, lying in the previous comment wrt. maintainership for
Ubuntu kernel.
Statement stands.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm this bug, after upgrade to feisty fawn herd 4, my wireless card
(broadcom 4318)
doen't work.
I've got the message:
/var/log/syslog.0:Feb 23 00:34:35 medula kernel: [ 418.60] bcm43xx:
YOUR FIRMWARE IS TOO OLD. Firmware from binary drivers older than
version 4.x is
Bug 85099 seems to be related to this one if not the same bug.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm this is broken and needs fixing before release.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed = Confirmed
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ditto.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please stop replying to this bug. It's being dealt with.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = In Progress
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I am also noticing the problems reported above. I am using a Dell
latitude d400 with a broadcom bcm4306 wireless chip set. I am not able
to view any wireless networks. Do the developers have enough
information here from other users or should I include more details?
--
bcm43xx completely
You do _NOT_ need to answer to this bug entry. We know exactly what's broken
and how to fix it.
It was a mismerge. There is absolutely no further testing or bugreporting
needed.
The whole purpose for which I opened this bug, is to make the ubuntu
developers aware of the breakage, as I
Hi Christian,
I've got the same problem with my HP Compag nx6125, so here are the
additional information you need:
1. uname -a:
Linux terra 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
2. dmesg lspci -vvnn
attached
** Attachment added: Log of dmesg and lspci -vvnn
Hi Cristian,
Same problem here on a desktop machine:
1. uname -a
Linux grant-desktop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686
GNU/Linux
2. dmesg lspci -vvnn
attached
** Attachment added: Contains dmesg.log and lspci-vvnn.log
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the
Feisty freezes here with kernel 2.6.20-6-368 using WEP 128 encryption.
anything else is the same as Aaron Ahlemeyer.
kernel 2.6.20-6-368 works fine.
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
bcm43xx does not work for my system with kernel 2.6.20-8-generic. I get
messages in the system log about needing firmware 4.x or later. The 4.x
firmware was challenging to obtain, I used fwcutter-006. With the 4.x
firmware that I found, network scanning works, but my system completely
freezes
Re-assign to right component.
** Changed in: linux-meta (Ubuntu)
Sourcepackagename: linux-meta = linux-source-2.6.20
--
bcm43xx completely broken in feisty
https://launchpad.net/bugs/85404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
25 matches
Mail list logo
