Ralink wifi
First, the older rt2400, rt2500, rt2570 (USB), rt61, rt73 (USB) wifi drivers.
Puppy versions 2.12-2.16 already contain these drivers, but here are the most recent updates, from the opensource rt2x00 project. The project homepage is here
http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page
These are the "legacy" code drivers based on the proprietary source code from Ralink, and are considered "final" because the rt2x00 developers have since moved to a different mac80211 code base for more modern kernels.

Wifi on the Eee 701SD and MSI Wind U100 (some versions) is the Realtek RTL8187SE chipset.
This is a miniPCI wifi device, not to be confused with the RTL8187 USB chipset. There is a modified proprietary driver for this chipset which I now attach.
The source code is from here -
http://code.google.com/p/msi-wind-linux/
After installing this dotpet, reboot. The new driver is called r8180, and will now appear in the Network Wizard.
This dotpet package adds a configuration line to /etc/modprobe.conf to ensure that all associated encryption modules are loaded.

A word of caution: apparently the MSI Wind is sold with 3 different wifi adaptors; as well as the RTL8187SE there is also a version with Ralink wifi chipset, and one with AzureWave chipset.
http://forums.msiwind.net/post41605.html#p41605

Forum member growler reports that the Fn+F11 keys must be pressed to turn on the wifi device.

Hotkeys on the Eee will be supported by the attached version of the asus_acpi module with associated pciehp (PCI Express Hot Plug Controller)module.
The pciehp module is a standard kernel module, but it is not enabled in Puppy's standard kernel configuration.

Here is the eee kernel module to control the Eee's fan, FSB, and voltage, and read out the CPU temperature.
Once installed, refer to /root/my-documents/eeepc-README.txt for instructions.
Additional information from the module's author -
http://forum.eeeuser.com/viewtopic.php?id=9797

Note especially that this is an experimental driver, and if you disable your automatic fan control it's possible to DESTROY your Eee!
Fan speed instructions thanks to jakfish:
To enable manual control of the fan, do this

Code:

echo 1 > /proc/eee/fan_manual

Now you can control the speed of the fan using values between 0 and 100. So if you want to set your fan speed at 50% do this

Code:

echo 50 > /proc/eee/fan_speed

To turn off the fan do this

Code:

echo 0 > /proc/eee/fan_speed

Of course, this is dangerous. jakfish recommends that should disable the fan only if you have conky running with "modprobe thermal" so you can monitor your CPU temperature.

Here is the r6040 driver for the RDC Semiconductor R6040 fast ethernet controller, as found on Vortex86 System on Chip processors. Currently these are mainly used in the eBox and MicroClient mini computers. The source code is from -
http://www.dmp.com.tw/tech/Vortex86SX/

After installing this dotpet, reboot. The r6040 driver should automatically load, but if not, you can load it from the Network Wizard.

UPDATE
Puppy 2.12-2.16 has inbuilt support for the audio chipset in the eBox/MicroClient with the sis7019 driver.
But this is one of the older OSS family of audio drivers (notice there's no "snd-" prefix in the driver name) so I suspect it cannot be configured with alsaconf. If audio on your eBox/MicroClient isn't working, I think (?) the solution would be to add these two lines to the end of /etc/modprobe.conf

But apparently there is a more recent B version of the Zydas chipset which is not supported by this driver, at least in early kernels, anyway.
So Puppy versions 214R and 214X
contain the zd1211 and zd1211b "Vendor-based community drivers" instead.

The situation becomes more complex, though, since it seems there are some variants of the Zydas chipset ...
possibly the versions released after Atheros bought out Zydas and renamed the chipset "AR5007UG" ...
which won't work with the vendor driver.
So here is the (normal) opensource zd1211rw driver

Once installed, there will now be 2 drivers trying to claim the same device, it may be necessary to unload the one you don't want, before loading the one you do want, like this -

If you see no error messages, go ahead and unload/reload your rt73 driver -

Code:

rmmod rt73
modprobe rt73

Now check dmesg again.

If still no success, I may have packaged the rt73 driver with the firmware in the wrong location. Over time, Ralink has changed their Linux driver code, and the location of the firmware, so this can be confusing.
I have just packaged the rt73 firmware to install to the old location of /etc/Wireless/RT73STA/

So as I understand it, the problem was simply the firmware_class module not loaded ...
and it was unnecessary to relocate the firmware file itself.

So I have removed the rt73-firmware-test1.pet attachment.

It's bizarre that of the 50 people who have downloaded the updated rt73 driver dotpet, just one person reported a problem with the driver ...
but within 24 hours 6 others had downloaded the hotfix which was specifically provided for one particular situation, and was unconfirmed to even be helpful!
I call this "download fever". Maybe the thinking is that if you click on any and all technical fixes, relevant or not, that your hardware may somehow magically work better with Puppy Linux?

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