ndiswrapper-no can do?

Hi,
I have a wap11 connected to a slack10.1 linux box that can talk to an airnet
awd154 pci wireless adapter under windows. According to the supplier this adapter
uses a marvell mrv8000c chipset, not supported by linux as afar as I know.

Under linux lspci finds the device and claims that is has an 8335
chipset, so I downloaded that driver from the appropriate website.

Ndiswrapper loads either driver. So far so good. With the ndiswrapper
module loaded and either of the drivers loaded iwlist finds my wap11
(along with some other nearby radio sources).

The command iwconfig wlan0 gives an output that includes a bunch of
zeros for the MAC address, and a listing of 0 quality for the link-not
good.

The command dhcpcd wan0 -d gives an immediate output with a different
MAC address, not the correct MAC address for this adapter.

Needless to say I cannot ping the wap11. There is some chatter on the
net about the mrv8000c driver and linux but I haven't seen any
foolproof method for getting it, or this adapter to work. If you can
figure this out for me I would really be grateful.
Cheers, JWC

A. Disable ALL security until you get things working. Trying to debug
multiple levels at once is more than exponential in the number of levels,
and a recipie for frustration.

B) Make sure that your system is trying to connect to the correct access
point. Ie, use the essid to tell it only to connect to the required one. No
point in tearing out your hair as to why your system does not work, only to
discover your wireless device is connected to your neighbor's access point.

C) you do not tell us how you have set up ndiswrapper. The fact that
iwlist s
works suggests that the wireless driver is working.

d) Connect your system to the wireless access point using iwconfig
(ie set up essid etc)
make sure that you have an ifconfig entry for the wireless connection.

e)Now run dhcp on that particular link (eth1, wlan0,...)
See if you get an address.

Look at
route -n
to see if the routes are reasonably set up. Look at /etc/resolv.conf to see
if you have reasonable dns nameserver.



jwc <(E-Mail Removed)> writes:

>Hi,
> I have a wap11 connected to a slack10.1 linux box that can talk to an airnet
>awd154 pci wireless adapter under windows. According to the supplier this adapter
>uses a marvell mrv8000c chipset, not supported by linux as afar as I know.

> Under linux lspci finds the device and claims that is has an 8335
>chipset, so I downloaded that driver from the appropriate website.

> Ndiswrapper loads either driver. So far so good. With the ndiswrapper
>module loaded and either of the drivers loaded iwlist finds my wap11
>(along with some other nearby radio sources).

> The command iwconfig wlan0 gives an output that includes a bunch of
>zeros for the MAC address, and a listing of 0 quality for the link-not
>good.

> The command dhcpcd wan0 -d gives an immediate output with a different
>MAC address, not the correct MAC address for this adapter.

> Needless to say I cannot ping the wap11. There is some chatter on the
>net about the mrv8000c driver and linux but I haven't seen any
>foolproof method for getting it, or this adapter to work. If you can
>figure this out for me I would really be grateful.
>Cheers, JWC

On Sat, 05 Nov 2005 00:26:04 +0000, Unruh wrote:

> A. Disable ALL security until you get things working. Trying to debug
> multiple levels at once is more than exponential in the number of levels,
> and a recipie for frustration.
>
> B) Make sure that your system is trying to connect to the correct access
> point. Ie, use the essid to tell it only to connect to the required one. No
> point in tearing out your hair as to why your system does not work, only to
> discover your wireless device is connected to your neighbor's access point.
>
> C) you do not tell us how you have set up ndiswrapper. The fact that
> iwlist s
> works suggests that the wireless driver is working.
>
> d) Connect your system to the wireless access point using iwconfig
> (ie set up essid etc)
> make sure that you have an ifconfig entry for the wireless connection.
>
> e)Now run dhcp on that particular link (eth1, wlan0,...)
> See if you get an address.
>
> Look at
> route -n
> to see if the routes are reasonably set up. Look at /etc/resolv.conf to see
> if you have reasonable dns nameserver.

Much obliged. It was a simple configuration problem and your outline was
all that was necessary. i. e.,

iwconfig wlan0 essid "xxx"
gave me the correct MAC and iwconfig wlan0 showed that the link was good.

dhcpcd wlan0 -d (to get the message on the monitor)
gave me the MAC address and the local ip address.

Thanks again, JWC