Page 2 of 2

Posted: Wed 30 Jan 2013, 13:44
by boof
I can edit the makefile, if someone will guide me. screens attached. The makefile is old, for kernel 2.6.x. This is the latest driver I can find.

Posted: Fri 01 Feb 2013, 10:37
by tempestuous
boof,
In response to your PM to me, it's important to note at the outset that your wifi device; USB ID 148F:5370, is supported in all Slacko 5.3.x and 5.4.x versions by the rt2800usb driver. That's a built-in, ready-to-go, true Linux driver.

It's remarkable to me that in a forum thread that spans 28 days, and 21 lengthy posts, there's not a single mention of this.

The rt2800usb driver, unfortunately, has been widely reported as unreliable in earlier Puppy versions, but you should at least try it first, before resorting to the complicated "minefield" of installing third-party drivers ... or worse, of resorting to Windows drivers via ndiswrapper.
Unfortunately, your failed ndiswrapper configuration is possibly now blocking all other drivers from accessing the device, so you must first remove this configuration.
How? I don't know. Someone else needs to step in, or you should do some Googling, yourself.
Worst case, you will need to do a fresh installation.

Once your system is "clean" and free of ndiswrapper, just run the Internet Connection Wizard - and select the "Network Wizard" .... NOT the "Simple Network Wizard".
Don't overthink the configuration - let Puppy auto-detect your device and accept whatever driver Puppy loads (it will be the rt2800usb driver).
Then you need to configure your wifi settings ...

If the rt2800usb driver fails to detect any wifi access points, then it's probably failing, and then we can move on to compile the proprietary Ralink RT5370 driver ... but that's for later.

boof wrote:now I have to convince my Nokia C3-00 to connect the internet into it. I do find the lack of user control very frustrating, as so much requires special settings and knowledge I don't have. I don't know what the name of my local network is, as I don't think I've seen it yet.
This lack of understanding may be part of your problem. Spend some time to learn what a wifi identifier (SSID) is, what forms of encryption are available, and then investigate what your local network's wifi settings are.

Posted: Sat 02 Feb 2013, 23:17
by boof
SOLVED!

Thank you!

had to connect with highest encryption and key from underside of device.

Very, very grateful.