*** This bug is a duplicate of bug 85404 ***
https://bugs.launchpad.net/bugs/85404
broadcom 4306 revision 02 is still broken in intrepid even in kernel
2.6.27-11 from the proposed repository. really awful
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://bugs.launchpad.net/bugs/85099
*** This bug is a duplicate of bug 85404 ***
there are 2 drivers in the feisty kernel for the bcm43xx, one is based
off the dscape drivers. So if you have an old card and wanna use version
3 firmware load the bcm43xx module and have the V3 firmware extracted to
/lib/firmware/ If you wanna try the
*** This bug is a duplicate of bug 85404 ***
I'll mark this one as a duplicate of bug 85404 then, as the other one is
set to "In Progress" and is being worked on. I hope this removes some
confusion.
** This bug has been marked a duplicate of bug 85404
bcm43xx completely broken in feisty
--
B
Ah, yes, bug 85404 seems to be identical, and is in-progress. I guess
that means we can expect a fix soon. Looks like Brian has already
cross-referenced both issues via comment.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu
This issue has gone awful quiet...
I'm still booting with the 2.6.20.6 kernel as a workaround for this
issue. Hope someone from the kernel team evaluates this problem soon
and assigns an importance. I'm looking for assurance that this bug is
on the radar screen for release. Otherwise I have to
This bug seems to be similar to bug 85404 if not the same issue.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
yS,
i have said package and have used it, still a no go on my firmware. thanks for
your recomendation though :-)
- Richard
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
@R Morrison: Try downloading ndiswrapper-utils-1.9 and useit to install
the driver again. It worked for me.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
until this is fixed i have no wireless support w/ the new kernel
2.6.20.8 either through bcm43xx which doesnt work, AND ndiswrapper which
no longer works. i havent blacklisted bcm43xx it doesnt crash my system,
im waiitng for a rix before feisty goes final.
--
Broadcom bcm43xx broken with 2.6.20.
I have the same problem, I blacklisted bcm43xx to prevent crashes until
we have a solution.
** Attachment added: "lspci output"
http://librarian.launchpad.net/6494004/pciinfo.txt
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubu
attempting v4 firmware loading won't hang the system, i believe. In my
case, a hang only came when actually trying to connect to something. I
believe the multiple error messages in dmesg occur before the hang,
during boot, so it should be possible to detect these problems during
card activation
AFAIK the hard lock is only due to a kernel bug and not because of the
firmware. If V4 firmware was unsupported it just wouldn't work rather
than lock the whole system. Nothing should lock the system.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bug
Thom said:
> The kernel could attempt to cut and use V4 firmware and devicescape stack,
> and if that fails, cut and use version 3 firmware and softmac stack instead.
Thom, AFAIK V4 firmware should work with with BCM4306 rev04 and rev05.
It would be great if it automatically uses V3 firmware for
Darren's description seems accurate to me. I also see the wmaster0
interface when booting with 2.6.20.8, though I can't confirm that's what
causes the v4 problems since I can't use v4 firmware.
bug 84917 should take care of the the bcm43xx-fwcutter problem.
Issues with bcm43xx and various firmwa
Rejecting the bcm43xx-fwcutter task, as it (WLAN broken) is no bug in
bcm43xx-fwcutter. For a newer release which can extract v4 firmwares,
see bug 84917.
** Changed in: bcm43xx-fwcutter (Ubuntu)
Status: Confirmed => Rejected
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchp
Just to confirm:
It seems like everyone has exactly the same problem,
V3 firmware won't work in the new devicescape driver.
V4 firmware would work fine if it wasn't for the bug in the 2.6.20-8 build
kernel which shows:
wmaster0 IEEE 802.11g Frequency:2.412 GHz
RTS thr:off Fragment thr
Actually, I think it's ok to set status to 'Rejected' for the bcm43xx-
fwcutter package.
This bug is now also registered against linux-source-2.6.20, where I
believe the fix would have to be implemented.
My suggestion is that the kernel should be modified to include two
parallel versions of bcm43
According to Thom the recommendation:In fact, this is no bug in
bcm43xx-fwcutter and support has not been dropped for older cards. The new
bcm43xx driver, which went to Feisty, requires a 4.x firmware version. In order
to get one, download the latest bcm43xx-fwcutter from
http://developer.berli
this seems to be a much broader problem than bcm43xx-fwcutter... it
looks like its a problem with this new non-softmac driver in kernel.
it'd be a pity to see Fiesty go to final with tricky or no broadcom wifi
support for a vast number of users, especially mobile users.
--
Broadcom bcm43xx broken
According to Thom the recommendation:In fact, this is no bug in
bcm43xx-fwcutter and support has not been dropped for older cards. The new
bcm43xx driver, which went to Feisty, requires a 4.x firmware version. In order
to get one, download the latest bcm43xx-fwcutter from
http://developer.berli
Bug confirmed on an iBook G4. Old firmware does not work with new kernel
and new firmware hard locks the machine.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
Just to be sure, I tried installing v4 firmware as per the instructions
above. It was a mini-disaster. First, for the firmware which would
seem to apply to my card, listed under bcmwl5.sys, both the links listed
in the readme seem to be broken:
4.10.40.0
http://rapidshare.de/files/1145873
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Confirmed
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thom, thanks for the clarification. This is a bad behavior then.
As the universe freeze already happened, new package versions need an
exception in order to go to Universe. I currently try to get one in bug
84917 in order to have the latest and greatest version of bcm43xx-
fwcutter in Universe.
By the way, why not include the latest bcm43xx-fwcutter in ubuntu, if
the current one is too old?
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi Martin, you've missed two key points:
1. Some 'older' cards, older meaning older than 1 year in some cases,
do not and will never accept v4 firmware. Thus for such cards, like my
BMC4306 rev 02, the current version of bcm43xx will never work, since it
requires v4 firmware which my hardware ca
i filed such a bug days ago :-) one step ahead of ya.
- Richard
On 2/19/07, Martin Jürgens <[EMAIL PROTECTED]> wrote:
>
> If some bcm43xx devices are not working anymore after a Feisty upgrade,
> although doing the procedure above, please file a bug against linux-
> source-2.6.20.
>
> --
> Broadco
To clarify my last point, you're right that this is not a bug in
bcm43xx-fwcutter. The 'bug' is in the kernel itself which contains
support only for v4 firmware, thus dropping support for the many people
who have older broadcom cards.
If you want to reclassify this bug to the kernel, that's fine.
If some bcm43xx devices are not working anymore after a Feisty upgrade,
although doing the procedure above, please file a bug against linux-
source-2.6.20.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Wait, I could have got something wrong.. Investigating..
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
In fact, this is no bug in bcm43xx-fwcutter and support has not been
dropped for older cards.
The new bcm43xx driver, which went to Feisty, requires a 4.x firmware
version.
In order to get one, download the latest bcm43xx-fwcutter from
http://developer.berlios.de/project/showfiles.php?group_id=45
Same here.
I've just updated to Feisty. I have a rev03 card bought one year ago,
and I can't use it.
[ 899.730877] bcm43xx: YOUR FIRMWARE IS TOO OLD. Firmware from binary
drivers older than version 4.x is unsupported. You must upgrade your
firmware files.
I won't install an v4 firmware, it's no
Confirm on iBook G4, Apple Extreme. I think this way, almost all Apple
laptops are affected by this bug.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Edit above: Apparently at least rev *04* is needed:
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Booted on 2.6.20.8 and attempted to install v4 firmware. bcm43xx
complained saying that the driver was either invalid or unsupported
checked dmesg output which loudly insisted that my firmware is too old
and that i must upgrade to version 4.x.
But it seems my wireless card does not support v4 fi
Adding link to a page with driver downloads, seems appropriate to this
issue:
http://linuxwireless.org/en/users/Drivers/bcm43xx
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
No connectivity and hard locks are exactly what everyone is getting with
the v4 firmware. bit of a show stopper this one, not sure if medium if
the correct importance...
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I have a broadcom 4309 and with 3.x firmware under the 2.6.20.8 kernel,
my wireless interface shows up under iwconfig, but if I try and set
anything like the SSID, if get a bunch of errors.
With a 4.x Windows drivers, it appears like it's going to work, ie APs
show up under network manager, but th
Just to put some extra info:
Here is a iwconfig with the 2.6.20-6 generic kernel:
[EMAIL PROTECTED]:~$ iwconfig
lono wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b/g ESSID:"Golgoth" Nickname:"Broadcom 4306"
Mode:Managed Frequency=2.452 GHz Ac
I just wanted to confirm this bug.
Why is it only medium status?!
If you don't have web access just because of a driver problem, it's a
shame...
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
I have a Broadcom 4318 wireless adapter in a laptop about 1 1/2 years
old (Model HP L2005CU). I was successfully using Network Manager and
ndiswrapper to connect wirelessly with Edgy.
When I switched to Feisty, I ran with ndiswrapper but was unable to
connect to unencrypted networks (connected fi
** Changed in: bcm43xx-fwcutter (Ubuntu)
Importance: Undecided => Medium
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm hoping the package maintainer or some other Ubuntu representative
weighs in on this soon. I'm also not looking forward to reverting to
the inferior Ndiswrapper alternative. I was hoping support for my
wireless card would get -better- with each coming ubuntu release, not
dropped entirely.
But
"oh by the way".. i was incorrect.. ndiswrapper with generic amd64 inf's is not
an alternative at least for me if you want working encrrption and a reliable
connection... i'd really like to see either a revert i n the next kernel to the
old-firmware-supporting driver, or create symmetric options
I've had a similar experience. See
http://www.ubuntuforums.org/showthread.php?p=2166540&posted=1#post2166540
I'm using a WPA encrypted network, and when I used the version 4
firmware under network manager, the machine locks up and needs a hard
reset. However, when I *don't* use NM and configure w
im finding ndiswrapper + the 64bit driver linked to at linuxuant to be my
best alternative. im disappointed i cant use the better native bcm43xx
driver.
On 2/16/07, darren <[EMAIL PROTECTED]> wrote:
>
> I actually have the BCM4318 card. I've tried the v4 firmware provided
> with the Windows driver
I actually have the BCM4318 card. I've tried the v4 firmware provided
with the Windows drivers for this card and it doesn't give any network
access and hard locks the machine, same as any other V4 firmware I try.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
Thom is right dropping support of older cards in order to support new ones is
stupid for a couple of reasons:
1. The people most impacted will of course be current users with cards that
have older firmware... suddenly Ubuntu will no longer natively support their
bcm43xx chipset w/ old firmware l
The current bcm43xx-fwcutter in the repos is 1:005 which pulls down the
V3 firmware:
12:57:40 (83.85 KB/s) - `wl_apsta.o' saved [652866/652866]
filename : wl_apsta.o
version: 3.130.20.0
I don't know if the 1:006 fwcutter pulls any newer firmware down?
--
Broadcom bcm43xx broken wit
More info here: http://www.mail-archive.com/bcm43xx-
[EMAIL PROTECTED]/msg03039.html
Seems to imply that it should be possible to install support for V3 and
V4 firmware in parallel, but doesn't look like a job for the end user.
Probably something like this could be done in the distro though.
--
Ugo, could you explain how you upgraded your firmware? 10 minutes
searching the net hasn't turned up anything helpful yet. Nothing on the
broadcom site, not can I find any other howto pages for upgrading to V4
firmware.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/
Hmm, dropping support for a wireless card in a laptop barely three years
old seems a bit rash. Especially considering that this support has only
been around for a year or so...
So is there no hope for a BCM4306, even with updated firmware?
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https:/
It looks like Ubuntu switched from the regular bcm43xx driver to the
DeviceScape driver in the last release. This breaks compatibility for
us who have older versions of the cards.
https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/004005.html
--
Broadcom bcm43xx broken with 2.6.20.8
Same here. I have the BCM4319 happily using the firmware that bcm43xx-
fwcutter downloads for me from the net until 2.6.20-8
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
By the way, I have a BCM4306 rev 02.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the same issue. The message states that it will not work with
older versions of the firmware (pre 4.0 version) however I updated my
firmware and can confirm that I have 4.1 installed and still no luck.
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
u
some potentially related info, with different specifics
http://lists.infradead.org/pipermail/fedora-ppc/2006-March/000805.html
I see an error very similar to this error in the above link:
*: Sorry, it's not posible to extract "bcm43xx_microcode11.fw".
*: Extracting firmware from an old dr
I can confirm the same bug here. Anyone know of any valid 4.x amd64
firmware source out there?
** Changed in: bcm43xx-fwcutter (Ubuntu)
Status: Unconfirmed => Confirmed
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-b
i want to confirm this bug but i am unable... new to launchpad so
perhaps im missing something... have done it on other bugs before...
--
Broadcom bcm43xx broken with 2.6.20.8 kernel
https://launchpad.net/bugs/85099
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
yup this happens to me as well, i did actually attempt to cut some
firmware out that was >4.x but bcm43xx-fwcutter rejected the .sys files
i tried. Why does the kernel update demand that seeing as there are no
easily available 4.x series firmware files out there to play with.
since we cant get the
yup this happens to me as well, i did actually attempt to cut some
firmware out that was >4.x but bcm43xx-fwcutter rejected the .sys files
i tried. Why does the kernel update demand that seeing as there are no
easily available 4.x series firmware files out there to play with.
since we cant get the
61 matches
Mail list logo
