wireless / wifi cards confirmed to work in puppy - OLD LIST

[chicks]

AirLink 101 AWLH3028

$11 at Fry's

Wizard used rtl8080, no good. Had to blacklist, download Windows drivers from AirLink, works perfectly with ndiswrapper and net8185 ndis driver, including WPA2 security.

[iansl2000]

Just got the above USB wireless network adaptor (less than £10 incl postage from ebay) working with puppy 3.01.
The 'Connect' wizard allocated driver rt2570 to this adaptor but has no WPA support.
I blacklisted this driver and loaded rt73 and all works perfectly with native WPA supported.

The easiest wireless card/usb yet.

Ian

[setecio]

Netgear 511T laptop card. working with WPA in Puppy 3.01

I was looking for a 'guaranteed' Puppy card, easily available in the UK, and wanted it to work with a module and NOT ndis ! I bought it six months ago but ran into problems, but now in Puppy 3.01 is was all so easy!

Puppy 3.01 > load ath_pci network module (which seems odd as it gave me the impression is was for desktop cards rather than laptop pcmcia type ... would it be possible to add 'pcmcia' into the text for this module?)

Ah this was soooo easy and pleasant to set up using WPA, it all just worked.

Toshiba Satellite Pro 4200, 500 Mhz, 192 MB, Netgear 511T using ath_pci module and WPA.

[kyroc]

The Belkin USB wireless adapter model FSD7050 works quite well in Puppy 3.01

[tommy]

I have a quite old Belkin F5D7011 PCMCIA 54g (Broadcom chipset) card and never succeeded in having it working under Puppy 1.13-2.14 on an old Acer Travelmate 514txv notebook (celeron 500 MHz - 256MB ram). It simply never seemed to got power (no led activity). In Windoze 98 it worked well, yet in Win2000 the card hanged the notebook as soon as it got inserted in PCMCIA slot.
Tried the Belkin card today on an Asus notebook ( Pentium 4 M 1.5 GHz - Ram 256 MB ddr) and Puppy 2.16. With the Belkin card inserted, the bcm43xx driver isn't loaded at startup (led lights turned off). I had to load the driver manually, and immediately the power led on the card switched on. Configuring the SSID and channel made it work FLAWLESSLY.
I'll never know if the problem was in puppy 2.14 or in the Acer 514txv motherboard, since that old Acer notebook has been stolen...

[Lobster]

Something like a spreadsheet wiki? Lobster might know of such a thing.

to add data as a table . . .
http://spreadsheets.google.com/

html tables can be added eg
http://puppylinux.org/wikka/AdditionalPrograms

here is existig wiki Wireless Working info
http://puppylinux.org/wikka/WirelessWorking

you can also add tables in the existig wiki

Code: Select all

{{table columns="3" cellpadding="1" cells="BIG;GREEN;FROGS;yes;yes;no;no;no;###"}}

[oldbox]

Netgear WG121 (vendor id 0846 product id 4200 revision number 1.10)
Puppy 3.01
works with Ndiswrapper and drivers from "ndis5" diretory of windows installation/driver CD

must be plugged into a usb2.0 port, does not work in a usb1.1 port, at least not on my machine. Other devices here work in both types of ports on this machine, so I don't think it's my ports.

Puppy was the first distribution besides Win98 that I got this adapter to work with reliably.

At long last!

[setecio]

Netgear WG311 (v1 I think) with Puppy NOP3.01r1 works with ath_pci module using WPA

[BlackWhizz]

I jult love puppy, did over a week to install and costumuze it, and it just didint work the second boot.

Got puppy now and it all works out of the box

Got my RaLink RT2400 Wireless lan card working under puppy 3.01 with the experimental driver which was already in the driverpack of puppy.

Sorry for my bad english, im from Holland

[jonyo]

Got my RaLink RT2400 Wireless lan card working under puppy 3.01 with the experimental driver which was already in the driverpack of puppy.

Got make, model, vers info for the card?

[BlackWhizz]

Got my RaLink RT2400 Wireless lan card working under puppy 3.01 with the experimental driver which was already in the driverpack of puppy.

Got make, model, vers info for the card?

Dont know, but the chip is a RT2400 chip, and i got it from a friend, which wanted 54mbps. That card didnt work under Puppy. The box of the card says its an E-Tech WL-101.

[tempestuous]

Got my RaLink RT2400 Wireless lan card working under puppy 3.01 with the experimental driver which was already in the driverpack of puppy.

You may be thinking of the experimental rt2x00 driver, but Puppy does not contain this.
Puppy has the (legacy) rt2400 Linux driver, which is quite stable, not experimental at all.

[jonyo]

The box of the card says its an E-Tech WL-101.

Thx for that info. Any detailed info can greatly help others with a search.

[mark2]

The TP-link wn610g v1.1 works in 2.15 using the ath_pci driver.
don't expect problems under 3.01 either

