The "B" version of the Realtek RTL8187 USB wifi chipset should now be supported by the rtl8187 driver.

But as always, total hardware support is a "moving goalpost".
Here are some additional third-party drivers and utilities.

Important update December 2009:
For any driver in this thread which conflicts with an existing driver in Puppy, you must install the modules-preference fix contributed by forum member rerwin here -
http://www.murga-linux.com/puppy/viewtopic.php?p=371659#371659
If not, the new driver will (likely) fail to override the older driver.Last edited by tempestuous on Sat 19 Dec 2009, 04:45; edited 1 time in total

Here are the "staging" (beta quality) wifi drivers from the official 2.6.30.5 kernel source.
These drivers were not enabled in the official release of Puppy 4.3.

- the rtl8187se driver is for the Realtek RTL8187SE wifi device, as found in the ASUS Eee 701SD and MSI Wind U100 netbooks. This is a miniPCI wifi device, not to be confused with the RTL8187 USB chipset.
The dotpet includes a PREFLIST entry so that this driver will be used in preference to the "Coffelius" modified proprietary driver.

- the agnx driver is for Airgo AGNX00 wifi devices.

- the prism2_usb driver is for USB versions of the Prism2/2.5/3 chipset. It supports WEP encryption, but not WPA/WPA2 encryption.
PCI/Cardbus versions of this wifi chipset are supported by the "hostap" drivers, which are standard in Puppy, and these do support WPA encryption.
It's worth noting that the prism2_usb driver uses an unconventional configuration process, completely incompatible with all other Linux wifi drivers. Thanks to Dougal's development efforts, this process is seamlessly incorporated within Puppy's Network Wizard.

After installing any of these dotpets, reboot. Puppy should automatically load the new driver at boot up, but if not, you can load it from the Network Wizard.

The source code is from
http://www.ralinktech.com/support.php?s=2
Note that there is an overlap of Ralink devices supported by some of these drivers.
So it's very important to install the "modules-preference" fix mentioned in the first post.

All of these dotpets include updated configuration files so that Puppy's Network Wizard will recognise the new drivers.

ASUS Eee ACPI support (hotkeys)
As before, the ACPI Daemon utility, acpid, is used to detect hotkey events to trigger various commands and scripts.
acpid relies on a suitable kernel module to expose the keypresses. With the 2.6.30 kernel this module is "eeepc-laptop" which Puppy 4.3 contains as standard.
But this module still can't expose control of fan speed (yet). So included in this collection of utilities is the third-party "eee" kernel module for this purpose. I obtained the source code from
http://code.google.com/p/eeepc-linux/

Don't be tempted to install "eeepc-acpi-utilities" from
http://sourceforge.net/projects/eeepc-acpi-util/
This is a more complex implementation of Eee ACPI functions specifically for Ubuntu, which require additional (large) libraries. It's generally incompatible with Puppy.

First ensure you have wifi working on your Eee.
Now install the following 3 dotpets in this order:
- eee-0.2-k2.6.30.5.pet
- xbacklight-1.1.pet
- acpid-1.0.10-Eee.pet

The acpid dotpet will detect your particular wifi device and save these settings as
/etc/acpi/wifi-driver and /etc/acpi/wifi-interface.
The acpid dotpet will also modify /etc/rc.d/rc.local so that the "eee" module is loaded at each bootup, and it will modify /usr/sbin/delayedrun so that the ACPI daemon is run at each bootup.

This dotpet will also modify /etc/rc.d/rc.local
so that the fan control daemon (originally written by Dougal) is run at each bootup.
Once all dotpets are installed, hotkeys should work straight away, but it would be a good idea to reboot.

Atom-and-Celeron.png

Description

Filesize

34.7 KB

Viewed

32359 Time(s)

Last edited by tempestuous on Mon 12 Oct 2009, 02:43; edited 2 times in total

Broadcom wifi devices.
Puppy 4.3 contains the b43 and b43legacy opensource wifi drivers. But some Broadcom wifi devices, especially those found in Dell and HP notebooks, are notorious for failing to work with these drivers.
For these troublesome devices the proprietary Broadcom hybrid driver will likely work better. The source code is from here
http://www.broadcom.com/support/802.11/linux_sta.php
Dotpet now attached. The new driver is called wl
Of course, you should always try the b43/b43legacy drivers first ... and report any errors relating to these drivers you may see when you run the "dmesg" command.

Now reboot. At each bootup this will unload the standard b43/ssb drivers and load the wl driver, but it means that you will need to run the Network Wizard at every bootup to reconfigure the wifi connection. Not very convenient.

Of more serious concern, your computer may contain other hardware which relies on the ssb driver, such as PCI/USB/Cardbus interfaces, and these will be disabled!

In such cases you will need the more comprehensive solution, which is to use a re-mastered version of Puppy 4.3.1 which includes the ssb driver specially modified to remove compatibility with Broadcom wifi devices. Get it here -
"Special Puppy431 for broadcom 4312 (and other?) wifi cards"
http://www.murga-linux.com/puppy/viewtopic.php?t=50570Last edited by tempestuous on Wed 30 Dec 2009, 04:34; edited 3 times in total

