DWA-125 and Puppy 5.2.5 on a Dell C400
DWA-125 and Puppy 5.2.5 on a Dell C400
I have Puppy 5.2.5 installed on a Dell C400. I'm trying to use a DWA-125 to connect.
Network Wizard recognizes wlan0 and assigns rt2800usb Ralink 11n Adapter, but the light on the adapter never shows up.
Also, once I proceed further into Network wizard and attempt to test wlan0 I get
"Error!
Failed to raise interface wlan0.
Failed command was: ifconfig wlan0 up
Error returned was:
ifconfig" SIOCSIFFLAGS: No such file or directory"
The same error shows when I try to scan for networks (no brainer, but I had to try.)
Please instruct.
Network Wizard recognizes wlan0 and assigns rt2800usb Ralink 11n Adapter, but the light on the adapter never shows up.
Also, once I proceed further into Network wizard and attempt to test wlan0 I get
"Error!
Failed to raise interface wlan0.
Failed command was: ifconfig wlan0 up
Error returned was:
ifconfig" SIOCSIFFLAGS: No such file or directory"
The same error shows when I try to scan for networks (no brainer, but I had to try.)
Please instruct.
You are talking about a wireless connection?
If so, make sure you are doing it per this guide:
http://www.murga-linux.com/puppy/viewtopic.php?t=65346
If so, make sure you are doing it per this guide:
http://www.murga-linux.com/puppy/viewtopic.php?t=65346
You could try the ndiswrapper method to load a Windows driver for the DWA-125.
When you get to this window.
Select Load Module
Follow directions for ndiswrapper..
When you get to this window.
Select Load Module
Follow directions for ndiswrapper..
- Attachments
-
- step-3.png
- (32.34 KiB) Downloaded 2163 times
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
N00bx1000,N00bx1000 wrote:I have Puppy 5.2.5 installed on a Dell C400. I'm trying to use a DWA-125 to connect.
Network Wizard recognizes wlan0 and assigns rt2800usb
The rt2800usb is a very new driver, and may require some troubleshooting. Please run this command -
Code: Select all
dmesg
It would also be useful if you could run this command -
Code: Select all
cat /proc/bus/usb/devices
Yeah, his name has come up in almost every other forum post about my previous networking questions.
cat /proc/bus/usb/devices returned this:
Vendor=07d1
ProdID=3c0d
Rev=1.01
dmesg didn't seem to return anything referencing wlan0. This may be my oversight, but I really checked it several times.
I hope this helps you help me.
EDIT: I found the rt2800usb referenced.
"registered led device: rt2800usb-phy0: :radio
Registered led device : rt2800usb-phy0: :assoc
Registered led device: rt2800usb-phy0: :quality
usbcore: registered new interface driver rt2800usb"
cat /proc/bus/usb/devices returned this:
Vendor=07d1
ProdID=3c0d
Rev=1.01
dmesg didn't seem to return anything referencing wlan0. This may be my oversight, but I really checked it several times.
I hope this helps you help me.
EDIT: I found the rt2800usb referenced.
"registered led device: rt2800usb-phy0: :radio
Registered led device : rt2800usb-phy0: :assoc
Registered led device: rt2800usb-phy0: :quality
usbcore: registered new interface driver rt2800usb"
A new device may need one of these drivers:N00bx1000 wrote:Yeah, his name has come up in almost every other forum post about my previous networking questions.
cat /proc/bus/usb/devices returned this:
Vendor=07d1
ProdID=3c0d
Rev=1.01
dmesg didn't seem to return anything referencing wlan0. This may be my oversight, but I really checked it several times.
I hope this helps you help me.
EDIT: I found the rt2800usb referenced.
"registered led device: rt2800usb-phy0: :radio
Registered led device : rt2800usb-phy0: :assoc
Registered led device: rt2800usb-phy0: :quality
usbcore: registered new interface driver rt2800usb"
http://www.murga-linux.com/puppy/viewto ... 450#346450
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Well your dmesg results look fine, but the Network Wizard reports that the interface cannot be raised. So it appears that the rt2800usb driver is failing.
You can use one of the proprietary Ralink wifi drivers instead, and thanks to your USB device ID I can say that the rt3370sta driver is definitely compatible. It's available for Puppy 5.1/5.2 here -
http://www.murga-linux.com/puppy/viewto ... 085#481085
After installing the dotpet, reboot. Puppy should automatically load the new driver next time you plug in your device.
You can use one of the proprietary Ralink wifi drivers instead, and thanks to your USB device ID I can say that the rt3370sta driver is definitely compatible. It's available for Puppy 5.1/5.2 here -
http://www.murga-linux.com/puppy/viewto ... 085#481085
After installing the dotpet, reboot. Puppy should automatically load the new driver next time you plug in your device.
I'll try it tonight. Thanks for making the time to help.Well your dmesg results look fine, but the Network Wizard reports that the interface cannot be raised. So it appears that the rt2800usb driver is failing.
You can use one of the proprietary Ralink wifi drivers instead, and thanks to your USB device ID I can say that the rt3370sta driver is definitely compatible. It's available for Puppy 5.1/5.2 here -
http://www.murga-linux.com/puppy/viewto ... 085#481085
After installing the dotpet, reboot. Puppy should automatically load the new driver next time you plug in your device.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
It sounds like the rt3370sta driver is not playing well with your device. I have seen this type of problem before, and I suspect you need the older rt3070sta driver, available later in the same thread as before -
http://www.murga-linux.com/puppy/viewto ... 360#513360
Test with no encryption first just to see if the driver is basically working, then try different forms of encryption one at a time. You may find, for example, that WPA2 encryption works, while WPA encryption fails.
http://www.murga-linux.com/puppy/viewto ... 360#513360
Test with no encryption first just to see if the driver is basically working, then try different forms of encryption one at a time. You may find, for example, that WPA2 encryption works, while WPA encryption fails.