tempestuous,
as I am still having issues w/ the Belkin usb, (http://www.murga-linux.com/puppy/viewtopic.php?p=512144#512144) I noted that the present version of the rt3070sta-v2.5.0.1-k2.6.33.2.pet just upgraded from 2.4x since yesterday. I therefore downloaded the new version in the hope of resolving my dilemma. However I am now faced with the following error message when I attempted to upload the module: "Loading rt3070sta failed with the following message: WARNING: Deprecated config file /etc/modprobe.cof, all config files belong into /etc/modprobe.d/. FATAL: Error inserting rt3070sta (/lib/modules/2.6.33.2/kernel/drivers/net/wireless/rt3070sta.ko): Unknown symbol in module, or unknown paramater (see dmesg) Maybe try a different driver.

Yes, that's bad. I just checked at my end, and I get the same error. It appears that Ralink's latest code for this driver breaks compatibility with the 2.6.33.2 kernel in Puppy 5.1/5.2.
So I have just reverted to the previous driver - rt3370sta ver 2.4.0.1.

Ralink RT3070 wifi devices have historically had their own driver, and this driver shared code with the earlier RT2870 devices/driver. So there has been an overlap of driver support for RT3070 and RT2870 devices. This was confusing, but manageable.

But recently (at April 2011) RT3070 driver code has been merged into the newer rt3370sta driver,
and RT2870 driver code has been merged into the newer rt3572sta driver. So the RT3070 and RT2870 codebase has been separated, and this has created a problem for "middle-era" RT3070 devices, which are technically closer to the older RT2870 devices than they are to the latest RT3070/RT3370 devices.

The solution is to use an older version of the Ralink rt3070sta driver, which I now attach.
So for Ralink RT3070 USB wifi devices you should probably try the latest RT3070/RT3370 driver first, available earlier in this thread -
http://www.murga-linux.com/puppy/viewtopic.php?p=481085#481085
but if you experience problems, particularly in terms of being able to connect to an unencrypted network but failing to connect to a WPA-encrypted network, then try this older driver.

There are several "families" of Atheros USB wifi chipsets. The AR9170 chipset is already supported in Puppy 4.3 and 5.x. by the ar9170usb driver. A complete list of supported devices is here -
http://linuxwireless.org/en/users/Drivers/ar9170#available_devices
Someone on the Puppy forum has so far reported success with the D-link DWA-160 revA2.

I have also modified the ar5523 driver to support the D-Link WUA-2340 rev A1, USB ID 07d1:3a08.

After installing this dotpet, reboot.
When you run the Network Wizard you should see that the new driver has automatically loaded.

I downloaded and ran the pet. Re-booted and my USB D-Link WUA-2340 still not detected. Could it be my mobo won't recognize a USB NIC? Its from 1999..._________________
Linux is NOT Windows. Doesn't PRETEND to be, Doesn't WANT to be; Don't try to MAKE it be.

The Intel GMA500 Poulsbo graphics devices, as typically found in recent netbooks, have not been supported by an Xorg driver until the recent release of the pcb driver.

Here is the pcb Xorg driver which I have repackaged from Ubuntu debs.
I considered this driver significant enough to have its own forum thread, here -
http://www.murga-linux.com/puppy/viewtopic.php?t=67024
Further information, installation and configuration can be found there.

UPDATE April 24 2011:
The pcb Xorg driver has not been successfully set up in Puppy 5.1/5.2 as yet.
But a working solution for the Poulsbo graphics device is the fbdev/uvesafb drivers,
now available for Puppy 5.1/5.2 here -
http://www.murga-linux.com/puppy/viewtopic.php?t=67166Last edited by tempestuous on Sun 24 Apr 2011, 07:52; edited 1 time in total

There's a range of Creative Labs/E-MU sound cards supported by the snd-emu10k1 ALSA driver already in Puppy,
but several of these cards require firmware as well. I'm uncertain about all the models involved, but certainly the well-known E-MU 0404 PCI card requires this firmware.

Note: the E-MU 0404 USB is a completely different animal, which uses the generic snd-usb-audio ALSA driver.

The Prism2/2.5/3 wifi chipsets originally supported only WEP encryption, not WPA, but later firmware upgrades added WPA compatibility. To confuse the issue, the "hostap" Linux drivers for these wifi devices require a higher version of firmware to achieve WPA support than the Windows drivers do. Specifically, station firmware ver 1.7.0 or higher is required. Firmware version 1.8.2 is generally considered the best.

To check your firmware version, run this command

Code:

hostap_diag wlan0

If the reported station firmware version is lower than 1.7.0, you need to consider the firmware upgrade. Onboard (non-volatile) firmware upgrades are inherently risky, and I warn that there's a risk of completely killing your wifi device. If you're happy to accept this risk, here's how to proceed:
First install the upgraded hostap wifi drivers (for Puppy 5.1/5.2) attached to this post. These drivers have the firmware-write function enabled, which is not enabled in the standard driver versions already in Puppy.
Then install the prism-NV-firmware-1.8.2.pet. This is the Prism firmware ver 1.8.2, which I repackaged from here
http://www.red-bean.com/~proski/firmware/
Reboot.

Once rebooted, we first need to run this test command, looking for any incompatibility warnings -

Code:

prism2_srec -v wlan0 /root/prism-1.8.2/sf010802.hex

If the result of this command looks OK, you can commit to the firmware upgrade with the additional "-f" parameter, as such -

Code:

prism2_srec -v -f wlan0 /root/prism-1.8.2/sf010802.hex

Now run this command again -

Code:

hostap_diag wlan0

to check that the new firmware version (1.8.2) is actually reported.
If all looks good, reboot again, and you're ready to attempt a WPA wifi connection.

After installing this dotpet, reboot.
Then run the "Internet by dialup analog or wireless modem" section of the Internet Connection Wizard.

UPDATE Aug 31 2011:
I inadvertently packaged the qcserial driver instead of the qcaux driver!
The level of silliness in my error was matched only by the 76 people who downloaded this dotpet package and didn't report this!
Correct driver now packaged, and reattached.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum