Puppy Linux Discussion Forum

[plankenstein]

I bought a netgear WN111 v2 wireless adapter, should have checked for usability first,but it was cheap (ish). Have tried it in 2 desktops and my laptop with 431 and dpup as well as 214x with ndiswrapper. All give the same result which tells me I'm obviously doing something wrong. The connection wizard shows the adapter as being there. But, when I scan for a connection it either comes back saying it can't find a network or else it locks up. As a side note, when ever it locks up, the computer won't shut down. I think this may be due to some module not unloading, saw a post about something similar recently. Another poster with the same kind of problem on a different adapter got theirs working by running auto dhcp before scanning for a network, but that didn't work for me. I'm still pretty much an uber noob so please try to be gentle with my tired old brain.

Thanks in Advance

[rjbrewer]

According to linux wireless lan, that device uses an Atheros
chipset.

It's possible there is no native driver for Atheros usb.

http://www.murga-linux.com/puppy/viewtopic.php?p=339200&search_id=572508174#339200

That was the case 6 months ago.

[smokey01]

[plankenstein]

@ Smokey, Thanks, your's is the post I was reffering to, just couldn't remember who had posted it. If I can ever get it to connect I'll try your fix for the lock up. But first I have to get it connected. ( grrrr) Might give stardust a try, who knows there might be something in there that likes that driver more. Do you do anything special when setting up this adapter? Or do you just run through Pwireless2 like normal? How about the save file, should I create one before I try to connect or do it on the first run?

@ rjbrewer, Thanks, but the kernel used in 431 and dpup has this module built in and as you can see Smokey is using it, so I know it can work. It's just a matter of if I can figure it out.

Thanks for the help so far, and I'm still open to any other suggestions out there.

[rjbrewer]

Thanks for the info. Smokey.

Plankenstein;

I have atheros pci and pcmcia cards that give me problems with
wpa on puppy 4.3.1. with the latest (26.30.5) kernel.
If it shows Ath5k in connect wizard that is the same kernel.

I use puppy4.1.2 with these cards; shows ath_pci in wizard.
Don't know if that will help with your usb dongle.

[tempestuous]

[plankenstein]

Sorry for not updating in a while. Life caught up with me and went nuts. Stardust did the same thing as 431 and Dpup, so that led me nowhere. Tempestuous's post reminded me that I had seen a thread by him about configuring wifi from the command line. So, decided to give that a try. Seemed to get a little farther this time, but still no go. To be honest, I can't even remember exactly what I did get. It's been a couple of weeks since then and I only managed to sneak in a few minutes on it at the time. When I can get things calmed back down in my little corner of the world, I'll try the command line again and see where it takes me. Thanks for the help and in the words of Arnold "I'll be Bach".

[smokey01]

Try puppy 432. It worked out of the box here.

The latest Stardust also works so 4.4 probably will too.

Smokey

[plankenstein]

Okay, managed to get a little time in on this and here's what I have so far. "lsmod" shows the ar9170usb module is loaded. "ifconfig -a" and "iwconfig" show wlan0, so far so good. I have my router running an open connection, so no need to set up encrytion. Entered the following from the command line:

[tempestuous]

[plankenstein]

Oops, my bad. I was a little foggy about the id there. Didn't know if I was declaring what ID to connect to or declaring an ID for my machine. Doesn't really matter a lot though. it still doesn't work even with NETGEAR as essid. Shouldn't I be able to see some lights flashing to indicate that the adapter is working? (like I do with iwlist.)

[tempestuous]

I think some diagnosis is in order.
Boot afresh. Don't run any wifi connection commands yet.
Plug in the wifi dongle and run this command -

[plankenstein]

Okay, on a fresh boot. I connected dongle and ran dmesg. The output didn't show anythig that looked like an error to me, so here it is from where I plugged in the adapter.

[tempestuous]

Well the driver looks perfectly healthy. It found the necessary firmware files (in /lib/firmware),
loaded, and created an interface without any errors.

I'm wondering if the problem is just with dhcpcd?

When running the dhcpcd command, you could use the alternative syntax as I explained in the wifi HOWTO:

[plankenstein]

Well, I'm embarrassed! The answer was right in front of me the whole time. The alternate dhcpcd statement did the trick. Here's what I used: