Now I just got hold of a dlink dwl-510 which uses the same chipset (atheros)...At the moment I'm running a 2.6.8 kernel on Slackware with the madwifi driver in master mode (ie access point)....All seems to be working fine.Once Barry decides on a kernel version for Puppy 1.0.3 I'll compile the drivers and forward them across. The only problem is that ad-hoc mode is "broken" according to the madwifi site..
So hopefully this will take the dependency away from ndiswrapper for these chips.

BTW in master mode (AP mode) it can also be used to bridge a wireless network to a wired network...

"Facilities"? Yes. "Abilities?" Maybe not so much I can put together a hard drive install on my primary 'puter with plenty of room to grow and work. So hardware and space aren't problems. I've never remastered a puppy before, though, so...it would be murky waters for me.

But I'm willing to give anything a shot, if folks are willing to help me along.

Well it's not really a full remaster, just redoing the iso, which can be done from windows, with the the new kernel. I'm pretty sure the instructions are on Barry's site. Well any way if not I can supply the required instructions for you. May take a day or so to get it built and sent off, but real glad to see you haven't let this die.

compiled them remade the initial ramdisk with the drivers (it's now 16MB uncompressed)

booted up with my new kernel

executed

#modprobe ath_pci
#ifconfig ath0 192.168.1.130 up
and as if by magic it connected to my Access point (no encryption or security yet)
and now I'm typing this on Puppy-1.0.3 on my Dell lappy (with neomagic card)
if you would like and if you have a hotmail account that can take large email attachments I can post you the new image.gz and vmlinuz (kernel) to get you card going.

I've been working hard with the same problem. I have an Atheros card, and some distros pick it up, others do not. None have out of the box. My successes have been with those that have the MadWiFi drivers and KDE, such as Slax and PCLinuxOS. I'm still having trouble with getting them to speak with my Wireless hub since I'm using WPA encryption rather than WEP or none at all.

Bladehunter,
I'm using the 2.4.29 kernel right now, thinking of moving onto that for Pup 1.0.4.
I've compiled it with framebuffer support (although only vesa2 and vga16) and acpi.
What extra crypto support do you need in the kernel? From memory, I think that I enabled md5sum, aes, des, crc32.

Bladehunter, I had PMed you with my email address (in an attempt to avoid it being picked up by spam bots), but if you're uploading a full ISO, there's no need to email me image.gz. I'm anxioius to see if this works! Thanks for all of your efforts!

Guess who is typing this message from his girlfriend's finally-working-with-puppy-and-pcmcia-wireless laptop 'puter? That's right, it's me!!

I downloaded and burned your iso (had to burn it in windows, as I couldn't get puppy to burn...that'll be another post), and fired everything up. Then I typed:

modprobe ath_pci

got some warnings, but the modules loaded (if you're surprised to hear that i got some warnings, I can post them for you). I then tried some random things with ifconfig and iwconfig, but because we're using dchp on this wireless router, I wasn't sure exactly what to do. so finally I just punched in:

dhcpcd ath0

and it's working like a charm! I added the two commands to etc/rc.d/rc.local and it works automagically upon boot! So, this saga of...urm....ten weeks? is now officially over! Thanks very much to everybody for the help and for sticking with me through all of this. I really really appreciate it. And my girlfriend is really really annoyed that every time she wants to use her computer, I'm using it in puppy.

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