(old)Puppy Linux Discussion Forum

I also have the latest Ralink PCI/Cardbus wifi drivers, but no one has asked for them.
Anyone who wants these should reveal their device ID.

For PCI/miniPCI wifi devices, determine device ID with this command - For Cardbus wifi devices, determine the device ID with these two commands -

Jan 20 2011
I have just updated the Ralink rt3572sta USB wifi driver to the latest version 2.5.0.0, and patched it to include support for the Linksys AE1000. The revised dotpet is attached to the earlier post in this thread -
http://www.murga-linux.com/puppy/viewto ... 085#481085

Ralink PCI/Cardbus wifi devices

rt3090sta for RT309X PCIe devices.

rt5390sta for RT5390 PCIe devices.
The first forum request for this driver is suitable for the inbuilt miniPCI card in the Compaq CQ56 laptop.

rt3562sta for RT3060/RT3062/RT3562/RT3592
The first forum request for this driver is suitable for the Sumvision Wireless N PCI card.

After installing either of these dotpets, reboot, and the new driver should be seen in the Network Wizard.

The Orinoco wifi chipset is a very early B-mode wifi device, generally well-supported in Puppy by the standard kernel drivers for PCI and PCMCIA variants.
But the very rare USB variants of this wifi device have only ever been supported by an experimental driver; orinoco_usb
orinoco_usb dotpet now attached.
I obtained the source code from
http://repo.or.cz/w/orinoco_usb.git

UPDATE May 2015
orinoco_usb dotpet attachment was corrupt. Now re-uploaded.
Please be aware that once you install this dotpet, it will break the Orinoco PCMCIA/PCI drivers. There's no way around this.

The iwlagn driver in Puppy 5.1/5.2 supports a range of Intel N-mode wifi devices, namely the IWL1000/3000/4000/5000/6000 series devices.

Puppy already includes the necessary firmware for most of these devices, but is missing the firmware for the IWL6000 series. I now attach this extra firmware as a dotpet.
Specifically, the firmware included is "iwlwifi-6000-4.ucode" and "iwlwifi-6050-4.ucode"

You may find that Puppy 5.1/5.2 still doesn't support your Intel wifi device, because since the 2.6.33 kernel was released there are now some extra Intel models; IWL6000G2A, IWL6000G2B, and IWL100. You will need to wait for a kernel upgrade before these models are supported.

EDIT: broken attachment now fixed.

Puppy already contains suitable drivers for many different brands of gamepad devices, including most Logitech models in the form of the hid-logitech driver. But the "force feedback" function of this driver is not enabled in Puppy.

Now attached is the hid-logitech driver with the force feedback functions enabled, to support the following gamepad devices:
- Logitech WingMan Cordless RumblePad
- Logitech WingMan Cordless RumblePad 2
- Logitech WingMan Force 3D
- Logitech Formula Force EX
- Logitech WingMan Formula Force GP
- Logitech MOMO Force wheel
- Logitech Rumblepad 2 devices

After installing this dotpet, reboot.
Hopefully force feedback will now work. To test, you can install the joystick-utils dotpet, then run this command - The joystick-utils package also contains these utilities:
evtest
inputattach
jstest
jscal
ffset

tempestuous wrote:Puppy already contains suitable drivers for many different brands of gamepad devices, including most Logitech models in the form of the hid-logitech driver. But the "force feedback" function of this driver is not enabled in Puppy.

Now attached is the hid-logitech driver with the force feedback functions enabled.
After installing this dotpet, reboot.

Supported "force feedback" devices:
- Logitech WingMan Cordless RumblePad
- Logitech WingMan Cordless RumblePad 2
- Logitech WingMan Force 3D
- Logitech Formula Force EX
- Logitech WingMan Formula Force GP
- Logitech MOMO Force wheel
- Logitech Rumblepad 2 devices

Any change of posting the sources, so I can get it working in 4.2 (for Puppy Arcade?).. Or even a .pet for 2.6.25.16 would be lovely!!

It's the standard kernel source. After running "make menuconfig" go to:
Device Drivers > HID Devices > Special HID drivers >
- Logitech force feedback support (press spacebar to enable)
- Logitech Rumblepad 2 force feedback support (press spacebar to enable)

then do "make modules" as usual. The module name is "hid-logitech.ko"
and it should be placed into
/lib/modules/<kernel version>/kernel/drivers/hid/
replacing the standard version already there.

And if you're going to modify the Logitech gameport driver for force feedback support, you might as well enable the other gameport drivers that support force feedback, namely;
DragonRise
Pantherlord
GreenAsia
SmartJoy
ThrustMaster
Zeroplus

tempestuous wrote:then do "make modules" as usual.

"as usual"... lol, I never done any of that before! I don't even know any commands or parameters I can add after the 'make' command... (Well, I do now! )

But it doesn't look too hard, easy enough I guess, thanks for the info.
Helpful and prompt as always, what would we do without you here?
(We would all have to buy the same hardware, I guess! )

Anyway, I will give it a go.

I will certainly look into more advanced uses of the 'make' command.. (Maybe it will finally help me compile stuff that seems to come with no makefile!)..

where do i get the kernel source to make the modules from?

http://distro.ibiblio.org/pub/linux/dis ... ppy4.1.sfs
for Puppy 4.1.x and 4.2.x

sc0ttman and blaarghalltheusernamesare,
if you have further questions about kernel compiling, please create a new forum thread. I would prefer to keep this thread for contributed drivers/applications, not a developers' how-to discussion.

Anyway, good news; I thought that my Puppy 4.1 installation was corrupted, but it seems OK, so I just compiled the force feedback-enabled gameport driver, now available here -
http://www.murga-linux.com/puppy/viewto ... 494#500494
In this earlier kernel, gameport support is built into the usbhid driver ... you may have already discovered that the kernel configuration settings are different than what I described for Puppy 5.1.
Only in later kernels was gamepad functionality split out into separate drivers.

tempestuous wrote:sc0ttman and blaarghalltheusernamesare,
if you have further questions about kernel compiling, please create a new forum thread.

Anyway, good news; I thought that my Puppy 4.1 installation was corrupted, but it seems OK, so I just compiled the force feedback-enabled gameport driver, now available here -
http://www.murga-linux.com/puppy/viewto ... 494#500494

Thanks for the info, file and link, didnt mean to go off topic!

sorry about that. i'll shut up now.

Here is the w35und wifi driver,
compatible with the Winbond/ISSC W89C35D wifi chipset, as found in certain Kohjinsha laptops, and in some stand-alone USB wifi devices.
This is one of the "staging" drivers in the kernel source, which was not enabled in the standard Puppy kernel. It's considered "experimental".

After installing this dotpet, reboot.

NOTE: apparently the default frequency settings for this driver are the USA standard.
If you connect to European wifi access points, you must run this command each time before running the Network Wizard:

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.

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

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.

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.

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 )