Re: b43 regression

2007-12-12 Thread Michael Buesch
On Wednesday 12 December 2007 04:16:22 Brennan Ashton wrote:
 On Dec 11, 2007 3:02 AM, Michael Buesch [EMAIL PROTECTED] wrote:
  On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote:
   https://bugzilla.redhat.com/show_bug.cgi?id=412861
   I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
   things started to stop working at, and could not find any part of this
   patch applied, so at least for that bug it is something else.
  
 
  Please find out which patch broke it then. Nobody but you can do this.
 
 What do you use to hammer the card with data to see if if fails?  I

You can use iperf or simply wget some file from a http server in the
network.


-- 
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: b43 regression

2007-12-11 Thread Michael Buesch
On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote:
 https://bugzilla.redhat.com/show_bug.cgi?id=412861
 I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
 things started to stop working at, and could not find any part of this
 patch applied, so at least for that bug it is something else.
 

Please find out which patch broke it then. Nobody but you can do this.

-- 
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: b43 regression

2007-12-11 Thread Brennan Ashton
On Dec 11, 2007 3:02 AM, Michael Buesch [EMAIL PROTECTED] wrote:
 On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote:
  https://bugzilla.redhat.com/show_bug.cgi?id=412861
  I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
  things started to stop working at, and could not find any part of this
  patch applied, so at least for that bug it is something else.
 

 Please find out which patch broke it then. Nobody but you can do this.

What do you use to hammer the card with data to see if if fails?  I
have been just surfing the web, and moving data back and forth, but it
is very inefficient and a poor form of a test. I think I may have
narrowed down the kernel were it starting failing, but I want to make
sure.

-- 
Brennan Ashton
Bellingham, Washington

The box said, 'Requires Windows XP or better'. So I installed Linux
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: b43 regression

2007-12-10 Thread Brennan Ashton
On Dec 10, 2007 2:36 AM, Michael Buesch [EMAIL PROTECTED] wrote:
 I have identified another regression introduced by
 commit f04b3787bbce4567e28069a9ec97dcd804626ac7.

 On my device it shows up as broken transmission after
 a suspend/resume cycle. The workaround for it is to boot
 a known good driver (in my case the vendor driver in OSX)
 and then reboot (without turning the machine off) into the
 broken driver.

 It seems like we unintentionally removed some significant
 initialization step in that patch. I could not identify it, yet.
 The patch I sent yesterday did fix two other bugs, but not this one.

 I am trying to find the reason for this.
 If someone wants to help searching, the best way would be to look
 at that patch I mentioned above and compare the stuff that it
 removes to the stuff that it adds. There must be some tiny line
 that it removes but does not re-add it at another place.
 Four eyes see more than two.

 I have no idea how this bug could be related to the few bugreports
 in the redhat bugzilla. Though, one could test that by trying a
 kernel that does not include the patch.

 Sorry for the inconvenience.

 --
 Greetings Michael.
 ___
 Bcm43xx-dev mailing list
 Bcm43xx-dev@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

RE:
https://bugzilla.redhat.com/show_bug.cgi?id=412861
I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that
things started to stop working at, and could not find any part of this
patch applied, so at least for that bug it is something else.

-- 
Brennan Ashton
Bellingham, Washington

The box said, 'Requires Windows XP or better'. So I installed Linux
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


b43: regression on bcm4318

2007-10-13 Thread Vitaly Bordug
Hello John et al,
(previous email had a typo in ML addr, sorry for the extra noise)

Both b43 and b43legacy fail to load on bcm4318 for a while now, while it used 
to work (with known issues) more or less
fine. The issue started happening not long before ssb united the support of b44 
as well. Therefor, I noticed the difference
soon, because I am not able to use ndiswrapper instead anymore (it does not 
like ssb, and my NIC, b44, does not like
ssb missing either).

dmesg looks like the below:

b43-phy1: Broadcom 4318 WLAN found
b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
phy1: Failed to select rate control algorithm
phy1: Failed to initialize rate control algorithm
b43: probe of ssb0:0 failed with error -2

