WiFi RT73 not working in 301

[Béèm]

After the boot I see that I have a rausb0 device but with the RT2570 loaded.
With the networkwizard I try to scan for my router, but the system starts to crawl and goes on forever.

With RutilT scan doesn't find my router, but at least the scan isn't looping.

I succeeded to unload the RT2570 driver and attempted to load the RT73 by hand. No WiFi device was found.

If I load the RT2570 again, I get again the rausb0 device, but my router still isn't found.

How can I correct?

[kyroc]

Hey Beem,

I had the same problem with my Belkin usb wireless adapter..

This is what I did to fix the problem:

1. Start the computer with the wireless adapter UNPLUGGED.
2. Open the terminal
3. Plug in the adapter
4. type (without quotes) "modprobe rt73"
5. Open up the window where it lists your adapter as rt2570, it should be listed as rt73 now! Click the button for your adapter
6. Set up the wireless configuration, then click auto DHCP
7. Now it should work!

If this doesn't work, please tell me!
Kyroc

[Béèm]

Hi Kyroc,
There is a a big problem to do so.
The RT73 altho being a USB device, it's built inside the PC.
So unplugging wouldn't be very easy to do, if possible.

But I think of something else.
Modprobe is the command to load a module.
Isn't there an equivalent command to unload?
Maybe I can unload the RT2570 and load the RT73 afterward.

[kyroc]

you probably could.. lol

Basically just make sure that puppy linux doesn't "know that the adapter is there" until you "modprobe rt73"

Kyroc

[HairyWill]

do this before trying to configure networking

Code: Select all

rmmod rt2570
modprobe rt73

if it works then add these two lines to the BEGINNING of /etc/rc.d/rc.network

[Béèm]

Thanks HairyWill
It was the rmmod command I was looking for.

[Béèm]

I tried this rmmod, modprob, but still it didn't work.
When using iwconfig I saw the SSID was ""
With the networkwizard up to the point that an IP had to be given by dhcp all was ok, but I didn't get an ip.

Alltho on my laptop I have no problem with the SSID in which there are accentuated characters, I changed the SSID in the access point with a name without accentuated characters.

I had to do several trials with the network wizard before I got an ip and the connection worked.
Maybe I was too impatient and did the trials too quickly one after the other.

Any case it seems to work and I'll see next boot.
BTW just before retrying with Puppy I tried the latest openSuse 10.3 LiveCD and I didn't get a connection either.
Could be caused by the accentuated characters in the SSID also, will try next time.

[Béèm]

Update of the issue.
I did put the statements in rc.network.
But on next boot, all tho the RT73 is loaded and the previously configuration saved successfully, I get no connection.
I have to do in the network wizard:
- delete the stored configuration profile
- rescan for the access point
- reconfigure it (WEP)
- save it and use it.
- test the connection (was ok now)
- demand an IP again with dhcp
- was successful and stored the configuration
I was then up and running on the internet.

Drawback, I have to do this procedure every time I reboot.
But ala, I can go on the net.

[Béèm]

Update of the issue.
I did put the statements in rc.network.
But on next boot, all tho the RT73 is loaded and the previously configuration saved successfully, I get no connection.
I have to do in the network wizard:
- delete the stored configuration profile
- rescan for the access point
- reconfigure it (WEP)
- save it and use it.
- test the connection (was ok now)
- demand an IP again with dhcp
- was successful and stored the configuration
I was then up and running on the internet.

Drawback, I have to do this procedure every time I reboot.
But ala, I can go on the net.

Confirmed when I rebooted the PC this morning.

[HairyWill]

Beem, I can give you hacky suggestions that might make it work but haven't been through rc.network enough to suggest why there is a problem or how it should be solved generally.
assuming the adapter is labeled wlan0, replacing the question marks try this in rc.local

Code: Select all

rm -f /etc/dhcpc/dhcpcd-wlan0*
ifconfig wlan0 down
sleep 1
ifconfig wlan0 up
iwconfig wlan0 essid ??????
iwconfig wlan0 mode managed
iwconfig wlan0 key ?????????
ifconfig wlan0 up #for good measure no idea if it helps
dhcpcd -d wlan0

this may work, if it didn't I would put sleep 1 in between every line.

Haven't we been here before?

[jonyo]

http://www.murga-linux.com/puppy/viewto ... 941#152639

Just got the above USB wireless network adaptor (less than £10 incl postage from ebay) working with puppy 3.01.
The 'Connect' wizard allocated driver rt2570 to this adaptor but has no WPA support.
I blacklisted this driver and loaded rt73 and all works perfectly with native WPA supported.

http://www.murga-linux.com/puppy/viewto ... 941#151380
http://www.murga-linux.com/puppy/viewto ... 57&t=15305
http://www.murga-linux.com/puppy/viewto ... 76&t=18535
http://www.murga-linux.com/puppy/search.php > rt73 > found 81 matches
~ http://www.murga-linux.com/puppy/viewto ... 76&t=14252

[davids45]

G'day Béèm,
More 'fun' with our 8818s???
I just received my 3.01 CD and 'full' installed it on my 8818. All very nice, except..............
the 3.01 Wifi wizard chooses the RT2750 usb driver for my in-board wireless network connection, when I think it needs the RT2500 pci driver. I have a WPA set-up so the message about this driver being only good for WEP was not what I was happy to see.
Irritating because I have no problem with Puppies 2.17 and 2.16 who found the right driver and are happy to run under WPA on the 8818.
I was going to ask the forum today how to delete/remove this incorrect driver choice made by the wizard so I can use the one I think I need. The other inputs to this thread should help me there (in fact, I now remember doing something like this before with Ubuntu and ndiswrapper on an old HP).
But you say you want to install the RT73 driver for your 8818? Are you sure it's the driver for the 8818's wifi? Maybe the European 8818s were different to the Australian 8818s? I'll check my set-up with Everest when I'm home tonight, just to be certain.
I had found ndiswrapper worked well for the Medion desktops when there were no Linux drivers for the RT-type cards, so that was to be my Plan B with 3.01.

David S.,
Chatswood, NSW.

[davids45]

G'day again, from home, on the 8818, using 3.01 (eth0),
Just to get my story straight from this afternoon,....
The RT2500 driver I was thinking of was the Medion/XP driver running under ndiswrapper. I use this with 2.15 and 2.16 Puppies with WPA.
Puppy 2.17 was the first to run immediately on my 8818, with WPA, using its Linux driver which is RT2570 usb BETA2 dated 2006/6/18 (if I read the networking file correctly).
Puppy 3.01's RT2570 usb driver is tagged 'CVS2007090808' and doesn't work with WPA, so I'm not happy, and doesn't work on your 8818 either although you have WEP and should be OK.
If you have no joy with the RT73, you could try the older RT2570 usb in 2.17, or run with ndiswrapper+XP/Medion ... if you can blacklist the default driver in 3.01.
If I have some time, I'll see if I can do something to get 3.01 running wirelessly with WPA on my 8818, and let you know.

David S.

[Béèm]

I am trying with the RT73 driver as this is the device which is found.
Being in Windows for now, I can only show what Windows found as device.
Maybe be there are manufacturing differences in different parts of the world.

I'll look again in the other drivers then.