glenn greenfield wrote:
eth0: no link during initialization.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
lp: driver loaded but no devices found
ppdev: user-space parallel port
Bryan Short wrote:
Kind folks:
I have an HP dv6408nr laptop. Here are the relevant things:
[EMAIL PROTECTED] ~ $ sudo lsmod
Password:
Module Size Used by
b43 149424 0
ndiswrapper 207264 0
rfkill_input6528 0
snd_seq_dummy
I have just tested the last four patches from Michael. Compilation is
fine and no regressions that I have seen as of yet. My 4306 and 4318 are
working just fine with the changes.
-Jory
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
Larry Finger wrote:
Has anyone used the new driver variation known as b43 from that branch of
wireless-dev and gotten
auto-loading at bootup of the b43 module on i386 or x86_64 platforms. It
still doesn't work here
even after upgrading to the latest version of udev. Before I post to LKML
Larry Finger wrote:
Jory A. Pratt wrote:
Yes I am able to reproduce it. I have done upgraded and downgraded my
enitre toolchain. exact same problem is present on my system when I
try my 4306 and 4318.
What encryption method are you using?
Larry
I use wep encryption on a WRT54G V3
Johannes Berg wrote:
Hi,
We were just discussing the negative effects of having too many
different firmwares (like the problem Andy ran into); if you're using
the version 4 driver and have a different firmware than
* 343.126 (this is the currently recommended one)
* 351.1092 (I'm using
Michael Buesch wrote:
On Friday 10 August 2007 04:27:33 Ehud Gavron wrote:
I have spent eight hours on this today and I can't find a way to do a
subset of the patches. I haven't quite given up, but I'm reaching a
point where I could use some insight. I didn't copy the list... but
feel
Larry Finger wrote:
John H. wrote:
Did I misunderstand something? I thought some script was available or
some easy way to use either bcm43xx or the new one. brennan says he
has a script to just let you use the newer driver with higher mbps,
but I have never heard back from him.
drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c: In function
'bcm43xx_write_probe_resp_plcp':
drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c:1152: error: too
few arguments to function 'ieee80211_generic_frame_duration'
drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c: In function
Pavel Roskin wrote:
Hello!
On Tue, 2007-06-26 at 18:58 -0700, Ehud Gavron wrote:
I've been alternately switching between 2.6.22-rc3 (Linville git tree)
and 2.5.22-rc6 (Linville git tree as of today), henceforth rc3 and rc6
respectively.
There have been significant changes in
Michael Buesch wrote:
John,
Please pull for-linville branch of my tree.
It contains a lot of bugfixes and makes a _big_ step towards
mergability for mainline.
It's not 100% ready for a merge, yet, but we are making good progress.
The transmission power problems on the 4306, that were one of
Johannes Berg wrote:
On Sun, 2007-04-08 at 03:42 -0500, John H. wrote:
What do I do?
Apply Larry's patches. I don't remember the URL and can't find it easily
right now, you'll find it with some searching on this mailing list.
johannes
Just so everyone is aware of how well development is coming along here
is some proof. Larry you have done an awsome job bring the softmac up to
a very usuable standard in todays modern home network!!
Wireless interface testing using Iperf
==
Testing
Hendrik Sattler wrote:
Am Dienstag 30 Januar 2007 16:22 schrieb Larry Finger:
This is the software I installed:
http://www.srcf.ucam.org/~mjg59/vbetool/
It won't even compile here. Perhaps it is because I have an x86_64 system.
I don't have time to debug that program.
You
Michael Buesch wrote:
On Wednesday 24 January 2007 20:08, Larry Finger wrote:
Michael Buesch wrote:
On Wednesday 24 January 2007 19:39, Larry Finger wrote:
switch (led_index) {
case 0:
led-behaviour = BCM43xx_LED_ACTIVITY;
+ led-activelow = 1;
Well after doing a serious upgrade on my line I discovered just how
bad off the bcm4318 truely is. I have a 3Mbp/s line and with bcm4318 I
am lucky if I can utilize a 1/3rd of that. ( i.e =1.0Mbps ) Those who
have this card might want to concider throwing it in the trash, it does
not work with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Buesch wrote:
Hi John,
Sorry, took a little bit longer than expected, but here it is. :)
Please queue for 2.6.18.
--
From: Daniel Drake [EMAIL PROTECTED]
Use Softmac-suggested TX ratecode:
ieee80211softmac_suggest_txrate()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Buesch wrote:
On Sunday 28 May 2006 18:37, you wrote:
On Sun, May 28, 2006 at 06:29:01PM +0200, Michael Buesch wrote:
Well, I would like to know it for sure. ;)
Could you load the kernel which crashed and look there. It is
quite important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well I have just gotten around to testing latest patch for 2.6.16-rc2,
exceptional work. All XMIT ERROR's are just about resolved except when
device attempts to suspend. I am gonna test proc entry patch a bit later
today, time to see if it will work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a reason we are not registering device completely yet? Main
reason behind me finding this is I can not use my normal network
configuration without an entry being in /proc/net/wireless.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2
Michael Buesch wrote:
On Thursday 05 January 2006 03:05, Jory A. Pratt wrote:
bcm43xx: XMIT ERROR
bcm43xx: Generic Reason: 0x4d80
bcm43xx: DMA reasons:0x, 0x, 0x, 0x
bcm43xx: DMA TX status: 0x2000, 0x36802368, 0x2000, 0x2000
bcm43xx
bcm43xx driver 0.0.1
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7,
bcm43xx: XMIT ERROR
bcm43xx: Generic Reason: 0x4d80
bcm43xx: DMA reasons:0x, 0x, 0x, 0x
bcm43xx: DMA TX status: 0x2000, 0x36802368, 0x2000, 0x2000
bcm43xx: XMIT ERROR
bcm43xx: Generic Reason: 0x4d80
bcm43xx: DMA reasons:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Berg wrote:
Since this is purely linux specific I figured I can submit...
johannes
Well after a bit of fooling around I got the bcm4318 AirForce One up and
working. I had to drop to 11M for now to keep association, but other
then that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hisham Muhammad wrote:
Hello,
I'm trying to get bcm43xx-dscape to work. I'm using:
* ieee80211-devicescape-051222 (applied fine on linux-2.6.15-rc6)
* wpa_supplicant-0.4.7_dscape-02.patch
* bcm43xx-dscape-20051226
I see packets being
25 matches
Mail list logo
