Wifi-beta dot pup released for testing
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
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
- BlackAdder
- Posts: 385
- Joined: Sun 22 May 2005, 23:29
- BlackAdder
- Posts: 385
- Joined: Sun 22 May 2005, 23:29
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.
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.
- BlackAdder
- Posts: 385
- Joined: Sun 22 May 2005, 23:29
- BlackAdder
- Posts: 385
- Joined: Sun 22 May 2005, 23:29
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.
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.
- BlackAdder
- Posts: 385
- Joined: Sun 22 May 2005, 23:29
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:
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:
This is another device supported by the RT2500 driver included with the package.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
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!
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!
It just works!
sadly you missed my comments/feedback
I see a few minor issue with it
1. eth1 has been taken on my machine, I had to use wlan0 (and think it SHOULD BE the default, no real gain to use eth1 for wireless)
2. rc.network called in rc.local0, before calling rc.wireless from rc.local, it errored out saying can't find interface or something similar
3. I had to remove dhcpcd-wlan0.pid to allow another dhcpcd refresh
4. so, I put followings in my rc.local
. /etc/rc.d/rc.wireless
rm -f /etc/dhcpc/dhcpcd-wlan0.pid
ifconfig wlan0 up
dhcpcd wlan0
I see a few minor issue with it
1. eth1 has been taken on my machine, I had to use wlan0 (and think it SHOULD BE the default, no real gain to use eth1 for wireless)
2. rc.network called in rc.local0, before calling rc.wireless from rc.local, it errored out saying can't find interface or something similar
3. I had to remove dhcpcd-wlan0.pid to allow another dhcpcd refresh
4. so, I put followings in my rc.local
. /etc/rc.d/rc.wireless
rm -f /etc/dhcpc/dhcpcd-wlan0.pid
ifconfig wlan0 up
dhcpcd wlan0
bladehunter wrote:Well my firnnd it look's as if you are single handedly beta testing.
Thank you
Belkin 802.11g F5D7000 working
This was a great job from bladehunter. I am up and running and posting this over wireless.
Card identified under PCI devices as Broadcom Corporation BCM94306 802.11g
(Rev3)
There were two issues:
The bcmwl5.inf file must have become corrupted as Puppy insisted it was an MP3 audio file despite the .inf type. For safety I copied both the .inf and .sys files from the Winblows driver disc and alhtough the system log says beware, all seems well!
I also had an old ethernet card installed and had to use wlan0 to make everything spring to life.
Card identified under PCI devices as Broadcom Corporation BCM94306 802.11g
(Rev3)
There were two issues:
The bcmwl5.inf file must have become corrupted as Puppy insisted it was an MP3 audio file despite the .inf type. For safety I copied both the .inf and .sys files from the Winblows driver disc and alhtough the system log says beware, all seems well!
I also had an old ethernet card installed and had to use wlan0 to make everything spring to life.
don't close the project! :(
This is a great project.
I just got "pupped" this week and used this to get my DWL-650 up in no time.
Will try another card (DWL-G630) this weekend and let you know.
Added to /etc/rc.d/rc.local:
No changes to /etc/rc.d/rc.wireless
/etc/rc.d/wireless.com is
WEP works great. DHCP assigns an address. Presto.
Relevant dmesg:
Only error I have is:
But no effect. I have commented out FREQ in the wireless.com (in favor of CHANNEL), so I'm not sure why it's trying to set frequency.
Let me know if you need any different beta feedback.
I just got "pupped" this week and used this to get my DWL-650 up in no time.
Will try another card (DWL-G630) this weekend and let you know.
Added to /etc/rc.d/rc.local:
Code: Select all
. /etc/rc.d/rc.wireless
dhcpcd eth1
/etc/rc.d/wireless.com is
Code: Select all
ESSID="xxxxx"
MODE="Managed"
CHANNEL="xx"
KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxx"
Relevant dmesg:
Code: Select all
ndiswrapper version 1.1 loaded (preempt=no,smp=no)
hermes.c: 4 Dec 2002 David Gibson <hermes@gibson.dropbear.id.au>
orinoco.c 0.13d (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.13d (David Gibson <hermes@gibson.dropbear.id.au> and others)
eth1: Station identity 001f:0004:0001:0003
eth1: Looks like an Intersil firmware version 1.3.4
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, xxx-bit key
eth1: MAC address xxxxxxxxxxxxxxxxxx
eth1: Station name "Prism I"
eth1: ready
eth1: index 0x01: Vcc 3.3, irq 9, io 0x0100-0x013f
Code: Select all
# . /etc/rc.d/rc.wireless
Using /lib/modules/2.4.29/net/wireless/ndiswrapper.o.gz
insmod: a module named ndiswrapper already exists
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth1 ; Operation not supported.
Let me know if you need any different beta feedback.