Extra drivers for Puppy 4.1 with 2.6.25.16 kernel

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

#201 Post by tempestuous »

Here are the Linux drivers for VIA wifi devices:
VIA VT6655 PCI device, the driver is called viawget
VIA VT6656 USB device, the driver is called vntwusb

The source code is from
http://www.viaarena.com/Drivers.aspx
After installing either of these dotpets, reboot.
Both drivers create an interface called eth#. Usually your LAN device takes eth0, so the wifi interface will probably become eth1.

For WPA-encrypted connections, both package include a modified version of wpa_supplicant compatible with the new driver.
I have included the necessary configuration file (/usr/sbin/wag-profiles.sh) so that Puppy's Network Wizard should be able to configure the connection.
But if you want to configure a WPA connection via the commandline, be aware that the wpa_supplicant "-D" parameter for the new drivers are the same name as the driver itself (which is quite unconventional).

As an example, with the viawget driver and a WPA2 connection, your command would be -

Code: Select all

wpa_supplicant -i eth1 -D viawget -c /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant2.conf -dd

noabody
Posts: 14
Joined: Mon 08 Jun 2009, 16:38

#202 Post by noabody »

I picked up an older 2WIRE and Qwest branded USB wireless adapter. Through research and the use of a screwdriver I have this information.
FCC ID: M4Y-XG702B
Manufacturer: ZCOM (ZCOMAX)
Chipset: Intersil, Controller NET2280, Wireless ISL3886 (PRISM Duette)
Vendor ID: 1630
Device ID: 0005
(1630:0005)
I think it's part of the existing p54 driver (p54usb, p54pci p54common) http://lekernel.net/prism54/snapshots/ . The chipset would make it a direct match to Linksys WUSB54G 5041:2234, and a host of others http://lekernel.net/prism54/newdrivers.html . It appears that driver development is dead so even though support might be as simple as adding the vendor and device id's to the source I don't know who to forward the information to.

I don't expect anyone on the forum to edit the source and recompile the driver since ndiswrapper works. I did think it would be useful to post this information somewhere although this isn't the best place. I would guess the amount of these USB adapters still in use is trivial.
Last edited by noabody on Thu 16 Jul 2009, 03:44, edited 1 time in total.

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

#203 Post by tempestuous »

Well the Prism54 project isn't dead, it continues under the umbrella of linuxwireless.org
http://linuxwireless.org/en/users/Drivers/p54
You will see mailing list contact details at the bottom of the page.

If, indeed, your device has a Prism54-softmac chipset then it should be supported by the p54usb driver ...
but the p54usb driver in Puppy 4.1/4.2 does not recognise your USB device number.
It's quite easy to hack the kernel source file (p54usb.c) to add your device number, but the driver is supposed to probe the device to determine the exact firmware file necessary to load (which for your ISL3886 + net2280 chipset will be isl3890usb) and I can't guarantee that this process will be successful for you.
Give it a try.
After installing this dotpet, reboot.
When you plug in your USB device, Puppy should automatically load the p54usb driver, but if not you can load it manually from the Network Wizard.

PenPen
Posts: 20
Joined: Mon 07 Jul 2008, 04:16
Location: Other Side of The World

I Thank You for the .pet

#204 Post by PenPen »

Tempestuous,

I thank you for compiling the broadcom-5.10.27.14-k2.6.25.16.pet

My Levono S10 now works without using Ndiswrapper and only connecting with Wep, Now I connect with Wap2 with no problems....

Again I thank you for the effort and work that you do...

PenPen

noabody
Posts: 14
Joined: Mon 08 Jun 2009, 16:38

#205 Post by noabody »

Thank you so much Tempestuous for building p54usb-ZCOM-k2.6.25.16.pet . It definitely initialized the usb adapter and gave me a wlan0 interface. Unfortunately it had problems with the host usb controller on my test machines whenever I tried to scan for wireless networks. I will derive lsusb -vvv and post that along with the other information to linuxwireless.org in the hopes that native support may be available in the future based on that information.

