Author |
Message |
Guest
Guest
|
Posted: Wed 06 Jul 2005, 05:29 Post subject:
Wifi-beta dot pup released for testing |
|
Greetings all, well as the heading says this is a very beta release. Would prefer just for the moment for those that are familar with wireless and using nidswrapper to test.
I downloaded the ndiswrapper tarball for vector linux, just to get easy access to all the windows driver files. I then installed each one for puppy and tarred them all up. As you can imagine this is a rather large download, around 3megs but should support many cards.
Once I know the scripts work nicely, no sanity checking for the moment as I just started scripting around christmas last year and have only attempted some rather basic stuff from time to time, I would like to split the scripts and seperate the drivers so it is only a small download.My idea would to be to name each file by it's pci-id and have a table and download link.....
My upload should complete in about 30 minutes, so please wait.
Please read the README.TXT, which is installed into /root/my-documents/wifi
http://www.edgarbrits.net/puppy/dotpups/wifi-beta.pup
|
Back to top
|
|
 |
BlackAdder

Joined: 22 May 2005 Posts: 382
|
Posted: Wed 06 Jul 2005, 21:06 Post subject:
|
|
Have just looked so far, bladehunter, but looks good to me.
Folks had better be aware that they need to have ndiswrapper and Perl installed. I have been tinkering with the versions provided by John Murga.
|
Back to top
|
|
 |
Guest
Guest
|
Posted: Wed 06 Jul 2005, 21:12 Post subject:
|
|
The perl driver is already standard with puppy and perl is not required as that part of the driver installation is already done for the included drivers.
What I want is feedback on the scripts and details of any other cards that need support.
|
Back to top
|
|
 |
drj
Joined: 26 Jun 2005 Posts: 41
|
Posted: Thu 07 Jul 2005, 05:24 Post subject:
|
|
I have two NICs with my laptop (built-in eth0 and docking_station eth1), so eth1 for wireless is no-go for me. I would suggest use wlan0 (ndiswrapper default) to avoid potential conflicts
|
Back to top
|
|
 |
Guest
Guest
|
Posted: Thu 07 Jul 2005, 05:39 Post subject:
|
|
The device name can be set in the wireless.conf file
|
Back to top
|
|
 |
BlackAdder

Joined: 22 May 2005 Posts: 382
|
Posted: Fri 08 Jul 2005, 05:34 Post subject:
|
|
Bladehunter you definitely are a star!
The Airplus drivers include the VID/PID for my DWL-650+ (PCMCIA card) so I ran your dot pup and set up the wireless.conf and now I'm surfing the web using Puppy and the wireless card.
There were a couple of errors reported:
Error for wireless request "Set Sensitivity" (8B08) :
SET failed on device eth1 ; Invalid argument.
Error for wireless request "Set Fragmentation Threshold" (8B24) :
SET failed on device eth1 ; No such device.
Will try to work out what they relate to; eth1 is definitely present and correct. Probably finger trouble on my part.
Don't know what was wrong with my previous attempts to use ndiswrapper with this card, but your version definitely works.
|
Back to top
|
|
 |
Guest
Guest
|
Posted: Fri 08 Jul 2005, 05:43 Post subject:
|
|
Cool...
btw if you run
#cardctl ident
what is the result ?
|
Back to top
|
|
 |
BlackAdder

Joined: 22 May 2005 Posts: 382
|
Posted: Fri 08 Jul 2005, 06:06 Post subject:
|
|
Result is:
# cardctl ident
Socket 0:
product info: "Wireless Network CardBus PC Card", "Global", "", ""
manfid: 0x0097, 0x8402
Socket 1:
no product info available
Interesting
|
Back to top
|
|
 |
BlackAdder

Joined: 22 May 2005 Posts: 382
|
Posted: Sat 09 Jul 2005, 02:21 Post subject:
|
|
Tested some more today.
1. For some reason, the combination of ndiswrapper and the driver does not like Sensitivity, RTS Threshold and Fragmentation Threshold being set by wireless.conf. Allowing them to default gets rid of error messages and does not seem to affect operation, although the thresholds are much higher than those set in the .inf file.
2. Setting the key before setting the ESSID does not turn on encryption. I thought at first it was finger problems on my part (again), but moving key setting to follow setting the ESSID works fine.
3. So far, have been manually invoking the wireless script and then setting the IP address etc. by hand or using DHCPCD. The latter seems to have a problem because it finds old .PID files and thinks that it is already running; will look at that some more.
Once the wireless link is operating it seems rock solid, running for hours without problems.
|
Back to top
|
|
 |
Guest
Guest
|
Posted: Sat 09 Jul 2005, 03:04 Post subject:
|
|
oh Yeah I think I may have forgot about removing the stale files in /etc/dhcpc
|
Back to top
|
|
 |
BlackAdder

Joined: 22 May 2005 Posts: 382
|
Posted: Wed 13 Jul 2005, 02:42 Post subject:
|
|
Well I took a Puppy to my son's place and tried out the wifi dotpup there.
He has an MSI PC54G2 card and a Netcomm NB1300W wireless router.
Up and running within 10 minutes. What more could you ask?
The tail of dmesg below, in case you are interested:
Quote: | PCI: Found IRQ 10 for device 00:0b.0
ndiswrapper: using irq 10
eth1: ndiswrapper ethernet device 00:13:d3:00:46:80 using driver rt2500
eth1: encryption modes supported: WEP, WPA with TKIP, AES/CCMP
ndiswrapper: driver rt2500 (Ralink Technology, Inc.,06/10/2004, 2.02.06.0000) addedPCI: Found IRQ 10 for device 00:0b.0 |
This is another device supported by the RT2500 driver included with the package.
|
Back to top
|
|
 |
Guest
Guest
|
Posted: Wed 13 Jul 2005, 05:05 Post subject:
|
|
Well my firnnd it look's as if you are single handedly beta testing.
Thank you
|
Back to top
|
|
 |
Guest
Guest
|
Posted: Sat 16 Jul 2005, 02:03 Post subject:
|
|
Project canned and no longer being supported.
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8826 Location: Perth, Western Australia
|
Posted: Sat 16 Jul 2005, 05:54 Post subject:
|
|
Don't can it bladehunter.
I'll do some beta testing soon too. I've just been tied up with other stuff.
|
Back to top
|
|
 |
peppyy

Joined: 27 Jun 2005 Posts: 442 Location: VT USA
|
Posted: Sat 16 Jul 2005, 11:00 Post subject:
|
|
I am sure the problem was not with your dot-pup since it seems to perform well with a lot of other cards.
I did farther reasearch on my wifi card and found that all the linux folks said to stay away from it and no reports of anyone getting it to work. Although it used the 8180 chipset the way it accesses the chipset is completely forign and these even had problems on vindows machines.
I will report that I bought an Orinoco Gold Classic card. Plugged it in, Booted up and was online. no config at all. Pupp 1.0.3 is one smart pup. Dont loose those drivers!
_________________ Puppy Linux...
It just works!
|
Back to top
|
|
 |
|