Atheros AR5007EG wifi chipset
This is a non-standard variant of the Atheros G-mode PCI/Cardbus wifi chipset, which is found in quite a few notebooks and netbooks, especially certain ASUS Eee models.
The opensource ath5k driver in Puppy 4.3 is now stable, and is reported to work reliably with the AR5007EG device in most cases ...
but there are some reports that the older MADWiFi driver (ath_pci) works better with certain hardware (Eee 900?).
Here's where confusion and misinformation can start. The standard MADWiFi driver does not support the AR5007EG chipset. A special variant of the MADWiFi driver is required; "madwifi-hal-0.10.5.6".
I now attach this driver for the 2.6.30.5 kernel in Puppy 4.3.
The source code is SVN revision 4100, from
http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6/

I reiterate: standard versions of the Atheros wifi chipset will not work with this driver.
This driver is for the Atheros AR5007EG wifi device only. And you should probably not install this driver unless the ath5k driver is definitely not working for you.

The dotpet package modifies Puppy's PREFLIST so that this driver (ath_pci) will be used in preference to the ath5k driver.
Update Oct 17 2009: PREFLIST fixed.

After installing this dotpet, reboot.Last edited by tempestuous on Sat 17 Oct 2009, 02:10; edited 7 times in total

Realtek seems to release new wifi (and ethernet) devices quite regularly.
The most recent Realtek wifi chipsets are the N-mode RTL819x series. And in Realtek's usual style, they write a Linux driver immediately, but they don't release it for public download. Individual developers must ask for it.
I managed to obtain the source code from various private download sites. Now attached are the PCI/PCIe version of the driver: r8192se_pci, and the USB versions of the driver: r8192s_usb

After installing either of these dotpets, reboot. Puppy should automatically load the new driver, and you will see the new driver in the Network Wizard.

UPDATE Feb 28 2010:
Configuration files fixed so that these drivers will be recognised as WPA-compatible in the Network Wizard.

UPDATE June 6 2010:
PCI version updated to the latest ver 15.0127.2010Last edited by tempestuous on Sun 06 Jun 2010, 05:04; edited 4 times in total

Apparently this driver generates the video image in a pixelformat most video/webcam applications cannot handle, so the libv4l library is required, also attached.
The README will install to /root/my-applications/libv4l-README.txt

Instructions for use with the MPlayer, using MPlayer's v4l2 interface:
Install libv4l-0.5.8.pet.
Before launching MPlayer, run this command -

Code:

export LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so

Now launch MPlayer like this -

Code:

mplayer tv:// -tv driver=v4l2:width=352:height=288:device=/dev/video0

NOTE:
It's important that MPlayer (or XawTV, or Skype, or whatever application you choose) is launched from the same xterminal that ran the "export LD_PRELOAD ..." command.

I have a Eeepc701SD and downloaded the appropriate drivers for the Celeron.

I hit a snag at the eee-0.2-k2.6.30.5.pet. It contains the eee.ko module needed for the fan and fsb settings for the Celeron processor. There is a pinstall.sh script in the pet that runs "depmod". There is a readme instructing the user to run "modprobe eee" to load the driver. I kept getting "module not found" error.

What to do? Puppy 4.3 includes the full depmod utility. It is called by typing "depmod-FULL" in a terminal. I did that, then ran "modprobe eee" again and the driver loaded successfully.

To check run "lsmod". I did that and "eee" is the first entry.

Cheers

No need to do what is in this post, the next post addresses the issue_________________Puppy Linux Blog - contact me for accessLast edited by 01micko on Mon 12 Oct 2009, 16:33; edited 1 time in total

All drivers in this thread updated to run depmod-FULL at post-installation instead of just depmod.

I just tested several of these drivers in a fresh boot to Puppy 4.3, and the standard depmod command seems to register the new driver just fine on my hardware, but since several users have reported this error I decided that depmod-FULL was the safe way to go.
But a word of caution - apparently depmod-FULL uses a lot more memory when running, so after doing a fresh (frugal) installation of Puppy, always reboot before installing any of these dotpets. This is because a "pupsave" file is created at first shutdown, and this will act as extra memory if your RAM is ever full, and will thus avoid a crash in such situations.

I followed the procedure... but it didn't work, much. The fan drive applet seems to work. But the buttons... screen brightness keys worked before, same now. External monitor on/off seriously messes up Xorg or something - screen resolution changes and dropping to text mode the screen is corrupted. Power button is still ignored.

The hotkeys need a little work on the 1005ha too. I will post fixes soon.

A few thoughts:

I think suspend will work fine on the eee with acpitool. The only caveat is that the i915/i810 modules probably don't get loaded by default, and that screws up suspend; you have to make sure those load.

The backlight off button needs to toggle! It's pointless to turn the backlight off, if you can't get it back.

Yaf-splash notification messages that tell you that you've successfully toggled your network or adjusted the volume would be the bomb. Toggling the powersave mode super-hybrid-engine style would also be awesome.

Ok so I've been working on this all day. Here's what I've come up with.

I created a file called keys that holds the function key codes. That way, you can just swap the file depending on the target machine and everything will work. This concept should extend beyond just EeePCs, to potentially provide acpi to all kinds of laptops. To find out what the function codes are you need to kill acpid and run it as 'acpid -d -l'. Then press a function key and see the code in the acpid debugging output as shown in the screenshot below.

I implemented a lot of missing stuff like power button, lid, and ac adapter functions. You need to modify the performance.sh and powersave.sh scripts to do the right thing on your machine when the ac adapter is plugged in or removed.

I added yaf-splash notifications like I was talking about above. Now you don't have to wonder if the scripts are working or not.

I'm attaching a tarball of my /etc/acpi. This is customized for my 1005ha, so if that's not what you have, you'll need to adjust the key file and power scripts. If people want to volunteer their keycodes, we can build a database of key files.

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