Thanks again!

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

#206 Post by tempestuous »

I suggest you look at the output of dmesg at each stage of your testing, to see what the driver is doing.

I also suggest you use manual commands to configure the wifi interface (if you're not, already).
I provided a HOWTO here if you're not familiar with these commands -
http://www.murga-linux.com/puppy/viewtopic.php?t=22469
noabody wrote:Unfortunately it had problems with the host usb controller on my test machines whenever I tried to scan for wireless networks.
I vaguely remember reading a similar problem such as this, where a workaround was to force the USB interface to USB1.1 instead of USB2.0.
I think (??) this was simply a matter of unloading the USB2 kernel module (ehci-hcd), at which point the underlying USB1.1 module (ohci-hcd) should become active.
Worth a try?

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

#207 Post by tempestuous »

July 18 2009
The acpid dotpets for hotkey wifi on/off for ASUS Eee have just been fixed in the earlier post.
http://www.murga-linux.com/puppy/viewto ... 744#237744
It's sad that after almost 2000 downloads of these packages since October 2008, only one forum member (jakfish) was sensible enough to identify and report this problem.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#208 Post by mikeb »

It's sad that after almost 2000 downloads of these packages since October 2008, only one forum member (jakfish) was sensible enough to identify and report this problem.
Indeed psychic abilities are pretty rare in these parts...good (or bad) feedback is essential.

mike

noabody
Posts: 14
Joined: Mon 08 Jun 2009, 16:38

#209 Post by noabody »

Hey tempestuous, I got my ZCOM 1630:0005 wireless adapter working in Ubuntu Jaunty with your help (see http://ubuntuforums.org/showthread.php?t=707972 ).
Eventually I setup Puppy 4.2.1 with the development environment on a bootable USB stick. This way I could compile the kernel drivers using a faster computer and test it on a slower computer. To date I have tested this NET2280+ISL3886 adapter on Intel 440BX chipset, Nvidia Nforce2 chipset, and ATI 780G chipset on PII-300, Athlon XP 2800+ and Athlon X2 3000+. The 440BX is USB1.1 where the others are 2.0.

I found that the USB bus seems to hang on the 440BX when using the network wizard to "scan" for networks. The driver seems to force USB 1.1 on the Nforce2 which stops my Puppy USB stick from being able to write changes (must have had both devices on the same host controller). There were no ill effects on the 780G but the USB stick and wireless device were probably on different host controllers.

After messing with this more dmesg provided the following information:

p54usb: no version for "struct_module" found: kernel tainted
p54: LM86 firmware
p54: FW rev 2.5.6.0 - Softmac protocol 3.0
phy1: Selected rate control algorithm 'pid'
phy1: hwaddr XX:XX:XX:XX:XX:XX, isl3886
usbcore: registered new interface driver prism54usb

Oddly if I run "ifconfig wlan1 up" then "iwlist wlan1 scan" I see networks but if I scan using the network manager dmesg shows pages of unknown frames:

phy1: unknown frame RXed (0x20) (also 30 31 37 54 6d 6f 72 73 77 78 )

The unknown frames are consistent regardless of computer.

I edited this post to let tempestuous know that I did try quite a few things (compiled from source, tried multiple firmwares, tested on multiple machines) and did not rely entirely on his efforts but had no better luck myself. I'm not sure if this will affect other NET2280+ISL3886 adapters in Puppy or if it's just this one. It may be somewhat chipset specific as far as the USB bus problems. I use wpa_supplicant but don't think it's affecting the connection, it seems to be a driver issue.

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

#210 Post by tempestuous »

Here is the at76_usb driver for USB wifi adaptors with the Atmel chipset,
models at76c503, at76c505 and at76c505a.

The source code is from
http://developer.berlios.de/projects/at76c503a/

After installing this dotpet, reboot.
Puppy should automatically load this driver, but if not you can load it from the Network Wizard.

The at76_usb driver supports only WEP encryption, not WPA encryption.

algyzas
Posts: 23
Joined: Mon 24 Nov 2008, 22:13

#211 Post by algyzas »

tempestuous wrote:Here is the "gspca_t613" webcam driver, which supports the TASCORP JPEG Webcam, NGS Cyclops, USB ID 17a1:0128.
This driver is from development source code from
http://linuxtv.org/hg/~eandren/gspca-m5602/

And also attached is the (standard) gspca webcam driver, patched to add support for the Logitech QuickCam E2500, using a patch from
http://forums.quickcamteam.net/showthre ... 49#pid1949
Some message from /var/log

Jul 26 11:40:41 (none) user.info kernel: usbcore: registered new interface driver gspca
Jul 26 11:40:41 (none) user.info kernel: /usr/src/3rd-party-drivers-extra/misc/gspcav1-20071224/gspca_core.c: gspca driver 01.00.20 registered
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: disagrees about version of symbol video_ioctl2
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: Unknown symbol video_ioctl2
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: disagrees about version of symbol video_devdata
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: Unknown symbol video_devdata
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: disagrees about version of symbol video_unregister_device
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: Unknown symbol video_unregister_device
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: disagrees about version of symbol video_register_device
Jul 26 11:40:51 (none) user.warn kernel: gspca_main: Unknown symbol video_register_device
Jul 26 11:40:51 (none) user.warn kernel: gspca_t613: Unknown symbol gspca_frame_add
Jul 26 11:40:51 (none) user.warn kernel: gspca_t613: Unknown symbol gspca_debug
Jul 26 11:40:51 (none) user.warn kernel: gspca_t613: Unknown symbol gspca_disconnect
Jul 26 11:40:51 (none) user.warn kernel: gspca_t613: Unknown symbol gspca_resume
Jul 26 11:40:51 (none) user.warn kernel: gspca_t613: Unknown symbol gspca_dev_probe
Jul 26 11:40:51 (none) user.warn kernel: gspca_t613: Unknown symbol gspca_suspend
Jul 26 11:42:24 (none) user.err kernel: hub 2-0:1.0: unable to enumerate USB device on port 3

Seems this device ID 17a1:0128 don't want to work on puppy 4.2 :(

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#212 Post by Aitch »

that deviceID does correspond to a tascorp usb videocam

http://hardware4linux.info/component/32730/

see also similar problem

http://www.mail-archive.com/fedora-list ... 43436.html

no solution found

Aitch :)

chasman666
Posts: 8
Joined: Tue 07 Jul 2009, 13:29

Wireless woes with belkin f5d7000 v2

#213 Post by chasman666 »

I can't get the wireless to work with a Belkin f5d7000 V2 PCI card on Puppy 4.2.1.

I've tried many different modules and read this whole thread about 8 times. The closest I can get is to modprobe b43 (this is what Ubuntu 8.04 auto chose and which works for it) which gives a wlan0 item in ifconfig but when I try to access it via network wizard it: 1) shows as PCMIA not PCI and 2) gives the error:
Failed to raise interface wlan0,
Failed command was: ifconfig wlan0 up
Error returned was:
ifconfig: SIOCSIFFLAGS: No such file or directory

As always any help gratefully received, it's probably something small and simple - just like me, but darned if I can find it!

Cheers,

Charlie

UPDATE
I just tried with 4.2.1Retro and it "worked out-of-the-box" as they say. It is using module bcm43xx.

So I guess that raises two things:
1. I hope that this information may be helpful to someone in the future
2. How can I make it work with the Standard version and future versions?

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

#214 Post by tempestuous »

Hermes II/II.5 wifi chipsets
The Lucent/Agere Orinoco wifi chipset was one of the very first wifi chipsets available. It was initially supported by the opensource orinoco Linux driver.
Then the chipset developed further as the "Hermes-I", then under the Intersil company as "Prism2". Several opensource drivers had emerged by this stage, the most advanced being from the hostap project.

The Hermes versions were then updated to Hermes-II and Hermes-II.5, and these rare devices are not compatible with the hostap driver. They are supported only by the proprietary "wlags49" drivers, which are now very old and incompatible with modern kernels ...
but the source code has been updated by Henk de Groot here -
http://home.hetnet.nl/~pe1dnn/linux/
Apparently the driver now supports WPA encryption, via the "wext" interface with wpa_supplicant.

Now attached are the two versions of the updated wlags49 driver:
wlags49_h2_cs
for Hermes-II devices with ID 0156 0003, such as
SpeedTouch 110 PCMCIA card.

wlags49_h25_cs
for Hermes-II.5 devices with ID 0156 0004, such as
Linksys WCF54G CompactFlash card.

After installing this dotpet, reboot.
Puppy should automatically detect your device and load the wlags driver, but if not, you can load it from the Network Wizard.

UPDATE: forum members sweatshirt and space_jazz both report success with the wlags49_h2_cs driver -
http://www.murga-linux.com/puppy/viewto ... 843#334843
Attachments
Hermes-2-2.5-k2.6.25.16.pet
for Puppy 4.1/4.2
(154.48 KiB) Downloaded 1728 times
Last edited by tempestuous on Wed 26 Aug 2009, 12:06, edited 3 times in total.

space_jazz
Posts: 6
Joined: Sat 22 Aug 2009, 15:02
Location: Poland

#215 Post by space_jazz »

I just downloaded and installed the patched hostap_cs driver and my speedtouch pcmcia wifi still won't work :|

There's now a network interface in the system (wifi0) but that'a all ... i cant see any network . Even in the control panel when i look to hardware info the network interface wifi0 have hardware adress 00:00:00:00:00.

Anybody can help me to get the thomson speedtouch 110 card to work ?

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

#216 Post by tempestuous »

"wifi0" is usually a virtual or placeholder interface, not the true interface.
Run this command -

Code: Select all

ifconfig -a
to see if there is another interface listed (other than the wired LAN interface).

If Puppy's Network Wizard is unable to configure this interface, then use manual commands as explained in
"How to configure wifi from the commandline"
http://www.murga-linux.com/puppy/viewtopic.php?t=22469

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

#217 Post by tempestuous »

Mwave winmodem
The Mwave 3780i device is found in the IBM Thinkpad 600, 600E and 770/ED/X/Z models.

Puppy 4.1/4.2 already contain the mwave kernel module, but the necessary Mwave utilities are missing. These are now provided as the attached dotpet. They were taken from the zdrv file in Puppy 4.0.
After installing this dotpet, reboot.
At bootup, the Mwave daemon, /etc/init.d/mwaved, should run. Pupdial should now be able to see your modem.

stevesr0
Posts: 169
Joined: Sun 24 Jun 2007, 17:25

re: Patched-snd-hd-intel pet of 9 April

#218 Post by stevesr0 »

I just tried to install this pet on my 4.2.1 frugal install.

The petget window checking appears and then disappears with no error messages.

I looked for an entry in the pet manager, but it isn't listed as installed.

The pet is sitting in my/initrd/pup_rw/mnt/sd3 directory.

What am I doing wrong?

stevesr0

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

#219 Post by tempestuous »

I just checked the mwavem-1.0.2.pet now. It installs fine.
Why are you using petget? The simplest way to install dotpets has always been to simply click on the file in ROX.

stevesr0
Posts: 169
Joined: Sun 24 Jun 2007, 17:25

re Tempestuous's reply to me

#220 Post by stevesr0 »

Are we talking about the same pet? You call it mwavem 1.02 and I am referring to the pet named patched snd hd intel that you posted on 13 April.

I tried direct clicking and this did the same thing.

stevesr0

Post Reply