Hi,
Yes I confirm. Installed Jaunty a couple of days ago and had to go thru a
set of instructions to do a workaround regarding the PCMCIA Linksys card
that uses that chip; only after that workaround I was able to connect to a
wi-fi network. The last three releases I had to use this set of
instruct
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
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
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
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
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
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
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
... 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
michael37 wrote:
> I have updated to 2.6.22-14 kernel and it did not resolve the issue.
>
> ~$ uname -a
>
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,
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
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
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
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
Hi Thom,
It's Rev 02. I've been checking the performance by running "apt-get
updates" against one of the Irish repository servers. With earlier
kernels (e.g. 2.6.20-16) I get close to 200Kb/s downloads. When I
upgraded to 2.6.22-x the performance dropped down to around 16Kb/s when
just a few m
Hi Thom,
I'm using the 4306 chipset.
Chris
Thom Pischke wrote:
> Chris, what chipset do you have?
>
>
--
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 con
19 matches
Mail list logo
