Greets,
________________________________ > Date: Wed, 19 Mar 2008 15:18:02 +0100 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: More on ASUS WL-138G V2 > CC: [email protected]; [EMAIL PROTECTED] > > 2.6.18 doesn't support 4318. Try 2.6.22 or 2.6.23 if you want proper > functionality. However, it would be good if you tried 2.6.24, 2.6.25 or > wireless-dev>(with new firmware, of course), as we are having extreme > problems with it, and you (from AU, which is outside of the US - what > channels can you use in>AU?) can help debug it. > ....okidoki, that more than less concurs with what I discovered last night. I've got 2.6.24 here ~ were there any changes (to b43 & co) in 2.6.25? . ......wireless-dev...[if this is] .compat-wireless-2.6] actually failed to compile on this {my} machine -- in .compat-wireless-2.6/net/ieee80211/ieee80211_module.c ....it bails due to no definition for 'init_net' -- I shouldn't need this anyhow if I'm running a late model penguin of 2.6.24 or greater, true? That will be my path...I'll look into what's going on here later on (..famous last words..) ...regarding channel restrictions here (if any), I can personally state that I don't know. -If- I were to take the example given to me by my son's XP box in the next room....same card + shipped wiin drivers and config GUI frontend...then I would report channels 1->13 inclusive. Regardless of more complete functionality or not, I've eventually shoved one of the cards in this machine running 2.6.22, and using the bcm43xx driver set it all -appears- to be as expected. In this case, debug pumped to dmesg reported more or less the same thing....the whole snippet reads ; bcm43xx: Radio turned off bcm43xx: DMA-32 0x0200 (RX) max used slots: 1/64 bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 bcm43xx: DMA-32 0x0220 (TX) max used slots: 2/512 bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 SoftMAC: Associate: Scanning for networks first. SoftMAC: Associate: failed to initiate scan. Is device up? bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0 bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: Radio turned on bcm43xx: Radio enabled by hardware bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1489:bcm43xx_find_lopair() bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1489:bcm43xx_find_lopair() bcm43xx: Chip initialized bcm43xx: 32-bit DMA initialized bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1489:bcm43xx_find_lopair() ADDRCONF(NETDEV_UP): eth1: link is not ready SoftMAC: Associate: Scanning for networks first. SoftMAC: Scanning finished: scanned 13 channels starting with channel 1 SoftMAC: Associate: Scanning for networks first. SoftMAC: Unable to find matching network after scan! ...Don't know if that's sane or typical -- the last line is the correct result though, there is no network setup yet. This may be blabla et_al ; the aim is to use b43 instead -- but for the sake of completeness this is what it looks like here under 2.6.22. I'll build & install (at least..) 2.4.24 here later and see what b43 thinks of it now...at least I know that hardware talks, firmware loading works, iwconfig works..etc.etc ...happy to help my end trying to debug things. Do you want a card to play with?... Regarding using one of these cards in AP mode, I've read a few threads describing patches needing to be included in various places - is this still the case? > On Wed, Mar 19, 2008 at 10:25 AM, Michael Buesch <[EMAIL PROTECTED]> wrote: > On Wednesday 19 March 2008 05:37:18 kala mazoo wrote: >> The kernel shipped with the deb3 release [linux-2.6.18-4-686] will use the >> (now deprecated) bcm43xx driver module, and it gives every impression via >> dmesg that things are going to work (once I get the firmware loading sorted >> and configure the stack itself)...; >> >> bcm43xx: Chip ID 0x4318, rev 0x2 >> bcm43xx: Number of cores: 4 >> bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled >> bcm43xx: Core 1: ID 0x812, rev b43-phy0: Broadcom 4318 WLAN found > > Ehm, what da hell is that? Are you probing b43 and bcm43xx at the same time? > Disable bcm43xx, please. > >> bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled >> bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled >> bcm43xx: PHY connected > Ummm...what that is, is an example of seamonkey's inability to recognize and correct the mistake made when a careless human being accidentally picks the wrong insertion point on a pending paste operation and goes click! Damn, i though I'd editted out all the splatter, apparently not, sorry about that. Hopefully, they'll fix seamonkey anyday soon now and get rid of this problem.... Regards, Donald _________________________________________________________________ Overpaid or Underpaid? Check our comprehensive Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fcontent%2Emycareer%2Ecom%2Eau%2Fsalary%2Dcentre%3Fs%5Fcid%3D595810&_t=766724125&_r=Hotmail_Email_Tagline_MyCareer_Oct07&_m=EXT _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
