After having given a good portion of my life to this problem, I turn to you fine people. Sorry if I make little sense as I'm a noob to Linux. Main Question: Where is /etc/modprobe.d in the newest puppy linux? I can say for certain the it isn't in the normal location. Secondary Question This is regarding the SMC 2802w V.2 on Linux Puppy 4.3. I'm having issues with ndiswrapper. The card is recognized but is unavailable under network wizard. This is what I did so far: depmod -a ndiswrapper -m ndiswrapper -l 2802w : driver installed device (1260:3890) (alternative: Prism54) alias wlan0 ndiswrapper ifconfig (card was identified as lo and not wlan0) On Linux mint 5 I did all that and also blacklisted prism54, prism54pci,p54pci but nothing worked even after reboot. The built in Prism54 driver is meant to work fine with my card but after many attempts to get that working, the most I got was recognition of the card as eth1 but I was unable to connect to any networks but that too was on Linux Mint 5. Any help at all will be greatly appreciated. I have read at least 50 different forums and I think I'll be forced to buy a different wireless card now. I have so much respect for Linux but problems like this are a big turn off. I intend to stick with it though.
Why don't you go and ask the good people on the puppy forums? They will know exactly what the problem is and will be able to advise. http://www.murga-linux.com/puppy/
I've never been able to get any non-Broadcom chipset cards to work under Puppy or other linux distro's yet myself, if you've researched/faffed about as much as you say you have, it's time for a known working card, at least the existing card will work under Windows. It's just not worth wasting time on stuff like this, just research the most compatible/cheapest card and buy it. I have 3 D-Link DWL-650's that have Prism drivers, they work perfectly under Windows but refuse to work under Puppy or anything else, i too wasted far too long trying to get them to work, sometimes you just have to realise that your free time is more valuable than the cost of a new card
You're both absolutely right and thank you very much for your replies. I could invade the puppy forums but it seems time for a new card. I bid you both a good day.
Very true creakster.. linux+cheap=works fine these cards have a certain aspect of "winmodem" about them.. a bad habit that should be stamped out.. you buy hardware, you expect to GET the hardware, not some software emulation of it.
I've always thoroughly researched any PCI or PCMCIA cards i've bought, to make sure they work under linux. For PCI that meant WMP54G cards and for PCMCIA it means Belkin - have loads of WMP54G and 3 Belkin PCMCIA; the Belkin's i have are all Broadcom chipset, i'm a Broadcom/ndiswrapper advocate myself. I'd bought the DWL-650's really cheap and specifically for Windows machines, but they're now sat in a draw as any laptops i have are usually dual or triple boots, therefore the Belkin's are perfect for whatever OS is on the laptops hence why the D-Links are consigned to a draw. Spooky, was talking about ndiswrapper & Puppy linux only yesterday ~ http://www.dd-wrt.com/phpBB2/viewtopic.php?t=61326 *edited for spelling*
http://opensource.bureau-cornavin.com/belkin/index.html I got the SMC card for free from a friend but I always do my research whether it's windows or linux. That's good advice though. I just placed a bid on this belkin usb adapter and according to this site it's fully supported.
I'm not familiar with the first two, all my Ralink stuff is RT2500 and RT61, so maybe those will be ok. Never heard of Zydas but Prism is mentioned there. So i'd be wary of that Belkin being as it's a lottery as to which chipset you end up with. Maybe the seller can provide more specific info. If it was me i'd go with an WMP54G as they will 'just work', they're very common and should be quite cheap. I bought all mine a few years ago new on Amazon, they used to be around the £17 mark back then edit- in fact there's one on (UK) eBay now, £7.99 buy-it-now plus £1.50 postage, what a steal. edit- just remembered, it's a bit late now but i did go to town on the in's and outs of ndiswrapper a couple years ago ~ http://forums.afterdawn.com/thread_view.cfm/563575
I have belkin everything.. bluetooth, and the firmware on my homebrew router.. don't do wireless.. if it don't work I just plug a wire in.
To solve my wireless problem for now I use my WAP54G Access Point as a wireless bridge. It works perfect, and I bought a WMP54G last week but haven't had a chance to test it yet. I have every intention of posting my results in the interest of thoroughness. I should add that I believe my problem was entirely caused by the linux distros used. I believe that if I carried out the same steps in PClinuxOS which I'm running now, it would work. I also intend to post those results when I get around to testing. Any additional info on the subject is still welcome. And Creaky that old link you posted and all your advice was informative, so thanks for that. RANDOM SIDE NOTE: For those that also wish to use the WAP54G as a wireless bridge but are concerned about the standard linksys firmware not offering WPA security, I highly recommend installing the alternative firmware DD-WRT which is actually fully functional on the WAP54G now and has WPA AES+TKIP. This is the version best suited for the WAP at the moment. http://www.dd-wrt.com/dd-wrtv2/downloads/others/eko/V24_TNG/svn12548/dd-wrt.v24-12548_NEWD_micro.bin A hard reset must be carried out directly before the flash and 5 minutes after the flashing process. It takes a total of 1 1/2 minutes and the reset button remains pressed the entire time. 1.Press and Hold reset button 30 seconds 2.While still holding reset pull out the power and continue holding for 30 sec 3.Still holding reset plug power back in holding for 30 seconds 4.You're done Once you've got that setup I suggest you turn off all routing functions since the WAP isn't a router. Now go to http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge in order to help you setup the wireless bridge. I couldn't get the linksys firmware to work for the life of me but the DD-WRT works flawlessly and my computer still uses DHCP which is perfect as setting up a static IP can get irritating.
Excellent, thanks for the update. Glad to hear that about DD-WRT also (check the routers in my signature), you might want to check out Static DHCP so that devices always get the exact same IP address. I have about 20 addresses listed in mine, it's great not having to guess which ones are which.
