This is very strange... I looked very closely at everything that happenspeppyy wrote: I know for certain on the Senao card that it will not scan unless I load a profile first, even a blank one works on Dingo 4 (kernel 2.6.21.7) I will try to gather all my cards and test each one individually as soon as I find the time.
when you do something like load a profile, then at what happens when you
press the "Scan" button, and cannot see anything that can affect the scan...
Pressing the different buttons just sets various GUI-related parameters,
while running the scan literally does just that -- run "iwlist $INTERFACE scan"
(except for the Prism2 card, which uses wlanctl-ng) -- and then parse the
output.
So the only thing I can think of which might be the cause is some timing
problem(?), where the extra delay before the scan does the trick... which
is odd, since I assume you don't always run it immediately upon boot, so
quickly that those couple of seconds matter.
Maybe you should try running a scan manually (iwlist $INTERFACE scan) before
you do the profile loading/button pressing -- see if the scan really fails
or it is the wizard (you'll need to run ifconfig $INTERFACE up before scanning).
Also, maybe try running "tail /var/log/messages" and see if something
happens that might be related to the interface...
No, it's something that Barry needs to sort in the startup scripts:I just looked again and this time it loaded the hostap_cs module. These cards, Senao, nl-2511cd plus seem to be detected differently every few times they load. Could be a bad batch of cards?
First, the prism2_ modules support the same devices as the hostap_ modules,
but the hostap_ are in-tree and should be the ones used. The only prism2_
module that actually should be included in Puppy is prism2_usb (since there
is no usb support in the hostap_ drivers) -- that is how it used to be in
the past.
Second, I just checked the modules.alias file for my 2.6.24 kernel and it
turns out a lot of device IDs matching hostap_cs also match orinoco_cs!
So you need to get Barry to do something about it -- give one preference
over the other at boot time.
To see the overlap between the two, the following command can be run:
Code: Select all
grep 'hostap_cs\|orinoco_cs' /lib/modules/`uname -r`/modules.alias | sort
then you just look for identical adjacent lines ending with orinoco_cs and
hostap_cs.
(Turns out there is also overlap between orinoco_nortel and hostap_plx,
orinoco_plx and hostap_plx, orinoco_pci and hostap_pci, and orinoco_tmd
and hostap_plx! Tempestuous, where art thou? It seems the hostap drivers
have been updated more recently, so maybe they are the better ones? Also,
they support WPA in the wizard.)
Yes, RutilT is very useful for quickly connecting and getting stats aboutNow I am off to look into rutilt. I do a lot of wireless network bridges, routers and repeaters and that has been very helpful when it works.
the network, but it doesn't have all the little tricks we use to get things
working in the wizard... (also the set_ip.sh script could be improved.)