On Marco's note
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/124159/comments/128
will mark this as Fix released.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You rece
ng
Sent: terça-feira, 12 de Maio de 2009 10:21
To: m.antu...@sapo.pt
Subject: [Bug 124159] Re: Broadcom bcm43xx Wireless driver regression in
gutsy
Unfortunately it seems this bug is still probably an issue. Can you confirm
this issue exists with the most recent Jaunty Jackalope 9.04 release
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin King (colin-king)
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Unfortunately it seems this bug is still probably an issue. Can you
confirm this issue exists with the most recent Jaunty Jackalope 9.04
release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let
us know your results. Thanks.
--
Broadcom bcm43xx Wireless driver regression in gutsy
h
This is Kubuntu 8.10,
Linux deneb 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64
GNU/Linux
My network controller identifies as lspci
Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
Under gutsy I installed ndiswrapper and manually copied the appropriate
drive
Marking invalid for linux-source-2.6.22, which is no longer present (in
gutsy and beyond).
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed =>
Leann,
Just to confirm I still see rather poor performance/sensitivity on my wireless
card with the latest updates. My details below:
$ uname -a
Linux inspiron-1501 2.6.27-4-generic #1 SMP Mon Sep 22 04:40:44 UTC 2008 i686
GNU/Linux
$ lspci -vvnn|grep etwork
05:00.0 Network controller [0280]: Br
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
>waddayaknow, previous comment was not entirely correct. It should have read:
>
>sudo su
>echo -e '#!/bin/sh\niwconfig eth1 rate 5.5M auto' >
>/etc/network/if-pre-up.d/fixed-rate
>echo -e '#!/bin/sh\niwconfig eth1 rate 5.5M auto' >
>/etc/network/if-up.d/fixed-rate
>chmod a+x /etc/network/if-pre-u
I'm running into range issues (2 meters max) with the latest Hardy Beta.
03:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g]
802.11g Wireless LAN Controller (rev 02)
Previously, when using ndiswrapper it was fine.
--
Broadcom bcm43xx Wireless driver regression in gutsy
h
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Problem still exists for me with Hardy Beta and BCM4318 AirForce One 54g
on Dell Inspiron 2200. Looks like poor sensivity for me:
$ iwconfig wlan0
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:17:9A:C9:B8:29
Bit Rate=2 Mb/s Tx-Pow
Leann,
Here's my report for Hardy.
I have a Broadcom card:
05:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev
01)
And I can confirm that it works half decently in Hardy, but the speed
still fluctuates a lot 12 kB/s to 109 kB/s (the later is the speed my
ISP provides
The problem is still present in Hardy Alpha 5 with b43legacy (and the
firmware that b43 firmware-cutter is automatically getting from the
net). However b43legacy is a small step forward compared to bcm43xx
since it now suspends/resumes OK :)
What is worse is that in Hardy there is also a big probl
Well, I sold the laptop on which I originally had the issue. I still
help the new owner with issues like these, so I will try to test with
the LiveCD next time I'm over at his place, but since I'm about to head
off on a three month vacation - this probably won't happen until after
hardy has releas
Hi Thom,
Since you are the original bug reporter, can you comment on if this is
still an issue for you with the latest Hardy Alpha release? You can
download and try the new Hardy Heron Alpha release from
http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then
test the new kernel v
i'm running Hardy alpha 4 with a Bcm4318 and the situation hasn't
improved at all since Gutsy. I used b43-fwcutter to get the card
working (seems like Ubuntu should prompt this automatically).
I'm getting sub 50Kps performance
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs
As Asleigh Gordon stated I can also confirm that my Broadcom card now
works solidly on Hardy using b43-fwcutter.
@trj021782 you might be interesting on trying this on previous releases,
as the page states these packages are unofficial so YMMV
http://backports.trausch.us/2008/01/04/new-package-
bac
The restricted Driver Manager should have offered to install it
automatically. This issue is about stability issues pertaining to the
driver it installs.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you
I am a new linux user who is experiencing a complete lack of
functionality at all out of my broadcom 4306 rev 3 chipset. I t is on a
belkin card. I would very much so like to know wher to get that
functional driver.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.ne
Testing Live CD:
http://cdimage.ubuntu.com/releases/hardy/alpha-2/
https://wiki.ubuntu.com/HardyHeron/Alpha2
** Tags added: b43
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bug
This looks like it is fixed in the Hardy alpha 2 with the 2.6.24 kernel.
The newer b43 driver seems to work quite well.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thom et. al.,
I've read with great interest this thread as I had recently crashed my
Feisty installation which connected well at 11 Mb/s wirelessly to my
router via the bcm43xx driver. I decided to move up to Gutsy, and
decided to try to get connected wirelessly via ndiswrapper. Everything
I tri
I can confirm this! When I tried to switch from one to another I saw much
faster throughput for a short period, then it would die off. I do not have
numbers like Thom does, but I saw same nonetheless.
zeddock
On Dec 21, 2007 11:03 AM, Thom Pischke <[EMAIL PROTECTED]> wrote:
> Interestingly, I
Don't expect much progress on bcm43xx since it has been deprecated for new
driver:
http://linuxwireless.org/en/users/Drivers/b43
http://bcm43xx.berlios.de/
Generally speaking don't expect much from these cards as Broadcom keeps
the documentation secret and the native drivers are 100% reverse-
eng
Ok, so here's my final complete workaround for this issue in gutsy,
thanks to all those who have contributed! Hopefully this hack will not
be needed in Hardy.
1. Create a new script "bitratehack" in /etc/NetworkManager/dispatcher.d/
2. Paste in the following:
#!/bin/sh
ACTION=$2
if [ "$ACTION"
Testing again with Samba transfers over my home network, I see no
practical difference between 2M and 5.5M, but 11M is definitely slower
Peak speed observed at 2M and 5.5M = 560 KB/s
Average: ~300 KB/s
(Rates observed via System Monitor Network Traffic Gauge)
--
Broadcom bcm43xx Wireless driver
Interestingly, I usually observe a short spike in speeds when I switch
the bit rate. It will run at nearly 500 KB/s right after I switch from
5.5M to 2M, for instance, and then sink back to around 300 after 5-10
seconds. Weird stuff.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https
Note that I personally get the best performance at a rate of 2M, *not*
5.5M, and **definitely not** 11M
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
One last speed test at 2M:
http://www.speedtest.net/result/214241873.png
Tried at 1M too, but it was slower than at 2M, around 2000 kbit/s
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of
so how about someone write up an easy HOWTO for noobs, explaining how to
set the rate to 5.5M permanently across reboots?
I'm also skeptical that this is fixed in hardy, since there has been
some confusion in this post with another bug about not being able to
connect to routers, which is unrelated
Doh! That last comment was potentially misleading. Should have said
that internet upload speed held constant at the limit of my internet
connection bandwidth, 360 kbits/sec, regardless of wireless interface
bitrate setting. This may be simply because it's far too slow to be
impacted by this drive
Upload speed is rock solid at all speeds.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
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
That was at 5.5M.
Here's the same test at 11M
http://www.speedtest.net/result/214238098.png
And here at 24M:
http://www.speedtest.net/result/214238517.png
The trend is clear, increasing bitrate past 5.5M results in greater
performance loss. Faster the bitrate, slower the transfer, ironically.
Did an online test here: http://www.speedtest.net/
http://www.speedtest.net/result/214237258.png
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
Speeds above were observed while transferring a 4GB file over Samba via
wireless connection. With other wireless cards, I typically get about
1.3 MB/s for the same transfer. With this frustrating broadcom
card/driver the peak was just over 500KB/s with an average closer to
300. Usable and adequa
Glad you are back onto this even though it is a pain again for you. It
seems silly to me that this problem has not yet been resolved, but without
feedback of quality, as your feedback seems to be, I guess the fixers don't
have a lot to work with.
Please tell me how you are measuring the throughpu
Worth noting that I get noticeably better performance with 5.5M than
11M, counterintuitively.
Peak actual speed at 5.5M fixed rate: ~500KB/s, Average: 200-300 KB/s
Peak actual speed at 11M fixed rate: ~300KB/s, Average: 100-150
Speeds are quite erratic, so numbers above are just to make the
c
The friend to whom I sold the laptop with the 4306 rev 2 decided to go
wireless, so I'm looking at this issue again. Can confirm that setting
wireless rate to 5.5M works wonders. Getting consistent 450 KB/s
transfer rates now and seems stable. Am I right in concluding from
previous comments that
On Dec 12, 2007 8:35 AM, Thom Pischke <[EMAIL PROTECTED]> wrote:
> Can we at least hope for a fix in Hardy?
In hardy now work with linux image 2.6.22-14, idem to gutsy.
--
Cristian
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this b
EvilPaddy,
I did not get a chance to try non DHCP static connections. I will let you know
asap.
My network controller Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
is working 100% fine with Gutsy, kernel 2.6.22-14-generic, compiled ndiswrapper
1.47, bcmwl5 drivers and nm.
--
Broadco
Can we at least hope for a fix in Hardy?
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
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.
Lau, What about non DHCP static connections?
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
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@li
I just kept the loopback interface in /etc/network/interfaces
Thus I removed all the ethx entries in this file.
On Gutsy, network-manager was able to detect the wifi controller and
connect to access-points.
Everything rox now!
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs
I too am experiencing this, with the following:
uname -r : 2.6.22-14-generic
lspci : 02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 02)
===
Not that its necessary, but I'll confirm the gutsy problems.
uname -r : 2.6.22-14-generic
lspci : 02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 02)
The sudo iwconfig hack seemed to work mildly for me. Before it was
unusable, now it is just frus
I have the issue too with gutsy released.
uname -r: 2.6.22-14-386
lspci: Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev
01)
I blacklisted the bcm43xx native driver and compiled ndiswrapper 1.47 to use
bcmwl5 one.
ndiswrapper -l
bcmwl5 : driver installed
device (
I can confirm this bug and that the line 'sudo iwconfig eth1 rate 5.5M fixed'
solves this issue on a Dell Latitude D610
with Broadcom BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You rece
@zeddock: Certainly.
I used this guide:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty_No-Fluff
My testimonial is posted inline on that page.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification becau
Would you mind linking to a post on HOW to get our wireless working
better?
Thanx,
zeddock
On 10/24/07, michael37 <[EMAIL PROTECTED]> wrote:
>
> After all this fighting, I upgraded to Gutsy release (wireless still
> wasn't working), installed ndiswrapper using Dell driver version 4.100
> with v
After all this fighting, I upgraded to Gutsy release (wireless still
wasn't working), installed ndiswrapper using Dell driver version 4.100
with v4 firmware. Works great. Very disappointed with the quality of
native driver.
As a reminder, the bcm43xx native driver worked for me in Feisty.
althou
After some digging it turned out that noapic doesn't work :( wifi sopts
working at all. I dongraded to feisty kernel and... guess what
everything works as a charm there is sth wrong with gutsy kernel I
suppose.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bug
I will second that "stellar product" comment.
However, these 43xx bugs really should be swatted. It's like a little stain
on an otherwise stunning white dress.
Please let me know how I can help.
zeddock
On 10/23/07, y2klemson <[EMAIL PROTECTED]> wrote:
>
> While I haven't tried the noapic solu
While I haven't tried the noapic solution, definitely resolved my flaky
throughput issues with the fixed bitrate <= 11Mbps. I tried different
drivers and even attempted to revert to using ndiswrapper.
It would make sense that it's the interrupt controller interaction. I'd
like to help fix it, bu
I had the same problem. Bu it seems that it was related to the interrupt
controller. Setting kernel option noapic helped.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Setting the rate down to 1M seems to work ok.
iwconfig eth1 rate 1M fixed
Strangely, I rebooted and it picked up the network fine. However, it has
picked up the network with a bit rate of 24 Mb/s, which it was never
able to before.
eth1 IEEE 802.11b/g ESSID:"zazz" Nickname:"Broadcom 4306"
I've upgraded to 7.10, and the bcm4306 driver no longer works properly.
It can scan network for the ssid, and with the speed set to 5.5M it can
authenticate, but fails when it tries to get an address from the router.
So this bug is definitely in 7.10.
--
Broadcom bcm43xx Wireless driver regressio
Just reporting this still shows really poor performance, I can "attach"
to the AP, but I can't ping any other host aside from the localhost DHCP
assigned IP. My specific bug is Bug #92088 and it seems related.
This is in the now released 7.10
--
Broadcom bcm43xx Wireless driver regression in gut
I note in the activity log that this bug has not been worked for over a
month. Please leave a short comment on why it would be changed to
Triaged if that is the correct status. I am not trying to make more
work on this, just trying to make sure the issue is still on the radar.
zeddock
** Change
Dell X300 + Dell Wireless a/b/g 1400 mini-pci
Broadcom 4324 I believe
Gutsi RC, all updates, 2 days before launch :)
The speed is still ABYSMAL - and indeed it can be made somehow better by
forcing the speed rate to 5.5M,
Bit Rate=5.5 Mb/s Tx-Power=14 dBm
RTS thr:off Fragment thr:off
but IT WORK
I thought the interfaces file was ... forget the word, but there is a rules
file which has now become the proper approach. Please confirm?
Thanx,
zeddock
On 10/15/07, Yakov Markovitch <[EMAIL PROTECTED]> wrote:
>
> Hi
> To restrict inrterface rate, you can add to configuration of the
> corresp
Hi
To restrict inrterface rate, you can add to configuration of the corresponding
interface in /etc/networks/interfaces
wireless-rate 5.5M
And yes, I confirm the problem (HP Pavilion zv3240 w/Broadcom adapter).
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/
I went back to Feisty using included bcm43xx driver and added firmware
to /lib/firmware, worked first time at full 54G speeds. That was until a
kernel update yesterday and now the erratic and slow speeds are back,
tried both bcm43xx and ndiswrapper methods, but its now just as bad as
it was in guts
Here we go.
Started driver. Went into NetworkManager and selected connect to other
wireless network. Put in my SSID and WEP key. NetworkManager said Attempting
to join the wireless netowork 'HOME'...
NetworkManager asked me for my WEP key two more times, and I got bored of that.
dmesg:
[ 3
... also, could you post your dmesg log?
michael37 wrote:
>> Hi,
>>
>> Did you use the restricted drivers manager to reload the firmware? If
>> you look at the dmesg output you'll probably see that the firmware has
>> changed from the 2.6.22-12 kernel.
>>
>> Chris
>>
>
> I never had 2.6.22-12
Hi Michael,
If you've got the firmware enabled then that should be all you need. Is
it just that the scan doesn't work? Can you manually connect to the
nearest access point?
Chris
michael37 wrote:
>> Hi,
>>
>> Did you use the restricted drivers manager to reload the firmware? If
>> you look at
>Hi,
>
>Did you use the restricted drivers manager to reload the firmware? If
>you look at the dmesg output you'll probably see that the firmware has
>changed from the 2.6.22-12 kernel.
>
>Chris
I never had 2.6.22-12 kernel installed -- my initial upgrade to Gusty
came with 2.6.22-13 kernel.
I lo
2.6.22-12 kernel is no longer in repositories, I can no longer install
it. I have 2.6.22-13 and 2.6.22-14 installed and neither of them work.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member
Hi,
Did you use the restricted drivers manager to reload the firmware? If
you look at the dmesg output you'll probably see that the firmware has
changed from the 2.6.22-12 kernel.
Chris
michael37 wrote:
> I have updated to 2.6.22-14 kernel and it did not resolve the issue.
>
> ~$ uname -a
>
I have updated to 2.6.22-14 kernel and it did not resolve the issue.
~$ uname -a
Linux longisland 2.6.22-14-generic #1 SMP Wed Oct 10 05:28:36 GMT 2007 x86_64
GNU/Linux
~$ sudo iwlist eth0 scan
eth0 No scan results
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launch
Looks like we just got some updates to restricted-modules, nvidia-glx
(important for me) and a new 2.6.22-14 kernel. Fingers crossed!
zeddock wrote:
> I too moved back Waiting for updates.
>
>
> On 10/9/07, Chris McCauley <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> Your problem could also be
I too moved back Waiting for updates.
On 10/9/07, Chris McCauley <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Your problem could also be with the 2.6.22-13 kernel. There are problems
> with the wireless support for the broadcom driver. I've moved back to
> 2.6.22-12 where everything seems fine.
>
>
Hi,
Your problem could also be with the 2.6.22-13 kernel. There are problems
with the wireless support for the broadcom driver. I've moved back to
2.6.22-12 where everything seems fine.
Chris
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You rece
Argh. My problem is seemingly different.
I rebooted in Feisty kernel and discovered that ESSID scanning didn't
work either. It used to work before Gutsy upgrade (and I used fwcutter
with Feisty). I suspect this has something to do with updated bcm43xx-
fwcutter and with enabling it via the Rest
I've had no problems using bcm43xx (granted, with 11Mbps rate) in
Fiesty. The driver loads just fine after upgrade to Gutsy, but is
unable to find any ESSIDs. Wrote a post in
http://ubuntuforums.org/showthread.php?p=3493272.
Linux longisland 2.6.22-13-generic #1 SMP Thu Oct 4 17:52:26 GMT 2007
Hi.
This is odd.
I did not experience any problems with my own accesspoint, using the above
mentioned workaround.
At my girlfriends place, however, it still doesn't work.
At least not with network-manager.
The new in-built GNOME functionality to connect to WPA encryptet wireless
networks works.
B
This is due to restrictions of the linux driver. Upstream is working on
it, but it seems to be not an easy task. Especially the bcm4318 (or
latest b43) seems to be only usable with rates <=11MBit/s.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You
I have the problem with the fixed rate of 24MBits/s too.
Why can`t we get rates higher than that?
If I get from the same machine from windows it reaches the full speed of
54MBits/s.
The linux driver?
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
I'm having this troubles, too, using bcm43xx on a 4318 chip. NM tries to
connect with 24M, which causes poor performance. In feisty the default
value was 11M, AFAIK due to restrictions in the kernel-driver, which
prevented higher rates. Now these seem to be no longer present, though
higher connecti
Hi,
Glad to hear that it's working for you. The problem is probably within
the kernel not the driver itself (earlier kernels had no such problem).
Dropping the transmission rate seems to be a workaround for this but
isn't the solution per se. Hopefully someone will debug the problem
correctly
Perfect.
Thanks Chris.
It works now as it should with using that command.
(Am I mistaken or does this only work until session logout? How to permanently
set it to that value?)
Nevertheless I think this should be possible by default. The new
Broadcom driver installation is so easy, but without ent
Hi,
I will test this as soon as I am back to my WiFi-Access-Point.
I guess that this is - even if it works - rather a workaround than a
fix, since I didn't need to do that on Feisty with ndiswrapper.
I furthermore experience this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15
Hi there,
Try setting the rate to 5.5M as suggested in an earlier post. For me
this brings the throughput back up to normal. Assuming that your
wireless interface is eth1 then the following should work for you:
iwconfig eth1 rate 5.5M
Chris
dennda wrote:
> Hi,
> this is gutsy with latest upd
Hi,
this is gutsy with latest updates.
I have the very same issue, as it seems.
Using this: 02:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce
One 54g] 802.11g Wireless LAN Controller (rev 02)
I was very happy that Gutsy found my wireless-hardware and installed the
drivers withou
That sounds like great news! Unfortunately I'm not in a position to
test it anymore, being back on Feisty, but if it works for both of you,
chances are good it will work for me. Hopefully a fix like this will
make it into the release, looks like it wouldn't be too difficult.
Having just bought a
WOW. That worked. Keep heart Thom!
Chris
Christoph wrote:
> I'm experiencing this problem on my machine equipped with a Linksys PCI
> Wireless Adapter (Broadcom 4306 Rev. 02 Chipset), too.
> However, manually setting the bitrate on the adapter to a low value seems to
> help a lot:
>
> After exe
I'm experiencing this problem on my machine equipped with a Linksys PCI
Wireless Adapter (Broadcom 4306 Rev. 02 Chipset), too.
However, manually setting the bitrate on the adapter to a low value seems to
help a lot:
After executing:
$ sudo iwconfig eth2 rate 5.5M fixed
my max. download rate no
I gave up and reinstalled Feisty by the way. My laptop was worthless
with gutsy.
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
Hey, so how about scheduling this bug to get fixed? It hasn't even made
it into the list to be fixed for beta, which makes me think it will
never be fixed before release. The Ubuntu team can save itself a lot of
howling broadcom users by getting this fixed before releasing. There
are enough conf
Sorry I forgot to mention that :
Even if the card is connected to an AP and is working the restricted-manager
still reports the firmware as not enabled / not in use.
Thanks
NDV
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug n
I can confirm the regression:
my card is
02:00.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN
Controller (rev 02)
and I'm running the kernel 2.6.22-11-386 on Gutsy
I can confirm poor performance, I can reach only ~40KB traffic from a cople
meters away from the AP.
I c
What does Triaged mean?
Please see this bug as well...
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/130511
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bug
Hi,
Ignore my earlier optimism the performance is very erratic and when more
than a few metres away it is very poor. Sometimes I get acceptable
performance but mostly it is about 10%-20% of the expected throughput.
With the new nvidia drivers I also cannot use the older kernel.
Chris
Thom Pi
More bad news. Seems the latest nvidia drivers in gutsy don't work with
the feisty kernel that I've been relying on, making my options even less
palatable:
I can either choose no wireless or the old kernel and no nvidia driver.
-Still- hope this gets fixed soon.
--
Broadcom bcm43xx Wireless dr
Tested again on latest kernel:
Linux zd7000 2.6.22-10-386 #1 Wed Aug 22 07:43:24 GMT 2007 i686
GNU/Linux
Still unusable 3 meters from router: 96.1 kilobits per second
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notificati
I'm experiencing the same behavior, except mine never quite worked
properly under Feisty either. Not sure if it's something with different
firmware or what. Same 4306, rev 02 (Marked as Dell TrueMobile 1300
WLAN Mini-PCI).
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.lau
Hmm, looks like that dmesg.log was for the feisty kernel, so attaching
another with the gutsy kernel. Probably not a bad thing to have both
for comparison purposes anyway.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/8795640/dmesg.log
--
Broadcom bcm43xx Wireless driver reg
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/8794206/uname-a.log
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/8794208/dmesg.log
--
Broadcom bcm43xx Wireless driver regression in gutsy
https://bugs.launchpad.net/bugs/124159
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
1 - 100 of 117 matches
Mail list logo
