Drivers for Puppy 5.1-5.2.8 with 2.6.33.2 kernel

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

#46 Post by tempestuous »

I have just added the Ralink rt5390sta wifi driver to the earlier post in this thead -
http://www.murga-linux.com/puppy/viewto ... 618#494618

I still have one additional Ralink wifi driver to add; rt3090sta
but no one has asked for it yet.

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

#47 Post by tempestuous »

I just updated the Ralink USB wifi drivers to the latest versions, in the earlier post here -
http://www.murga-linux.com/puppy/viewto ... 085#481085

mdenard
Posts: 8
Joined: Sat 09 Apr 2011, 22:11

#48 Post by mdenard »

tempestuous,
as I am still having issues w/ the Belkin usb, (http://www.murga-linux.com/puppy/viewto ... 144#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.

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

#49 Post by tempestuous »

mdenard wrote:Error inserting rt3070sta (/lib/modules/2.6.33.2/kernel/drivers/net/wireless/rt3070sta.ko): Unknown symbol in module, or unknown paramater
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.

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

#50 Post by tempestuous »

Older Ralink rt3070sta USB wifi driver.

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/viewto ... 085#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.

UPDATE Aug 25 2011:
I have further modified this driver to support these additional wifi devices:
- Belkin F6D4050 v1, USB ID 050d:935a (confirmed working by forum member Norm678)
- Belkin F6D4050 v2, USB ID 050d:935b
- Buffalo WLI-UC-GN (newer version) USB ID 0411:015d
- Keebox W150NU, USB ID 14b2:3c2c
- Linksys WUSB100 v2 USB ID 1737:0078 (confirmed working by forum member tubeguy)
- TP-Link TL-WN321G & the older Tenda W541U, both with USB device ID 148f:2070
(confirmed working by forum member Rafal07BC )
Last edited by tempestuous on Thu 25 Aug 2011, 10:38, edited 2 times in total.

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

#51 Post by tempestuous »

Atheros USB wifi devices

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/Drive ... le_devices
Someone on the Puppy forum has so far reported success with the D-link DWA-160 revA2.

The Atheros AR5523 (AR5005UG/AR5005UX) chipset requires the third-party driver; ar5523
which I have finally succeeded in compiling. ar5523 driver dotpet now attached.
I obtained the source code via svn, from here
http://linuxwireless.org/en/users/Drivers/ar5523
Supported devices:
D-link DWL-AG132
D-link DWL-G132
D-link DWL-AG122
Gigaset SMCWUSBTG
Gigaset USB 108
Netgear WG111U
Netgear WG111T
Netgear WG111T v2
Netgear WPN111
Umedia TEW444UBEU
plus generic Conceptronic, Globalsun, Wistronneweb, and Zcom devices.

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.
Attachments
ar5523-svn-r29060-k2.6.33.2.pet
for Puppy 5.1/5.2
(100.77 KiB) Downloaded 1651 times

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

#52 Post by tempestuous »

Atheros AR9271/AR7010 USB wifi chipsets require a very new driver; ath9k_htc
and it's not possible to compile this driver for the 2.6.33.2 kernel in Puppy 5.x

At the time of writing, April 2001, there is just one Puppy derivative, "Fluppy"
http://www.murga-linux.com/puppy/viewtopic.php?t=56156
which has a kernel version suitably high enough (2.6.35.7)
and I have just provided the ath9k_htc driver for Fluppy here -
http://www.murga-linux.com/puppy/viewtopic.php?t=66857
A complete list of supported devices is here -
http://linuxwireless.org/en/users/Drive ... tc/devices
This list includes several TP-Link TL-WNxx models, which a few people on the forum have been asking about.

UPDATE: at September 2011
there are now several new Puppy versions with updated kernel version,
and these two definitely contain the ath9k_htc wifi driver -

- Three-Headed Dog (Puppy Lucid 5.29 alpha)
http://www.murga-linux.com/puppy/viewtopic.php?t=70736
download - http://diddywahdiddy.net/Puppy500/luci-001.iso

- Dpup Exprimo
http://www.murga-linux.com/puppy/viewtopic.php?t=71755

in both cases the ath9k_htc firmware might (?) be missing, but you can install it from here -
http://www.murga-linux.com/puppy/viewto ... 425#555425
Last edited by tempestuous on Mon 26 Sep 2011, 11:16, edited 1 time in total.

User avatar
mickee
Posts: 207
Joined: Tue 08 Feb 2011, 14:59
Location: Saskatoon SK Canada, Gateway 5300 Laptop, 600MHz Celeron, 384MB RAM, lucid puppy 5.2 (Full Install)
Contact:

#53 Post by mickee »

tempestuous wrote:Atheros USB wifi devices


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...
[img]http://i17.photobucket.com/albums/b68/The_Wizard_of_OZ/Lindows-NOT-1.jpg[/img]
Linux is [i][b]NOT[/b][/i] Windows. Doesn't [i][b]PRETEND[/b][/i] to be, Doesn't [i][b]WANT [/b][/i]to be; Don't try to [i][b]MAKE[/b][/i] it be.

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

#54 Post by tempestuous »

Intel GMA500 Poulsbo Xorg driver

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=67166
Last edited by tempestuous on Sun 24 Apr 2011, 11:52, edited 1 time in total.

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

#55 Post by tempestuous »

The basic components are these two:
Attachments
psb-module-k2.6.33.2.pet
ONLY compatible with Puppy 5.1/5.2
(149.89 KiB) Downloaded 1298 times

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

#56 Post by tempestuous »

And here are the 3D components. You will also need the Xorg OpenGL libraries -
http://distro.ibiblio.org/pub/linux/dis ... -Lucid.pet

It may require some experimentation to get 3D functions working.

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

#57 Post by tempestuous »

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.

After installing this dotpet, reboot. Then run the ALSA Wizard.
Attachments
snd-emu10k1-firmware.pet
(151.15 KiB) Downloaded 1232 times

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

#58 Post by tempestuous »

Here is the dvb-usb-rtl2832u driver,
for Realtek RTL2832U DVB-T / RTL2836 DTMB USB tuner devices.

One such example is the Sandberg Mini DVB-T/DAB dongle.
Attachments
dvb-usb-rtl2832u_k2.6.33.2.pet
for Puppy 5.1/5.2
(50.62 KiB) Downloaded 1416 times

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

#59 Post by tempestuous »

WPA firmware upgrade for Prism2/2.5/3 PCI/PCMCIA wifi devices.

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

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

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

prism2_srec -v -f wlan0 /root/prism-1.8.2/sf010802.hex
Now run this command again -

Code: Select all

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.
Attachments
prism-NV-firmware-1.8.2.pet
(115.27 KiB) Downloaded 1095 times

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

#60 Post by tempestuous »

Here is the Qualcomm "Auxiliary" serial port driver, called qcaux
to support a range of recent USB wireless modems. The complete list of supported devices is here -
http://cateee.net/lkddb/web-lkddb/USB_SERIAL_QCAUX.html
I backported this driver from 2.6.39 kernel source.

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.
Attachments
qcaux-k2.6.33.2.pet
for Puppy 5.1 - 5.2.8
(1.81 KiB) Downloaded 1055 times
Last edited by tempestuous on Wed 31 Aug 2011, 07:15, edited 1 time in total.

User avatar
goolwa_pup
Posts: 59
Joined: Thu 29 Oct 2009, 20:31

8192cu-k2.6.33.2.pet

#61 Post by goolwa_pup »

Hi Tempestuous, I want to thank you for 8192cu-k2.6.33.2.pet (realtek)..and just want to let you know your work is very much appreciated

this driver worked on Puppy 525 001 update using a mini usb wireless stick on my thinkpad t43 without needing any firmware. It also works on my am3 quad core desktop

tried it on luci262 all good as well

I also tried it on Pemasu's midnight sun 003 but it did not work (different kernel)

With that in mind, I don't know what kernel puppy 5.2.6 will end up using.... (64 bit with 32 bit compatibility i hope) but it would be great if these drivers could be made for whatever kernel(s) 526 ends up with.

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

#62 Post by tempestuous »

July 23 2011: I just updated the older Ralink rt3070sta USB wifi driver
to support the TP-Link TL-WN321G & the older Tenda W541U, both with USB device ID 148F:2070
See earlier post in this forum thread -
http://www.murga-linux.com/puppy/viewto ... 360#513360

WiZard
Posts: 119
Joined: Sun 11 Sep 2005, 20:04
Location: Oklahoma USA

#63 Post by WiZard »

I posted this first in House Training/Users, but was referenced to this thread hoping that your success with compiling for the newer kernel could help.
'm trying to compile a usb wireless adapter driver with a RTL8188CUS chipset (uses RTL8192CU driver) . I work on old hardware and use Puppy 4.12. This is my setup:
- Puppy 4.12 frugal install
- 512kb save file
- /mnt/home/devx_412.sfs, confirmed loading from terminal by typing cc command
- /mnt/home/kernel-src-2.6.25.16-patched-puppy4.1.sfs conigured to load in boot manager
- /root/rtl8192CU, the directory containing the driver source supplied with the adapter

I opened a terminal in /root/rtl8192CU and typed make, this is the output:

make ARCH=i386 CROSS_COMPILE= -C /lib/modules/2.6.25.16/build M=/root/rtl8192CU modules
make[1]: Entering directory `/lib/modules/2.6.25.16/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.25.16/build'
make: *** [modules] Error 2

Thanks
Gary

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

#64 Post by tempestuous »

It might be that the build script cannot find your kernel sources?
I'm generally unfamiliar with the use of sfs files in a frugal environment, and that may have a bearing??

Here's a thought - upgrade to Puppy 5.2.5 and I have the Realtek wifi driver ready-to-use.
Contrary to popular belief, older Puppy versions (and older kernel versions) do not necessarily work better on older hardware!
From my own observations with a Pentium3-733, Puppy 4.x is no faster/better than Puppy 5.x.
Same applies to Puppy 3.x.

Puppy 2.x, on the other hand, is noticeably faster ... and Puppy 1.0.4 is lightning-fast!

WiZard
Posts: 119
Joined: Sun 11 Sep 2005, 20:04
Location: Oklahoma USA

#65 Post by WiZard »

tempestuous, guess I can eliminate any problems of the frugal install and sfs files with a full install, can you point me to instructions for adding the development files and kernal resources to a full install? In our case, using 4.12 instead of 5.x isn't a speed issue as much as it would be the hours it would take to recreate and reconfigure the highly modified 4.12 image we are using (goes on refurbrished computers that are donated to non-profit groups). Also, our image now is very close to the 256kb ram limit (we do frugal installs and lots of the computers only have 256kb) and I'm not sure we could get the same functionality in since the 5.x kernel is about 30kb larger than 4.12. I will start setting up a system with a full install to compile the driver and will let you know what happens.

thanks
Gary

Post Reply