ASUS WL-138G v2 working with different sprom values
Greets, Following up on this idea of substituting sprom images; > Oops, sorry, here is the attached SPROM file.> > >On Tue, Apr 15, 2008 at 11:39 PM, Stefanik Gábor >wrote: > > Looks like this is an Asus-specific issue. Can you try flashing the > attached SPROM file (with a modified MAC address, of course) into your card > to see if it results in *any* transmission? (Back up your SPROM first!) This > is from a non-Asus 4318/02, extracted from a working card. (I can't test it > myself now, as I don't have a usable Linux system ATM.) > > Using that sprom dump which Stefanik provided, the card in question here appears to be now working (although I've not yet tested it at any length) - b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) b43-phy0 debug: Chip initialized b43-phy0 debug: 32-bit DMA initialized Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx b43-phy0 debug: Wireless interface started HW CONFIG: channel=1 freq=2412 phymode=2 b43-phy0 debug: Adding Interface type 2 b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:1e:2a:61:7d:2c wlan0: RX authentication from 00:1e:2a:61:7d:2c (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associated with AP 00:1e:2a:61:7d:2c wlan0: associated phy0: Added STA 00:1e:2a:61:7d:2c ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready -- This was using a pristine 2.6.24 tree on 32bit ix86 -- only the sprom contents were changed. I'll check this on my 64bit machine a bit later -- I'll test out and monitor this (now working) card to make sure it remains sane. Hopefully this provides a clue as to what's going on. Oh...btw, I doubt I've ever seen the led devices registering themselves before (with the shipped sprom contents that is) ... Regards, Donald _ You dream job is up for grabs. Grab it. http://mycareer.com.au/?s_cid=596065 ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: HP Pavillion Woes
Quoting Robert Williams <[EMAIL PROTECTED]>: > Hi All! Been trolling for couple months trying to > learn...just when I think I know what to do & in what > sequence you guys change everything! > I've an HP Pavilion dv9310us w/bcm4311 rev 2 mini-pci. > temp dual-boot xp(sp2)/opensuse 10.3. works on > xp(ugh!) did work on suse for 2 weeks, added security > & other patches, hasn't worked since. kernel: > 2.6.22.17-0.1-default > Prefer operate linux exclusively, but many probs > w/ndiswrapper, if-iw/config and other stuff. really > need wireless access so I can learn remote admin of > tux servers, config, etc. course is avail & free, but > i'm not up to recomp of kernel and/or reverse eng. > just yet. Anybody got a step-by-step for a n00b that > isn't convoluted?? Maybe now there is a pkg or util > which auto-magics?? Please read this document: http://catb.org/~esr/faqs/smart-questions.html Please pay special attention to the following parts: http://catb.org/~esr/faqs/smart-questions.html#forum http://catb.org/~esr/faqs/smart-questions.html#beprecise http://catb.org/~esr/faqs/smart-questions.html#id306968 http://catb.org/~esr/faqs/smart-questions.html#writewell -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
HP Pavillion Woes
Hi All! Been trolling for couple months trying to learn...just when I think I know what to do & in what sequence you guys change everything! I've an HP Pavilion dv9310us w/bcm4311 rev 2 mini-pci. temp dual-boot xp(sp2)/opensuse 10.3. works on xp(ugh!) did work on suse for 2 weeks, added security & other patches, hasn't worked since. kernel: 2.6.22.17-0.1-default Prefer operate linux exclusively, but many probs w/ndiswrapper, if-iw/config and other stuff. really need wireless access so I can learn remote admin of tux servers, config, etc. course is avail & free, but i'm not up to recomp of kernel and/or reverse eng. just yet. Anybody got a step-by-step for a n00b that isn't convoluted?? Maybe now there is a pkg or util which auto-magics?? Have A Healthy, Prosperous Day! Registered Linux User #356732 Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with PCI (not Cardbus) BCM43xx
On Thu, Apr 17, 2008 at 5:18 PM, Michael Buesch <[EMAIL PROTECTED]> wrote: > [ 966.619496] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor > 0x4243) > [ 966.619496] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor > 0x4243) > [ 966.619496] ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243) > [ 966.619496] ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor > 0x4243) > [ 966.637500] ssb: SPROM revision 2 detected. > [ 966.658366] ssb: Sonics Silicon Backplane found on PCI device > :02:05.0 > [ 966.674476] b43-phy3: Broadcom 4318 WLAN found > [ 966.714105] b43-phy3 debug: Found PHY: Analog 3, Type 2, Revision 7 > [ 966.714105] b43-phy3 debug: Found Radio: Manuf 0x17F, Version 0x2050, > Revision 8 > [ 966.734069] phy3: Selected rate control algorithm 'pid' > [ 966.736778] Broadcom 43xx driver loaded [ Features: PNR, Firmware-ID: > FW13 ] > [ 988.593922] input: b43-phy3 as /class/input/input8 > [ 987.781568] b43-phy3: Loading firmware version 351.126 (2006-07-29 > 05:54:02) > [ 987.781568] b43-phy3 warning: You are using an old firmware image. > Support for old firmware will be removed in July 2008. > [ 987.781568] b43-phy3 warning: You must go to > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download > the latest firmware (version 4). > [ 987.895936] b43-phy3 debug: Chip initialized > [ 987.896206] b43-phy3 debug: 32-bit DMA initialized > [ 988.967223] b43-phy3 debug: Wireless interface started > [ 988.967247] b43-phy3 debug: Adding Interface type 2 > [ 988.981264] phy3: HW CONFIG: freq=2412 > [ 991.039238] b43-phy3 debug: Removing Interface type 2 > [ 991.061533] b43-phy3 debug: Wireless interface stopped > [ 990.024893] b43-phy3 debug: DMA-32 rx_ring: Used slots 0/64, Failed > frames 0/0 = 0.0%, Average tries 0.00 > [ 990.026360] b43-phy3 debug: DMA-32 tx_ring_AC_BK: Used slots 0/128, > Failed frames 0/0 = 0.0%, Average tries 0.00 > [ 990.031396] b43-phy3 debug: DMA-32 tx_ring_AC_BE: Used slots 0/128, > Failed frames 0/0 = 0.0%, Average tries 0.00 > [ 990.038040] b43-phy3 debug: DMA-32 tx_ring_AC_VI: Used slots 0/128, > Failed frames 0/0 = 0.0%, Average tries 0.00 > [ 990.048005] b43-phy3 debug: DMA-32 tx_ring_AC_VO: Used slots 0/128, > Failed frames 0/0 = 0.0%, Average tries 0.00 > [ 990.056402] b43-phy3 debug: DMA-32 tx_ring_mcast: Used slots 0/128, > Failed frames 0/0 = 0.0%, Average tries 0.00 Hmm, that looks like no data reaches the TX rings. For comparision, can you post the output of a non-Asus 4318? What happens if you flash a non-Asus SPROM into the card? -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: New Device
On Thursday 17 April 2008 21:26:17 Larry Finger wrote: > Michael Buesch wrote: > > On Thursday 17 April 2008 19:47:57 Larry Finger wrote: > >> b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5, Revision 1) > > > > Heh, with an LP-PHY. That is not going to be supported anytime, soon, unless > > somebody else shows up and writes some specifications and code. > > > > I didn't figure it would. I'll have to put on my RE hat again, check > out the LP-PHY handler, and generate some specs. After I do that, I > hope that someone else will actually write code. > > Fortunately, I have a BCM4311/2 on the shelf that I can use in the > meantime. Once we have trial code, I can test it with my new device. note that this device also has one of the newer wireless cores, so there will also be some modifications needed for some non-PHY code. And of course the changed backplane bits. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: New Device
Michael Buesch wrote: > On Thursday 17 April 2008 19:47:57 Larry Finger wrote: >> b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5, Revision 1) > > Heh, with an LP-PHY. That is not going to be supported anytime, soon, unless > somebody else shows up and writes some specifications and code. > I didn't figure it would. I'll have to put on my RE hat again, check out the LP-PHY handler, and generate some specs. After I do that, I hope that someone else will actually write code. Fortunately, I have a BCM4311/2 on the shelf that I can use in the meantime. Once we have trial code, I can test it with my new device. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with PCI (not Cardbus) BCM43xx
Michael Buesch wrote: > On Thursday 17 April 2008 19:07:22 Larry Finger wrote: >> I'm glad it is not working. > > Haha. And people call _me_ inhuman. :D > Believe me, you have no corner on that market! You just happen to be the only one that has been called that on this list. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: New Device
On Thursday 17 April 2008 19:47:57 Larry Finger wrote: > b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5, Revision 1) Heh, with an LP-PHY. That is not going to be supported anytime, soon, unless somebody else shows up and writes some specifications and code. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
New Device
I wrote earlier about my laptop losing access to my wifi card. I sent it in for a warranty repair through Best Buy. Yesterday, I got a phone call from Best Buy stating that HP had authorized giving my a replacement machine! Somehow, replacing a machine because a backplane needed to be repaired doesn't make sense. I suspect someone dropped my computer off the bench, or some other kind of human error. In any case, I now have an HP dv2815nr, which increases the speed of my dual-core AMD processors from 1.6 to 2.0 GHz, my RAM goes from 1 to 3 GB, and my disk goes from 120 to 250 GB. Not too shabby for a total outlay of $124 on my part. That was the cost of a new 3-year service plan less the difference in cost of the two machines. I'm happy. Of course, there is a brand-new Broadcom wifi card in this computer, which is the subject of this E-mail. The details are as follows: lspci -v output: 04:00.0 Network controller: Broadcom Corporation BCM4310 USB Controller (rev 01) Subsystem: Hewlett-Packard Company Unknown device 137c Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at fc00 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [d0] Express Endpoint IRQ 0 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 1a-00-fe-ff-ff-73-64-ad Capabilities: [16c] Power Budgeting lspci -n output: 04:00.0 Class 0280: 14e4:4315 (rev 01) Relevant output from dmesg (some code modifications were needed): ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) ssb: SPROM revision 8 detected. ssb: Sonics Silicon Backplane found on PCI device :04:00.0 b43-phy0: Broadcom 4312 WLAN found b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5, Revision 1) AFAIK, this is the first rev 8 SPROM that has been found. What happened to revs 5-7??? As can be seen in the dump below, this is a 440-byte SPROM, just like rev 4; however, everything has been moved. I'm still trying to find out where stuff is - the MAC address starts at be16 offset 0x008C. 01287C133C107800BE6DC42B 0010 642A6429642CE73CFF467F47000C4078 0020 A000 0030 0040 0050 0060 1543008002100018 0070 0080 72531112010A06001A00FE73 0090 64AD53550100FF83030002FF 00A0 0F006C00FAFF 00B0 00C0 4A3E571A8AF991FE 00D0 00E0 00F0 0100 0110 0120 0130 0140 0800 0150 0160 0170 0180 0190 01A0 01B0 085C Do any of the RE's know anything about this rev of the SPROM? Is there any documentation available? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with PCI (not Cardbus) BCM43xx
Michael Buesch wrote: > On Thursday 17 April 2008 19:07:22 Larry Finger wrote: > >> I'm glad it is not working. >> > > Haha. And people call _me_ inhuman. :D > > No, _people_ did not call you inhuman. A non-human called you inhuman. E ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with PCI (not Cardbus) BCM43xx
On Thursday 17 April 2008 19:07:22 Larry Finger wrote: > I'm glad it is not working. Haha. And people call _me_ inhuman. :D -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with PCI (not Cardbus) BCM43xx
Michael Buesch wrote: > > Yeah well. I got the card and indeed it isn't able to transmit any data. > Of course I can't make any forecasts on whether I will be able to solve > this issue, but I will look into it. > Thanks a lot for _finally_ providing me one of these cards instead of > providing only hatemail (not you, but other people) :) > > The device doesn't produce any transmit status reports. I'm glad it is not working. I was afraid that you would get it, and by some quirk of nature everything would work there. I will be very interested in seeing what turns out to be the problem. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems with PCI (not Cardbus) BCM43xx
On Monday 14 April 2008 17:56:30 Larry Finger wrote: > > > Any ASUS WL-138G V2 R3.00 or R3.01 would fit the bill. The chip is a > > > BCM4318. If anyone has one in Europe and is willing to participate, > > > that would be great. If not, I could send the one that I have. It was > > > donated to me, and I would not need it to be replaced; however, > > > amazon.de has one for sale for 16 Euro, which is about what it would > > > cost for me to ship mine to you if you want it anytime soon. > > > > This one? > > > > http://www.amazon.de/ASUS-WL-138G-Funk-LAN-Adapter-Mbps/dp/B000H5UYCC/ref=sr_1_1?ie=UTF8&s=ce-de&qid=1208186185&sr=8-1 > > > > I'll immediately order it, if you're sure that's one that doesn't work. > > > > The picture looks exactly like mine. Yeah well. I got the card and indeed it isn't able to transmit any data. Of course I can't make any forecasts on whether I will be able to solve this issue, but I will look into it. Thanks a lot for _finally_ providing me one of these cards instead of providing only hatemail (not you, but other people) :) The device doesn't produce any transmit status reports. That's what I see from a first look. Here come some hardware details in case somebody is interested: [ 966.619496] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243) [ 966.619496] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243) [ 966.619496] ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243) [ 966.619496] ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243) [ 966.637500] ssb: SPROM revision 2 detected. [ 966.658366] ssb: Sonics Silicon Backplane found on PCI device :02:05.0 [ 966.674476] b43-phy3: Broadcom 4318 WLAN found [ 966.714105] b43-phy3 debug: Found PHY: Analog 3, Type 2, Revision 7 [ 966.714105] b43-phy3 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 [ 966.734069] phy3: Selected rate control algorithm 'pid' [ 966.736778] Broadcom 43xx driver loaded [ Features: PNR, Firmware-ID: FW13 ] [ 988.593922] input: b43-phy3 as /class/input/input8 [ 987.781568] b43-phy3: Loading firmware version 351.126 (2006-07-29 05:54:02) [ 987.781568] b43-phy3 warning: You are using an old firmware image. Support for old firmware will be removed in July 2008. [ 987.781568] b43-phy3 warning: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the latest firmware (version 4). [ 987.895936] b43-phy3 debug: Chip initialized [ 987.896206] b43-phy3 debug: 32-bit DMA initialized [ 988.967223] b43-phy3 debug: Wireless interface started [ 988.967247] b43-phy3 debug: Adding Interface type 2 [ 988.981264] phy3: HW CONFIG: freq=2412 [ 991.039238] b43-phy3 debug: Removing Interface type 2 [ 991.061533] b43-phy3 debug: Wireless interface stopped [ 990.024893] b43-phy3 debug: DMA-32 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00 [ 990.026360] b43-phy3 debug: DMA-32 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 [ 990.031396] b43-phy3 debug: DMA-32 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 [ 990.038040] b43-phy3 debug: DMA-32 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 [ 990.048005] b43-phy3 debug: DMA-32 tx_ring_AC_VO: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 [ 990.056402] b43-phy3 debug: DMA-32 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
