Do not know about the wifi-driver thing...If driver present and recognized (including firmware drivers) they are normally loaded during boot...If the extra driver are not present at boot but installed after boot they might not be picked up - but unsure how to get you further there. I think if the right drivers are loaded ifconfig/iwconfig will give you some response...
I have the SNS--retro working with pupngo2012 on an asus eeepc900 and on stationary pc with usb-zd1211 wireless-stick. Also the wired network adapters on both machines are recognized and connected.

if anyone is looking to do a no-rox version, I wrote some C that checks file extension and gives you the MIME-type:
http://murga-linux.com/puppy/viewtopic.php?t=80916
These are the ones that (by default - not necessarily in pet packages) are semicolon separated in .desktop files as
MimeType=application/vnd.ms-asf;application/vnd.rn-realmedia;...

...of note, the Dell C600 (it's xvesa friendly ) I used this time has no ethernet connector IIRC. (The CPi doesn't either.)

I think we need a copy of the "wireless module loader/tester" from Classic Network Wizard. I'd say port the whole thing over... but it's a goodly bit bigger, to say the least.

Unfortunately, I have no idea if it's one single script or a collection. I suspect one single script, which will make lifting out the loader-tester portion that much harder. I'd have to go looking to be sure tho._________________

and does "ifconfig" show any change after each of those? Also, goingnuts suggested to me to "Try to look in /tmp/interfaces to view what interfaces was found". Does that contain any info? If not, does anything show there after you try to run the wireless manager wizard?

/tmp/interfaces does not exist, as a file or directory. /tmp/ has a number of files, but the only directory is /tmp/.X11 . (I assume it is not to be a file? There isn't one with that name anyways.)_________________

Burnt a closed CD, and this laptop does not have a hard drive -- and it has only one USB port, and my experience with pUPnGO is that it does not like hubs. So no savefile.

I could remaster it with Woofy to include the pet so that I could boot with it like that, but I'm getting low on CD-Rs (again) and the local stores do not sell -RW discs

So the in-there-at-boot-time test will have to wait.

As for your other question... I do have an old Prism2 card out of a router that I can try... it's Wifi "b" rather than "g" but I don't think it'll slow the entire network to a crawl if I use it... just the one connection. Let me go see if I can find it, and I will try it. That I *can* install before booting.

EDIT: nada. Although I may have an idea of the issue... the SNS shell script (as carried over into SNS-Retro) references a file I did not know about listed as /etc/simple_network_setup/connections . I will try to hunt down this file and see if adding that in fixes things.

EDIT: looks like /etc/simple_network_setup/connections is /generated/ by SNS. Either way, copying it over from Puplite 5 does not appear to affect anything. My best guess is that there is some module-chaining not going on. Perhaps modules.dep is not being properly altered with the drivers sfs? (I suspect this because I ran into some errors with that while trying to manually load various modules.)_________________

starhawk: You really are working hard on this! Sorry the network does not turn out as we hoped - I looked into the traditional network-setup script but it might not solve the problem to port it - and it will be a huge work to do. I don't think there was a "pUPnGO-2012-compliant" sticker on your hardware when you got it...
I will try to cut out the module loading/testing part from the old network setup script but it might take a while before I can post it...
Do you have a USB-wireless adapter? If so it might be worth a try...

* Rosewill is the generic 'store brand' of Newegg[dot]com.
** This card is from a D-Link router. A friend gave me the card; apparently it was not the cause of his router's demise.
*** Tried both drivers, no go.
# Madwifi (ath_pci) does not load in pUPnGO, complains that ath_pci is not found in modules.dep -- editing that file to fix, causes other different errors (probably loading/chaining modules in wrong order so it errors out).

All driver information from WikiDevi. They have some REALLY nice and useful info!

One other thing: rc.pcmcia might be faulty -- I had problems with a USB hub cardbus card at one point -- just that it wouldn't recognize. I blamed it at the time on the fact that it was during my one USB boot, BUT we might have a problem there after all. (Or not. I don't know for sure!)_________________

starhawk
Might be a firmware problem. Try running the firmware installer from the menu.
If no joy, try unpacking the tarball in /lib/modules/all-firmware/ AND putting the firmware files in /lib/firmware/###/
Then stand on one leg, rub your belly and sing "My Old Man's a Dustman" in Kurdish.
YMMV
[/b]

Sometimes firmware does not get installed properly - don't really know why, and it is not exclusive to pupngo. I had problems with my pcmcia card which use the b43 module.
If the firmware installer does not identify your module, check
/etc/modules/firmware.dep.2.6.25.16, and see if it is listed. It can be added manually if needed. But you may have to practice your Kurdish...

starhawk - When you insert/remove your wireless interfaces do you see those changes reflected in Dmesg? Also, I guess the pcmcia interfaces may be detected differently depending on whether the port is set for cardbus or 16bit - does your bios offer any control of that?

I tried a variety of wireless adapters last night in case I could offer any useful fragments of info and the results I got varied quite a bit. Of course my hardware is different to yours (this testing was with a 10 year old Tosh laptop but I'm hoping to try a Dell Latitude cpt later in the week..)

1) I do get your "ifconfig: SIOCGIFFLAGS: No such device" error if an interface is not able to be detected for some reason. Sometimes a hotplug got me past this.

2) The /tmp/interfaces file that goingnuts got me to check is not always there. It only showed up after I ran the wireless manager and clicked "connect". If there was a useable interface that the wireless manager recognised it would create the /tmp/interfaces file. The name given to that wireless interface would be different for different cards. Some cards would be referred to as eth1 and some as wlan0.

Wireless lan adapters I tried in pUPnGO:

EDUP usb adapter ED-1296 uses zd1211rw .Detected ok at boot and/or after boot. Detects as wlan0 via wireless manager. (also brings up a "wmaster0-oo showing in ifconfig). (This one took a bit of mucking around to successfully pick up an IP - had to manually run dhcpcd then rerun wireless manager). Websurfing ok.

Compex WavePort WL11A+ pcmcia adapter. Dmesg was aware of card being inserted and removed but wireless manager did not detect and no relevant module seemed to be loaded. (Got a feeling I saw a note somewhere that this needs special treatment before it becomes visible. Maybe firmware). Couldnt surf web.

3com 3CRWE154G72 pcmcia adapter. Did not detect during boot, but did detect after hotplug. Showed up as "p54: LM86 firmware (seems to be a cardbus card). Wireless manager was able to bring this up as wlan0 and could surf web fine.

Inbuilt Intel 2200/2915ABG wireless card. Uses ipw2200. Detects as eth1. Wireless manager cant make it work but I can make it work via cli. Web surfing fine.

I don't understand why some cards cause a "wmaster" to be found/set up and others don't.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum