Extra drivers for Puppy 2 with 2.6.18.1 kernel

For drivers and kernel modules.
Message
Author
tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

Extra drivers for Puppy 2 with 2.6.18.1 kernel

#1 Post by tempestuous »

These drivers are compatible with the 2.6.18.1 kernel in:
- Puppy 2.12-2.16
- Puppy 214R by pakt and Dougal
- Puppy 214X.. by ttuuxx

These drivers are not compatible with Barry's Pup218, which has a completely overhauled 2.6.18.8 kernel.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#2 Post by tempestuous »

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.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#3 Post by tempestuous »

Next, the newer Ralink rt2860sta and rt2870sta wifi drivers.
These are from the proprietary Ralink source code at
http://www.ralinktech.com/ralink/Home/S ... Linux.html
Note: the very recent Ralink rt3070 driver would not compile against this older kernel.

The RT2860 wifi chipset is found in these ASUS Eee models:
901, 1000, 1000H, and 1000HE.
EDIT Oct 20 2009:
rt2860sta driver updated to ver 2.2.0.0

These Eee models also require a special LAN driver; the Atheros atl1e. Now attached.
The source code was obtained from Attansic, via the Ubuntu developer forum
http://launchpadlibrarian.net/7382416/L ... er_new.rar
After installing any of these dotpets, reboot.
Attachments
atl1e-v1.0.1.0-k2.6.18.1.pet
for Puppy 2.12-2.16
(20.33 KiB) Downloaded 1664 times
Last edited by tempestuous on Mon 19 Oct 2009, 16:36, edited 2 times in total.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#4 Post by tempestuous »

ASUS Eee drivers, continued:
Most early Eee models have the Atheros AR5007EG wifi chipset, which requires a special variant of the MADWiFi (ath_pci) driver, now attached. Models:
Eee 700-series (but not 701SD), 900, 900A, 900HA, 901GO, 904HA, 904HD, 1000HA, 1000HD:

The source code is from here
http://snapshots.madwifi-project.org/ma ... -0.10.5.6/
Note that the very recent Atheros N-mode wifi chipset, as found in several Eee 1000 models, cannot be supported with this older kernel.

This MADWiFi package should ONLY be used with the AR5007EG variant, all "standard" Atheros wifi devices will be supported by the standard ath_pci module in Puppy 214X.

These Eee models also require a special LAN driver; the Atheros atl2. Now attached.
The source code was obtained from http://people.redhat.com/csnook/atl2/
After installing these dotpets, reboot.
Attachments
atl2-1.0.40.4-k2.6.18.1.pet
for Puppy 2.12-2.16
(16.22 KiB) Downloaded 1739 times
Last edited by tempestuous on Tue 16 Jun 2009, 14:32, edited 1 time in total.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#5 Post by tempestuous »

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.
Attachments
rtl8187se-coffelius0.4-k2.6.18.1.pet
for Puppy 2.12-2.16
(113.24 KiB) Downloaded 1625 times

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#6 Post by tempestuous »

Here is the driver for the webcam in the ASUS Eee.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#7 Post by tempestuous »

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.

Please get the acpid package compatible with your wifi device (Atheros AR5007EG, Realtek RTL8187SE, or Ralink RT2860) from the Puppy 4.1 extras thread -
http://www.murga-linux.com/puppy/viewto ... 744#237744

Hotkeys supported:

Fn+F2: Toggle Wireless on/off
Fn+F5 external monitor on/off (NOT TESTED)
Fn+F7: Toggle Mute/Unmute (NOT WORKING)
Fn+F8: Decrease Volume Level
Fn+F9: Increase Volume Level

INSTRUCTIONS:
Install eee-asus_acpi-pciehp-k2.6.18.1.pet
plus the ACPI daemon (acpid) package compatible with your wifi device (ath_pci, r8180, or rt2860sta).
The acpid dotpet will add the following 3 commands to your /etc/rc.d/rc.local

Code: Select all

modprobe pciehp pciehp_force=1
modprobe asus_acpi
acpid
If you haven't done so already, configure your wifi connection with the Network Wizard.
Reboot. Enjoy.
Attachments
eee-asus_acpi-pciehp-k2.6.18.1.pet
for Puppy 2.12-2.16
(48.06 KiB) Downloaded 1582 times

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#8 Post by tempestuous »

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: Select all

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: Select all

echo 50 > /proc/eee/fan_speed
To turn off the fan do this

Code: Select all

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.

Dougal has created a fan control script and configuration gui here
http://www.murga-linux.com/puppy/viewtopic.php?t=34886
Attachments
eee-fan-CPU-0.1-k2.6.18.1.pet
for Puppy 2.12-2.16
(2.91 KiB) Downloaded 1532 times

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#9 Post by tempestuous »

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

Code: Select all

alias snd-card-0 sis7019
alias sound-slot-0 sis7019
Then reboot.
Attachments
r6040-k2.6.18.1.pet
for Puppy 2.12-2.16
(8.11 KiB) Downloaded 1564 times

mawebb88
Posts: 246
Joined: Sun 13 Jul 2008, 09:54
Location: France nr Lyon

Great found your thread for EeePC901 wifi drivers

#10 Post by mawebb88 »

tempestuous wrote:Next, the newer Ralink rt2860sta and rt2870sta wifi drivers.
These are from the proprietary Ralink source code at
http://www.ralinktech.com/ralink/Home/S ... Linux.html
Note: the very recent Ralink rt3070 driver would not compile against this older kernel.

