channel 6. It appears b43legacy might have
the same bugs as the bwi driver as I immediately began seeing beacons
once I started using channel 6.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de
for the ssid it configured the
interface for. This isn't much information to go on but it points us
in a direction to where the problem(s) may exist. Again, any help
would be appreciated.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev
On Fri, Apr 10, 2009 at 3:30 PM, Larry Finger larry.fin...@lwfinger.net wrote:
David Ellingsworth wrote:
I'd like to try and get b43legacy running in AP mode this weekend. Can
anyone tell me what modifications to b43legacy need to be made in
order to do so? The last time I tried, I applied
to the upper layers.
Cheers,
-FG
Your patch was mangled by your email client. Maybe you should inline
your patches and attach a copy of it before sending in the future.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev
environments. Thus, rather than
always adding unneeded complexity to the driver, it might be better if
changes like these could be placed under a general network define
kernel option. Then users wishing to have strict frame checks when
FCSFAIL is set have the option to do so.
Regards,
David Ellingsworth
.fw
[ 60.347726] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[ 60.377113] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[ 60.520049] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
Regards,
David Ellingsworth
for
this problem can be achieved by using dhcpcd rather than dhclient for
obtaining ip addresses from a dchp server. In my case, merely
installing dhcpcd was enough as all my distribution's network scripts
preferred it over dhclient, ymmv.
Regards,
David Ellingsworth
be simply ported over to legacy.
--
Greetings, Michael.
Thank you all for the helpful information... Once the weekend comes
around again, I'll take a look a trying to get something working. I'm
willing to help test and port the necessary changes to legacy as well.
Regards,
David Ellingsworth
a use for.
johannes
I'm interested in the PCI card if it's still available.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
driver.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
style license. *cough*
bcm *cough*
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
then you can blame the b43legacy
driver. Until then, like Michael, I am suspect to believe the
b43legacy driver is the cause of your issue.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de
Broadcom's proprietary driver or use ndiswrapper. There has been
limited success with these approaches in the past. Your mileage may
vary.
Regards,
David Ellingsworth
On Wed, Oct 1, 2008 at 12:10 PM, Filadelfo Fiamma [EMAIL PROTECTED] wrote:
That's output produced by lspci -nnv
This is section
it has ever been in the past, bcm43xx
included. I'd like to thank you all for all the hard work you have
invested in this driver, your efforts have been greatly appreciated.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx-dev
the above information is
that there is something wrong with how packets are created locally and
delivered to the device. I'm willing to provide any help necessary
needed to correct the issue.
Regards,
David Ellingsworth
___
Bcm43xx-dev mailing list
Bcm43xx
On Sun, Jul 6, 2008 at 2:37 PM, Larry Finger [EMAIL PROTECTED] wrote:
David Ellingsworth wrote:
While using the latest b43legacy driver, I have severe packet loss
originating from the machine using the b43legacy driver. However, when
packets are routed through the machine using NAT, no packet
On Wed, Jun 18, 2008 at 6:02 AM, Johannes Berg
[EMAIL PROTECTED] wrote:
On Tue, 2008-06-17 at 23:20 +0200, Michael Buesch wrote:
On Tuesday 17 June 2008 22:59:52 David Ellingsworth wrote:
I ran into this error today from a kernel I built last night based on
the latest wireless-testing branch
:36:27)
b43legacy-phy0 debug: Chip initialized
b43legacy-phy0 debug: 30-bit DMA initialized
b43legacy-phy0 debug: Wireless interface started
b43legacy-phy0 debug: Adding Interface type 2
b43legacy-phy0 warning: Unexpected value for chanstat (0x7C00)
Regards,
David Ellingsworth
On Tue, Jun 17, 2008 at 5:20 PM, Michael Buesch [EMAIL PROTECTED] wrote:
On Tuesday 17 June 2008 22:59:52 David Ellingsworth wrote:
I ran into this error today from a kernel I built last night based on
the latest wireless-testing branch. Correct me if I'm wrong, but it
looks to be b43legacy
CCing list
On Tue, Jun 17, 2008 at 5:38 PM, David Ellingsworth
[EMAIL PROTECTED] wrote:
On Tue, Jun 17, 2008 at 5:19 PM, Pavel Roskin [EMAIL PROTECTED] wrote:
On Tue, 2008-06-17 at 16:59 -0400, David Ellingsworth wrote:
I ran into this error today from a kernel I built last night based
after attempting to
use dhclient
results in transmission timeouts while trying to ping another node on the
network.
Thus indicating that the interface is indeed not associated as otherwise
indicated.
Regards,
David Ellingsworth
Output from uname -r: 2.6.26-rc4-wl
Output from lspci -vvn
Resend. Message attached.
Regards,
David Ellingsworth
_
Enjoy 5 GB of free, password-protected online storage.
http://www.windowslive.com/skydrive/overview.html?ocid=TXT_TAGLM_WL_Refresh_skydrive_062008For a while now, I've been
additional testing with a WEP encrypted network later this week.
Regards,
David Ellingsworth
_
Pack up or back up–use SkyDrive to transfer files or keep extra copies. Learn
how.
hthttp://www.windowslive.com/skydrive/overview.html?ocid
seems much more stable. iwlist shows the signal level
bouncing between -55dbm and -63dbm, with link qualities between
61 to 68 and a constant noise level of -66dbm. I will try to do some
additional testing with a WEP encrypted network later this week.
Regards,
David Ellingsworth
Just noticed
On Tue, 8 Jan 2008 19:46:41 -0500
David Ellingsworth wrote:
I wish I could say the same for the b43legacy driver.. here are my results
from the same version of aireplay:
# ./aireplay-ng -9 wlan0
19:27:51 Trying broadcast probe requests...
19:27:53 No Answer...
19:27:53 Found 2 APs
it to the b43legacy
driver.
Regards,
David Ellingsworth
_
Share life as it happens with the new Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008
Michael -
On Tuesday 08 January 2008 16:31:53 David Ellingsworth wrote:
mac80211 supposedly has support for packet injection. Like you however, I
have have not been able to get packet injection to work with the
b43/b43legacy drivers and the developers have expressed
directed probe requests...
19:27:53 00:14:D1:43:88:04 - channel: 6 - 'ap1'
19:28:00 0/30: 0%
19:28:00 00:06:25:67:1D:14 - channel: 6 - 'ap2'
19:28:06 0/30: 0%
Regards,
David Ellingsworth
_
Make distant family not so
the driver again.
Any help in finding the cause of the error would be appreciated.
Regards,
David Ellingsworth
_
Don't get caught with egg on your face. Play Chicktionary!
http://club.live.com/chicktionary.aspx?icid
callback deadlock
Date: Mon, 29 Oct 2007 01:16:05 +0100
On Monday 29 October 2007 01:06:51 David Ellingsworth wrote:
- mutex_lock(wl-mutex);
+ /* When RFKILL is registered, it will call back into this callback.
+ * wl-mutex will already be locked when this happens.
+ * So first trylock
From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [PATCH] b43: Fix
rfkill callback deadlock Date: Sun, 28 Oct 2007 17:27:10 +0100 CC: [EMAIL
PROTECTED]; bcm43xx-dev@lists.berlios.de; [EMAIL PROTECTED] wl-mutex
might already be locked on initialization. Signed-off-by: Michael Buesch
Sorry, hopefully its readable this time.
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [PATCH] b43: Fix rfkill callback deadlock
Date: Sun, 28 Oct 2007 17:27:10 +0100
CC: [EMAIL PROTECTED]; bcm43xx-dev@lists.berlios.de; [EMAIL PROTECTED]
wl-mutex might already be locked on
=PEAP
identity=username
password=password
}
Regards,
David Ellingsworth
_
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE
Larry Finger wrote:
Ehud Gavron wrote:
I've git clone'd the wireless-dev tree, and the test tree, and there
ain't* not bcm43xx_mac80211 or b43 or b44 or anything similar in the
.config.
1) How can I get access to update the berlios.de wiki? I'd like to
contribute, and I think I
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: newbie question
Date: Tue, 14 Aug 2007 01:34:27 -0400
CC: bcm43xx-dev@lists.berlios.de
Larry Finger wrote:
Ehud Gavron wrote:
I've git clone'd the wireless-dev tree, and the test tree, and there
ain't* not
to determine if the issues I see
are range related as well.
Regards,
David Ellingsworth
_
Find a local pizza place, movie theater, and more….then map the best route!
http://maps.live.com/default.aspx?v=2ss=yp.bars~yp.pizza~yp.movie
Date: Thu, 9 Aug 2007 15:01:34 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]; bcm43xx-dev@lists.berlios.de
Subject: Re: firmware versions?
David Ellingsworth wrote:
Subject: firmware versions?
From: [EMAIL PROTECTED]
To: bcm43xx-dev@lists.berlios.de
37 matches
Mail list logo
