________________________________
> 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.
>


 Hello again,

                   Well, things have moved along a bit here -- nothing works, 
but it all looks like it wants to...

Upgraded to 2.6.24, now using b43 driver + debug on

  Perhaps I'm doing something wrong....anyhow, the background realm consists of 
my son's XP box, running one of the same cards with the asus proprietary 
drivers + config frontend, and is setup in so called 'softAP' mode instead of 
'station' mode, I'm telling it channel 1...and no additional encryption (which 
I hope infers WEP only encryption), it's network IP is set on 192.168.1.0/24 
space, and as far as the blowz' box is concerned, everything it's end is 
hunky-dory. Except it can't seemingly see this machine at all...

....on this linux end (and being all new to this), I'm not sure if what I'm 
seeing is actually correct. For instance ;

[EMAIL PROTECTED]:# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:"dfg"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:1B:FC:61:19:58   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B   
          Encryption key:1122-3344-55
          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

...the AP Mac is that of the XP box -- I didn't expect to see 'Link Quality:0  
Signal level:0  Noise level:0'...

Looking at the same situation from another point of view....;

[EMAIL PROTECTED]:# iwlist wlan0 scanning
wlan0     Scan completed :
          Cell 01 - Address: 00:1B:FC:61:19:58
                    ESSID:"dfg"
                    Mode:Master
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=73/100  Signal level=-15 dBm  Noise level=-52 dBm
                    Encryption key:on
                    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=00000004c4c6c18b

....and I'll convince myself that sortta looks correct...but shouldn't the 
link/signal/noise stats have appeared in the output of iwconfig? Why are they 
not? 

What is the purpose of the wmaster0 interface, and when does it get used? 
Issuing 'ifconfig' returns ;

wlan0     Link encap:Ethernet  HWaddr 00:1B:FC:61:15:E1  
          inet addr:192.168.1.123  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wmaster0  Link encap:UNSPEC  HWaddr 
00-1B-FC-61-15-E1-0A-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

...and I've no idea if that's correct, whether wmaster0 has to be ifconfigured 
or not, or indeed whether wlan0 has to be bridged or not, because I'm having 
trouble finding any good, new, recent documentation about some of this stuff...

All the zeros are correct - as far as XP and this box are concerned, there is 
no route to either host

...I'm seeing a lot of this in dmesg....

b43-phy0 debug: RX: Packet dropped
b43-phy0 debug: RX: Packet dropped
b43-phy0 debug: RX: Packet dropped
b43-phy0 debug: RX: Packet dropped
b43-phy0 debug: RX: Packet dropped
b43-phy0 debug: RX: Packet dropped
b43-phy0 debug: RX: Packet dropped

....and 2.6.24 breaks lircd-0.8.2 so my IR remote control is lame (^;

....am I doing something wrong here, or am I seeing 'the problem'?

                        Regards,
                                       Donald
_________________________________________________________________
New music from the Rogue Traders - listen now!
http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&referral=hotmailtaglineOct07&URL=http://music.ninemsn.com.au/roguetraders
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to