[edoc]

I tried to follow the instructions (below) but am not certain how to proceed. It is very possible that I skipped a step or did something else incorrectly. Here are the steps I followed:

1. Opened geany
2. Pasted in all of the text following "Code:" below.
3. Saved as /root/my-applications/franklincdu550/cdu550.sh
4. cd to: /root/my-applications/franklincdu550
5. Clicked on "cdu550.sh"
6. No errors, just a new "#" prompt

Did I do things correctly?

How do I get Setup - Network Wizard to see my USB modem, please?

Here is the information (direct from Franklin) for getting the Franklin USB EVDO CDU-550 Modem working with Linux.

Quote:
Linux systems already have USB modem driver but needs to assign a device to a special node. After the assignment, user can use the node as a modem device.

Attached file is a shell script to create a node for "C-motech" modem. The script produces nodes which mount modem as a serial device. The CDU-550 modem will be mounted on /dev/ttyACM# where # is a number, for example, /dev/ttyACM2.

Code:
#!/bin/bash
# usb : acm
echo -e "\033[32mMake Modem Device\033[0m"
for i in `seq 0 2` ; do
mknod /dev/ttyACM$i c 166 $i
done

echo -e "\033[32mMake Dual Mode Device\033[0m"
for i in `seq 0 2` ; do
mknod /dev/ttyUSB$i c 188 $i
done

echo -e "\033[32mMake driver rule\033[0m"
/sbin/modprobe usbserial vendor=0x16d8 product=0x5511
/sbin/modprobe usbserial vendor=0x16d8 product=0x5512
/sbin/modprobe usbserial vendor=0x16d8 product=0x5513
/sbin/modprobe usbserial vendor=0x16d8 product=0x5521
/sbin/modprobe usbserial vendor=0x16d8 product=0x5522
/sbin/modprobe usbserial vendor=0x16d8 product=0x5523
/sbin/modprobe usbserial vendor=0x16d8 product=0x5531
/sbin/modprobe usbserial vendor=0x16d8 product=0x5532
/sbin/modprobe usbserial vendor=0x16d8 product=0x5533
/sbin/modprobe usbserial vendor=0x16d8 product=0x5541
/sbin/modprobe usbserial vendor=0x16d8 product=0x5542
/sbin/modprobe usbserial vendor=0x16d8 product=0x5543
/sbin/modprobe usbserial vendor=0x16d8 product=0x5551
/sbin/modprobe usbserial vendor=0x16d8 product=0x5552
/sbin/modprobe usbserial vendor=0x16d8 product=0x5553
/sbin/modprobe usbserial vendor=0x16d8 product=0x5561
/sbin/modprobe usbserial vendor=0x16d8 product=0x5562
/sbin/modprobe usbserial vendor=0x16d8 product=0x5563
/sbin/modprobe usbserial vendor=0x16d8 product=0x6011
/sbin/modprobe usbserial vendor=0x16d8 product=0x6012
/sbin/modprobe usbserial vendor=0x16d8 product=0x6013
/sbin/modprobe usbserial vendor=0x16d8 product=0x6021
/sbin/modprobe usbserial vendor=0x16d8 product=0x6022
/sbin/modprobe usbserial vendor=0x16d8 product=0x6023
/sbin/modprobe usbserial vendor=0x16d8 product=0x6511
/sbin/modprobe usbserial vendor=0x16d8 product=0x6512
/sbin/modprobe usbserial vendor=0x16d8 product=0x6513
/sbin/modprobe usbserial vendor=0x16d8 product=0x6521
/sbin/modprobe usbserial vendor=0x16d8 product=0x6522
/sbin/modprobe usbserial vendor=0x16d8 product=0x6523
/sbin/modprobe usbserial vendor=0x16d8 product=0x6531
/sbin/modprobe usbserial vendor=0x16d8 product=0x6532
/sbin/modprobe usbserial vendor=0x16d8 product=0x6533
/sbin/modprobe usbserial vendor=0x16d8 product=0x6541
/sbin/modprobe usbserial vendor=0x16d8 product=0x6542
/sbin/modprobe usbserial vendor=0x16d8 product=0x6543
/sbin/modprobe usbserial vendor=0x16d8 product=0x6551
/sbin/modprobe usbserial vendor=0x16d8 product=0x6552
/sbin/modprobe usbserial vendor=0x16d8 product=0x6553
/sbin/modprobe usbserial vendor=0x16d8 product=0x6561
/sbin/modprobe usbserial vendor=0x16d8 product=0x6562
/sbin/modprobe usbserial vendor=0x16d8 product=0x6563

[hornplayer]

Computer Dell Inspiron 2500 model
Network card Linksys Wireless-G Notebook adapter 2.4GHz 802.11g
Model # WPC54G v2

Linux Puppy version 3.01

Puppy Hardware - Interfaces application read the
adapter as follows:

