Custom Search
|
Date: March 31, 2006
From: "LUCA BENINI" <lbenini-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<200603302325.11751.florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx>
References:
<200603302255.31052.mbuesch@xxxxxxxxxx> <200603302325.11751.florian@xxxxxxxxxxxxx>
Hi... ehm... i use 4318 with 2.6.16, and absolutly no real problem (sometimes i must bring eth down, up, down to put in monitor mode, but hey it's work!). I read this ml to stay updated to release and news, but if i can help ask without problem. The card works for Florian and me, so seem like the drivers is good, but some config broken it.... Luca 2006/3/30, Florian Fainelli <florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx>: > Hello Michael, > > I got a bcm 4318 card (Airport Extreme) and do not have that much problems > with it, wpa is working etc ... > > Which kind of problems are you mentioning ? > > Le Jeudi 30 Mars 2006 22:55, Michael Buesch a écrit: > > Please, don't waste your time by doing experiments with > > the 4318 device, yet. > > > > ==> It is broken. > > ==> We _know_ that. > > > > And we are in the progress to fix this. > > I will announce on this mailing list, when the driver > > is ready for testing on the 4318. Until this announcement, > > please _don't_ send 4318 related bugreports anymore. It is > > just a waste of time. > > > > (If you see problems with the 4318 _after_ I made the > > announcement here, please send bugreports) > > -- > Cordialement, Florian Fainelli > --------------------------------- > Email: florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx > Portail: http://www.alphacore.net > Tel: +33609026495 > --------------------------------- > > >
Date: March 30, 2006
From: Florian Fainelli <florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx>
In-reply-to:
<200603302255.31052.mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
References:
<200603302255.31052.mbuesch@xxxxxxxxxx>
Hello Michael, I got a bcm 4318 card (Airport Extreme) and do not have that much problems with it, wpa is working etc ... Which kind of problems are you mentioning ? Le Jeudi 30 Mars 2006 22:55, Michael Buesch a écrit : > Please, don't waste your time by doing experiments with > the 4318 device, yet. > > ==> It is broken. > ==> We _know_ that. > > And we are in the progress to fix this. > I will announce on this mailing list, when the driver > is ready for testing on the 4318. Until this announcement, > please _don't_ send 4318 related bugreports anymore. It is > just a waste of time. > > (If you see problems with the 4318 _after_ I made the > announcement here, please send bugreports) -- Cordialement, Florian Fainelli --------------------------------- Email: florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx Portail: http://www.alphacore.net Tel: +33609026495 ---------------------------------
pgpl80d7m3OxY.pgp
Description: PGP signature
Date: March 30, 2006
From: Michael Buesch <mbuesch-KuiJ5kEpwI6ELgA04lAiVw@xxxxxxxxxxxxxxxx>
Please, don't waste your time by doing experiments with the 4318 device, yet. ==> It is broken. ==> We _know_ that. And we are in the progress to fix this. I will announce on this mailing list, when the driver is ready for testing on the 4318. Until this announcement, please _don't_ send 4318 related bugreports anymore. It is just a waste of time. (If you see problems with the 4318 _after_ I made the announcement here, please send bugreports) -- Greetings Michael.
pgpWFQ9Dd5Wgq.pgp
Description: PGP signature
Date: March 30, 2006
From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143712332.10771.7.camel@localhost
>
References:
<1143712332.10771.7.camel@localhost
>
On Thu, 2006-03-30 at 02:52 -0700, Nix N. Nix wrote: > Does the 2006-03-30 all-in-one snapshot contain these changes ? I have > tried the latest snapshot with NetworkManager, but to no avail. I think it should -- certainly everything was submitted. However, I was testing with the NetworkManager from FC4, not the new one from FC5. With _new_ versions of NetworkManager you need one more change, which Dan Williams provided. It makes softmac produce a standard 'association' event, rather than a custom event of its own. This makes the new NetworkManager work for me with WEP, although WPA still doesn't work (unless I use wpa_supplicant manually). That's in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183245 WPA doesn't work with a network which doesn't broadcast its SSID either -- not even with wpa_supplicant, unless I use the evil hack at http://david.woodhou.se/wpa_supplicant-hack.patch --- [SOFTMAC] Send WEXT assoc/disassoc events to userspace For whatever reason, softmac is sending custom events to userspace already, but it should _really_ be sending the right WEXT events instead. Signed-off-by: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx> Signed-off-by: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@xxxxxxxxxxxxxxxx> --- a/include/net/ieee80211softmac.h.assoc 2006-03-09 13:14:56.000000000 -0500 +++ b/include/net/ieee80211softmac.h 2006-03-09 13:15:22.000000000 -0500 @@ -267,8 +267,9 @@ #define IEEE80211SOFTMAC_EVENT_AUTH_FAILED 5 #define IEEE80211SOFTMAC_EVENT_AUTH_TIMEOUT 6 #define IEEE80211SOFTMAC_EVENT_ASSOCIATE_NET_NOT_FOUND 7 +#define IEEE80211SOFTMAC_EVENT_DISASSOCIATED 8 /* keep this updated! */ -#define IEEE80211SOFTMAC_EVENT_LAST 7 +#define IEEE80211SOFTMAC_EVENT_LAST 8 /* * If you want to be notified of certain events, you can call * ieee80211softmac_notify[_atomic] with --- a/net/ieee80211/softmac/ieee80211softmac_event.c.assoc 2006-03-09 13:05:09.000000000 -0500 +++ b/net/ieee80211/softmac/ieee80211softmac_event.c 2006-03-09 15:21:12.000000000 -0500 @@ -67,6 +67,7 @@ "authenticating failed", "authenticating timed out", "associating failed because no suitable network was found", + "disassociated", }; @@ -128,13 +129,32 @@ ieee80211softmac_call_events_locked(struct ieee80211softmac_device *mac, int event, void *event_ctx) { struct ieee80211softmac_event *eventptr, *tmp; - union iwreq_data wrqu; - char *msg; if (event >= 0) { - msg = event_descriptions[event]; - wrqu.data.length = strlen(msg); - wireless_send_event(mac->dev, IWEVCUSTOM, &wrqu, msg); + union iwreq_data wrqu; + int we_event; + char *msg = NULL; + + if (event == IEEE80211SOFTMAC_EVENT_ASSOCIATED) { + struct ieee80211softmac_network *network = + (struct ieee80211softmac_network *)event_ctx; + wrqu.data.length = 0; + wrqu.data.flags = 0; + memcpy(wrqu.ap_addr.sa_data, &network->bssid[0], ETH_ALEN); + wrqu.ap_addr.sa_family = ARPHRD_ETHER; + we_event = SIOCGIWAP; + } else if (event == IEEE80211SOFTMAC_EVENT_DISASSOCIATED) { + wrqu.data.length = 0; + wrqu.data.flags = 0; + memset(&wrqu, '\0', sizeof (union iwreq_data)); + wrqu.ap_addr.sa_family = ARPHRD_ETHER; + we_event = SIOCGIWAP; + } else { + msg = event_descriptions[event]; + wrqu.data.length = strlen(msg); + we_event = IWEVCUSTOM; + } + wireless_send_event(mac->dev, we_event, &wrqu, msg); } if (!list_empty(&mac->events)) --- a/net/ieee80211/softmac/ieee80211softmac_assoc.c.assoc 2006-03-09 13:13:54.000000000 -0500 +++ b/net/ieee80211/softmac/ieee80211softmac_assoc.c 2006-03-09 13:21:00.000000000 -0500 @@ -104,6 +104,7 @@ /* Do NOT clear bssvalid as that will break ieee80211softmac_assoc_work! */ mac->associated = 0; mac->associnfo.associating = 0; + ieee80211softmac_call_events_locked(mac, IEEE80211SOFTMAC_EVENT_DISASSOCIATED, NULL); spin_unlock_irqrestore(&mac->lock, flags); } @@ -378,6 +379,7 @@ spin_lock_irqsave(&mac->lock, flags); mac->associnfo.bssvalid = 0; mac->associated = 0; + ieee80211softmac_call_events_locked(mac, IEEE80211SOFTMAC_EVENT_DISASSOCIATED, NULL); schedule_work(&mac->associnfo.work); spin_unlock_irqrestore(&mac->lock, flags); -- dwmw2
Date: March 30, 2006
From: wrobell <wrobell-k0Z414SquRyhPH1hqNUYSQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<200603301643.22073.frafore-IWqWACnzNjyonA0d6jMUrA@xxxxxxxxxxxxxxxx>
References:
<slrne2mkgm.p7u.joerg@xxxxxxxxxxxx> <200603301643.22073.frafore@xxxxxxxxxx>
On Thu, 2006-03-30 at 16:43 +0200, Francesco Foresti wrote: > On Thu, 2006-03-30 at 05:35, Joerg Sommer wrote: > [cut] > > Hi, > > I've got the same problem here, in a much similar environment: > ibook g4, debian with 2.6.15-1-powerpc (debian image), > bcm43xx source 2006-02-12, same firmware as Joerg. [...] > output from '# iwevent' says: > eth1 Custom driver event:authenticated > eth1 Custom driver event:associating failed [...] try setting rate to 11 as the first step. this helped me. regards, wrobell <wrobell-k0Z414SquRyhPH1hqNUYSQ@xxxxxxxxxxxxxxxx>
Date: March 30, 2006
From: Francesco Foresti <frafore-IWqWACnzNjyonA0d6jMUrA@xxxxxxxxxxxxxxxx>
In-reply-to:
<slrne2mkgm.p7u.joerg-au2b9oQwubsjnolme5KbmQ@xxxxxxxxxxxxxxxx>
References:
<slrne2mkgm.p7u.joerg@xxxxxxxxxxxx>
On Thu, 2006-03-30 at 05:35, Joerg Sommer wrote: [cut] Hi, I've got the same problem here, in a much similar environment: ibook g4, debian with 2.6.15-1-powerpc (debian image), bcm43xx source 2006-02-12, same firmware as Joerg. i won't put here the output from lspci, iwconfig and ip because they are the same as Joerg's. here are my dmesg bcm43xx/softmac/iee80211 related lines: ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.7 ieee80211: Copyright (C) 2004-2005 Intel Corporation<jketreno-VuQAYsv1563A2t4k+OOtxA@xxxxxxxxxxxxxxxxxx> bcm43xx driver SoftMAC: Open Authentication completed with 00:02:72:4e:29:bb output from '# iwevent' says: eth1 Custom driver event:authenticated eth1 Custom driver event:associating failed i've also tried with a 2.6.16 kernel, patched with bcm43xx-dscape-060329__forlinux2.6.16__.patch, following the howto provided in Documentation/networking/ and using wpa_supplicant v0.4.7 (debian unstable package), with quite the same results (no association - i can post logs if they are useful). if there are other infos i could provide please let me know. thanks, Francesco -- =================================================================== Francesco Foresti Registered Linux User #332599 key fingerprint = 59D5 1E61 6631 5DEF DC88 C64C 7F53 2F45 99FB CD21
pgp1GABadQCeo.pgp
Description: PGP signature
Date: March 30, 2006
From: Hans Fugal <hans-YQVBAyIcbkJeoWH0uzbU5w@xxxxxxxxxxxxxxxx>
In-reply-to:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx>
If you mean you don't like the name ethX, there are many ways you can change that yourself, as indicated in other posts. I for one don't consider it broken; I prefer the ethX naming. On Tue, 28 Mar 2006 at 02:11 -0500, Simon wrote: > Are there any plans to change softmac so that wireless interfaces aren't > treated as wired interfaces? -- Hans Fugal ; http://hans.fugal.net There's nothing remarkable about it. All one has to do is hit the right keys at the right time and the instrument plays itself. -- Johann Sebastian Bach
signature.asc
Description: Digital signature
Date: March 30, 2006
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@xxxxxxxxxxxxxxxx>
In-reply-to:
<slrne2mkgm.p7u.joerg-au2b9oQwubsjnolme5KbmQ@xxxxxxxxxxxxxxxx>
References:
<slrne2mkgm.p7u.joerg@xxxxxxxxxxxx>
On Thu, 2006-03-30 at 03:35 +0000, Joerg Sommer wrote: > % ip link list eth1 > 6: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen > 1000 > link/ether 00:11:24:90:ca:3b brd ff:ff:ff:ff:ff:ff > > and it seams the card does not send out any signals. I can receive > others, but nothing can receive my signals. > > What means NO-CARRIER? Is the air too thin? :-) It means that it hasn't associated. Oh and could you remove that Newsgroups: header from your outgoing mails? It really doesn't belong here. johannes
signature.asc
Description: This is a digitally signed message part
Date: March 30, 2006
From: Gerard Eviston <gerard-0+YW2OzL9crR7s880joybQ@xxxxxxxxxxxxxxxx>
I'm getting "ASSERTION FAILED (radio_attenuation < 10)", the same error Jory Pratt reported here on 22 March. I have an Acer Travelmate with an integrated Broadcom 4318. Radio details from dmesg: bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) I see that Michael Buesch implemented setting default radio attenuation on 19 March in this commit: http://bu3sch.de/git?p=wireless-2.6.git;a=commit;h=db2c248cfd20f6cd8d1595fb80ca9584236a113f and he did so according to the specs at http://bcm-specs.sipsolutions.net/DefaultRadioAttenuation Here's the thing - those specs say the default attenuation value for a 2050 type radio, rev 8, should be 0x1A; while for all other radio types the default value is < 10. And http://bcm-specs.sipsolutions.net/LocalOscillator only specifies how to set up LO tables for values < 10. So it's probably more a gap in the specs than anything else, but the bcm43xx driver was working fine for me a few weeks back. Anyhow I've tried messing around with different default radio attenuation values (no success), and the proper 0x1A value while faking bcm43xx_find_lopair() (partial success) and various other stuff I should be afraid to touch, but I'm new to the code & specs and I don't understand it well. A sensible workaround or a push in the right direction would be great.
Date: March 30, 2006
From: Joerg Sommer <joerg-au2b9oQwubsjnolme5KbmQ@xxxxxxxxxxxxxxxx>
Hi,
I've an Apple Airport Extreme and running linux 2.6.15.4 with the bcm43xx
drives from 2006-02-12 (the latest debian version). But I get this message
% ip link list eth1
6: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:11:24:90:ca:3b brd ff:ff:ff:ff:ff:ff
and it seams the card does not send out any signals. I can receive
others, but nothing can receive my signals.
What means NO-CARRIER? Is the air too thin? :-)
# iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"home" Nickname:"Broadcom 4306"
Mode:Ad-Hoc Frequency=2.417 GHz Cell: Invalid
Bit Rate:54 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
# lspci -s 10:12 -v
0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
Subsystem: Apple Computer Inc. AirPort Extreme
Flags: bus master, fast devsel, latency 16, IRQ 52
Memory at 80084000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
My fireware is
http://downloads.openwrt.org/sources/kernel-binary-wl-0.5.tar.gz
Any ideas, why my card does not send any signals?
Bye, Jörg.
--
"Politics is for the moment, equations are forever"
-- Albert Einstein
Date: March 30, 2006
From: "Nix N. Nix" <nix-Jf+CiVwcgUb3fQ9qLvQP4Q@xxxxxxxxxxxxxxxx>
Hi! >From Fedora Core kernel 2.6.16-1.2080_FC5: > * Fri Mar 24 2006 David Woodhouse > <dwmw2-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx> > > - Fix lockup when someone takes the bcm43xx device down while it's > scanning (#180953) > > * Wed Mar 22 2006 David Woodhouse > <dwmw2-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx> > > - Update the bcm43xx driver to make it work nicely with initscripts > and NetworkManager without user intervention. Does the 2006-03-30 all-in-one snapshot contain these changes ? I have tried the latest snapshot with NetworkManager, but to no avail. Please let me know!
Date: March 30, 2006
From: Martin Langer <martin-langer-Mmb7MZpHnFY@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143697389.11170.3.camel@localhost
>
References:
<1143697389.11170.3.camel@localhost
>
On Wed, Mar 29, 2006 at 10:43:09PM -0700, Nix N. Nix wrote: > FATAL: Error inserting bcm43xx > (/lib/modules/2.6.16.1/kernel/drivers/net/wireless/bcm43xx.ko): Invalid > module format > > Mar 29 22:39:08 mactop kernel: bcm43xx: no version magic, tainting > kernel. > Mar 29 22:39:08 mactop kernel: Module doesn't contain .plt or .init.plt > sections. Try the all-in-one patch instead of the standalone module. That was my solution... Martin
Date: March 30, 2006
From: "Bin Zhang" <yangtze31-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<20060330053858.GA19833-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@xxxxxxxxxxxxxxxx>
References:
<29151.1143696312@xxxxxxxxxxxxxx> <20060330053858.GA19833@xxxxxxxxxxxxxxxxxxxxx>
On 3/30/06, Scott Robinson <scott-EVKT21ZUZflWk0Htik3J/w@xxxxxxxxxxxxxxxx> wrote: > On Thu, Mar 30, 2006 at 07:25:12AM +0200, Michael Lampard wrote: > > Hy, > > > > could you please offer a wiki at bcm43xx.berlios.de? I think that way users > > could find informations faster than searching through this mailinglist or > > the forum over at bcm43xx.spugna.org. especially when it comes to how-tos > > and hands-on installation instructions. And it would be less work for the > > maintainers of bcm43xx.berlios.de > > > > Michael > > > > You mean like here? > > http://openfacts.berlios.de/index-en.phtml?search=bcm43xx > For using latest bcm43xx-dscape with 2.6.16, read 1) Documentation/networking/bcm43xx-d80211.txt http://bu3sch.de/git?p=wireless-2.6.git;a=blob;h=89b101d1ffc42ffaf76434b22055495d5fbd1f61;hb=dscape;f=Documentation/networking/bcm43xx-d80211.txt 2) Documentation/networking/bcm43xx-d80211-HOWTO.txt http://bu3sch.de/git?p=wireless-2.6.git;a=blob;h=90e4ddfc877cf9fea115481827be789793866b22;hb=dscape;f=Documentation/networking/bcm43xx-d80211-HOWTO.txt Regards, Bin > Scott. > > -- > http://quadhome.com/ - Personal webpage > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.5 (GNU/Linux) > > iEYEARECAAYFAkQrbvIACgkQ2wcaZqTSGsRNYQCfYYW3hGeYxRWJQmaHm4jDK6su > OWQAnAgOPSMbrDHdmJGiFwrSu10ktaCO > =BZSE > -----END PGP SIGNATURE----- > > >
Date: March 30, 2006
From: "Nix N. Nix" <nix-Jf+CiVwcgUb3fQ9qLvQP4Q@xxxxxxxxxxxxxxxx>
Hi! I tried the 2006-03-29 snapshot against 2.6.16.1, and I get FATAL: Error inserting bcm43xx (/lib/modules/2.6.16.1/kernel/drivers/net/wireless/bcm43xx.ko): Invalid module format on the modprobe command line, and Mar 29 22:39:08 mactop kernel: bcm43xx: no version magic, tainting kernel. Mar 29 22:39:08 mactop kernel: Module doesn't contain .plt or .init.plt sections. In my syslog. How should I compile the module, if not with "make" ? I compiled the latest softmac-snapshot, and it compiled and modprobe-ed just fine. I would really like to test it with NetworkManager, since I've heard that it's been made to work with it. Please let me know! Thanks!
Date: March 30, 2006
From: Scott Robinson <scott-EVKT21ZUZflWk0Htik3J/w@xxxxxxxxxxxxxxxx>
In-reply-to:
<29151.1143696312-EFwyyEn9xm2TNgMzhvGLKQ@xxxxxxxxxxxxxxxx>
References:
<29151.1143696312@xxxxxxxxxxxxxx>
On Thu, Mar 30, 2006 at 07:25:12AM +0200, Michael Lampard wrote: > Hy, > > could you please offer a wiki at bcm43xx.berlios.de? I think that way users > could find informations faster than searching through this mailinglist or > the forum over at bcm43xx.spugna.org. especially when it comes to how-tos > and hands-on installation instructions. And it would be less work for the > maintainers of bcm43xx.berlios.de > > Michael > You mean like here? http://openfacts.berlios.de/index-en.phtml?search=bcm43xx Scott. -- http://quadhome.com/ - Personal webpage
signature.asc
Description: Digital signature
Date: March 30, 2006
From: "Michael Lampard" <mila61-Mmb7MZpHnFY@xxxxxxxxxxxxxxxx>
Hy, could you please offer a wiki at bcm43xx.berlios.de? I think that way users could find informations faster than searching through this mailinglist or the forum over at bcm43xx.spugna.org. especially when it comes to how-tos and hands-on installation instructions. And it would be less work for the maintainers of bcm43xx.berlios.de Michael -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
Date: March 29, 2006
From: Louis E Garcia II <louisg00-Bdlq13kUjeyLZ21kGMrzwg@xxxxxxxxxxxxxxxx>
Looking at a new Dell E1705 which has a Dell 1390 wireless mini-card, it is broadcom 4311 based. Is there info on what cards the bcm43xx driver supports? I think this is a pci-e card, reading the archives this driver had problems with them. Has this issue been resolved? Thanks, --Louis
Date: March 28, 2006
From: "Paul T.Threshold" <paultt-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<6D535040-D262-40E5-A8DE-C4A472F3DBE2-hi6Y0CQ0nG0@xxxxxxxxxxxxxxxx>
References:
<6D535040-D262-40E5-A8DE-C4A472F3DBE2@xxxxxxx>
On 3/24/06, Thomas Ploch <Thomas.Ploch-hi6Y0CQ0nG0@xxxxxxxxxxxxxxxx> wrote: > > Hello, > I have a problem concerning the wpa-psk tkip encryption. Which > iwconfig command do I have to use for WPA? Is it : > "iwconfig eth1 key restricted s:my_passphrase" > > or do I have to enable the TKIP encryption beforehand? Because in my > desktop environment I can only use WEP with the network configuration > tool. Tried to look for a solution on the net, couldn find one. On my > other network, which is WEP encrypted, everything works fine > > > I am running on a 2.6.16-rc6 kernel with in-tree softmac bcm43xx > driver. The driver loads fine and Open authentication to my essid is > printed to printk is during boot. Unfortunately i get no dhcp- > response, so I am assuming that something is wrong with > authentication. I tried static settings, too. But nothing changed. > > Thanks to all developers for all the good work. > Gratefully, > Thomas you should use wpa_supplicant to join a wpa network install it and look at its documentation :-)
Date: March 28, 2006
From: "Imre Kaloz" <kaloz-p3rKhJxN3npAfugRpC6u6w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143558184.3241.3.camel@hidalgo
>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx> <1143534038.5600.14.camel@xxxxxxxxxxxxxxxxxx> <44294C43.9000109@xxxxxxxxx> <1143558184.3241.3.camel@hidalgo
>
On Tue, 2006-03-28 at 08:46 -0600, Timothee Besset wrote:Worse than naming the wireless interface eth%d, it also calls it eth0 or eth1 randomly on my machine.it depends on the first interface detected / on the first module loaded, doesnt it ?
He should just 'man ifrename'... Imre
Date: March 28, 2006
From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143558927.25913.69.camel-8OOqt/S+jKAjOxct69p1dh/sF2h8X+2i0E9HWUfgJXw@xxxxxxxxxxxxxxxx>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx> <1143534038.5600.14.camel@xxxxxxxxxxxxxxxxxx> <44294C43.9000109@xxxxxxxxx> <1143558927.25913.69.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx>
David Woodhouse wrote:
On my distro (SuSE 10.0), the name (wlan0) is determined by the contents of /etc/udev/rules.d/30-net_persistent_names.rules. According to the comments in that file, the rules are autogenerated by /sbin/rename_netiface.On Tue, 2006-03-28 at 08:46 -0600, Timothee Besset wrote:Worse than naming the wireless interface eth%d, it also calls it eth0 or eth1 randomly on my machine. That's reason enough to force a specific name for me. Simon, check this thread in the forums:http://bcm43xx.spugna.org/index.php?topic=18.0That happens on my machine too, but the MAC address is consistent, the network scripts (and NetworkManager) cope with that, and it all works fine. The names just aren't that relevant.
Larry
Date: March 28, 2006
From: Yves-Alexis Perez <corsac-vD43ovf/fd+sTnJN9+BGXg@xxxxxxxxxxxxxxxx>
In-reply-to:
<44294C43.9000109-T9rrwGA3OdBeoWH0uzbU5w@xxxxxxxxxxxxxxxx>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx> <1143534038.5600.14.camel@xxxxxxxxxxxxxxxxxx> <44294C43.9000109@xxxxxxxxx>
On Tue, 2006-03-28 at 08:46 -0600, Timothee Besset wrote: > Worse than naming the wireless interface eth%d, it also calls it eth0 > or > eth1 randomly on my machine. it depends on the first interface detected / on the first module loaded, doesnt it ? -- Yves-Alexis Perez
Date: March 28, 2006
From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<44294C43.9000109-T9rrwGA3OdBeoWH0uzbU5w@xxxxxxxxxxxxxxxx>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx> <1143534038.5600.14.camel@xxxxxxxxxxxxxxxxxx> <44294C43.9000109@xxxxxxxxx>
On Tue, 2006-03-28 at 08:46 -0600, Timothee Besset wrote: > Worse than naming the wireless interface eth%d, it also calls it eth0 > or eth1 randomly on my machine. That's reason enough to force a > specific name for me. Simon, check this thread in the forums: > http://bcm43xx.spugna.org/index.php?topic=18.0 That happens on my machine too, but the MAC address is consistent, the network scripts (and NetworkManager) cope with that, and it all works fine. The names just aren't that relevant. -- dwmw2
Date: March 28, 2006
From: Timothee Besset <ttimo-T9rrwGA3OdBeoWH0uzbU5w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143534038.5600.14.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@xxxxxxxxxxxxxxxx>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx> <1143534038.5600.14.camel@xxxxxxxxxxxxxxxxxx>
David Woodhouse wrote:
Worse than naming the wireless interface eth%d, it also calls it eth0 or eth1 randomly on my machine. That's reason enough to force a specific name for me. Simon, check this thread in the forums:On Tue, 2006-03-28 at 02:11 -0500, Simon wrote:Are there any plans to change softmac so that wireless interfaces aren't tr= eated as wired interfaces?<br>Don't send HTML to public fora. The question doesn't make much sense. With the current code, I treat mine as a wireless interface -- surely that's just up to the user's policy? It doesn't need any changes in softmac. I suspect you're actually asking if there's an plan to assign bizarre _names_ to the device rather than using the standard 'eth%d'? I'm not aware of any plans, or any reason why anyone would want such a thing.
http://bcm43xx.spugna.org/index.php?topic=18.0 TTimo
Date: March 28, 2006
From: Martin Langer <martin-langer-Mmb7MZpHnFY@xxxxxxxxxxxxxxxx>
In-reply-to:
<20060324171508.10b02d5a@electricsheep
>
References:
<20060324171508.10b02d5a@electricsheep
>
On Fri, Mar 24, 2006 at 05:15:08PM +0100, Andrea Lusuardi - UoVoBW wrote: > Today, in a momentary lapse of "if it ain't broken, FIX it" (my bad) i > have installed the latest 2.6.16 kernel along with the latest > softmac patch (24) and then (again mea culpa) i tryied to use the new > 4.* firmware listed in the fwcutter Readme. The bcm43xx_microcode*.fw images are a little bit different in the 4.x driver compared to 3.x. So I think I've choosen the wrong names, but actually I'm not sure about the right ones. bcm43xx_microcode2.fw can be either bcm43xx_microcode2.fw, bcm43xx_microcode4.fw or anything unknown. Most likely they removed old microcode2 firmware support. bcm43xx_microcode4.fw can be either bcm43xx_microcode5.fw, bcm43xx_microcode11.fw or anything unknown. There I was totally wrong. bcm43xx_microcode5.fw can be either bcm43xx_microcode5.fw, bcm43xx_microcode11.fw or anything unknown. > It does this with both the 4.*.......0 and .1 listed in the readme. All 4.10.x.x drivers have the same firmware files inside, IIRC. Therefore it's enough to extract from one 4.x driver. You will get the same results for 4.10.40.0, 4.10.40.1 and 4.10.47.2. That's no surprise. > Ideas? Reverse engineering, but unfortunately nobody likes win drivers. > suggestions? I will add the DRIVER_UNSUPPORTED flag to those 4.x drivers until we understand it better. Martin
Date: March 28, 2006
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@xxxxxxxxxxxxxxxx>
In-reply-to:
<000b01c6517e$e954dd60$5858a8c0@inkmobile
>
References:
<000b01c6517e$e954dd60$5858a8c0@inkmobile
>
On Mon, 2006-03-27 at 17:14 +0800, ink wrote: > i have hp ZE2000, only few broadcom 4306 can be used in it, i want to > change broadcom 4306 's subsystem id and vendor > > atheros 5211/2/3 can use "idchange" program to change it,but i don't > know how ro change broadcom..... Don't send HTML here. And check out the sprom tool in the berlios svn. johannes
signature.asc
Description: This is a digitally signed message part
Date: March 28, 2006
From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<c1fa8edf0603272311i414b4ecay5c17e3219a9ea2be@xxxxxxxxxxxxxx>
On Tue, 2006-03-28 at 02:11 -0500, Simon wrote: > Are there any plans to change softmac so that wireless interfaces > aren't tr= > eated as wired interfaces?<br> Don't send HTML to public fora. The question doesn't make much sense. With the current code, I treat mine as a wireless interface -- surely that's just up to the user's policy? It doesn't need any changes in softmac. I suspect you're actually asking if there's an plan to assign bizarre _names_ to the device rather than using the standard 'eth%d'? I'm not aware of any plans, or any reason why anyone would want such a thing. -- dwmw2
Date: March 28, 2006
From: Simon <simon80-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
Date: March 27, 2006
From: Dick Streefland <Dick.Streefland-qWit8jRvyhVmR6Xm/wNWPw@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143450935.21103.4.camel@RECENT-CONVERT
>
References:
<1143193677.1095.170.camel@RECENT-CONVERT
> <20060325121759.GA6529@xxxxxxxxxxxxxxxxxxxx> <1143450935.21103.4.camel@RECENT-CONVERT
>
I've created a small python script to extract the bcm43xx and softmac changes from the all-in-one patch. In addition, you also need some "glue" patches to integrate the new code in the kernel. Both files are attached to this email. I don't guarantee that the glue patches are correct, but the resulting kernel compiles. To extract the core changes from today's all-in-one patch, use the following command: bzcat bcm43xx-060327__forlinux2.6.16__.patch.bz2 | bcmgrep.py > core.diff -- Dick Streefland //// De Bilt dick.streefland-qWit8jRvyhVmR6Xm/wNWPw@xxxxxxxxxxxxxxxx (@ @) The Netherlands ------------------------------oOO--(_)--OOo------------------
bcmgrep.py
Description: Text Data
glue.diff
Description: Text document
Date: March 27, 2006
From: Louis E Garcia II <louisg00-Bdlq13kUjeyLZ21kGMrzwg@xxxxxxxxxxxxxxxx>
In-reply-to:
<7cbb09760603252211i4d3d6924i627f88ee97c77717-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<1143245200.5392.7.camel@soncomputer
> <1143276192.9892.14.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <7cbb09760603252211i4d3d6924i627f88ee97c77717@xxxxxxxxxxxxxx>
when was the last time you tried with the bcm43xx driver? Also does your laptop have the ati or nvidia video card? -Louis On Sun, 2006-03-26 at 01:11 -0500, Jim Smyth wrote: > It's a broadcom 4311 to be specific. I have the same card and the same > laptop, but NDISWrapper didn't like it. Kept dieing when loading the > ndiswrapper kernel module (on multiple distros). I also haven't had > any luck with the bcm43xx driver. > > - Jim > > On 3/25/06, Cedric Blancher > <blancher-cPThYx3uDionEikN29/hQkZa+K1vlBrA@xxxxxxxxxxxxxxxx> wrote: > Le vendredi 24 mars 2006 à 19:06 -0500, Louis E Garcia II a > écrit : > > Who knows anything about this card? > > I used to have one, but had to drive it with ndiswrapper... > > > I think it's broadcom based. > > It is, some web crawling should confirm it quite fast : > > http://www.modem-help.com/mfcs.php?mid=29&nid=14698 > > > Will this driver drive it? > > It should. > > > Also is it 802.11b compatible? > > 802.11g compliance implies 802.11b compliance. > > > -- > http://sid.rstack.org/ > PGP KeyID: 157E98EE FingerPrint: > FA62226DA9E72FA8AECAA240008B480E157E98EE > >> Hi! I'm your friendly neighbourhood signature virus. > >> Copy me to your signature file and help me spread! > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx > http://lists.berlios.de/mailman/listinfo/bcm43xx-dev >
Date: March 27, 2006
From: Mathieu Bouchard <mbouchar-xSWhflkr/NGosttpCeJDwPd9D2ou9A/h@xxxxxxxxxxxxxxxx>
Hi,
I am testing one of the new Lenovo 3000 C100 with linux.
The laptop has a Lenovo 11a/b/g Wi-Fi Wireless II, which is
in fact a broadcom card.
I tried the latest driver (060324 for 2.6.16) with both the softmac and the
dscape patches,
but none were able to detect the hardware. When I load the driver, there
is no output on dmesg, except the first line showing that the module has
loaded :
# modprobe 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
lspci returns :
0000:01:02.0 Network controller: Broadcom Corporation: Unknown device 4319
(rev 02)
Subsystem: Broadcom Corporation: Unknown device 044a
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort-<MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin A routed to IRQ 225
Region 0: Memory at c0002000 (32-bit, non-prefetchable) [size=8K]
The card is working with ndiswrapper and the bcmwl5 driver.
Is bcm43xx the good driver for this card?
Thanks
--
Mathieu Bouchard
Centre de bio-informatique
Pavillon Charles-Eugène-Marchand
Université Laval
Québec, Canada
www.bioinfo.ulaval.ca
Avis relatif à la confidentialité/Notice of Confidentiality
http://www.rec.ulaval.ca/lce/securite/confidentialite.htm
Date: March 27, 2006
From: Gavin Holland <gdholland-i/L4Se5z2Uw@xxxxxxxxxxxxxxxx>
In-reply-to:
<200603241750.35748.mb-fseUSCV1ubazQB+pC5nmwQ@xxxxxxxxxxxxxxxx>
References:
<200603241750.35748.mb@xxxxxxxxx>
The term "firmware" is general, so I just coined "nic-side" driver to mean the firmware in the nic that implements the hard real-time portions of the MAC (i.e. the part that drives, among other things, the BB and RF asics). Implementations of 802.11 are usually split between the firmware on the nic and the host kernel. It used to be that almost all of the 802.11 spec was in the firmware, but more recently it seems that much of the implementation has been moved to the kernel. What's usually left in the firmware is the hard real-time portions of the MAC, which is the software that I need to modify. -Gavin On Fri, 24 Mar 2006, Michael Buesch wrote: > Date: Fri, 24 Mar 2006 17:50:34 +0100 > From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@xxxxxxxxxxxxxxxx> > To: Gavin Holland <gholland-i/L4Se5z2Uw@xxxxxxxxxxxxxxxx>, > Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@xxxxxxxxxxxxxxxx>, Simon > <simon80-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>, > bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx > Subject: Re: mac firmware core hacks? > > On Friday 24 March 2006 17:30, Gavin Holland wrote: > > > Uh, no? Why would we reverse engineer then? > > > > I assumed there were drivers for some Prism54 devices in the list > > of files on their GPL Code Center site, but regardless the point is > > that there are host-side drivers but no nic-side drivers. > > WTF is a "host-side" and "nic-side" driver? > > -- > Greetings Michael. >
Date: March 27, 2006
From: Florian Fainelli <florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx>
Hello all, I just wanted to know whether there was some work done on the master mode ? Do you plan to integrate WDS features and multi-SSID ? Thank you in advance for your answer and keep on the great work ! -- Cordialement, Florian Fainelli --------------------------------- Email: florian-aFeEDtPIk9MqcZcGjlUOXw@xxxxxxxxxxxxxxxx Portail: http://www.alphacore.net Tel: +33609026495 ---------------------------------
pgpo5Q4y1I2sS.pgp
Description: PGP signature
Date: March 27, 2006
From: Robert <robwilkens-p32f3XyCuykqcZcGjlUOXw@xxxxxxxxxxxxxxxx>
My card; Dell Wireless 1450Normal connection: Linksys Wireless G network, seems problem free. (except iwconfig reports speed of 11MB/s, I don't know if that's right.)
Currently: At another location (sister's house), with wireless B (Also linksys). What I've noticed is that if I "ifdown eth1" "ifup eth1" (eth1 is the wireless card) a few times it works, but rarely does it work the first time or on boot. It may, the first time, say it got the address successfully, but connecting to hosts may not work. One time the routing table was messed up (I don't know if this is every time) to the point where getting the list of routes resulted in a real long (if not indefinite) pause before ever seeing the 'default gw' route (had to reboot, I think). Note i was, seemingly, at that point able to ping by IP address the gateway despite the internet connectivity not working.
I share this here not because i need it fixed (I can work around it) but in the hopes that the details help the developers trace down any related issues their working on.
Thanks for all the work you've done. -Rob
Date: March 27, 2006
From: wrobell <wrobell-k0Z414SquRyhPH1hqNUYSQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<20060325121759.GA6529-QlKM4qLeon3ugA6rFgE59ZQPcHd2y3zB@xxxxxxxxxxxxxxxx>
References:
<1143193677.1095.170.camel@RECENT-CONVERT
> <20060325121759.GA6529@xxxxxxxxxxxxxxxxxxxx>
On Sat, 2006-03-25 at 13:17 +0100, Dick Streefland wrote: > On Friday 2006-03-24 09:47, wrobell wrote: > | just to make you aware > | > | bcm43xx-060324__forlinux2.6.16__.patch.bz2 snapshot > | adds -rc6 EXTRAVERSION to 2.6.16 vanilla kernel. > > Not only that, but the patches consist of mostly unrelated changes, > that are also going backwards. In other words: recent changes are > reverted. Only about 60 files out of more than 300 are mcb43xx or > softmac related. After applying the patch, I have no idea which > kernel version I am using. It is neither 2.6.16 nor 2.6.16-pre6. > > Isn't it possibly to publish patches with only the bcm43xx/softcam > additions/modifications? that would be very nice. how can we help with this situation? best regards, wrobell <wrobell-k0Z414SquRyhPH1hqNUYSQ@xxxxxxxxxxxxxxxx>
Date: March 27, 2006
From: "ink" <czzink123-Lve0A9HpOKasTnJN9+BGXg@xxxxxxxxxxxxxxxx>
|
i have hp ZE2000, only few broadcom 4306 can be used in
it, i want to change broadcom 4306 's subsystem id and vendor
atheros 5211/2/3 can use "idchange" program to change it,but i
don't know how ro change broadcom.....
Thanks!
|
Date: March 26, 2006
From: Michael Marineau <marineam-CJG/fkoVOTIdnm+yROfE0A@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143226881.28632.13.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@xxxxxxxxxxxxxxxx>
References:
<1143226881.28632.13.camel@xxxxxxxxxxxxxxxxxx>
David Woodhouse wrote: > If the device is taken down during a scan, the bcm43xx driver can lock > up the system the next time ->set_channel() is called. This avoids the > lockup by checking whether the card is running before poking at it. Thanks, this is a big help on Gentoo since the gentoo wireless setup script at one point does: iwconfig ethX any; ifconfig ethX down; ifconfig ethX up Attached is an updated version that will play nice with the current development git tree. -- Michael Marineau marineam-CJG/fkoVOTIdnm+yROfE0A@xxxxxxxxxxxxxxxx Open Source Lab Oregon State University
diff --git a/drivers/net/wireless/bcm43xx/bcm43xx_main.c
b/drivers/net/wireless/bcm43xx/bcm43xx_main.c
index 2b7ef9b..8c47ac7 100644
--- a/drivers/net/wireless/bcm43xx/bcm43xx_main.c
+++ b/drivers/net/wireless/bcm43xx/bcm43xx_main.c
@@ -3530,12 +3530,17 @@ static void bcm43xx_ieee80211_set_chan(s
u8 channel)
{
struct bcm43xx_private *bcm = bcm43xx_priv(net_dev);
+ struct bcm43xx_radioinfo *radio = bcm43xx_current_radio(bcm);
unsigned long flags;
bcm43xx_lock_mmio(bcm, flags);
- bcm43xx_mac_suspend(bcm);
- bcm43xx_radio_selectchannel(bcm, channel, 0);
- bcm43xx_mac_enable(bcm);
+ if (likely(bcm->initialized)) {
+ bcm43xx_mac_suspend(bcm);
+ bcm43xx_radio_selectchannel(bcm, channel, 0);
+ bcm43xx_mac_enable(bcm);
+ } else {
+ radio->initial_channel = channel;
+ }
bcm43xx_unlock_mmio(bcm, flags);
}
signature.asc
Description: OpenPGP digital signature
Date: March 26, 2006
From: "Jim Smyth" <jimsmyth-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143276192.9892.14.camel-wh53gMSPbNLbFIwZ3jqLltgfHpRXVu16X36uYwy3hK3k1uMJSBkQmQ@xxxxxxxxxxxxxxxx>
References:
<1143245200.5392.7.camel@soncomputer
> <1143276192.9892.14.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Le vendredi 24 mars 2006 à 19:06 -0500, Louis E Garcia II a écrit :
> Who knows anything about this card?
I used to have one, but had to drive it with ndiswrapper...
> I think it's broadcom based.
It is, some web crawling should confirm it quite fast :
http://www.modem-help.com/mfcs.php?mid=29&nid=14698
> Will this driver drive it?
It should.
> Also is it 802.11b compatible?
802.11g compliance implies 802.11b compliance.
--
http://sid.rstack.org/
PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE
>> Hi! I'm your friendly neighbourhood signature virus.
>> Copy me to your signature file and help me spread!
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Date: March 25, 2006
From: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143256213.5182.15.camel-gFj3TxrJJouwvWHyBIo2NlaTQe2KTcn/@public.gmane.org>
References:
<1143256213.5182.15.camel@xxxxxxxxxxxxxxxxxxxx>
On Fri, 2006-03-24 at 22:10 -0500, Robert Wilkens wrote: > Can someone point me towards any documentation on how to get started > with the driver? (No hurry) > > I've been trying to get the bcm43xx standalone driver to work (Dell > Wireless 1450 card), and have been having some issues. > > This is on Fedora Core 5, which is said to also include a version of the > driver. I just don't know how to use it if it's there. http://lists.infradead.org/pipermail/fedora-ppc/2006-March/000804.html -- dwmw2
Date: March 25, 2006
From: Robert <robwilkens-p32f3XyCuykqcZcGjlUOXw@xxxxxxxxxxxxxxxx>
Per Subject - Here is relevant output: after "modprobe bcm43xx" I'm told to "see dmesg output" dmesg says: bcm43xx: no version magic, tainting kernel. bcm43xx: Unknown symbol ieee80211softmac_wx_set_rate bcm43xx: Unknown symbol ieee80211_wx_set_auth bcm43xx: Unknown symbol alloc_ieee80211softmac bcm43xx: Unknown symbol ieee80211softmac_wx_trigger_scan bcm43xx: Unknown symbol ieee80211_wx_get_auth bcm43xx: Unknown symbol ieee80211softmac_wx_get_scan_results bcm43xx: Unknown symbol device_create_file bcm43xx: Unknown symbol ieee80211softmac_wx_get_genie bcm43xx: Unknown symbol ieee80211softmac_start bcm43xx: Unknown symbol ieee80211softmac_wx_set_essid bcm43xx: Unknown symbol debugfs_remove bcm43xx: Unknown symbol ieee80211softmac_wx_get_wap bcm43xx: Unknown symbol ieee80211softmac_wx_get_rate bcm43xx: Unknown symbol debugfs_create_file bcm43xx: Unknown symbol ieee80211softmac_wx_get_essid bcm43xx: Unknown symbol ieee80211softmac_wx_set_wap bcm43xx: Unknown symbol ieee80211softmac_wx_set_genie bcm43xx: Unknown symbol ieee80211softmac_stop bcm43xx: Unknown symbol free_ieee80211softmac bcm43xx: Unknown symbol debugfs_create_dir bcm43xx: Unknown symbol device_remove_file Note, below are loaded drivers at the time, per lsmod output: [root@dell_notebook bcm43xx]# lsmod | grep bcm [root@dell_notebook bcm43xx]# lsmod | grep 80211 ieee80211softmac 28160 0 ieee80211 30536 1 ieee80211softmac ieee80211_crypt 6272 1 ieee80211 [root@dell_notebook bcm43xx]#I specifically haven't install ndiswrapper in this kernel such that no conflicts would occur. 80211 softmac was "built into" kernel, per instructions, I think (if I did it right).
# uname -aLinux dell_notebook.robertwilkens.com 2.6.16 #1 Sat Mar 25 08:33:04 EST 2006 i686 i686 i386 GNU/Linux
Thanks for any direction Rob
Date: March 25, 2006
From: Dick Streefland <Dick.Streefland-qWit8jRvyhVmR6Xm/wNWPw@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143193677.1095.170.camel@RECENT-CONVERT
>
References:
<1143193677.1095.170.camel@RECENT-CONVERT
>
On Friday 2006-03-24 09:47, wrobell wrote: | just to make you aware | | bcm43xx-060324__forlinux2.6.16__.patch.bz2 snapshot | adds -rc6 EXTRAVERSION to 2.6.16 vanilla kernel. Not only that, but the patches consist of mostly unrelated changes, that are also going backwards. In other words: recent changes are reverted. Only about 60 files out of more than 300 are mcb43xx or softmac related. After applying the patch, I have no idea which kernel version I am using. It is neither 2.6.16 nor 2.6.16-pre6. Isn't it possibly to publish patches with only the bcm43xx/softcam additions/modifications? -- Dick Streefland //// De Bilt dick.streefland-qWit8jRvyhVmR6Xm/wNWPw@xxxxxxxxxxxxxxxx (@ @) The Netherlands ------------------------------oOO--(_)--OOo------------------
Date: March 25, 2006
From: Yves-Alexis Perez <corsac-vD43ovf/fd+sTnJN9+BGXg@xxxxxxxxxxxxxxxx>
In-reply-to:
<51ad2e0d0603250022lf4c022dmfc7be74ddf4e39c9-JsoAwUIsXosN+BqQ9rBEUg@xxxxxxxxxxxxxxxx>
References:
<1143193677.1095.170.camel@RECENT-CONVERT
> <51ad2e0d0603250022lf4c022dmfc7be74ddf4e39c9@xxxxxxxxxxxxxx>
On Sat, 2006-03-25 at 09:22 +0100, Bin Zhang wrote: > I think it's correct (the patch is _for_ linux 2.6.16). yes, but for 2.6.16 not 2.6.16-rc6 -- Yves-Alexis Perez
Date: March 25, 2006
From: Cedric Blancher <blancher-cPThYx3uDionEikN29/hQkZa+K1vlBrA@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143245200.5392.7.camel@soncomputer
>
References:
<1143245200.5392.7.camel@soncomputer
>
Le vendredi 24 mars 2006 à 19:06 -0500, Louis E Garcia II a écrit : > Who knows anything about this card? I used to have one, but had to drive it with ndiswrapper... > I think it's broadcom based. It is, some web crawling should confirm it quite fast : http://www.modem-help.com/mfcs.php?mid=29&nid=14698 > Will this driver drive it? It should. > Also is it 802.11b compatible? 802.11g compliance implies 802.11b compliance. -- http://sid.rstack.org/ PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE >> Hi! I'm your friendly neighbourhood signature virus. >> Copy me to your signature file and help me spread!
Date: March 25, 2006
From: "Bin Zhang" <yangtze31-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143193677.1095.170.camel@RECENT-CONVERT
>
References:
<1143193677.1095.170.camel@RECENT-CONVERT
>
On 3/24/06, wrobell <wrobell-k0Z414SquRyhPH1hqNUYSQ@xxxxxxxxxxxxxxxx> wrote: > just to make you aware > > bcm43xx-060324__forlinux2.6.16__.patch.bz2 snapshot > adds -rc6 EXTRAVERSION to 2.6.16 vanilla kernel. > I think it's correct (the patch is _for_ linux 2.6.16). After applying the (latest) patch, you get the softmac branch of Buesch's git tree : http://bu3sch.de/git?p=wireless-2.6.git;a=shortlog;h=softmac Regards, Bin > wrobell <wrobell-k0Z414SquRyhPH1hqNUYSQ@xxxxxxxxxxxxxxxx> > > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx > http://lists.berlios.de/mailman/listinfo/bcm43xx-dev >
Date: March 25, 2006
From: "Bin Zhang" <yangtze31-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143256213.5182.15.camel-gFj3TxrJJouwvWHyBIo2NlaTQe2KTcn/@public.gmane.org>
References:
<1143256213.5182.15.camel@xxxxxxxxxxxxxxxxxxxx>
On 3/25/06, Robert Wilkens <robwilkens-p32f3XyCuykqcZcGjlUOXw@xxxxxxxxxxxxxxxx> wrote: > Can someone point me towards any documentation on how to get started > with the driver? (No hurry) > You can get some ideal at http://forums.gentoo.org/viewtopic-t-409194.html (this howto is for 20050125 version) Regards, Bin > I've been trying to get the bcm43xx standalone driver to work (Dell > Wireless 1450 card), and have been having some issues. > > This is on Fedora Core 5, which is said to also include a version of the > driver. I just don't know how to use it if it's there. > > All i'm looking for is a raw set of steps to type in to get things > working. From reading the list I learned enough to put (I think) the > firmware in the right place. Beyond that, I know nothing. > > By the way, I made a 20-euro donation -- don't take that as me saying > "you own me support" but rather as in me saying "hey, I may not have the > technical ability to help out, but at least i'm helping in _some_ way." > > I already have NDISWRAPPER up and running, so i'm in no hurry to get > this information. I'd just like to switch over to the bcm43xx driver as > soon as it is feasible to. > > -Rob > > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx > http://lists.berlios.de/mailman/listinfo/bcm43xx-dev >
Date: March 25, 2006
From: Benj FitzPatrick <benjfitz-/E1597aS9LQAvxtiuMwx3w@xxxxxxxxxxxxxxxx>
In-reply-to:
<1143256213.5182.15.camel-gFj3TxrJJouwvWHyBIo2NlaTQe2KTcn/@public.gmane.org>
References:
<1143256213.5182.15.camel@xxxxxxxxxxxxxxxxxxxx>
Can someone point me towards any documentation on how to get started
with the driver? (No hurry)
I've been trying to get the bcm43xx standalone driver to work (Dell
Wireless 1450 card), and have been having some issues.
This is on Fedora Core 5, which is said to also include a version of the
driver. I just don't know how to use it if it's there.
All i'm looking for is a raw set of steps to type in to get things
working. From reading the list I learned enough to put (I think) the
firmware in the right place. Beyond that, I know nothing.
By the way, I made a 20-euro donat! ion -- don't take that as me saying
"you own me support" but rather as in me saying "hey, I may not have the
technical ability to help out, but at least i'm helping in _some_ way."
I already have NDISWRAPPER up and running, so i'm in no hurry to get
this information. I'd just like to switch over to the bcm43xx driver as
soon as it is feasible to.
-Rob
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@xxxxxxxxxxxxxxxx
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Date: March 25, 2006
From: Robert Wilkens <robwilkens-p32f3XyCuykqcZcGjlUOXw@xxxxxxxxxxxxxxxx>
Can someone point me towards any documentation on how to get started with the driver? (No hurry) I've been trying to get the bcm43xx standalone driver to work (Dell Wireless 1450 card), and have been having some issues. This is on Fedora Core 5, which is said to also include a version of the driver. I just don't know how to use it if it's there. All i'm looking for is a raw set of steps to type in to get things working. From reading the list I learned enough to put (I think) the firmware in the right place. Beyond that, I know nothing. By the way, I made a 20-euro donation -- don't take that as me saying "you own me support" but rather as in me saying "hey, I may not have the technical ability to help out, but at least i'm helping in _some_ way." I already have NDISWRAPPER up and running, so i'm in no hurry to get this information. I'd just like to switch over to the bcm43xx driver as soon as it is feasible to. -Rob