Currently this is latest rawhide kernel, but has been happening for awhile
(since, at least, 2.6.22.5, where ssb was not yet merged and I still able to 
use ndiswrapper.

Any hint to debug/investigate it appreciated. It does not look like hw 
malfunction, since ndiswrapper,
when able to load, still works fine.

-- 
Sincerely, Vitaly
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: b43: regression on bcm4318

2007-10-13 Thread Michael Buesch
On Saturday 13 October 2007 10:17:30 Vitaly Bordug wrote:
 phy1: Failed to select rate control algorithm
 phy1: Failed to initialize rate control algorithm

That's nothing b43 or ssb related.
Compile and load the rc80211_simple module.

-- 
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


b43: regression on bcm4318

2007-10-13 Thread Vitaly Bordug
Hello John et al,

Both b43 and b43legacy fail to load on bcm4318 for a while now, while it used 
to work (with known issues) more or less
fine. The issue started happening not long before ssb united the support of b44 
as well. Therefor, I noticed the difference
soon, because I am not able to use ndiswrapper instead anymore (it does not 
like ssb, and my NIC, b44, does not like
ssb missing either).

dmesg looks like the below:

b43-phy1: Broadcom 4318 WLAN found
b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
phy1: Failed to select rate control algorithm
phy1: Failed to initialize rate control algorithm
b43: probe of ssb0:0 failed with error -2

Currently this is latest rawhide kernel, but has been happening for awhile
(since, at least, 2.6.22.5, where ssb was not yet merged and I still able to 
use ndiswrapper.

Any hint to debug/investigate it appreciated. It does not look like hw 
malfunction, since ndiswrapper,
when able to load, still works fine.

-- 
Sincerely, Vitaly
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: b43: regression on bcm4318

2007-10-13 Thread Vitaly Bordug
Hello Michael,

On Sat, 13 Oct 2007 10:24:47 +0200
Michael Buesch wrote:

 On Saturday 13 October 2007 10:17:30 Vitaly Bordug wrote:
  phy1: Failed to select rate control algorithm
  phy1: Failed to initialize rate control algorithm
 
 That's nothing b43 or ssb related.
 Compile and load the rc80211_simple module.
 
oh, thanks, that was broken module dependencies. Well at least it is saved in 
archive now, no nobody else
would step into it.

Another question: is this driver known to work okay in ad-hoc or master mode? I 
gave it a try and there is no
driver-side whine, but it does not seem to work either. I see couple of 
packages turnaround, sometimes even
dhcp server is able to feed IP via wlan (host is acting as kinda AP), but 
nothing after that.

And, soon after actual b43 replaced bcm... in rawhide, the same worked, e.g. 
for at least 5 minutes my wifi-enabled
E61 was able stay up and connected (b43 was in ad-hoc mode that time).

I would appreciate any feedback.
TIA

-- 
Sincerely, Vitaly
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: b43: regression on bcm4318

2007-10-13 Thread Michael Buesch
On Saturday 13 October 2007 16:14:31 Vitaly Bordug wrote:
 Hello Michael,
 
 On Sat, 13 Oct 2007 10:24:47 +0200
 Michael Buesch wrote:
 
  On Saturday 13 October 2007 10:17:30 Vitaly Bordug wrote:
   phy1: Failed to select rate control algorithm
   phy1: Failed to initialize rate control algorithm
  
  That's nothing b43 or ssb related.
  Compile and load the rc80211_simple module.
  
 oh, thanks, that was broken module dependencies. Well at least it is saved in 
 archive now, no nobody else
 would step into it.
 
 Another question: is this driver known to work okay in ad-hoc or master mode? 
 I gave it a try and there is no
 driver-side whine, but it does not seem to work either. I see couple of 
 packages turnaround, sometimes even
 dhcp server is able to feed IP via wlan (host is acting as kinda AP), but 
 nothing after that.

Master and adhoc is not stable, yet.
It might work, though. But I didn't really test that recently.

-- 
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev