Custom Search
|
Date: January 31, 2006
From: "Paul T.Threshold" <paultt-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1137884461.12998.79.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@xxxxxxxxxxxxxxxx>
References:
<42eed4b90601170948r5db5371dj33fc193c24636cfd@xxxxxxxxxxxxxx> <8254e41f0601180356h3bcb6678k24aad923775b5f15@xxxxxxxxxxxxxx> <42eed4b90601180853i21bb769fk571f1cf9271d0629@xxxxxxxxxxxxxx> <1137884461.12998.79.camel@xxxxxxxxxxxxxxxxxxxxx>
On 1/22/06, Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@xxxxxxxxxxxxxxxx> wrote: > On Wed, 2006-01-18 at 17:53 +0100, Paul T.Threshold wrote: > > On 1/18/06, Kasper Jordaens > > <kasper.jordaens-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: > > > cool patch! > > :-) > > > > > will it cause trouble when the HD-activity blinking is enabled in the > > > kernel? > > i think not. to be honest i didn't yet tried it with 2.6.15 kernel, > > since in this i didn't enabeld hd led... > > i'll try when i'll reboot.... > > when, don't know i. > > Whe should move the blink code out of the ide driver then to some common > place. It's carefuly written to avoid too much locks in the hot path, > and can be called pretty much at any time, it will trigger a "blink" of > a given amount of ms. i think i could make the effort... or better, to write a patch to get it working this way in the kernel... i need only directions on how to really do this, i mean, i need to know: . where i have to put the resulting source file (in which kernel src dir) . and what name i have to give to it... for the rest i think i can do it myself:-) tell me if i could try thanx, Paul
Date: January 31, 2006
From: "Paul T.Threshold" <paultt-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<43DD6589.9050502-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
References:
<42eed4b90601170958s712a6891g62db41d97b8fea03@xxxxxxxxxxxxxx> <43CD3859.9080306@xxxxxxxxxxxx> <42eed4b90601171322w63fa1a2cs5e81b804657f328@xxxxxxxxxxxxxx> <43CD65EB.70802@xxxxxxxxxxxx> <42eed4b90601181650h2d124686w566814d20cc1a839@xxxxxxxxxxxxxx> <43CF1CAE.9030205@xxxxxxxxxxxx> <42eed4b90601291505k5316e679u2505386b2378c741@xxxxxxxxxxxxxx> <43DD6589.9050502@xxxxxxxxxxxx>
... > I had to go on-line to find out what you meant by a "closed" network. Not > broadcasting the essid > does very little for security. My neighbor doesn't broadcast, but I can see > his AP anyway if I put > my interface in promiscous mode. As long as you use WPA with TKIP and a > reasonably short period > between key changes, no one will be able to collect enough packets to crack > your password, > particularly if the password is not in a dictionary and it has 10 or more > characters init. eheheh i know, infact is not a problem, it would be without encryption, but with it, it is not :-))))
Date: January 31, 2006
From: Jason Lunz <lunz-G4qweqaPUAhg9hUCZPvPmw@xxxxxxxxxxxxxxxx>
In-reply-to:
<20060131194958.26446.qmail-yjhJdvcAZaWvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@xxxxxxxxxxxxxxxx>
References:
<20060131194958.26446.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Just curious if anyone has this working on an hp pavilion > zv5000/compaq r3000 laptop? I believe it has a mini-pci based on the > bcm4309 chipset with 802.11b/g support. Yes, I've used it successfully on an HP zv5000 with an amd64 kernel. It has a little trouble scanning for access points, and takes a good deal of prodding to associate with one, but it certainly works. I've used it both without encryption and with WPA/CCMP. Jason
Date: January 31, 2006
From: Josh Coffman <josh_coffman-/E1597aS9LQAvxtiuMwx3w@xxxxxxxxxxxxxxxx>
Hi all, Just curious if anyone has this working on an hp pavilion zv5000/compaq r3000 laptop? I believe it has a mini-pci based on the bcm4309 chipset with 802.11b/g support. -j -j __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Date: January 31, 2006
From: Lucio Tarantino <ltarantino2-ZTO5kqT2PaM@xxxxxxxxxxxxxxxx>
Hi,
I have a notebook ( HP / Compaq nx6125 ) with a bcm4xx wireless minipci card.
I have try the driver ( the package from gentoo called 0.0.1-r20060125 ... i
think the snapshot 20060125 )
but when the driver is loaded by the colplug script throw the following error:
Jan 31 13:14:04 barolo64 ----------- [cut here ] --------- [please bite here ]
---------
Jan 31 13:14:04 barolo64 Kernel BUG at arch/x86_64/kernel/traps.c:336
Jan 31 13:14:04 barolo64 invalid operand: 0000 [1]
Jan 31 13:14:04 barolo64 CPU 0
Jan 31 13:14:04 barolo64 Modules linked in: ohci1394 ieee1394 pcmcia
yenta_socket rsrc_nonstatic pcmcia_core bcm43xx firmware_class ieee80211softmac
ieee802
Jan 31 13:14:04 barolo64 Pid: 8172, comm: ip Tainted: G M 2.6.15-gentoo-r1 #9
Jan 31 13:14:04 barolo64 RIP: 0010:[<ffffffff8010fe30>]
<ffffffff8010fe30>{out_of_line_bug+0}
Jan 31 13:14:04 barolo64 RSP: 0018:ffff81005149fc70 EFLAGS: 00010206
Jan 31 13:14:04 barolo64 RAX: ffffffffc0000000 RBX: ffff810054f488c0 RCX:
0000000000000964
Jan 31 13:14:04 barolo64 RDX: 0000000051fe0974 RSI: 0000000000000000 RDI:
ffff81005678e870
Jan 31 13:14:04 barolo64 RBP: ffff81005229a9c0 R08: 0000000000000964 R09:
ffff810054f488c0
Jan 31 13:14:04 barolo64 R10: 0000000000000001 R11: 0000000000000000 R12:
0000000051fe0010
Jan 31 13:14:04 barolo64 R13: ffff81000049d000 R14: ffff810055872000 R15:
0000000000000000
Jan 31 13:14:04 barolo64 FS: 00002aaaaaefbdd0(0000) GS:ffffffff8046b800(0000)
knlGS:0000000000000000
Jan 31 13:14:04 barolo64 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jan 31 13:14:04 barolo64 CR2: 00007fffff8d6330 CR3: 0000000051449000 CR4:
00000000000006e0
Jan 31 13:14:04 barolo64 Process ip (pid: 8172, threadinfo ffff81005149e000,
task ffff810055378340)
Jan 31 13:14:04 barolo64 Stack: ffffffff880befeb 0000000000000000
ffffffff8011dd0c 0000000000001000
Jan 31 13:14:04 barolo64 ffff81005229a9c0 ffff81005678e870 0000000000000000
0000000000000200
Jan 31 13:14:04 barolo64 0000000000000000 ffff81005268ac38
Jan 31 13:14:04 barolo64 Call
Trace:<ffffffff880befeb>{:bcm43xx:setup_rx_descbuffer+203}
Jan 31 13:14:04 barolo64 <ffffffff8011dd0c>{dma_alloc_coherent+188}
<ffffffff880bf306>{:bcm43xx:bcm43xx_setup_dmaring+486}
Jan 31 13:14:04 barolo64 <ffffffff880bf635>{:bcm43xx:bcm43xx_dma_init+181}
<ffffffff880bc662>{:bcm43xx:bcm43xx_init_board+4050}
Jan 31 13:14:04 barolo64 <ffffffff8015273a>{filemap_nopage+394}
<ffffffff802af6ad>{dev_open+61}
Jan 31 13:14:04 barolo64 <ffffffff802b0828>{dev_change_flags+104}
<ffffffff802ee4a5>{devinet_ioctl+773}
Jan 31 13:14:04 barolo64 <ffffffff802ef90c>{inet_ioctl+92}
<ffffffff802a6481>{sock_ioctl+577}
Jan 31 13:14:04 barolo64 <ffffffff801825b1>{do_ioctl+33}
<ffffffff8018287b>{vfs_ioctl+651}
Jan 31 13:14:04 barolo64 <ffffffff801828ed>{sys_ioctl+77}
<ffffffff8010e916>{system_call+126}
Jan 31 13:14:04 barolo64
Jan 31 13:14:04 barolo64
Jan 31 13:14:04 barolo64 Code: 0f 0b 68 65 25 33 80 c2 50 01 c3 66 66 90 66 90
48 83 ec 08
Jan 31 13:14:04 barolo64 RIP <ffffffff8010fe30>{out_of_line_bug+0} RSP
<ffff81005149fc70>
Full boot log if usefull is attached to email.
My uname -a is:
Linux barolo64 2.6.15-gentoo-r1 #9 Tue Jan 31 09:30:05 CET 2006 x86_64 AMD
Turion(tm) 64 Mobile ML-34 AuthenticAMD GNU/Linux
For non gentoo users the kernel is a 2.6.15.1 plus some non network revelent
patch.
With ndiswrapper (v 1.8 ) the wireless work fine.
Any information to correct the problem is accepted.
Thx
Lucio
dmesg_bcm4xx_boot.txt.gz
Description: GNU Zip compressed data
Date: January 31, 2006
From: Arhtur Peters <amp-L7HoNwkZanS2JDTeqX/53Ni2O/JbrIOy@xxxxxxxxxxxxxxxx>
In-reply-to:
<6088.195.188.213.34.1138703000.squirrel-Sf9dbTz1eueS4hrmTveuuQ@xxxxxxxxxxxxxxxx>
References:
<6088.195.188.213.34.1138703000.squirrel@xxxxxxxxxxxxxx>
Sorry if this is not relevant or already known, but when I first started using the driver it took me a while to realize that I needed to "ifconfig up" the interface to make the firmware load and the interface initialize. Please correct me if this is no longer the case. Thought it might help. -Arthur
Date: January 31, 2006
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<16735.195.188.213.34.1138699310.squirrel-Sf9dbTz1eueS4hrmTveuuQ@xxxxxxxxxxxxxxxx>
References:
<25665.195.188.213.34.1138670471.squirrel@xxxxxxxxxxxxxx> <43DEEA94.8080207@xxxxxxxxxxxx> <16735.195.188.213.34.1138699310.squirrel@xxxxxxxxxxxxxx>
rbnw07377-QgLWrMLu8clzjhtm8Ag3mw@xxxxxxxxxxxxxxxx wrote:
Thanks Larry, I cant' get Ndiswrapper to work under this kernel (it's a custom 2.6.15 kernel with the DSDT patches 'cos the DSDT is broken on this laptop). I'm wondering after reading a few more posts if this is to do with the stack size. Will need to check this. Would this make a difference to the bcm43xx driver?
No. The bcm43xx driver will be happy with 4 or 8K stacks.
My main worry is that I'm not getting any of the softmac messages after the bcm43xx module looks like it's loaded fine. I realise that there are problems with the module and this chipset at the moment but most seem to be gettig further with this than me. I'm at work at the moment so I can't post any debug but i'm not getting anything new with the latest builds than I got in my earlier posts.
I don't understand the lack of messages. If you are using the standard download, then Makefile in bcm43xx/driver should have a statement "DEBUG = y", which should turn on debugging. I wonder if your special kernel is doing something funny with the log messages.
Larry
Date: January 31, 2006
From: simonwoodward-QgLWrMLu8clzjhtm8Ag3mw@xxxxxxxxxxxxxxxx
---------------------------- Original Message ---------------------------- Subject: Re: [Bcm43xx-dev] BCM4318 On Acer Aspire 3003 From: rbnw07377-QgLWrMLu8clzjhtm8Ag3mw@xxxxxxxxxxxxxxxx Date: Tue, January 31, 2006 9:21 am To: "Larry Finger" <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> Cc: bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx -------------------------------------------------------------------------- Thanks Larry, > simonwoodward-QgLWrMLu8clzjhtm8Ag3mw@xxxxxxxxxxxxxxxx wrote: >> Hi, >> >> I've been trying this for several days now with no success. >> >> I'm building the softmac layers with the daily snapshot each time and also >> the BCM43xx driver from the daily snapshot. >> >> I get warnings when compiling but no errors. >> >> I've got eth1 aliased to bcm43xx in my modprobe.conf >> >> The modules ieee80211_crypt ieee80211 and ieee80211softmace and bcm43xx all load with no errors (see my earlier posts) >> >> NOTE: I don' get the firmware_class module bt I'm using Fedora 4 and I believe that FC4 doesn't use firmware_class. >> >> I can ifconfig eth1 up with no errors but I get nothing further from dmesg. >> >> Looking at other peoples posts, they all get Softmac lines in their dmesg. >> I don't get any of these. >> >> There is a process which starts bcm43xx_wx/0 >> >> Whenever I unload the modules, they are automatically loaded again. Can I >> stop this action? > > Unplug the card. Unfortunately the card is integral to the laptop. It does have a switch on the front (integrated with the Link LED) so I'll try that. > >> How can I check that my firmware is loading? > > At or near line 2267 of bcm43xx_main.c is where the firmware is loaded. If loading failed, you would > get a message in your logs from the printk statement contained there. Have you checked > /var/log/messages for any bcm43xx messages? Cool, I don't get any error messages loading the driver so I presume the firmware is getting loaded. (extracted with latest revision of fwcutter to answer your later question). > > >> I don't get the LED on the front lighting up which indicates the wireless >> is on. >> >> BTW this works fine under 2.6.14 with Ndiswrapper, but of course Ndiswrapper is broken under 2.6.15. > > I don't understand this statement. On my system, 2.6.15 works with ndiswrapper. I don't use it > anymore but keep one kernel so that I can use it if necessary. > I cant' get Ndiswrapper to work under this kernel (it's a custom 2.6.15 kernel with the DSDT patches 'cos the DSDT is broken on this laptop). I'm wondering after reading a few more posts if this is to do with the stack size. Will need to check this. Would this make a difference to the bcm43xx driver? >> Any ideas, a list of basic things to check please. >> Other people seem to have got this working fine so I don't know where I'm >> going wrong :-( > > Did you use fwcutter on the driver version that you used to use with ndiswrapper? Yup. Only came up with the usual messages about microcode.dll and latest revision but fwcutter -i "file" says the driver revision is supported. > My main worry is that I'm not getting any of the softmac messages after the bcm43xx module looks like it's loaded fine. I realise that there are problems with the module and this chipset at the moment but most seem to be gettig further with this than me. I'm at work at the moment so I can't post any debug but i'm not getting anything new with the latest builds than I got in my earlier posts. Thanks Simon. > Larry > >
Date: January 31, 2006
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<25665.195.188.213.34.1138670471.squirrel-Sf9dbTz1eueS4hrmTveuuQ@xxxxxxxxxxxxxxxx>
References:
<25665.195.188.213.34.1138670471.squirrel@xxxxxxxxxxxxxx>
simonwoodward-QgLWrMLu8clzjhtm8Ag3mw@xxxxxxxxxxxxxxxx wrote:
Hi, I've been trying this for several days now with no success. I'm building the softmac layers with the daily snapshot each time and also the BCM43xx driver from the daily snapshot. I get warnings when compiling but no errors. I've got eth1 aliased to bcm43xx in my modprobe.conf The modules ieee80211_crypt ieee80211 and ieee80211softmace and bcm43xx all load with no errors (see my earlier posts) NOTE: I don' get the firmware_class module bt I'm using Fedora 4 and I believe that FC4 doesn't use firmware_class. I can ifconfig eth1 up with no errors but I get nothing further from dmesg. Looking at other peoples posts, they all get Softmac lines in their dmesg. I don't get any of these. There is a process which starts bcm43xx_wx/0 Whenever I unload the modules, they are automatically loaded again. Can I stop this action?
Unplug the card.
How can I check that my firmware is loading?
At or near line 2267 of bcm43xx_main.c is where the firmware is loaded. If loading failed, you would get a message in your logs from the printk statement contained there. Have you checked /var/log/messages for any bcm43xx messages?
I don't get the LED on the front lighting up which indicates the wireless is on. BTW this works fine under 2.6.14 with Ndiswrapper, but of course Ndiswrapper is broken under 2.6.15.
I don't understand this statement. On my system, 2.6.15 works with ndiswrapper. I don't use it anymore but keep one kernel so that I can use it if necessary.
Any ideas, a list of basic things to check please. Other people seem to have got this working fine so I don't know where I'm going wrong :-(
Did you use fwcutter on the driver version that you used to use with ndiswrapper? Larry
Date: January 31, 2006
From: simonwoodward-QgLWrMLu8clzjhtm8Ag3mw@xxxxxxxxxxxxxxxx
Hi, I've been trying this for several days now with no success. I'm building the softmac layers with the daily snapshot each time and also the BCM43xx driver from the daily snapshot. I get warnings when compiling but no errors. I've got eth1 aliased to bcm43xx in my modprobe.conf The modules ieee80211_crypt ieee80211 and ieee80211softmace and bcm43xx all load with no errors (see my earlier posts) NOTE: I don' get the firmware_class module bt I'm using Fedora 4 and I believe that FC4 doesn't use firmware_class. I can ifconfig eth1 up with no errors but I get nothing further from dmesg. Looking at other peoples posts, they all get Softmac lines in their dmesg. I don't get any of these. There is a process which starts bcm43xx_wx/0 Whenever I unload the modules, they are automatically loaded again. Can I stop this action? How can I check that my firmware is loading? I don't get the LED on the front lighting up which indicates the wireless is on. BTW this works fine under 2.6.14 with Ndiswrapper, but of course Ndiswrapper is broken under 2.6.15. Any ideas, a list of basic things to check please. Other people seem to have got this working fine so I don't know where I'm going wrong :-( Thanks Simon.
Date: January 30, 2006
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<200601291138.56241.mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
References:
<200601271842.54347.mbuesch@xxxxxxxxxx> <200601291138.56241.mbuesch@xxxxxxxxxx>
On Sun, Jan 29, 2006 at 11:38:56AM +0100, Michael Buesch wrote: > On Friday 27 January 2006 18:42, you wrote: > > Please do a > > git pull git://bu3sch.de/bcm43xx.git master-upstream > > to pull the bcm43xx-softmac branch. > > > > Please do a > > git pull git://bu3sch.de/bcm43xx.git dscape-upstream > > to pull the bcm43xx-dscape branch. > > Did you already pull? I did not see it in your git logs. > I have to do some maintainance work on my public repository > and I am waiting for your pull, before I shut down the server. I have it now. Sorry for being slow! John -- John W. Linville linville-2XuSBdqkA4R54TAoqtyWWQ@xxxxxxxxxxxxxxxx
Date: January 30, 2006
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@xxxxxxxxxxxxxxxx>
In-reply-to:
<2BBF92B6.3FF06568.C96398AC-YDxpq3io04c@xxxxxxxxxxxxxxxx>
References:
<2BBF92B6.3FF06568.C96398AC@xxxxxxx>
On Sun, 2006-01-29 at 02:46 -0500, JoschkaSulzer-YDxpq3io04c@xxxxxxxxxxxxxxxx wrote: > I want to spend hardware to this long needed project > How do i get the chipset of my card? Load the driver, it'll print out all the relevant information if it can at least detect your card. johannes
signature.asc
Description: This is a digitally signed message part
Date: January 30, 2006
From: Jason Lunz <lunz-G4qweqaPUAhg9hUCZPvPmw@xxxxxxxxxxxxxxxx>
This patch contains the beginnings of ethtool support for bcm43xx.
It only implements get_drvinfo and get_link, but that's enough for
ifplugd to use ethtool to know whether we're associated or not and then
start or stop dhcp as necessary.
Signed-off-by: Jason Lunz <lunz-G4qweqaPUAhg9hUCZPvPmw@xxxxxxxxxxxxxxxx>
---
Makefile | 2 +-
bcm43xx_ethtool.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++
bcm43xx_ethtool.h | 8 ++++++++
bcm43xx_main.c | 2 ++
4 files changed, 58 insertions(+), 1 deletion(-)
Index: bcm43xx/bcm43xx_ethtool.c
===================================================================
--- /dev/null
+++ bcm43xx/bcm43xx_ethtool.c
@@ -0,0 +1,47 @@
+/*
+
+ Broadcom BCM43xx wireless driver
+
+ ethtool support
+
+ Copyright (c) 2006 Jason Lunz <lunz-G4qweqaPUAhg9hUCZPvPmw@xxxxxxxxxxxxxxxx>
+
+ Some code in this file is derived from the 8139too.c driver
+ Copyright (C) 2002 Jeff Garzik
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; see the file COPYING. If not, write to
+ the Free Software Foundation, Inc., 51 Franklin Steet, Fifth Floor,
+ Boston, MA 02110-1301, USA.
+
+*/
+
+#include "bcm43xx.h"
+#include "bcm43xx_ethtool.h"
+
+#include <linux/netdevice.h>
+#include <linux/pci.h>
+#include <linux/string.h>
+
+static void bcm43xx_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo
*info)
+{
+ struct bcm43xx_private *bcm = bcm43xx_priv(dev);
+ strncpy(info->driver, DRV_NAME, sizeof(info->driver));
+ strncpy(info->version, DRV_VERSION, sizeof(info->version));
+ strncpy(info->bus_info, pci_name(bcm->pci_dev), ETHTOOL_BUSINFO_LEN);
+}
+
+struct ethtool_ops bcm43xx_ethtool_ops = {
+ .get_drvinfo = bcm43xx_get_drvinfo,
+ .get_link = ethtool_op_get_link,
+};
Index: bcm43xx/bcm43xx_ethtool.h
===================================================================
--- /dev/null
+++ bcm43xx/bcm43xx_ethtool.h
@@ -0,0 +1,8 @@
+#ifndef BCM43xx_ETHTOOL_H_
+#define BCM43xx_ETHTOOL_H_
+
+#include <linux/ethtool.h>
+
+extern struct ethtool_ops bcm43xx_ethtool_ops;
+
+#endif /* BCM43xx_ETHTOOL_H_ */
Index: bcm43xx/bcm43xx_main.c
===================================================================
--- bcm43xx.orig/bcm43xx_main.c
+++ bcm43xx/bcm43xx_main.c
@@ -49,6 +49,7 @@
#include "bcm43xx_pio.h"
#include "bcm43xx_power.h"
#include "bcm43xx_wx.h"
+#include "bcm43xx_ethtool.h"
MODULE_DESCRIPTION("Broadcom BCM43xx wireless driver");
@@ -4390,6 +4391,7 @@
net_dev->wireless_handlers = &bcm43xx_wx_handlers_def;
net_dev->irq = pdev->irq;
net_dev->watchdog_timeo = BCM43xx_TX_TIMEOUT;
+ net_dev->ethtool_ops = &bcm43xx_ethtool_ops;
/* initialize the bcm43xx_private struct */
bcm = bcm43xx_priv(net_dev);
Index: bcm43xx/Makefile
===================================================================
--- bcm43xx.orig/Makefile
+++ bcm43xx/Makefile
@@ -37,7 +37,7 @@
bcm43xx_radio.o bcm43xx_phy.o \
bcm43xx_power.o bcm43xx_wx.o \
bcm43xx_pio.o bcm43xx_ilt.o \
- bcm43xx_leds.o
+ bcm43xx_leds.o bcm43xx_ethtool.o
else
Date: January 30, 2006
From: Matt Eaton <bcm-bP/ZHATvpparTqXogv3Pbg@xxxxxxxxxxxxxxxx>
Using a vanilla kernel 2.6.15.1 + bcm43xx-20060125 + softmac-snapshot
downloaded Jan 29:
When modprobing bcm43xx:
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.7
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno-VuQAYsv1563Yd54FQh9/CA@xxxxxxxxxxxxxxxx>
bcm43xx driver 0.0.1
ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKB] -> GSI 5 (level,
low) -> IRQ 5
bcm43xx: Chip ID 0x4306, rev 0x2
bcm43xx: Number of cores: 6
bcm43xx: Core 0: ID 0x800, rev 0x2, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x4, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x80d, rev 0x1, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x807, rev 0x1, vendor 0x4243, disabled
bcm43xx: Core 4: ID 0x804, rev 0x7, vendor 0x4243, enabled
bcm43xx: Core 5: ID 0x812, rev 0x4, vendor 0x4243, disabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 1, Type 2, Revision 1
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: PHY disconnected
bcm43xx: Detected PHY: Version: 1, Type 0, Revision 2
bcm43xx: Detected Radio: ID: 1206017f (Manuf: 17f Ver: 2060 Rev: 1)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
Unable to handle kernel paging request at virtual address 00001533
printing eip:
d89ceef3
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: bcm43xx ieee80211softmac ieee80211 ieee80211_crypt
speedstep_centrino cpufreq_userspace cpufreq_powersave pcmcia
firmware_class joydev tsdev pcspkr rtc yenta_socket rsrc_nonstatic
pcmcia_core tg3 snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss
snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc ehci_hcd uhci_hcd
usbcore intel_agp agpgart evdev lp
CPU: 0
EIP: 0060:[<d89ceef3>] Not tainted VLI
EFLAGS: 00010286 (2.6.15.1)
EIP is at bcm43xx_channel_is_allowed+0xd/0xd5 [bcm43xx]
eax: d25ede46 ebx: 00000024 ecx: d25ede5c edx: 00001437
esi: 00000024 edi: 00000024 ebp: 00000024 esp: d25edc88
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 4615, threadinfo=d25ec000 task=d6872a50)
Stack: 0000000a 00000001 00000000 0000000d 0019a000 0000143c d89cf06c
00001437
00000024 d25ede46 d25ede47 00000006 d25ec000 d25ede64 0000000a
00000001
d89eed69 00000000 00000000 00000000 00000000 00000000 00000000
00000000
Call Trace:
[<d89cf06c>] bcm43xx_geo_init+0xb1/0x292 [bcm43xx]
[<d89d6cee>] bcm43xx_init_one+0xc6/0x148 [bcm43xx]
[<c0226382>] __pci_device_probe+0x4a/0x55
[<c02263b6>] pci_device_probe+0x29/0x3f
[<c0287289>] driver_probe_device+0x3a/0xa4
[<c028735e>] __driver_attach+0x0/0x43
[<c028739f>] __driver_attach+0x41/0x43
[<c028696b>] bus_for_each_dev+0x58/0x78
[<c02873c7>] driver_attach+0x26/0x2a
[<c028735e>] __driver_attach+0x0/0x43
[<c0286df1>] bus_add_driver+0x6b/0xc5
[<c02265d1>] __pci_register_driver+0x72/0x96
[<d8958028>] bcm43xx_init+0x28/0x2c [bcm43xx]
[<c01331af>] sys_init_module+0xbc/0x1f1
[<c0102f17>] sysenter_past_esp+0x54/0x75
Code: 9a 74 e7 e9 b7 fe ff ff c7 04 24 d8 ed 9e d8 e8 c6 9a 74 e7 b8 f4
ff ff ff e9 78 ff ff ff 53 83 ec 14 8b 54 24 1c 0f b6 5c 24 20 <8b> 82
fc 00 00 00 8b 40 08 0f b6 48 01 8b 44 24 24 c6 00 00 8b
Date: January 30, 2006
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<42eed4b90601291505k5316e679u2505386b2378c741-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<42eed4b90601170958s712a6891g62db41d97b8fea03@xxxxxxxxxxxxxx> <43CD3859.9080306@xxxxxxxxxxxx> <42eed4b90601171322w63fa1a2cs5e81b804657f328@xxxxxxxxxxxxxx> <43CD65EB.70802@xxxxxxxxxxxx> <42eed4b90601181650h2d124686w566814d20cc1a839@xxxxxxxxxxxxxx> <43CF1CAE.9030205@xxxxxxxxxxxx> <42eed4b90601291505k5316e679u2505386b2378c741@xxxxxxxxxxxxxx>
Paul T.Threshold wrote:
yes it works without patches, great!!! the only thing i'm concerned about is that up till now i've got to tell my airport base st. not to be a "closed" network, whe i'm the only computer connected... not a problem anyway :-)))))
I had to go on-line to find out what you meant by a "closed" network. Not broadcasting the essid does very little for security. My neighbor doesn't broadcast, but I can see his AP anyway if I put my interface in promiscous mode. As long as you use WPA with TKIP and a reasonably short period between key changes, no one will be able to collect enough packets to crack your password, particularly if the password is not in a dictionary and it has 10 or more characters init.
Larry
Date: January 29, 2006
From: "Paul T.Threshold" <paultt-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1C29166A-296B-43E4-AB27-6B03469E7CDF-ee4meeAH724@xxxxxxxxxxxxxxxx>
References:
<38294b740601221321n461c35c8r15bdec7d4062f9f6@xxxxxxxxxxxxxx> <200601222321.28052.mbuesch@xxxxxxxxxx> <38294b740601221440h31a389c2yd9951c36ed626b1f@xxxxxxxxxxxxxx> <43D42623.4020705@xxxxxxxxxx> <1C29166A-296B-43E4-AB27-6B03469E7CDF@xxxxxxx>
about dscap'ing, why do you want to use it? i'm using the driver as is, whit softmac implementation and it works like a chime :-)))) (wep, wpa or wpa2 too :-))))
Date: January 29, 2006
From: "Paul T.Threshold" <paultt-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<43CF1CAE.9030205-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
References:
<42eed4b90601170958s712a6891g62db41d97b8fea03@xxxxxxxxxxxxxx> <43CD3859.9080306@xxxxxxxxxxxx> <42eed4b90601171322w63fa1a2cs5e81b804657f328@xxxxxxxxxxxxxx> <43CD65EB.70802@xxxxxxxxxxxx> <42eed4b90601181650h2d124686w566814d20cc1a839@xxxxxxxxxxxxxx> <43CF1CAE.9030205@xxxxxxxxxxxx>
On 1/19/06, Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> wrote: > Paul T.Threshold wrote: > > > > thank you very much > > now it works, i had to add a patch to wpa_supplicant, posted before on > > the list :-) > > The only patch to wpa_supplicant that I know about was to implement the > dscape interface. That is > not needed for the softmac/bcm43xx combination. I'm using wpa_supplicant just > as I downloaded it. As > I said earlier, I configured it to handle both the wext and ndiswrapper > interfaces because I am > keeping a kernel with 8kB stacks that can run my wifi card with ndiswrapper. > I don't plan to use it, > but I'm comforted to know it is there if I need it. The kernel that I use > with bcm43xx has 4kB stacks. yes it works without patches, great!!! the only thing i'm concerned about is that up till now i've got to tell my airport base st. not to be a "closed" network, whe i'm the only computer connected... not a problem anyway :-)))))
Date: January 29, 2006
From: Bin Zhang <yangtze31-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<ed6b23a00601291228mc107a02x103e4195e5c55f8e-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<ed6b23a00601290935k448c6817q3d434afa46f66219@xxxxxxxxxxxxxx> <43DD0B3B.8050603@xxxxxxxxxxxx> <ed6b23a00601291228mc107a02x103e4195e5c55f8e@xxxxxxxxxxxxxx>
See the updated http://forums.gentoo.org/viewtopic-t-409194-postdays-0-postorder-asc-start-0.html Regards, Bin
Date: January 29, 2006
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<ed6b23a00601291228mc107a02x103e4195e5c55f8e-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<ed6b23a00601290935k448c6817q3d434afa46f66219@xxxxxxxxxxxxxx> <43DD0B3B.8050603@xxxxxxxxxxxx> <ed6b23a00601291228mc107a02x103e4195e5c55f8e@xxxxxxxxxxxxxx>
Travis Friesen wrote:
Thanks for the input, Larry. I have incoroporated most of your suggestions, but not the talk on the kernel stack size. As I see it (and by all means correct me if I am wrong) the size of the stack the kernel is using does not affect the bcm43xx driver. It would be a useful thing to discuss if the guide were a talk on ndiswrapper, or on kernel optimization techniques.
The only effect is that your kernel will handle more threads for a given amount of memory and not suffer from memory fragmentation if 4K stacks are used; therefore, 4K is recommended. You are correct that the bcm43xx driver will work with both 4 and 8K stacks, whereas the Windows driver should have 8K stacks. --snip --
If you intend to use WPA encryption with your wireless connection, it is necessary to use the separate WPA utility. This can be acquired either through your distribution, or downloaded and installed separately.
I think that wpa_supplicant should be mentioned by name as that gives a search name that will locate the appropriate site. Googling for "WPA utility" didn't provide a direct reference to the wpa_supplicant site in the first 50 entries.
Larry
Date: January 29, 2006
From: Travis Friesen <travis_friesen-EkmVulN54Sk@xxxxxxxxxxxxxxxx>
In-reply-to:
<43DD0B3B.8050603-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
References:
<ed6b23a00601290935k448c6817q3d434afa46f66219@xxxxxxxxxxxxxx> <43DD0B3B.8050603@xxxxxxxxxxxx>
Thanks for the input, Larry. I have incoroporated most of your suggestions, but not the talk on the kernel stack size. As I see it (and by all means correct me if I am wrong) the size of the stack the kernel is using does not affect the bcm43xx driver. It would be a useful thing to discuss if the guide were a talk on ndiswrapper, or on kernel optimization techniques. The newest version of the file will also be available on http://random.blackworlds.org/bcm43xx-how-to.txt On 1/29/06, Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> wrote: > Travis Friesen wrote: > > > > The purpose of this document is to provide a basic how-to for installing > > the bcm43xx Linux driver > > with the ieee8011 softmac wireless stack. To use more davanced driver > > features, such as WPA, it > > is necessary to apply the devicescape wireless patch to the kernel, but > > that is outside the scope > > of this guide. > > It is not necessary to use the devicescape stack to enable WPA. I first used > dscape, but found that > I succeeded in getting a connection only about 25% of the time. I then turned > to softmac, coded some > patches that were included at least two weeks ago, and have been using WPA on > softmac ever since. > > > So let's get right into it. > > > > Before we begin, you will need a 2.6.15 kernel. To my knowledge, and as of > > this writing, no major > > distribution is yet using the 2.6.15 kernel, with the exception of Gentoo > > (brief plug for my > > favorite distro). This document will assume that the user has a 2.6.15 or > > better kernel, and/or > > is capable of acquiring and configuring it. > > I think you should say "2.6.15 or later kernel". There is lots of debate if > later kernels are in > fact better. > > > While most major distributions will include these options by default, > > anyone compiling his or her > > own kernel should be sure to select them. > > > > Loadable Module Support ---> Enable loadable Module Support Module > > Unloading (I recommend) > > Forced Module Unloading (I also recommend) Automatic Kernel Module Loading > > (I recommend) Bus > > options (PCI etc.) ---> PCI Hotplug Support ---> Support for PCI Hotplug > > > > Networking ---> Networking Support Generic IEEE 802.11 Networking Stack > > IEEE 802.11 WEP > > Encryption (recommended) > > > > Kernel Hacking ---> Kernel debugging Debug Filesystem (recommended) > > > > If you wish to compile any of these as modules, go right ahead. Of course, > > include any other > > drivers and options that your system requires. > > There should probably be a discussion of Kernel Stack size under Kernel > Hacking. I would suggest > something like: Users of i386 hardware (PC's) should select the 4K Kernel > Stack option unless they > plan to use ndiswrapper, which requires 8K kernel stacks. > > > Once your Kernel is setup, we will need to acquire the source files for > > each of the three parts > > of the driver. > ---snip --- > > > If no error messages are returned, then success! You have successfully > > installed the Linux driver > > for the Broadcom 43xx wireless chipset. Otherwise, go back and try again, > > perhaps with newer > > firmware. If worse comes to worst, include a detailed description of your > > problem, error messages > > received and the contents of dmesg and post it to the bcm43xx mailing list. > > More information is > > available at http://bcm43xx.berlios.de > > Here I would add a section describing that wpa_supplicant is needed to use > WPA encryption. The > program can either be added from their distribution, or downloaded. At a > minimum, the supplicant > must be configured for the wext (wireless extensions) interface. A suitable > wpa_supplicant.conf for > WPA-PSK TKIP is as follows: > > ctrl_interface=/var/run/wpa_supplicant > network={ > scan_ssid=1 > ssid=<your ssid> > key_mgmt=WPA-PSK > psk=<your shared secret> > } > > > > > As this driver is a work in progress, there is no guarantee that > > successfully installing the > > driver means you will be able to connect seamlessly to any wireless access > > point. Stay on top of > > recent developments by joining the bcm43xx mailing list, also at the above > > address. > > > > > > This first draft was written by Travis Friesen, and I guess is released > > under the GPL? Questions, > > comments suggestions: travis_friesen-EkmVulN54Sk@xxxxxxxxxxxxxxxx > > You have a really good first start. > > Thanks, > > Larry >
bcm43xx-how-to.txt
Description: Text document
Date: January 29, 2006
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<ed6b23a00601290935k448c6817q3d434afa46f66219-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<ed6b23a00601290935k448c6817q3d434afa46f66219@xxxxxxxxxxxxxx>
Travis Friesen wrote:
The purpose of this document is to provide a basic how-to for installing the bcm43xx Linux driver with the ieee8011 softmac wireless stack. To use more davanced driver features, such as WPA, it is necessary to apply the devicescape wireless patch to the kernel, but that is outside the scope of this guide.
It is not necessary to use the devicescape stack to enable WPA. I first used dscape, but found that I succeeded in getting a connection only about 25% of the time. I then turned to softmac, coded some patches that were included at least two weeks ago, and have been using WPA on softmac ever since.
So let's get right into it. Before we begin, you will need a 2.6.15 kernel. To my knowledge, and as of this writing, no major distribution is yet using the 2.6.15 kernel, with the exception of Gentoo (brief plug for my favorite distro). This document will assume that the user has a 2.6.15 or better kernel, and/or is capable of acquiring and configuring it.
I think you should say "2.6.15 or later kernel". There is lots of debate if later kernels are in fact better.
While most major distributions will include these options by default, anyone compiling his or her own kernel should be sure to select them.Loadable Module Support ---> Enable loadable Module Support Module Unloading (I recommend) Forced Module Unloading (I also recommend) Automatic Kernel Module Loading (I recommend) Busoptions (PCI etc.) ---> PCI Hotplug Support ---> Support for PCI Hotplug Networking ---> Networking Support Generic IEEE 802.11 Networking Stack IEEE 802.11 WEP Encryption (recommended) Kernel Hacking ---> Kernel debugging Debug Filesystem (recommended) If you wish to compile any of these as modules, go right ahead. Of course, include any other drivers and options that your system requires.
There should probably be a discussion of Kernel Stack size under Kernel Hacking. I would suggest something like: Users of i386 hardware (PC's) should select the 4K Kernel Stack option unless they plan to use ndiswrapper, which requires 8K kernel stacks.
Once your Kernel is setup, we will need to acquire the source files for each of the three parts of the driver.
---snip ---
If no error messages are returned, then success! You have successfully installed the Linux driver for the Broadcom 43xx wireless chipset. Otherwise, go back and try again, perhaps with newer firmware. If worse comes to worst, include a detailed description of your problem, error messages received and the contents of dmesg and post it to the bcm43xx mailing list. More information is available at http://bcm43xx.berlios.de
Here I would add a section describing that wpa_supplicant is needed to use WPA encryption. The program can either be added from their distribution, or downloaded. At a minimum, the supplicant must be configured for the wext (wireless extensions) interface. A suitable wpa_supplicant.conf for WPA-PSK TKIP is as follows:
ctrl_interface=/var/run/wpa_supplicant
network={
scan_ssid=1
ssid=<your ssid>
key_mgmt=WPA-PSK
psk=<your shared secret>
}
As this driver is a work in progress, there is no guarantee that successfully installing the driver means you will be able to connect seamlessly to any wireless access point. Stay on top of recent developments by joining the bcm43xx mailing list, also at the above address. This first draft was written by Travis Friesen, and I guess is released under the GPL? Questions, comments suggestions: travis_friesen-EkmVulN54Sk@xxxxxxxxxxxxxxxx
You have a really good first start. Thanks, Larry
Date: January 29, 2006
From: Travis Friesen <travis_friesen-EkmVulN54Sk@xxxxxxxxxxxxxxxx>
Hello all. I've noticed on the mailing list that a number of people have been asking for instructions on how to install the driver, and let's face it: As it stands now, getting the bcm43xx driver installed is not a task for Linux newcomers. So, I have thrown together a basic guide on how to install the bcm43xx driver from scratch with the softmac stack. Please reply with your thoughts, suggestions, comments, etc. I have no personal attachment to this work, so feel free to criticize liberally.
how-to.txt
Description: Text document
Date: January 29, 2006
From: Christian <email-IGuAFssZLu0ncmUr42MLT3dH8wOhNw5B@xxxxxxxxxxxxxxxx>
In-reply-to:
<20060128110016.2110.81594.Mailman-p+i3VeVUqem2FBT93xDlsQ@xxxxxxxxxxxxxxxx>
References:
<20060128110016.2110.81594.Mailman@xxxxxxxxxxxxxx>
On Saturday 28 January 2006 12:00, bcm43xx-dev-request-tdrK/OAtAx2ELgA04lAiVw@xxxxxxxxxxxxxxxx wrote: > [Bcm43xx-dev] DHCP and access point association Hi, I have the same problem on gentoo. Seems that an ifconfig up <interfacename> is missing somewhere and then /lib/rcscripts/net.modules.d/iwconfig (called from the init net.<interfacename> script) is checking the interface in /proc/net/wireless which the driver doesn't seem to create. But even with removing the check and the additional ifconfig up I was not able to figure out the correct order in which to do the ifconfig up, iwconfig key, etc commands. So unfortunatly I switched back to ndiswrapper for now. Greets Chris -- email at christian hoffmann . info
Date: January 29, 2006
From: Michael Buesch <mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
In-reply-to:
<200601271842.54347.mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
References:
<200601271842.54347.mbuesch@xxxxxxxxxx>
On Friday 27 January 2006 18:42, you wrote: > Please do a > git pull git://bu3sch.de/bcm43xx.git master-upstream > to pull the bcm43xx-softmac branch. > > Please do a > git pull git://bu3sch.de/bcm43xx.git dscape-upstream > to pull the bcm43xx-dscape branch. Did you already pull? I did not see it in your git logs. I have to do some maintainance work on my public repository and I am waiting for your pull, before I shut down the server. -- Greetings Michael.
pgplQZoiaPWWQ.pgp
Description: PGP signature
Date: January 29, 2006
From: JoschkaSulzer-YDxpq3io04c@xxxxxxxxxxxxxxxx
I want to spend hardware to this long needed project How do i get the chipset of my card?
Date: January 28, 2006
From: Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@xxxxxxxxxxxxxxxx>
As somebody may have noticed, I set up a PayPal account for donations. These will be used to buy unsupported hardware (currently we think of focusing on card with B PHYs), in order to possibly make it working. There's a link for donating on the webpage, https://www.paypal.com/cgi-bin/webscr?cmd=_xclick&business=st3%40riseup%2enet&item_name=Support%20the%20bcm43xx%20project&no_shipping=1&cn=List%20me%3f%20Yes%2fNo%2fWith%20amount&tax=0¤cy_code=EUR&lc=GB&bn=PP%2dDonationsBF&charset=UTF%2d8 and list of donations here: http://openfacts.berlios.de/index-en.phtml?title=Bcm43xxDonations -- ciao st3
Date: January 27, 2006
From: Jesse Barnes <jbarnes-Y1mF5jBUw70BENJcbMCuUQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<645b596b0601271422y385cbdd2ra3773cfa4be5da3c-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<645b596b0601271422y385cbdd2ra3773cfa4be5da3c@xxxxxxxxxxxxxx>
On Friday, January 27, 2006 2:22 pm, Marc Morrisette wrote: > I checked my > kernel logs, and it appears that it's not associating/authenticating > with the access point properly. It tries several times but seems to > give up. Here's the relevant portion from the kernel logs. Am I > doing something wrong, or do I just need a newer version of the > driver? I currently have my system set to emerge sync on Sunday > morning, so my portage tree should update then if this is a known > issue that has been fixed. Also, why do the entries for softmac show > /var/tmp/portage/xxx/work? I believe that this is the portage build > directory, not where the files are actually installed. I see similar behavior on my PowerBook. Doing an 'ifconfig up' on the interface before doing the 'iwconfig essid <foo>' makes it associate properly though. I'm not sure how hard this is to fix (seems like it should be a simple init ordering issue), I was hoping to have time to look at it this weekend (though some of the others on the list could probably fix it just by looking at the code). Jesse
Date: January 27, 2006
From: Marc Morrisette <akaihiryuu-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
Date: January 27, 2006
From: jeff-+Shh3Y/l6y5dz2imjWt+ww@xxxxxxxxxxxxxxxx
What is the current state of the bcm43xx driver with regards to software suspend 2? If it currently, properly coexists, has anyone had any luck with bcm43xx and swsusp2 on an amd64 platform? Thanks, Jeff
Date: January 27, 2006
From: Michael Buesch <mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
Hi John,
I synced my git repository with the bcm43xx SVN repository.
I will continue to develop the driver in git, so these ugly syncing
will not be needed any longer. I will poke you from time to time
to pull from my repos. (I don't know how the other bcm43xx developers
will handle it. I suggest they set up a git repository, too)
Please do a
git pull git://bu3sch.de/bcm43xx.git master-upstream
to pull the bcm43xx-softmac branch.
Please do a
git pull git://bu3sch.de/bcm43xx.git dscape-upstream
to pull the bcm43xx-dscape branch.
master ShortLog:
Michael Buesch:
[bcm43xx] sync with svn.berlios.de
[bcm43xx] remove linux version compatibility code.
[bcm43xx] Move README file to Documentation directory.
[bcm43xx] remove redundant COPYING file.
dscape ShortLog:
Michael Buesch:
[bcm43xx] sync with svn.berlios.de
[bcm43xx] Move documentation to Documentation subdirectory and move
scripts to scripts subdirectory.
[bcm43xx] Remove redundant COPYING file.
--
Greetings Michael.
pgpWS5TaZaOXI.pgp
Description: PGP signature
Date: January 27, 2006
From: Christopher Hotchkiss <christopher.hotchkiss-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
Hey everyone, I am currently having problems getting the network interface of the softmac branch to run. I am running a 2.6.15 kernel, amd64, gentoo. I am able to build and modprobe the 20060125 snapshot but when i try to ifconfig up it, it causes ifconfig to segfault and hangs the terminal. Checking dmesg I get the following output: bcm43xx driver 0.0.1 ACPI: PCI Interrupt 0000:05:02.0[A] -> GSI 20 (level, low) -> IRQ 20 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, vendor 0x4243, enabled bcm43xx: PHY connected bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7 bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) bcm43xx: Radio turned off bcm43xx: Radio turned off bcm43xx: PHY connected bcm43xx: Radio turned on bcm43xx: Chip initialized ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at arch/x86_64/kernel/traps.c:336 invalid operand: 0000 [1] PREEMPT CPU 0 Modules linked in: bcm43xx ieee80211softmac ieee80211 ieee80211_crypt ide_cs ipv6 pcmcia firmware_class pcspkr yenta_socket rsrc_nonstatic pcmcia_core 8139too mii snd_atiixp_modem snd_atiixp snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd snd_page_alloc video thermal processor fan container button battery ac radeon drm dm_mirror dm_mod ata_piix ahci sata_qstor sata_vsc sata_uli sata_sis sata_sx4 sata_nv sata_via sata_svw sata_sil sata_promise libata sbp2 ohci1394 ieee1394 sl811_hcd ohci_hcd uhci_hcd usb_storage usbhid ehci_hcd usbcore Pid: 15126, comm: ifconfig Tainted: GF 2.6.15-gentoo-r1 #1 RIP: 0010:[<ffffffff8010fb03>] [<ffffffff8010fb03>] RSP: 0018:ffff81001a4d5c50 EFLAGS: 00010206 RAX: ffffffffc0000000 RBX: ffff810056deb380 RCX: 0000000000000964 RDX: 0000000042361974 RSI: 0000000000000000 RDI: ffff810057617870 RBP: ffff8100439ecac0 R08: 0000000000000964 R09: ffff810056deb380 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000042361010 R13: 0000000000000000 R14: ffff81000009c000 R15: ffff81004b471000 FS: 000000000052dae0(0000) GS:ffffffff80479800(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00000032f08219a0 CR3: 000000001cbe2000 CR4: 00000000000006a0 Process ifconfig (pid: 15126, threadinfo ffff81001a4d4000, task ffff8100443496d0) Stack: ffffffff881a8559 0000000000000000 ffffffff8014cbaa ffffffff803f4ef0 ffff810057617870 ffff8100439ecac0 0000000000000000 ffff81003d2fcc38 0000000000000200 0000000000000000 Call Trace:[<ffffffff881a8559>] [<ffffffff8014cbaa>] [<ffffffff881a8957>] [<ffffffff881a8dc9>] [<ffffffff881a50d2>] [<ffffffff8019486a>] [<ffffffff8032a14c>] [<ffffffff8032b1c4>] [<ffffffff8036356b>] [<ffffffff803647eb>] [<ffffffff80321bb4>] [<ffffffff80321dc3>] [<ffffffff80176ea9>] [<ffffffff8017716e>] [<ffffffff801771bb>] [<ffffffff8010e72a>] Code: 0f 0b 68 a0 50 39 80 c2 50 01 c3 51 9c 8f 04 24 fa bf 01 00 RIP [<ffffffff8010fb03>] RSP <ffff81001a4d5c50> Any ideas on what is wrong? Also since I only belong to the digest version of the list, please CC me if you need more information. -- Christopher Hotchkiss chotchki-30IwKtKq/fj2fBVCVOL8/A@xxxxxxxxxxxxxxxx (813)326-2030 -- Christopher Hotchkiss christopher.hotchkiss-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx (813)326-2030
Date: January 27, 2006
From: Christopher Hotchkiss <christopher.hotchkiss-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
Hey everyone,
I am currently having problems getting the network interface of the softmac
branch to run. I am running a 2.6.15 kernel, amd64, gentoo. I am able to
build and modprobe the 20060125 snapshot but when i try to ifconfig up it, it
causes ifconfig to segfault and hangs the terminal. Checking dmesg I get the
following output:
bcm43xx driver 0.0.1
ACPI: PCI Interrupt 0000:05:02.0[A] -> GSI 20 (level, low) -> IRQ 20
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, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: Chip initialized
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at arch/x86_64/kernel/traps.c:336
invalid operand: 0000 [1] PREEMPT
CPU 0
Modules linked in: bcm43xx ieee80211softmac ieee80211 ieee80211_crypt ide_cs
ipv6 pcmcia firmware_class pcspkr yenta_socket rsrc_nonstatic pcmcia_core
8139too mii snd_atiixp_modem snd_atiixp snd_ac97_codec snd_ac97_bus snd_pcm
snd_timer snd snd_page_alloc video thermal processor fan container button
battery ac radeon drm dm_mirror dm_mod ata_piix ahci sata_qstor sata_vsc
sata_uli sata_sis sata_sx4 sata_nv sata_via sata_svw sata_sil sata_promise
libata sbp2 ohci1394 ieee1394 sl811_hcd ohci_hcd uhci_hcd usb_storage usbhid
ehci_hcd usbcore
Pid: 15126, comm: ifconfig Tainted: GF 2.6.15-gentoo-r1 #1
RIP: 0010:[<ffffffff8010fb03>] [<ffffffff8010fb03>]
RSP: 0018:ffff81001a4d5c50 EFLAGS: 00010206
RAX: ffffffffc0000000 RBX: ffff810056deb380 RCX: 0000000000000964
RDX: 0000000042361974 RSI: 0000000000000000 RDI: ffff810057617870
RBP: ffff8100439ecac0 R08: 0000000000000964 R09: ffff810056deb380
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000042361010
R13: 0000000000000000 R14: ffff81000009c000 R15: ffff81004b471000
FS: 000000000052dae0(0000) GS:ffffffff80479800(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000032f08219a0 CR3: 000000001cbe2000 CR4: 00000000000006a0
Process ifconfig (pid: 15126, threadinfo ffff81001a4d4000, task
ffff8100443496d0)
Stack: ffffffff881a8559 0000000000000000 ffffffff8014cbaa ffffffff803f4ef0
ffff810057617870 ffff8100439ecac0 0000000000000000 ffff81003d2fcc38
0000000000000200 0000000000000000
Call Trace:[<ffffffff881a8559>] [<ffffffff8014cbaa>] [<ffffffff881a8957>]
[<ffffffff881a8dc9>] [<ffffffff881a50d2>] [<ffffffff8019486a>]
[<ffffffff8032a14c>] [<ffffffff8032b1c4>] [<ffffffff8036356b>]
[<ffffffff803647eb>] [<ffffffff80321bb4>] [<ffffffff80321dc3>]
[<ffffffff80176ea9>] [<ffffffff8017716e>] [<ffffffff801771bb>]
[<ffffffff8010e72a>]
Code: 0f 0b 68 a0 50 39 80 c2 50 01 c3 51 9c 8f 04 24 fa bf 01 00
RIP [<ffffffff8010fb03>] RSP <ffff81001a4d5c50>
Any ideas on what is wrong? Also since I only belong to the digest version of
the list, please CC me if you need more information.
--
Christopher Hotchkiss
chotchki-30IwKtKq/fj2fBVCVOL8/A@xxxxxxxxxxxxxxxx
(813)326-2030
Date: January 27, 2006
From: Mike Leahy <mgleahy-6duGhz7i8susTnJN9+BGXg@xxxxxxxxxxxxxxxx>
Hello list, I'm just wondering if anyone knows where I can find some instructions or How-to documentation - I've got the same WPC54G pcmcia card on my laptop, with FC5 test 2 fully updated. I can get as far as getting some basic info on the card from iwconfig (which reported a "Broadcom 4306" as the nickname), but I can't seem to get it to connect to a wireless hub either by mucking around with iwconfig or KWifiManager. I've been looking around online, now that I see this post, I'd be delighted to know how anyone else may have got this card working (whether or not the LED works is secondary given my current problem)... Thanks in advance for any help, Mike
Date: January 26, 2006
From: Michael Buesch <mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
In-reply-to:
<200601260032.50602.ceriloch-Oofn5nlGvgtg9hUCZPvPmw@xxxxxxxxxxxxxxxx>
References:
<200601260032.50602.ceriloch@xxxxxxxxxxxx>
On Thursday 26 January 2006 09:32, Ceriloch wrote: > One of the if statements in bcm43xx_phy_lo_b_measure in bcm43xx_phy.c had > been > incorrectly set to == 2053 instead of == 0x2053. Thanks, applied. -- Greetings Michael.
pgpxTLl6UdxSU.pgp
Description: PGP signature
Date: January 26, 2006
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@xxxxxxxxxxxxxxxx>
Probably a long shot, but... Has anyone approached Broadcom about making a pristine firmware image available? Such an image should (might?) eliminate the need for using fwcutter to take firmware from binary drivers. Distro vendors will probably want something like that to be available...? Presuming that no pristine firmware image is currently available, does anyone have specific contacts at Broadcom who might be worth approaching? Thanks, John -- John W. Linville linville-2XuSBdqkA4R54TAoqtyWWQ@xxxxxxxxxxxxxxxx
Date: January 26, 2006
From: Denis Vlasenko <vda@xxxxxxxxxxxxx>
In-reply-to:
<20060125154402.GB9224@xxxxxxxxxxxx>
References:
<20060118200616.GC6583@xxxxxxxxxxxxx> <1138026752.3957.98.camel@localhost
> <20060125154402.GB9224@xxxxxxxxxxxx>
On Wednesday 25 January 2006 17:44, Stuffed Crust wrote: > On Mon, Jan 23, 2006 at 03:32:32PM +0100, Johannes Berg wrote: > > Shouldn't you BSS-filter management packets too? > > Filtering on BSSID is necessary for management frames, especially when > multicast management frames are thrown into the mix. ieee80211_rx_mgt can do any filtering necessary. Foreign mgmt packets, if properly used, can provide us with constantly updated info about local wireless neighborhood: available Ad-hoc networks and BSSes, signal quality of APs etc. Something resembling constantly running scan. For example, acx driver does exactly this. Note that typically mgmt traffic is rather low and processing it (instead of dropping) won't add much overhead. > For example, STAs are supposed to respect broadcast disassoc/deauth > messages, but of course should ignore them if they're not destined for > the local BSSID. This filtering can (should) be done in ieee80211_rx_mgt. > The only extra-BSS management frames that should not be dropped are are > beacons and probe responses. That said, probe responses are directed so > our A1 (RA) filter will probably drop the frame if it is not destined > for us. -- vda
Date: January 26, 2006
From: Ceriloch <ceriloch-Oofn5nlGvgtg9hUCZPvPmw@xxxxxxxxxxxxxxxx>
One of the if statements in bcm43xx_phy_lo_b_measure in bcm43xx_phy.c had been incorrectly set to == 2053 instead of == 0x2053. - Adam Shewchuk
2053phy.patch
Description: Text Data
Date: January 25, 2006
From: Michael Tautschnig <michael.tautschnig-t/GRpO4CuxUg9ELcbhaJlAC/G2K4zDHf@xxxxxxxxxxxxxxxx>
In-reply-to:
<20060125143655.GA26657-0duS9x1uEQtGWvitb5QawA@xxxxxxxxxxxxxxxx>
References:
<20060124150625.GA12960@xxxxxxxxxx> <20060124155713.GB29721@xxxxxxxxx> <20060125143655.GA26657@xxxxxxxxxx>
> > I have the same here. > > Did you enable a special hotplug option in the kernel? > > I have CONFIG_FW_LOADER=y in my .config > I've built that as a module, but that shouldn'