Re: HELP BROADCOM bcm43xxx driver instalation on mandriva 2006
dont use the bcm43xx driver use b43 and the firmware at www.linuxwireless.org (directions there as well) On Tue, Mar 11, 2008 at 6:03 PM, lowdown <[EMAIL PROTECTED]> wrote: > I'm trying to install bcm43xxx driver for mandriva, here are the steps: > (Before cutting the windows diriver and "make installfw" there wasn't > directory in /lib/ named firmware, is there anythig with default > firmwire directory. > Somwhre i've read that mandriva default firmware directory is > /lib/firmware/ but the directory firmwire was't there before commnad > "make installfw") > > ./bcm43xx-fwcutter /home/kristijan/Desktop/broadcom\ > 4318/R102320/bcmwl5*.sys > > filename : bcmwl5.sys > version : 3.120.27.0 > MD5 : 8d49f11238815a320880fee9f98b2c92 > microcodes : 2 4 5 > pcms : 4 5 > > microcode : 2 > revision : 0x0123 > patchlevel : 0x0023 > date : 2005-03-22 > time : 00:11:18 > > microcode : 4 > revision : 0x0123 > patchlevel : 0x0023 > date : 2005-03-22 > time : 00:11:18 > > microcode : 5 > revision : 0x0123 > patchlevel : 0x0023 > date : 2005-03-22 > time : 00:11:18 > > extracting bcm43xx_microcode2.fw ... > extracting bcm43xx_microcode4.fw ... > extracting bcm43xx_microcode5.fw ... > extracting bcm43xx_pcm4.fw ... > extracting bcm43xx_pcm5.fw ... > extracting bcm43xx_initval01.fw ... > extracting bcm43xx_initval02.fw ... > extracting bcm43xx_initval03.fw ... > extracting bcm43xx_initval04.fw ... > extracting bcm43xx_initval05.fw ... > extracting bcm43xx_initval06.fw ... > extracting bcm43xx_initval07.fw ... > extracting bcm43xx_initval08.fw ... > extracting bcm43xx_initval09.fw ... > extracting bcm43xx_initval10.fw ... > [EMAIL PROTECTED] bcm43xx-fwcutter-006]# make installfw > if ! [ -d /lib/firmware ]; then mkdir -p /lib/firmware; fi > install -o 0 -g 0 -m 600 bcm43xx_*.fw /lib/firmware > [EMAIL PROTECTED] bcm43xx-fwcutter-006]# lsmod | grep bcm43xx > [EMAIL PROTECTED] bcm43xx-fwcutter-006]# > [EMAIL PROTECTED] bcm43xx-fwcutter-006]# modprobe bcm43xx > FATAL: Module bcm43xx not found. > > What i'm doing wrong, any ideas? > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows XP or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 regression
On Dec 11, 2007 3:02 AM, Michael Buesch <[EMAIL PROTECTED]> wrote: > On Tuesday 11 December 2007 02:14:05 Brennan Ashton wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=412861 > > I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that > > things started to stop working at, and could not find any part of this > > patch applied, so at least for that bug it is something else. > > > > Please find out which patch broke it then. Nobody but you can do this. What do you use to hammer the card with data to see if if fails? I have been just surfing the web, and moving data back and forth, but it is very inefficient and a poor form of a test. I think I may have narrowed down the kernel were it starting failing, but I want to make sure. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows XP or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 regression
On Dec 10, 2007 2:36 AM, Michael Buesch <[EMAIL PROTECTED]> wrote: > I have identified another regression introduced by > commit f04b3787bbce4567e28069a9ec97dcd804626ac7. > > On my device it shows up as broken transmission after > a suspend/resume cycle. The workaround for it is to boot > a known good driver (in my case the vendor driver in OSX) > and then reboot (without turning the machine off) into the > broken driver. > > It seems like we unintentionally removed some significant > initialization step in that patch. I could not identify it, yet. > The patch I sent yesterday did fix two other bugs, but not this one. > > I am trying to find the reason for this. > If someone wants to help searching, the best way would be to look > at that patch I mentioned above and compare the stuff that it > removes to the stuff that it adds. There must be some tiny line > that it removes but does not re-add it at another place. > Four eyes see more than two. > > I have no idea how this bug could be related to the few bugreports > in the redhat bugzilla. Though, one could test that by trying a > kernel that does not include the patch. > > Sorry for the inconvenience. > > -- > Greetings Michael. > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > RE: https://bugzilla.redhat.com/show_bug.cgi?id=412861 I downloaded the source for 2.6.23.8-63.fc8.src.rpm the package that things started to stop working at, and could not find any part of this patch applied, so at least for that bug it is something else. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows XP or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Any hope ?
On 9/9/07, Arne Chr. Jorgensen <[EMAIL PROTECTED]> wrote: > hi, > > I am very sorry ! I am dead tired - have been working for 10 days on these > problems, - constantly. > > Larry wrote: > > For the most part, I have stopped answering your posts because you > > don't seem to understand what I say, and you ramble without making your > > thoughts clear. > > Sorry, see above. The objective here is the wireless !! > > ( sorry about the distraction regarding the tapping - as with power button, > other buttons, it wrongly connect to something with recent Fedora kernels. > Okay, lets drop it ! ) > > Documentations from Hewlet-Packard is wrong ! The chip I found inside, IS > a BCM4311KFBG/HDO717 P20 /819737B5. > > - Is that understood ?! > > ( in my last post - I quoted exactly what HP says, and they are lying ! What > I tried to convey, so others may be warned about it ) > > Larry wrote earlier: > > > > This is exactly the computer I have. The wireless is a BCM4311. > > > > I said: if I understood you correctly, you do have this working, and > if so - there is a driver for it ?? git the wireless dev git-pull git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git/ compile with b43 not the b43legacy get the newer fwcutter from the cvs on the bcm43xx page get the firmware from here http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 and extract it with fwcutter sorry for be sort of vague but i have given these directions in various detail various times you can find more in the archives if you need it. Fedora 7 has given me and others some greef in the past getting it to work, i found F6 more cooperative. > > ( And here I don't mean a ndiswrapper ) > > --- > > My last question had to do with kernel configuration for including a driver > for the 4311 or as Vista seem to identify it: 4312. > What needs to be done ? > > > //ARNE > > - hope this will clear up the issues. > > > > > Got a little couch potato? > Check out fun summer activities for kids. > > > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows XP or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Any hope ?
On 9/9/07, Arne Chr. Jorgensen <[EMAIL PROTECTED]> wrote: > Hmmm...why didn't yahoo include the list ?.. > > "Arne Chr. Jorgensen" <[EMAIL PROTECTED]> wrote: > hi, > > In my dialog with Larry, I asked: > > > > Well, just some idea. Perhaps I could install Suse, replicate your > > settings and check it ? > > > > Now, I am running OpenSuse 10.2, with default x86_86 kernel 2.6.18.2-34. > I am unfamilar with Suse, and a bit unsure as how to set it up. > At the moment it uses a Vesa frame buffer device, and perhaps I should > try to compile a NVIDIA driver - any suggestions ? > > ( did try once, but didn't get it working) > > Next, I had to download and install nForceth driver from NVIDIA, as the wire > ethernet wouldn't be recognized. Then I have got some code installed to > control the "tapping" feature of the touchpad. > > As reported earlier, the Fedora update kernels had the machine go crazy. > So even with the "tapping enabled" in Suse, the behaviour isn't as wild as > it was with Fedora. Perhaps Fedora kernels don't recognize the AMD stuff. > > My confusion have had something to do with the impression that in one > particular install - I had wireless up. I still cannot swear it, I could > have been fooled by something it pulled up from the cache, but as I have > said - this wasn't my impression. I have been checking pages all over to > figure out this thing. In the end I did open this damn thing, to see what > this card looked like. > > Surprise - the chips says BCM4311KFBG... what the heck ?? Checking data at > HP, which says what I have reported earlier. But in the end I found some > partlist that seems to operate with two different part numbers, not saying > what the chip set might be, but there is 2 and 3 wire antenna versions. > > Checking registry in Vista - reveals Broadcom..and then 4312 ? > > Larry wrote: > > > > This is exactly the computer I have. The wireless is a BCM4311. > > > > ( take it that your wireless is working, that there is some driver for it ?) > Looking at those specifications from HP again - it does say: > > "Broadcom 4321AGN Wi-Fi Adapter (802.11 a/b/g/ draft-n) + Bluetooth w/2 > antennas" As was said before there are no supported Broadcom Wireless draft-n cards, why DRAFT-n has caught on so much is beond me, its not even the real deal yet. So you have three options return and get a new laptop, fight with finding a card that your computer wont reject (some people have had all kinds of problems tricking there computer to think the card is the one it came with), or get a USB wireless stick. > > > So.. where do I go from here ? > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows XP or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4306 totally exausted
On 9/8/07, Larry Finger <[EMAIL PROTECTED]> wrote: > Brennan Ashton wrote: > > On 9/8/07, Guillermo Javier Nardoni <[EMAIL PROTECTED]> wrote: <> > >>> I believe for that revision you have to use b43-legacy or > >>> bcm43xx depending on your kernel version, however i have been > >>> out of town during most of the naming changes and am just catching up. > > No, a rev 9 802.11 core uses b43. Only chips with a rev < 5 use b43legacy. > Yes, when i said that i was replying to the origional post he made where he said, " De wrt54gl chipset revision is 02" I did not yet have this info ">> ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)" which is why i asked for the output of our standard base info commands (uname lspci dmesg etc) > When you change to b43, you will need to use b43-fwcutter. The firmware files > have different names > and occur in different directories than for bcm43xx varieties. > > Larry > > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows XP or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4306 totally exausted
Please keep in the mailing list no Private conversations. Made some responces bellow. On 9/8/07, Guillermo Javier Nardoni <[EMAIL PROTECTED]> wrote: > > > -Mensaje original- > > De: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] En nombre de > > Brennan Ashton > > Enviado el: Domingo, 26 de Agosto de 2007 08:02 p.m. > > Para: [EMAIL PROTECTED] > > CC: bcm43xx-dev@lists.berlios.de > > Asunto: Re: BCM4306 totally exausted > > > > On 8/26/07, Guillermo Javier Nardoni <[EMAIL PROTECTED]> wrote: > > > Hi everyone, this is my first time here so i'll give a > > brief introducing.. > > > My name is Guillermo and i'm from Argentina, i am in a > > wireless team > > > group building wifi comunnities but... A few days ago we bought > > > 2 linksys wrt54gl v1.1 s/N: CL7B... Wich means it is a broadcom > > > chipset > > > based.- > > > Well, we want to put openwrt with 2.6 kernel but it is doesn't have > > > wireless support yet due to Broadcom. > > > So, i have searched and readed and watch some tv show too but it is > > > still doesn't work. > > > Does anybody tried to compile the driver with linux 2.6 > > vanilla kernel > > > and work properlly? > > > De wrt54gl chipset revision is 02 > > > > Could you post the result of > > > > uname -r > 2.6.22 > > > ispci | grep Broadcom > Don't work, i've installed the package from openwrt > But it shows nothing (empty output when i type "lspci -v") that is lspci with an L not an i, it is a core PCI util so you should have it, if nothing shows up it would have to be on a different buss? > > > dmesg | grep bcm > When i type dmesg | grep bcm (nothing greped) > So i copied this... > > [EMAIL PROTECTED]:/lib/modules/2.6.22# clear > [EMAIL PROTECTED]:/lib/modules/2.6.22# insmod bcm43xx-mac80211.ko; dmesg > Linux version 2.6.22 ([EMAIL PROTECTED]) (gcc version 4.1.2) #3 Thu Jul 26 > 18:00:50 > CEST 2007 > CPU revision is: 00029008 > ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0E, vendor 0x4243) > ssb: Core 1 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243) > ssb: Core 2 found: MIPS 3302 (cc 0x816, rev 0x06, vendor 0x4243) > ssb: Core 3 found: USB 1.1 Host (cc 0x817, rev 0x02, vendor 0x4243) > ssb: Core 4 found: MEMC SDRAM (cc 0x80F, rev 0x01, vendor 0x4243) > ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243) > ssb: Core 6 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243) > ssb: Initializing MIPS core... > ssb: set_irq: core 0x0806, irq 2 => 2 > ssb: set_irq: core 0x0817, irq 3 => 3 > ssb: set_irq: core 0x0812, irq 4 => 4 > ssb: Sonics Silicon Backplane found at address 0x1800 > Determined physical RAM map: > memory: 0100 @ (usable) > Initrd not found or empty - disabling initrd > On node 0 totalpages: 4096 > Normal zone: 32 pages used for memmap > Normal zone: 0 pages reserved > Normal zone: 4064 pages, LIFO batch:0 > Built 1 zonelists. Total pages: 4064 > Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 > init=/etc/preinit noinitrd console=ttyS0,115200 > Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes. > Primary data cache 8kB, 2-way, linesize 16 bytes. > Synthesized TLB refill handler (20 instructions). > Synthesized TLB load handler fastpath (32 instructions). > Synthesized TLB store handler fastpath (31 instructions). > Synthesized TLB modify handler fastpath (30 instructions). > PID hash table entries: 64 (order: 6, 256 bytes) > Using 100.000 MHz high precision timer. > Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) > Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) > Memory: 13628k/16384k available (2030k kernel code, 2756k reserved, 297k > data, 120k init, 0k highmem) > Calibrating delay loop... 199.16 BogoMIPS (lpj=398336) > Mount-cache hash table entries: 512 > NET: Registered protocol family 16 > Time: MIPS clocksource has been installed. > NET: Registered protocol family 2 > IP route cache hash table entries: 1024 (order: 0, 4096 bytes) > TCP established hash table entries: 512 (order: 0, 4096 bytes) > TCP bind hash table entries: 512 (order: -1, 2048 bytes) > TCP: Hash tables configured (established 512 bind 512) > TCP reno registered > squashfs: version 3.0 (2006/03/15) Phillip Lougher > Registering mini_fo version $Id$ > JFFS2 version 2.2. (NAND) C 2001-2006 Red Hat, Inc. > io scheduler noop registered > io scheduler deadline registered (default) > Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing enabled > serial8250: ttyS0 at MMIO 0
Re: BCM4306 totally exausted
On 8/26/07, Guillermo Javier Nardoni <[EMAIL PROTECTED]> wrote: > Hi everyone, this is my first time here so i'll give a brief introducing.. > My name is Guillermo and i'm from Argentina, i am in a wireless team group > building wifi comunnities but... A few days ago we bought > 2 linksys wrt54gl v1.1 s/N: CL7B... Wich means it is a broadcom chipset > based.- > Well, we want to put openwrt with 2.6 kernel but it is doesn't have wireless > support yet due to Broadcom. > So, i have searched and readed and watch some tv show too but it is still > doesn't work. > Does anybody tried to compile the driver with linux 2.6 vanilla kernel and > work properlly? > De wrt54gl chipset revision is 02 Could you post the result of uname -r ispci | grep Broadcom dmesg | grep bcm have you used fwcutter yet, if so what version I believe for that revision you have to use b43-legacy or bcm43xx depending on your kernel version, however i have been out of town during most of the naming changes and am just catching up. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 and knetworkmanager
> Yes I remember, do you know in what circumstances this happens for you? What > distro are you using, and are you using a networkmanager? > I can poweroff my system properly if I don't attempt to unload the b43 module > first. > > I'm trying to track down where this happens, but I'm not that good, it may > take some time. > Fedora 6 kernel from wireless-dev 2.6.23-rc2 networkmanager command to brake it: rmmod bcm43xx_mac80211 it may take a few times, but it will happen. It does not matter if the wireless was working at that time or not. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 and knetworkmanager
On 8/18/07, Richard Jonsson <[EMAIL PROTECTED]> wrote: > On Saturday 18 August 2007 22:17:22 you wrote: > > > > It's a bug in mac80211 > > Ok, is it a known bug, and is there a patch? Should I bother finding it? > And finally, is this the wrong list to ask these questions beeing a mac80211 > bug? > > Thanks in advance, > Richard > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > I also reported this a few weeks ago, you will note that it is not knetworkmanager specific, also happens with GNOME. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
On 8/10/07, John H. <[EMAIL PROTECTED]> wrote: > doesn't that still require compiling another kernel? That's what we > already discussed. I was looking for a simple driver to download to > use the fedora kernels but a custom driver, like the bcm43xx i am > currently using from larry. > no, it is just like any other kernel update from fedora. It has already been compiled, all you need to do is install the RPM -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
On 8/10/07, John H. <[EMAIL PROTECTED]> wrote: > I tried that:( > > Any chance of your script being out now so I can use the bcm43xx-mac80211?:) > > On 8/10/07, Brennan Ashton <[EMAIL PROTECTED]> wrote: > > as root > > modprobe -r bcm43xx > > modprobe bcm43xx > > > > then you dont need to reboot > > > > On 8/10/07, John H. <[EMAIL PROTECTED]> wrote: > > > Larry, your driver seems to work pretty well, the bcm43xx one, > > > however, sometimes I have to reboot to get it working right again(I > > > just can't ping anything, etc). > > > > > > I was wondering if that file you linked to is updated often? > > > > > > On 8/8/07, Larry Finger <[EMAIL PROTECTED]> wrote: > > > > John H. wrote: > > > > > I am using larry's .bz2 of bcm43xx and I get this ... > > > > > > > > > > wlan0 IEEE 802.11b/g ESSID:"Network4Home" Nickname:"Broadcom > > > > > 4311" > > > > > Mode:Managed Frequency=2.437 GHz Access Point:blah > > > > > Bit Rate=24 Mb/s Tx-Power=18 dBm > > > > > RTS thr:off Fragment thr:off > > > > > Link Quality=50/100 Signal level=-69 dBm Noise level=-71 > > > > > dBm > > > > > Rx invalid nwid:0 Rx invalid crypt:11 Rx invalid frag:0 > > > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > > > > > > > > > > Is it possible to get 54mb/s? Should I care if it's mainly for > > > > > residential cable modem right now? > > > > > > > > To get a setting of 54M, look at 'man iwconfig'. To get throughput at > > > > 54M, you need a different > > > > driver, and much better signal to noise! The highest residential cable > > > > rates in my area are 8Mbs > > > > down and 512Kbs up. Business rates ate 10 Mbs down and 2 Mbs up, but > > > > that costs a lot more. Your 24M > > > > setting should give you something in the range of 12Mbs throughput. You > > > > do the math. > > > > > > > > Larry > > > > > > > > > > > _______ > > > Bcm43xx-dev mailing list > > > Bcm43xx-dev@lists.berlios.de > > > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > > > > > > > > > -- > > Brennan Ashton > > Bellingham, Washington > > > > "The box said, 'Requires Windows 98 or better'. So I installed Linux" > > > The script that i was going to write is unnessisary, pull the latest kernel from Fedoras koji, see Jogn Linville's post. The new patches have been applied. http://koji.fedoraproject.org/koji/buildinfo?buildID=13224 for the RPMS That should work, otherwise pull the new wireless-dev kernel source. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
as root modprobe -r bcm43xx modprobe bcm43xx then you dont need to reboot On 8/10/07, John H. <[EMAIL PROTECTED]> wrote: > Larry, your driver seems to work pretty well, the bcm43xx one, > however, sometimes I have to reboot to get it working right again(I > just can't ping anything, etc). > > I was wondering if that file you linked to is updated often? > > On 8/8/07, Larry Finger <[EMAIL PROTECTED]> wrote: > > John H. wrote: > > > I am using larry's .bz2 of bcm43xx and I get this ... > > > > > > wlan0 IEEE 802.11b/g ESSID:"Network4Home" Nickname:"Broadcom 4311" > > > Mode:Managed Frequency=2.437 GHz Access Point:blah > > > Bit Rate=24 Mb/s Tx-Power=18 dBm > > > RTS thr:off Fragment thr:off > > > Link Quality=50/100 Signal level=-69 dBm Noise level=-71 dBm > > > Rx invalid nwid:0 Rx invalid crypt:11 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > > > > Is it possible to get 54mb/s? Should I care if it's mainly for > > > residential cable modem right now? > > > > To get a setting of 54M, look at 'man iwconfig'. To get throughput at 54M, > > you need a different > > driver, and much better signal to noise! The highest residential cable > > rates in my area are 8Mbs > > down and 512Kbs up. Business rates ate 10 Mbs down and 2 Mbs up, but that > > costs a lot more. Your 24M > > setting should give you something in the range of 12Mbs throughput. You do > > the math. > > > > Larry > > > > > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
Sorry work has been calling (very late nights from server migration), I will try to get the script going soon, as i need to upgrade to the new tree anyway. On 8/7/07, John H. <[EMAIL PROTECTED]> wrote: > Did I misunderstand something? I thought some script was available or > some easy way to use either bcm43xx or the new one. brennan says he > has a script to just let you use the newer driver with higher mbps, > but I have never heard back from him. > > On 8/3/07, John H. <[EMAIL PROTECTED]> wrote: > > yes, please post such a script so I can use it and not need > > ndiswrapper anymore:) > > > > On 8/3/07, Brennan Ashton <[EMAIL PROTECTED]> wrote: > > > > The OP's meaning of this thread, which is that bcm43xx_mac80211 doesn't > > > > work well enough for him, > > > > has been lost. He wants bcm43xx (softmac)! > > > > > > > > One other option is to get the stand-alone version of bcm43xx from my > > > > FTP site > > > > (ftp://lwfinger.dynalias.org/patches/bcm43xx-softmac-sa.tar.bz2), and > > > > build that. > > > > > > which is what the directions that i posted do, with the new version of > > > bcm43xx_mac80211 it should work fine, that is what i have on F7 with > > > the same card, and i am getting speeds over 1mb/s. This weekend, i > > > could write a script to automate the process if people are interested. > > > > > > -- > > > Brennan Ashton > > > Bellingham, Washington > > > > > > "The box said, 'Requires Windows 98 or better'. So I installed Linux" > > > > > > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Odd network locking
> I've seen this while testing the 4301 driver (also mac80211). > I do not get it when booting into recovery mode, but is 100% reproducible when > booting into X. A guess is that networkmanager is involved in it. I am also > pretty sure that "Usage count" equals the number of times the driver has been > reloaded. I can shut down fine when I've not reloaded the module. > > My specs: 2.6.23-rc1+bcm4301 driver, 4311 hardware, kubuntu feisty. I will do some tests to see if killing NM first will resolve this. This is not the first NM bug with this driver that i have noticed. The nice thing about this bug is that it is easy to reproduce. Also i have notice that failure rate has risen to ~50% PS Sorry for the top post on that last message -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Odd network locking
When the bcm43xx_mac80211 driver stops communicating, and needs to be reset (this seems to happens when coming from strong to week to strong signal area quickly) i have been rmmod and then modprobing it. this works most of the time, but some times (~20%), it will lock up the network with this error that repeats. Message from [EMAIL PROTECTED] at Fri Aug 3 00:55:41 2007 ... localhost kernel: [19316.256549] unregister_netdevice: waiting for eth1 to becom e free. Usage count = 5 usage count varies, but renders the system unusable (extremely slow, like when localhost is not defined) until the laptop is turned off, the system will hang during shutdown requiring a power interrupt. This did not happen with the bcm43xx driver in 2.6.22-rc7. Current Data [EMAIL PROTECTED] ~]# uname -r 2.6.23-rc1 [EMAIL PROTECTED] ~]# lspci | grep Broadcom 03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01) dmesg is over filled with TKIP decrypt info, so little info is there [EMAIL PROTECTED] ~]# iwlist eth1 scanning Warning: Driver for device eth1 has been compiled with version 22 of Wireless Extension, while this program supports up to version 20. Some things may be broken... eth1 Scan completed : Cell 01 - Address: 00:12:17:AA:84:67 ESSID:"thishome" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=41/100 Signal level=-61 dBm Noise level=-68 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:tsf=0298702da2c8 Cell 02 - Address: 00:18:3F:64:47:D9 ESSID:"2WIRE199" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=31/100 Signal level=-77 dBm Noise level=-68 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=00401364c181 Cell 03 - Address: 00:03:52:C7:E3:B0 ESSID:"bbx" Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Quality=27/100 Signal level=-83 dBm Noise level=-68 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Extra:tsf=000002711d4b -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
> The OP's meaning of this thread, which is that bcm43xx_mac80211 doesn't work > well enough for him, > has been lost. He wants bcm43xx (softmac)! > > One other option is to get the stand-alone version of bcm43xx from my FTP site > (ftp://lwfinger.dynalias.org/patches/bcm43xx-softmac-sa.tar.bz2), and build > that. which is what the directions that i posted do, with the new version of bcm43xx_mac80211 it should work fine, that is what i have on F7 with the same card, and i am getting speeds over 1mb/s. This weekend, i could write a script to automate the process if people are interested. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
> Failing that, you can just rebuild the bcm43xx module _without_ the PCI > IDs removed -- there's no reason for you to rebuild the whole kernel. Except to keep up with current patches in the whole wireless system, and enable more debugging as this is still very much in development. By rebuilding the whole thing, he can use bcm43xx_mac80211 -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
On 8/2/07, John H. <[EMAIL PROTECTED]> wrote: > It blacklisted bcm43xx-mac80211 but it still loads anyway, and so does > ndiswrapper, despite being blacklisted. > so i renamed bcm43xx-mac80211.ko to bcm43xx-mac80211.bak and did the > same for ndiswrapper and pasted what I got as a result on boot. > Basically no wireless with just bcm43xx and softmac modules. > > On 8/3/07, Larry Finger <[EMAIL PROTECTED]> wrote: > > John H. wrote: > > > I will send that in the next email. > > > > > > I am confused. I am using 2.6.22. Are you saying bcm43xx-mac80211 > > > should not be bitrate limited then? > > > > > > uname -a > > > Linux laptop 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 > > > i686 i386 GNU/Linux > > > > No -bcm43xx-mac80211 does not work very well at the moment. If you had a > > real 2.6.22 distribution, > > it would work. What Fedora did was strip out the PCI ID's from bcm43xx for > > all the > > 802.11g-compatible devices and force you to use bcm43xx-mac80211. If you > > get a new copy of the > > source, configure it for softmac and bcm43xx, it will work. > > > > The script I sent you should have blacklisted bcm43xx-mac80211 and > > installed the PCI ID for your > > device. It seems that it didn't work. > > > > Larry > > > > > > > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > try what i have posted earlier, http://lists.berlios.de/pipermail/bcm43xx-dev/2007-July/004985.html -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Report on BCM4318 under Fedora 7
> No I don't. Hum. > But today I get rather good performance (well compared to yesterday) > from my tree. Seems to depend on the moonphase or something. > > I hate benchmarking. > I am willing to help with benchmarking, just tell me what you want. Card: bcm4311 on the edge of lost signal eth1 IEEE 802.11b/g ESSID:"thishome" Nickname:"Broadcom 4311" Mode:Managed Frequency=2.437 GHz Access Point: 00:12:17:AA:84:67 Bit Rate=24 Mb/s Tx-Power=18 dBm RTS thr:off Fragment thr:off Encryption key:FC73-2B97-E56C-128C-EA93-BCCF-37C0-F940-F79D-1CA0-AC32-A2A4-24B5-6E1A-B930-B64C Security mode:open Link Quality=58/100 Signal level=-69 dBm Noise level=-69 dBm Rx invalid nwid:0 Rx invalid crypt:74 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: trouble installing driver for bcm4318
look back in the archive a little, you will find a detailed list of instructions that i posted. here it is i think http://lists.berlios.de/pipermail/bcm43xx-dev/2007-July/004985.html On 7/10/07, Larry Finger <[EMAIL PROTECTED]> wrote: > Eddy Zhu wrote: > > Hi > > > > I am a newbie to Linux world. I have successfully installed Fedora 6.0 > > in my compaq presario laptop. But my wireless card doesn't seem to > > work. I have already spent hours researched online but I can't get a > > complete instructions step by step on installing a driver for bcm4318. > > > > Please kindly post a complete step by step installation instruction on > > how to download and install the bcm43xx driver in Fedora 6.0 O.S. > > Under Linux, it is important to list your kernel version in addition to your > distro version for two > reasons. Firstly, there are so many distros that one cannot remember what > each one includes. > Secondly, the kernel may have been updated independently of the distro. For > example, I'm running the > x86-64 version of openSUSE 10.2 for which the standard kernel is 2.6.18; > however, I'm running kernel > 2.6.22. You use the command 'uname -r' (without the quotes) to get the kernel > version. > > As stated above, I'm not a Fedora user and I may get some of the following > wrong. > > Have you installed the firmware for your bcm43xx card? If not, you will need > to do the following as > root: > > Find your Windows driver. It will likely be named bcmwl5.sys. > > Issue the following commands: > > yum install bcm43xx-fwcutter > bcm43xx-fwcutter -w /lib/firmware XX.sys > > where XX is replaced by the path and name of your Windows driver. > > If you send your kernel version, we will be able to get you the rest of the > way. > > Larry > > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4318 on again, off again (Larry Finger)
Made a type-o On 7/7/07, Brennan Ashton <[EMAIL PROTECTED]> wrote: > >>SNIP<< > > [EMAIL PROTECTED] ~]# uname -a > > Linux localhost.localdomain 2.6.21-1.3228.fc7 #1 SMP Thu Jun 28 16:42:25 > > CDT 2007 i686 i686 i386 GNU/Linux > > [EMAIL PROTECTED] ~]# lspci | grep Broadcom > > 0a:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One > > 54g] 802.11g Wireless LAN Controller (rev 02) > > [EMAIL PROTECTED] ~]# dmesg | grep bcm43xx > > [EMAIL PROTECTED] ~]# > > > > > > ___ > > Bcm43xx-dev mailing list > > Bcm43xx-dev@lists.berlios.de > > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > > > The fact that dmesg had nothing to say means you are not using the > bcm4xx driver. > you are not using a kernel from kernel.org or wireless-dev you need to > get one of them, > Linux localhost.localdomain 2.6.21-1.3228.fc7 > that - with a number after it is a dead give away. You want uname -r > to give 2.6.22-rc7 > try this: > su - > yum install bcm43xx-fwcutter > wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.9.2.tar.bz2 > tar -xjvf broadcom-wl-4.80.9.2.tar.bz2 > bcm43xx-fwcutter -w /lib/firmware/ broadcom-wl-4.80.9.2/kmod/wl_apsta.o > when you set up ndiswrapper you may have blacklisted bcm43xx > if so you need to remove it (edit /etc/modprobe.d/blacklist) > > cd /usr/src > yum install git > git-clone > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git > cd wireless-dev here this > cp /boot/config-`uname -r` ./.config > make mrproper should be this make mrproper cp /boot/config-`uname -r` ./.config > make menuconfig > select load alternative config file, it should sugest .config select yes > then navigate to: > device-drivers-->Network-device-support-->Wireless-LAN-->press space > when broadcom BCM43xx is selected (an M should appear next to it, if > not hit space a few more times) do the same for broadcom BCM43xx > mac80211 stack. you may want to enable some debugging in the same > location. > press esc a few times, it will say do you want to save, select yes > then on the command line again (this part will take a while): > make all > make modules_install > make install > now reboot > select the new kernel at boot when grub comes up > command line again: > su - > modprobe bcm43xx > > That should get u up and running, or at least to a state in which we > can help. I don't know what other damage ndiswrapper may have done > that you need to remove maybe someone else can way in on that. If it > works, you can change /boot/grub/menu.lst so that the new kernel is > default. > -- > Brennan Ashton > Bellingham, Washington > > "The box said, 'Requires Windows 98 or better'. So I installed Linux" > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4318 on again, off again (Larry Finger)
>>SNIP<< > [EMAIL PROTECTED] ~]# uname -a > Linux localhost.localdomain 2.6.21-1.3228.fc7 #1 SMP Thu Jun 28 16:42:25 > CDT 2007 i686 i686 i386 GNU/Linux > [EMAIL PROTECTED] ~]# lspci | grep Broadcom > 0a:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One > 54g] 802.11g Wireless LAN Controller (rev 02) > [EMAIL PROTECTED] ~]# dmesg | grep bcm43xx > [EMAIL PROTECTED] ~]# > > > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > The fact that dmesg had nothing to say means you are not using the bcm4xx driver. you are not using a kernel from kernel.org or wireless-dev you need to get one of them, Linux localhost.localdomain 2.6.21-1.3228.fc7 that - with a number after it is a dead give away. You want uname -r to give 2.6.22-rc7 try this: su - yum install bcm43xx-fwcutter wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.9.2.tar.bz2 tar -xjvf broadcom-wl-4.80.9.2.tar.bz2 bcm43xx-fwcutter -w /lib/firmware/ broadcom-wl-4.80.9.2/kmod/wl_apsta.o when you set up ndiswrapper you may have blacklisted bcm43xx if so you need to remove it (edit /etc/modprobe.d/blacklist) cd /usr/src yum install git git-clone git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git cd wireless-dev cp /boot/config-`uname -r` ./.config make mrproper make menuconfig select load alternative config file, it should sugest .config select yes then navigate to: device-drivers-->Network-device-support-->Wireless-LAN-->press space when broadcom BCM43xx is selected (an M should appear next to it, if not hit space a few more times) do the same for broadcom BCM43xx mac80211 stack. you may want to enable some debugging in the same location. press esc a few times, it will say do you want to save, select yes then on the command line again (this part will take a while): make all make modules_install make install now reboot select the new kernel at boot when grub comes up command line again: su - modprobe bcm43xx That should get u up and running, or at least to a state in which we can help. I don't know what other damage ndiswrapper may have done that you need to remove maybe someone else can way in on that. If it works, you can change /boot/grub/menu.lst so that the new kernel is default. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4312 on again, off again
On 7/5/07, Robert Easter <[EMAIL PROTECTED]> wrote: > Thanks, man- Just after I decided to make a display of my native > asininity the thing came back on, but I am keeping this letter as a > first try for next time it craps out. > > Brennan Ashton wrote: > > > > First there is a transmit power problem that has been hard to fix > > (correct me if i have misunderstood some of the other emails that flow > > though here) this is going to make connecting to some networks very > > flaky if not impossible when you are father away. > I guess that would explain the light-related problem, especially if it's > a power indicator and not a tx/rx detector... I would guess that the like is a link tx/rx indicator. There is usually a light that tells you if the wireless is turned on. > > > > As for the ability to connect sometimes and not others, it is > > something called i need to use the new kernel. > He pulled in the latest kernel last week off kernel.org, so I would at I wonder if he got 2.6.21.4 or 2.6.22.rc7 there is a big difference. run uname -a that will tell us > least hope it will be top kernel for a while before the next F7 build > comes out, & even then there's at least the hope that the new one will > adapt... (No?) > > Or use rmmod bcm43xx a > > lot. > I'll have to check that out & see what it is. it is a command. > > If you are using a distros kernel, it is very likely that it > > won't work, so i direct your attention toward www.kernel.org. At the > > time that my system was exhibiting that behavior, i applied this patch > > and it went away > > https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003819.html > I will hang on to that link- thanx! wont work on the newer kernels > > > . With the newer kernels, it should not be a problem. I still have > > problems when i am to far away from my AP, but in a reasonable range, > > it is very functional. > > > > a uname -a would be helpful > > lspci | grep Broadcom > > dmesg | grep bcm43xx > What do these mean / do, by the way? it is a | not a / it is the shift \ looks like a colon, it is known as a pipe, and allows you to "pipe" the output of one command to another. Grep is used to search the result for a string (as well as other things). > > > > Also that tidbit about the light was completely useless, it is > > hardware not software (the filament in your ceiling light does not > > effect whether or not the wall switch opens and closes) > Yeah, but when the wifi was available again, the light started > flashing. When it had quit, so had the light. Maybe there's a hardware > issue I need to look into? doubt it, suggests that it is a link light. > > > > If wont use the bcm43xx driver you are not going to find what people > > say here very useful. > Well, what else is there? you said that you were using ndiswrapper you need to use that opensource driver bcm43xx with a firmware cutter. you will need to remove the ndiswrapper stuff, extract the firmware and load the modules (bcm43xx-mac80211). I believe once you have delt with ndiswrapper (cant help you there) you need to do somthing like this: wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.9.2.tar.bz2 tar -xjvf broadcom-wl-4.80.9.2.tar.bz2 bcm43xx-fwcutter -w /lib/firmware/ broadcom-wl-4.80.9.2/kmod/wl_apsta.o echo 'blacklist bcm43xx' >> /etc/modprobe.d/blacklist (not positive about this) when you set up ndiswrapper you may have blacklisted bcm43xx-mac80211 if so you need to remove it. modprobe bcm43xx-mac80211 I think that is all correct. > > > > Well that is my best guess at what you were trying to say. > Sounds like you're a good guesser. I guess! > > Blessings on ya! > > r.e. > > > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4312 on again, off again
On 7/4/07, Robert Easter <[EMAIL PROTECTED]> wrote: > It took a BS programmer over five hours, but he got my bcm4318 chip > talking to my computer with the NDISWrapper and a kernel build. Before > that the wireless was showing on the laptop's wifi switch light but not > making up to the computer to actually use the signal. Now, after six > days, it suddenly stops. Give it a few days, and it's on again. Any clues? Ok i am going to try to be nice, as i myself have been chewed out by this forum before (improper email reply edict), and as i had a similar problem i think, but as has been explained before its hard to tell. First there is a transmit power problem that has been hard to fix (correct me if i have misunderstood some of the other emails that flow though here) this is going to make connecting to some networks very flaky if not impossible when you are father away. As for the ability to connect sometimes and not others, it is something called i need to use the new kernel. Or use rmmod bcm43xx a lot. If you are using a distros kernel, it is very likely that it wont work, so i direct your attention toward www.kernel.org. At the time that my system was exhibiting that behavior, i applied this patch and it went away https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003819.html . With the newer kernels, it should not be a problem. I still have problems when i am to far away from my AP, but in a reasonable range, it is very functional. a uname -a would be helpful lspci | grep Broadcom dmesg | grep bcm43xx Also that tidbit about the light was completely useless, it is hardware not software (the filament in your ceiling light does not effect whether or not the wall switch opens and closes) If wont use the bcm43xx driver you are not going to find what people say here very useful. Well that is my best guess at what you were trying to say. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [bcm43xx-users] 4311 still not receiving
On 7/1/07, Larry Finger <[EMAIL PROTECTED]> wrote: > Chuckk Hubbard wrote: > > On 6/23/07, *Larry Finger* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Chuckk Hubbard wrote: > > > Larry, I think I forgot to mention something... might the fact > > that it's > > > a 64-bit machine and a 64-bit distro possibly make it not work? > > > > No, it shouldn't matter. I use a 64-bit distro on an AMD 64 X2 cpu. > > > > I just looked to see what Synaptic is. As it messed up your wired > > network as well as wireless, > > something must have gotten destroyed in the networking section. Does > > your distro have a "repair" > > option? If so, try it. > > > > > > > > I haven't found a repair option; it is not possible to downgrade is what > > I was told. I have gone through this process several times since then- > > reinstalling, compiling a 2.6.22 kernel, having wireless, doing some > > updates, losing the wireless. I noticed a couple of things... > > I believe the package that is updating that is killing my wireless is > > the linux-image-2.6.18 etc. package. > > Also, a message I kept getting said that the driver I had was version > > 22, and the program (iwconfig) only supported up to 20. > > > > I've now reinstalled and put a hold on the linux image package, although > > I haven't compiled my new kernel just yet. > > I also tried buying an Intel mini PCI express wireless card that I saw > > highly recommended for Linux, but my BIOS is configured to reject it. > > Never buy Gateway. > > Download and install the 64-bit version of openSUSE 10.2. Then upgrade the > kernel to 2.6.21 and all > will be well. You will find NetworkManager to be a very nice way to connect. > > Larry > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > I have done the same thing with Fedora with a gateway with 4311 every so often i have to restart the computer and the wireless access point, but other than that it works fine. -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [bcm-users]
On 6/18/07, Chuckk Hubbard <[EMAIL PROTECTED] > wrote: Hi. I have a 4311 on a Gateway MX6447. I am running 64studio, an offshoot of Debian. I downloaded kernel 2.6.21 and patched it to 2.6.22-rc4 (for my soundcard), copied the configuration, and made sure all the bcm43xx options were selected. I compiled the kernel, installed bcm43xx-fwcutter, and ran it on wl_apsta.o from http://boredklink.googlepages.com/wl_apsta.o I did try re-cutting the firmware, and now "bcm43xx-fwcutter /lib/firmware ./wl_apsta.o" says that wl_apsta.o has an invalid checksum; however, when I checked the sum under Windows, it told me a different number than what fwcutter said. I think that that is an old firmware, try the one here http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 very unstable in kernel 2.6.21.4
2.6.22-rc4 fixed it On 6/10/07, Brennan Ashton <[EMAIL PROTECTED]> wrote: I got it off of the mailing list see https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003819.html This patch took my sub 1Mb peformace and brought it up to full speed. This was on the 2.6.20.3 kernel. The patch no longer works in the 2.6.21.4kernel. Read my first mailing. I have downloaded the new kernel and am patching it with 2.6.44-rc4 now. On 6/10/07, Larry Finger <[EMAIL PROTECTED]> wrote: > > Where did you get this patch? It alone will ruin the performance of the > BCM4311, which has phy->rev > == 8!! For any 2.6.21.Y, you need to get and apply > ftp://lwfinger.dynalias.org/patches/combined_2.6.21.patch. > Alternatively, you can download > 2.6.22-rc4, which has all the patches for 2.6.21 built in. > > Larry > > -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: TX power stuff confusion
I have the same card (on fedora), it is working great now that i used the new kernel and firmware code. kernel 2.6.22-rc4, dont use the 2.6.21.4kernel. When you update, make shure you go in menuconfig and select to install as a module, it's placement has changed and will not load with your old config file (third time compiling tonight). Hope you get that card working. On 6/10/07, Pavel Roskin <[EMAIL PROTECTED]> wrote: On Sun, 2007-06-10 at 19:13 +0200, Michael Buesch wrote: > I implemented the new stuff for the TX power adjustment and > it seems to work fine. Good work on the specs! :) I'm very glad about it! I checked out the current code http://bu3sch.de/git/wireless-dev.git and compiled it. First time the kernel would not even boot (Fedora is "too smart" to load all modules on startup), but I saw debugfs in the stck track. CONFIG_DEBUG_FS was disabled, so I enabled it. This time I could boot, but I saw some stack traces and messages you may want to see. This is the part of the kernel log starting with wireless initialization. It's going to be a busy week for me, so I don't expect to participate in debugging much, but I'm ready to send more information if needed. This is Fedora 7 x86_64 on Dell D-520 laptop with PCIe BCM4311. Thanks to everybody involved! Even if it's not working for me now, I'm sure it will work really soon. -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 very unstable in kernel 2.6.21.4
I got it off of the mailing list see https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003819.html This patch took my sub 1Mb peformace and brought it up to full speed. This was on the 2.6.20.3 kernel. The patch no longer works in the 2.6.21.4kernel. Read my first mailing. I have downloaded the new kernel and am patching it with 2.6.44-rc4 now. On 6/10/07, Larry Finger <[EMAIL PROTECTED]> wrote: Where did you get this patch? It alone will ruin the performance of the BCM4311, which has phy->rev == 8!! For any 2.6.21.Y, you need to get and apply ftp://lwfinger.dynalias.org/patches/combined_2.6.21.patch. Alternatively, you can download 2.6.22-rc4, which has all the patches for 2.6.21 built in. Larry -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm4311 very unstable in kernel 2.6.21.4
I applied the new firmware with similar results, failed within 5min this time. The console if filled with this message hundreds of times. bcm43xx: ASSERTION FAILED (!ring->suspended) at: drivers/net/wireless/bcm43xx/bcm43xx_dma.c:71:request_slot() Then i lose connection altogether (networkmanager locks up). I go to the console and see this message: bcm43xx: Controller RESET (TX timeout) ... bcm43xx: IRQ_READY timeout bcm43xx: core_up for active 802.11 core failed (-19) bcm43xx: Controller restart failed When i go to do a rmmod bcm43xx i get this: rmmod bcm43xx bcm43xx: ASSERTION FAILED (!err) at: drivers/net/wireless/bcm43xx/bcm43xx_main.c:4095:bcm43xx_net_stop() and rmmod never completes execution, system then becomes very unstable. Also wifi speeds seem to be less when it is actually running then in kernel 2.6.20.3, with the earlier patch. The kernel is currently vanilla, are there any other patches that i should try? This patch seemed relaited, but looks like it may have already been upstreamed http://lists.berlios.de/pipermail/bcm43xx-dev/2006-November/003223.html? On 6/10/07, Martin Langer <[EMAIL PROTECTED]> wrote: On Sat, Jun 09, 2007 at 10:23:47PM -0700, Brennan Ashton wrote: > bcm43xx: Chip ID 0x4311, rev 0x1 > bcm43xx: Number of cores: 4 > bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243 > bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243 > bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243 > bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243 > bcm43xx: PHY connected > bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8 > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) > bcm43xx: Radio turned off > bcm43xx: Radio turned off > bcm43xx: PHY connected > bcm43xx: Microcode rev 0xf5, pl 0x5a (2003-12-22 20:11:25) Did you already tried newer firmware files? e.g. http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o Martin -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
bcm4311 very unstable in kernel 2.6.21.4
My bcm4311 has become very unsable in the new 2.6.21.4 kernel. It frequently
has core crashes, and recently when i modprobed, caused the system to crash.
bcm43xx: ASSERTION FAILED (!err) at:
drivers/net/wireless/bcm43xx/bcm43xx_main.c :4095:bcm43xx_net_stop()
rmmod bcm43xx
never finshed running command.
The patch that i have been using is this one
Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_phy.c
===
--- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_phy.c
+++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_phy.c
@@ -1225,7 +1225,7 @@ static void bcm43xx_phy_initg(struct bcm
}
if (phy->rev < 3 && phy->connected)
bcm43xx_phy_write(bcm, 0x047E, 0x0078);
- if (phy->rev >= 6 && phy->rev <= 8) {
+ if (phy->rev >= 6 && phy->rev < 8) {
bcm43xx_phy_write(bcm, 0x0801, bcm43xx_phy_read(bcm, 0x0801) |
0x0080);
bcm43xx_phy_write(bcm, 0x043E, bcm43xx_phy_read(bcm, 0x043E) |
0x0004);
}
But after going from the 2.6.20.3 kernel to 2.6.21.4 kernel, i could not use
the patch. Looking at the kernel change log, this might be because of the
change in 2.6.20.7? But that is just a guess.
dmesg listing:
[EMAIL PROTECTED] ~]# dmesg | grep bcm43xx
bcm43xx driver
bcm43xx: Chip ID 0x4311, rev 0x1
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243
bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243
bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: PHY connected
bcm43xx: Microcode rev 0xf5, pl 0x5a (2003-12-22 20:11:25)
bcm43xx: Radio turned on
bcm43xx: Chip initialized
bcm43xx: 32-bit DMA initialized
bcm43xx: Keys cleared
bcm43xx: Selected 802.11 core (phytype 2)
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
bcm43xx: set security called, .active_key = 0, .level = 2, .enabled = 1,
.encrypt = 1
bcm43xx: set security called, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .enabled = 1, .encrypt = 1
lspci listing
[EMAIL PROTECTED] ~]# lspci | grep Broadcom
03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card (rev 01)
This card is a bcm4311
--
Brennan Ashton
Bellingham, Washington
"The box said, 'Requires Windows 98 or better'. So I installed Linux"
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