Texas Instruments ACX III 54 mbps wireless interface Vendor 104C Device 9066 Kernel module: ACX

Interface ONLY works with NO Encryption...I don't like that...Anyone have a solution?

Number two: When I tried to use ndiswrapper to load a .inf file called "lstinds.inf" I got the following messages:

bcmwl5 driver installed
istinds:invalid

The reason I used LSTINDS.INF file was from some information that this was the driver for this particular TEXAS chip...Apparently puppy linux v3.01 will not accept this module....Unless I am installing it wrong...

I have been a Puppy Linux user for only a week and much to learn...

Another problem: Computer Dell Inspiron B130...using a Dell Wireless 1470 dual band wlan mini-pci card...which has a BCM4318 chip made by Broadcom...I haven't been able to locate the proper driver to work with linux....I tried the module bcm43xxpci doesn't work...unless again I turn off the router's encryption codes....

So anybody out there in the world can give me some help would be greatly appreciated....

[BlackWhizz]

The box of the card says its an E-Tech WL-101.

Thx for that info. Any detailed info can greatly help others with a search.

How do i get the info? I really want to help, but i dont know how?

[Delboy]

Linksys WMP54G (v2) PCI card works well with Puppy 1.07/1.08/1.09 under ndiswrapper

I have just finished a full install and setup of NOP pUppy (based on 3.01 I believe) uisng my Linksys WPC54GS speedbooster card. Unlike several other distros (eg. Tinyme,Sam) the Broadcom chip driver supplied in this Puppy works properly loading it under Network Wizard and using ndiswrapper with the Linksys supplied windows .inf driver doesn't work ("driver invalid"). Great stuff! There is a fair bit of chat in other forums about the broadcom chip not quite working - Puppy works! Speed is good.
This card works well in other distros too using ndiswrapper.
I am using a cheap Micronet wireless and adsl router from Maplins in britain. This works brillaintly with wired ethernet connection into my main PC. box with several distros running live including Puppy.

[Linus]

2WIRE 802.11g PCMCIA (PC Card) H/W Revision 0.3

I finally got this card to work.

Computer:

Compaq Presario 1200 Notebook
AMD K-6 498 Mhz Processor
Type 2 card bus
192 MB RAM

OS:

Puppy Linux 3.01

First I download and installed NDISWrapper-1.51.pet from here:

http://distro.ibiblio.org/pub/linux/dis ... r-1.51.pet

Then I downloaded the windows drivers from here:

http://www.2wire.com/pages/drvrs/twwgpc_2.3.1.3.exe

You can extract this exe with your archiver of choice.

Copy the WlanUIG.inf & the wlanCIG.sys into a separate folder that you will be able to browse to in Ndiswrapper later.

Now do a search for "prism54". I will edit this post later, but basically you need to remove (Move to another folder for safe keeping...do not delete) the prism54 wlan modules so that the network wizard won't automatically recognize your card as prism54 module.

Once you have moved it out of the 2.21.6.7 (or whatever I'll edit this later) folder......open up the network wizard and click on the Load Button.

Then Click on the "More" tab in the new screen that appears. Then click on NDISWrapper and drill down on the left to the folder where you saved WlanUIG.inf & the wlanCIG.sys. Select the WlanUIG.inf.

At this point, it should say:

wlanuig: driver installed
device (XXXX:XXXX) present (alternate driver: prism54)

Click finish.

Now click on the DHCP button if you have you ip address auotmatically assigned from the wireless access point. Otherwise click Static IP and set it up.

Now click on the "Wireless" button. Press the "Scan" button. Select you Access Point. Then click what type of encryption you have setup on your wireless access point (I clicked on WPA2, then entered my SSID and Passkey, changed the security to restricted and left the other selection on managed....unless you connect to you access point through another computer (Which is Ad Hoc) leave this setting as it's default.


My set up on the wireless was :

Wireless G Only

SSID Broadcast: Off

MAC ADDRESS Filtering ON

WPA-Pre Shared Key (WPA-PSK)

AES

9 alphnumeric passkey for testing purposes (I usually use a 63 random alpha-numeric characters (a-z, A-Z, 0-9) from https://www.grc.com/passwords.htm)

Hopefully this has worked for you.

[howarddy]

Interesting set of posts....

I am trying to get Puppy installed on an old Hitachi notebook with 128 MB of RAM and a 300 Mhz Pentium II chip.

I was mostly able to install AntiX Mepis but it complains a bit about the BIOS being pre-year-2000 [its 1998].

AntiX finds and automagically uses my older Zyxel wireless card. Just Boots.

Puppy does not see the card or the PCIMCA interfaces....

Is there a customization I need to perform to get the cardbus interface running??? Or should I try to load the cardbus modules from AntiX, after booting, to get the wireless card running.

Puppy takes up less RAM and look friendlier, so I'd prefer to get it running in the 2nd partition, perhaps as part of a dual boot setup.....