For the ASUS Eee 700-series (but not 701SD) and 900, 900A, 900HA, 901GO, 904HA, 904HD, 1000HA, 1000HD:
Ethernet is supported out-of-the-box by the new atl2 module, and the webcam is supported by the new gspca module.

But the wifi chipset (Atheros AR5007EG) requires a non-standard variant of the MADWiFi (ath_pci) driver.
Quite a few other recent notebook computers now use this chipset, too. Obviously they, too, will be supported by this driver.
This dotpet package contains a suitably modified /etc/rc.d/MODULESCONFIG file so that the new ath_pci module will be used in preference to the ath5k module.
But this madwifi package should ONLY be used with the AR5007EG variant, all "standard" Atheros wifi devices will be supported by the ath_pci module (or ath5k module) already contained in Puppy 4.1.

UPDATE July 1 2009:
After 4000 downloads, I thought it was time to update to the latest driver revision - r4031.

Some people get "no wireless interface detected" in the Network Wizard after installing this package.
Forum member glassparrot reports that to get this driver installed and working you must first disable the Eee's wifi device in bios, then later re-enable the wifi device after the driver is installed -
http://www.murga-linux.com/puppy/viewtopic.php?p=208066#208066
I cannot see how or why this method would make any difference ... but if it works, great!

Ethernet for the ASUS Eee 901, 1000, 1000H, and 1000HE
is supported out-of-the-box by the new Atheros atl1e module.
Wifi is supported out-of-the-box by the new Ralink rt2860sta module.

Eee internal microphone (all models)
The mic in the Eee is problematic. With older versions of the ALSA audio driver it was necessary to load the snd-hda-intel driver with extra parameters. This was achieved by adding either of these lines to /etc/modprobe.conf

Hotkeys on all ASUS Eee models:
Hotkeys on the Eee should be supported by the attached version of the "asus_acpi" module with associated "pciehp" (PCI Express Hot Plug Controller)module.
I hacked the standard asus_acpi source code by comparing it with the version from the Asus website.
The pciehp module is a standard kernel module, but it is not enabled in Puppy's standard kernel configuration.

The Mute/Unmute function doesn't work because Puppy's version of the ALSA snd-hda-intel driver fails to respond to the "amixer set Master toggle" command. This could be fixed by creating a script which determines the volume state of the master channel, then use volume adjustments to respond accordingly, but I couldn't be bothered.

I didn't add the Fn+F1 suspend-to-ram function, because this is likely to crash Puppy.
If you want to experiment with Puppy-compatible suspend, there is a script here -
http://www.murga-linux.com/puppy/viewtopic.php?t=13410
but looking through that script I see that it's probably not compatible with Puppy4.x
Further experimentation is required.

If you haven't done so already, configure your wifi connection with the Network Wizard.
Reboot. Enjoy.

Toshiba laptop owners, you can adapt the instructions here for your situation.
Instead of loading the "asus_acpi" module, load "toshiba_acpi" instead.
And in /etc/acpi/wlan.sh change "wlan_control=/proc/acpi/asus/wlan" to "wlan_control=/proc/acpi/toshiba/wlan", and change the "ath_pci" module references to the name of the relevant wifi driver for your inbuilt wifi device.

UPDATE July 18 2009
acpid packages revised so that for wifi toggle ON, rc.network is run without the "restart" case.
jakfish reports that network re-connection is more reliable this way.

Finally on the subject of the ASUS Eee, here is the eee kernel module to control the 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.

There is a very recent wifi chipset from Realtek called RTL8187SE, which is found in the MSI Wind U100 mini-notebook computer and ASUS Eee 701SD. This is a miniPCI wifi device, not to be confused with the RTL8187 USB chipset.
There is a proprietary driver for this chipset (at beta stage) which I now attach.
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.
If you find that a wifi connection is unsuccessful, it might just be that the final stage of configuration, DHCP, has failed. A possible workaround is to take the interface down and bring it back up again, like this

Code:

ifconfig wlan0 down
ifconfig wlan0 up

now try to obtain an IP address again with dhcpcd -

Code:

dhcpcd wlan0

UPDATE Nov 2 2008
The Sep 4 version of the proprietary rtl8187se driver from Realtek was found to fail under Puppy 4.1, but this same source code has recently been bugfixed and improved by forum member coffelius on the MsiWind forum. The updated source code is from here -
http://code.google.com/p/msi-wind-linux/
growler has tested this updated driver in Puppy 4.1 and it appears to be working well. Driver now attached.

Ethernet on the MSI Wind is supported out-of-the-box by the new r8101 module.

Nice info in this thread. Thank you.
Maybe the thread should be made sticky to have the full attention._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

Installed Puppy 4.1 on my two ASUS Eee 4G's along with the Madwifi and function key patches described above. Works fine with my WPA2 TKIP wireless, but on reboot the wifi does not reconnect. Is there another tweak I missed?

The wifi connect on boot works consistently in Pupeee b4 which I have been using for several months.

A second separate but smaller problem is that shutdown does not always complete. I do a "hard" power off to shut down when it occurs.

Puppy 4.1 works great on my HP and Acer laptop dual boot with Vista from USB flash drive, and boots and auto connects wifi in under 30 seconds.

Puppy 4.00 worked fine (from a USB stick) but when I upgraded to 4.1 (not the retro) the wireless interface is recognized but the wireless scanner did not not find and networks (there are and the Laptop's wireless is switched on).

The both the scanner in the new Network Wizard and Pwireless fail to find any networks (including my router).

Tried all the usual things from a command line (ifup/down dhcpcd etc) but no joy. So I have plugged in a Ethernet wire to send this.

Installed the Network Wizard from Puppy 4.00 in 4.1 but still no joy scanning wireless networks.

The correct module is used as far as I can tell (at5k_pci. Windows reports the card as Atheros AR5005G using driver ar5211.sys).

Tried to go down the Ndiswapper route but there is a problem with the wizard. When it goes to the open file dialogue box it comes up with an error about could not find a directory(several times). Just tried to repeat this and the error has gone (think is was PUPPYLASTLOCATON?).

So just got Ndiswrapper working (still with the 4.00 wizard). Will break there and go back to 4.1 wizard and try all over again.

Mike

BTW many thanks for all your effort. Puppy is great and the speed of booting 4.1 is brilliant.

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