The RT2860 wifi chipset is found in these ASUS Eee models:
901, 1000, 1000H, and 1000HE.

These Eee models also require a special LAN driver; the Atheros atl1e. Now attached.
The source code was obtained from Attansic, via the Ubuntu developer forum
http://launchpadlibrarian.net/7382416/L ... er_new.rar
After installing any of these dotpets, reboot.
I reported in ttuxxx 214x thread over at http://www.murga-linux.com/puppy/viewto ... 444#317444 that no interfaces were found. I will now try these.
Thanks Mike

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#11 Post by tempestuous »

Zydas ZD1211 wifi devices

Puppy versions 2.12, 2.13, 2.14, 2.15CE, 2.16
contain the opensource zd1211rw driver.

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 -

Code: Select all

rmmod zd1211b
modprobe zd1211rw
Now it will be necessary to run the Network Wizard.

Updated with core wifi (ieee80211) modules, July 30 2009.
Attachments
zd1211rw-k2.6.18.1.pet
for Puppy 214R & 214X
(69.2 KiB) Downloaded 1646 times

EZ4arabs
Posts: 82
Joined: Wed 19 Jul 2006, 09:18

RT73 usb

#12 Post by EZ4arabs »

I installed rt73-20090412-k2.6.18.1.pet but I get this error:



FATAL: Error inserting rt73 (/lib/modules/2.6.18.1/extra/rt73.ko): Unknown symbol in module, or unknown parameter (see dmesg)
sh-3.00# dmesg

rt73: Unknown symbol release_firmware
rt73: Unknown symbol request_firmware
rt73: Unknown symbol release_firmware
rt73: Unknown symbol request_firmware

what am I doing wrong here ?! Can you please me .
I am trying to get the linksys usb wifi adapter to work under ver 2.16

Thank you

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#13 Post by tempestuous »

Mmm. Maybe the "firmware_class" module has failed to load.
Do this -

Code: Select all

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

Code: Select all

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/

Edit: attachment removed.
Last edited by tempestuous on Sun 16 Aug 2009, 09:00, edited 1 time in total.

EZ4arabs
Posts: 82
Joined: Wed 19 Jul 2006, 09:18

#14 Post by EZ4arabs »

tempestuous wrote:Mmm. Maybe the "firmware_class" module has failed to load.
Do this -

Code: Select all

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

Code: Select all

rmmod rt73
modprobe rt73
that fixed the problem.
Thank you so much for your time and help sir.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#15 Post by tempestuous »

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?

It's difficult to offer sound, accurate, and sensible technical solutions when new users treat Linux as alchemy.

jakfish
Posts: 762
Joined: Fri 18 Jul 2008, 19:09

#16 Post by jakfish »

Even though I don't use puppy 2, I've been reading this thread and feel badly at how it's ending.

When hard-working folks use their time to design key pets for others, the community does owe a response to say if the pets function or not.

That said, tempestuous, your work is legendary and I know many users, starting with me, are eternally grateful. The eee pets you made for puppy 4.* have made me a puppy user for life--you made wifi, fan control, etc. available, and had you not, many, many eee users would've moved on to another flavor of linux.

You built a subcommunity, and thank you for it,
Jake

User avatar
ecomoney
Posts: 2178
Joined: Fri 25 Nov 2005, 07:00
Location: Lincolnshire, England
Contact:

#17 Post by ecomoney »

Users requiring alchemy? Yes that sounds about right. Many users are totally unaware of what wireless hardware there is inside their computers. Puppy is a linux distro for beginners so thats to be expected.

How would someone discover what hardware they have or drivers they need?
Puppy Linux's [url=http://www.murga-linux.com/puppy/viewtopic.php?p=296352#296352]Mission[/url]

Sorry, my server is down atm!

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#18 Post by 01micko »

jakfish wrote:Even though I don't use puppy 2, I've been reading this thread and feel badly at how it's ending.

When hard-working folks use their time to design key pets for others, the community does owe a response to say if the pets function or not.

That said, tempestuous, your work is legendary and I know many users, starting with me, are eternally grateful. The eee pets you made for puppy 4.* have made me a puppy user for life--you made wifi, fan control, etc. available, and had you not, many, many eee users would've moved on to another flavor of linux.

You built a subcommunity, and thank you for it,
Jake
Seconded :)
tempestuous wrote: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?

It's difficult to offer sound, accurate, and sensible technical solutions when new users treat Linux as alchemy.
Users, just sign up and post. It costs you nothing. A developers job is to evaluate all the input available, no matter how trivial you think it is.

Thanks tempestuous
Puppy Linux Blog - contact me for access

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#19 Post by 01micko »

ecomoney wrote:Users requiring alchemy? Yes that sounds about right. Many users are totally unaware of what wireless hardware there is inside their computers. Puppy is a linux distro for beginners so thats to be expected.

How would someone discover what hardware they have or drivers they need?
Erm, Rob.

While I believe your intentions are good, the questions you pose are for Barry. Ask him.
Puppy Linux Blog - contact me for access

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#20 Post by tempestuous »

Thanks for your words of support Jake and Mick, but I don't desire a pat on the back.
I simply want the forum to be an informational resource, rather than a worthless repository of random guesswork, and a convenient excuse for new users to claim that Linux is unworkable.
ecomoney wrote:How would someone discover what hardware they have or drivers they need?
Ask. That's my point.
I'm not discouraging new users from getting involved. I'm encouraging them to get involved in a sensible and productive fashion, rather than wasting effort with silly, unproductive guesswork.
01micko wrote:Users, just sign up and post.
Indeed.

Post Reply