[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: MSI PC60G wireless adaptor problem



On Fri, Jul 13, 2007 at 15:37:36 -0700, I M wrote:

[...]

> Here is the output for dmesg | egrep 'eth|rt61' :
> 
> -------------------
> eth0: RealTek RTL8139 at 0xc800, 00:0e:2e:83:77:16, IRQ 201
> eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> eth1: link down
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> eth1: Promiscuous mode enabled.
> device eth1 entered promiscuous mode
> audit(1184365375.210:3): dev=eth1 prom=256 old_prom=0 auid=4294967295
> bridge-eth1: enabling the bridge
> bridge-eth1: up
> bridge-eth1: already up
> bridge-eth1: attached
> -------------------

That looks OK to me. I assume your eth0 interface works fine?

> And for /sbin/iwconfig :
> 
> -------------------
> lo        no wireless extensions.
> 
> eth1      no wireless extensions.
> 
> ra0       RT61 Wireless  ESSID:""
>           Mode:Auto  Frequency:2.412 GHz  Bit Rate=54 Mb/s
>           RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Link Quality=0/100  Signal level:-121 dBm  Noise level:-111 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> sit0      no wireless extensions.
> 
> vmnet8    no wireless extensions.
> 
> vmnet1    no wireless extensions.
> 
> -------------------

Here I don't like "Mode:Auto" and the link quality / signal level. The
interface does not associate with an access point. This is the first
thing that has to be fixed. (There is no use in trying to get a DHCP
lease if your are not associated with any access point.)

> And here is some other usefull info that i think youll help you guys in
> determining my problem:
> 
> "dmesg | grep ra0" :
> 
> -------------------
> ra0: no IPv6 routers present
> device ra0 entered promiscuous mode
> audit(1184365373.666:2): dev=ra0 prom=256 old_prom=0 auid=4294967295
> ra0 (WE) : Driver using old /proc/net/wireless support, please fix
> driver !
> -------------------

For the moment that is OK as /proc/net/wireless is still supported.

[ snip: dhclient cannot get a lease. ]

I think you should first try if you can change the settings of the card.
As root, run

iwconfig ra0 mode Managed

Then check the result with "iwconfig ra0". You should now see something
like

Mode:Managed  Frequency:2.4.. GHz  Access Point: XX:XX:XX:XX:XX:XX

The "XX:XX:XX:XX:XX:XX" should be the mac address of your access point.
If the interface associates with the wrong AP then you can change this
with:

iwconfig ra0 ap YY:YY:YY:YY:YY:YY

If you get "Access Point: not associated" then we have to check if the
card can see any access points at all. Run

iwlist ra0 scan

and post the output here. You can remove all real mac addresses from the
output if you want to. I only need to see the signal levels and if your
access point is using WEP or WPA encryption.

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |



Reply to: