On Sun, 2008-04-27 at 18:07 +0200, Michael Buesch wrote:
> I'm interested in buying multi-PHY cards (dual-PHY and multi-core).
> Do you know a source for such cards?
Look for Dell 1450. There are some on ebay.de. It's miniPCI (at least
some of them).
--
Regards,
Pavel Roskin
_
On Sunday 27 April 2008 18:57:20 Larry Finger wrote:
> Michael Buesch wrote:
> > On Sunday 27 April 2008 17:36:22 Larry Finger wrote:
> >> Richard Jonsson wrote:
> >>> With the reverted commit "b43: Fix bandswitch" back in, and the above
> >>> patch applied the bad behavior is back. This is on mai
Michael Buesch wrote:
> On Sunday 27 April 2008 17:36:22 Larry Finger wrote:
>> Richard Jonsson wrote:
>>> With the reverted commit "b43: Fix bandswitch" back in, and the above
>>> patch applied the bad behavior is back. This is on mainline.
>>>
>>> regards, Richard
>> My interface was definitely
Michael Buesch skrev:
> Please test whether this fixes the regression.
>
> Index: wireless-testing/drivers/net/wireless/b43/main.c
> ===
> --- wireless-testing.orig/drivers/net/wireless/b43/main.c 2008-04-27
> 17:47:49.0
On Sunday 27 April 2008 17:36:22 Larry Finger wrote:
> Richard Jonsson wrote:
> >
> > With the reverted commit "b43: Fix bandswitch" back in, and the above
> > patch applied the bad behavior is back. This is on mainline.
> >
> > regards, Richard
>
> My interface was definitely a BCM4311 with onl
Please test whether this fixes the regression.
Index: wireless-testing/drivers/net/wireless/b43/main.c
===
--- wireless-testing.orig/drivers/net/wireless/b43/main.c 2008-04-27
17:47:49.0 +0200
+++ wireless-testing/drive
On Sunday 27 April 2008 17:36:22 Larry Finger wrote:
> Richard Jonsson wrote:
> >
> > With the reverted commit "b43: Fix bandswitch" back in, and the above
> > patch applied the bad behavior is back. This is on mainline.
> >
> > regards, Richard
>
> My interface was definitely a BCM4311 with onl
Richard Jonsson wrote:
With the reverted commit "b43: Fix bandswitch" back in, and the above
patch applied the bad behavior is back. This is on mainline.
regards, Richard
My interface was definitely a BCM4311 with only B/G mode. I don't have it
anymore as it came in a laptop that was repla
>> I have no idea as to why the interface is switching from 5 to 2.4 GHz,
>> and back endlessly. Perhaps Michael knows. It is also possible that the
>> bug is in the new mac80211 band API, which isn't used by b43 when the
>> "bad" commit is backed out.
>>
>> The patch contained in
>> http://lis
Larry Finger skrev:
> Richard Jonsson wrote:
>> Larry Finger skrev:
>>> Richard Jonsson wrote:
Larry Finger skrev:
> If Linus's latest git still has the problem, please do a bisection. I
I've now completed the bisection, result below. I'm not really sure
this is the bad commit,
Michael Buesch wrote:
> Yeah, well. We shouldn't tell mac80211 about the A-PHY, as that doesn't
> work, yet.
Will this patch do the trick, at least until A-PHY's work?
Index: wireless-testing/drivers/net/wireless/b43/main.c
===
---
On Sunday 27 April 2008 01:42:24 Larry Finger wrote:
> I have no idea as to why the interface is switching from 5 to 2.4 GHz,
Well, most likely it's scanning the channels, right?
> and back endlessly. Perhaps Michael knows. It is also possible that
> the bug is in the new mac80211 band API, whi
Richard Jonsson wrote:
> Larry Finger skrev:
>> Richard Jonsson wrote:
>>> Larry Finger skrev:
If Linus's latest git still has the problem, please do a bisection. I
>>> I've now completed the bisection, result below. I'm not really sure
>>> this is the bad commit, as v2.6.25 is fine, and thi
Larry Finger skrev:
Richard Jonsson wrote:
Larry Finger skrev:
If Linus's latest git still has the problem, please do a bisection. I
I've now completed the bisection, result below. I'm not really sure this
is the bad commit, as v2.6.25 is fine, and this commit is from february.
But then again
Richard Jonsson wrote:
> Larry Finger skrev:
>> If Linus's latest git still has the problem, please do a bisection. I
>
> I've now completed the bisection, result below. I'm not really sure this
> is the bad commit, as v2.6.25 is fine, and this commit is from february.
> But then again, I don't
Larry Finger skrev:
> Richard Jonsson wrote:
>> Larry Finger skrev:
>>> Richard Jonsson wrote:
flipping switch a few times, led unchanged
[ 1534.770048] b43-phy0: Radio hardware status changed to ENABLED
[ 1550.778511] b43-phy0: Radio hardware status changed to DISABLED
[ 1562.7
Richard Jonsson skrev:
> Larry Finger skrev:
>> If Linus's latest git still has the problem, please do a bisection. I
>
> I've now completed the bisection, result below. I'm not really sure this
> is the bad commit, as v2.6.25 is fine, and this commit is from february.
> But then again, I don't
Larry Finger skrev:
> If Linus's latest git still has the problem, please do a bisection. I
I've now completed the bisection, result below. I'm not really sure this
is the bad commit, as v2.6.25 is fine, and this commit is from february.
But then again, I don't fully understand how git does it'
Richard Jonsson wrote:
> Larry Finger skrev:
>> Richard Jonsson wrote:
>>> flipping switch a few times, led unchanged
>>> [ 1534.770048] b43-phy0: Radio hardware status changed to ENABLED
>>> [ 1550.778511] b43-phy0: Radio hardware status changed to DISABLED
>>> [ 1562.783474] b43-phy0: Radio hardw
Larry Finger skrev:
> Richard Jonsson wrote:
>> flipping switch a few times, led unchanged
>> [ 1534.770048] b43-phy0: Radio hardware status changed to ENABLED
>> [ 1550.778511] b43-phy0: Radio hardware status changed to DISABLED
>> [ 1562.783474] b43-phy0: Radio hardware status changed to ENABLED
Here comes a slice of dmesg with debugging turned on. This is from
v2.6.25-4571-g87322bc of mainline. Same as before.
Richard Jonsson skrev:
>> OK, after bootup with v2.5.25-rc3-git I get this, looks sane to me:
>>
>> [ 32.474786] b43-phy0: Loading firmware version 351.126 (2006-07-29
>> 05
Richard Jonsson wrote:
> flipping switch a few times, led unchanged
> [ 1534.770048] b43-phy0: Radio hardware status changed to ENABLED
> [ 1550.778511] b43-phy0: Radio hardware status changed to DISABLED
> [ 1562.783474] b43-phy0: Radio hardware status changed to ENABLED
> [ 1565.788237] b43-phy0:
>
> OK, after bootup with v2.5.25-rc3-git I get this, looks sane to me:
>
> [ 32.474786] b43-phy0: Loading firmware version 351.126 (2006-07-29
> 05:54:02)
> [ 32.474797] b43-phy0 warning: You are using an old firmware image.
> Support for old firmware will be removed in July 2008.
> [ 32
Richard Jonsson skrev:
> Larry Finger skrev:
>> Richard Jonsson wrote:
>>> [10493.303801] b43-phy0 warning: You are using an old firmware image.
>>> Support for old firmware will be removed in July 2008.
>>> [10493.303807] b43-phy0 warning: You must go to
>>> http://linuxwireless.org/en/users/Dri
Larry Finger skrev:
> Richard Jonsson wrote:
>> [10493.303801] b43-phy0 warning: You are using an old firmware image.
>> Support for old firmware will be removed in July 2008.
>> [10493.303807] b43-phy0 warning: You must go to
>> http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and
>
Michael Buesch skrev:
> On Friday 25 April 2008 18:09:27 Richard Jonsson wrote:
>> To add, I thought that my hardware had died judging by the messages
>> above, so I temporarily connected to an access point in the area and
>> could successfully load a few webpages before I disconnected.
>
> You
Richard Jonsson wrote:
> [10493.303801] b43-phy0 warning: You are using an old firmware image.
> Support for old firmware will be removed in July 2008.
> [10493.303807] b43-phy0 warning: You must go to
> http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and
> download the latest firmw
On Friday 25 April 2008 18:09:27 Richard Jonsson wrote:
> To add, I thought that my hardware had died judging by the messages
> above, so I temporarily connected to an access point in the area and
> could successfully load a few webpages before I disconnected.
You really need to be a bit more de
Michael Buesch skrev:
> On Friday 25 April 2008 17:21:00 Richard Jonsson wrote:
>> I use a custom kernel, but I think I turned off b43/ssb debugging some
>> time ago. Anyway dmesg is drowning in this:
>
> Oh, finally something useful. Great!
>
>> [ 7389.533848] b43-phy0 warning: You must go to
On Friday 25 April 2008 17:21:00 Richard Jonsson wrote:
> I use a custom kernel, but I think I turned off b43/ssb debugging some
> time ago. Anyway dmesg is drowning in this:
Oh, finally something useful. Great!
> [ 7389.533848] b43-phy0 warning: You must go to
> http://linuxwireless.org/en/use
Larry Finger skrev:
> Richard Jonsson wrote:
>> Pavel Roskin skrev:
>>> On Thu, 2008-04-24 at 21:48 +0200, Richard Jonsson wrote:
Hello,
First some background:
I am currently running latest mainline from git. This kernel suffers
from a scheduler?
>>> I think this question
Richard Jonsson wrote:
> Pavel Roskin skrev:
>> On Thu, 2008-04-24 at 21:48 +0200, Richard Jonsson wrote:
>>> Hello,
>>>
>>> First some background:
>>> I am currently running latest mainline from git. This kernel suffers
>>> from a scheduler?
>> I think this question is more suited for LKML.
>>
>
Pavel Roskin skrev:
> On Thu, 2008-04-24 at 21:48 +0200, Richard Jonsson wrote:
>> Hello,
>>
>> First some background:
>> I am currently running latest mainline from git. This kernel suffers
>> from a scheduler?
>
> I think this question is more suited for LKML.
>
I'm sorry for being a bit vague
On Thu, 2008-04-24 at 21:48 +0200, Richard Jonsson wrote:
> Hello,
>
> First some background:
> I am currently running latest mainline from git. This kernel suffers
> from a scheduler?
I think this question is more suited for LKML.
> While trying to find what these hickups come from I ran watch
Hello,
First some background:
I am currently running latest mainline from git. This kernel suffers
from a scheduler? issue where keys get stuck and audio skips every now
and then. Confirmed to be triggered by a commit named "sched: fix fair
sleepers".
I am currently on wired lan and have the w
35 matches
Mail list logo