Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I, as many other Atheros wifi users, am having trouble with my Wifi. I'm on an Asus X58C Laptop with an Atheros AR5B91 integrated chip. I have loaded what I am told is the relevant in-built driver and it fails to recognise what is there. I have also tried NdisWrapping the xp driver (the program told me that vista drivers don't work) but still no luck, I tried the vista driver too just in case still no device registered.
Then I discovered MadWifi, which I thought might just do the trick. I downloaded the latest version (a tarball), extracted it and got stuck.
Linux Puppy 4 Can't do 'Make' and can't do 'Apt-Get' and the Petget repository is very small, I can't seem to make MadWifi work at all, I know other Atheros wifi users got theirs to work with Madwifi in Ubuntu but Puppy doesn't the tools to complete the install and I don't know how to get them.
I'm a little lost, I'm only a noob really, but if you give me an instruction i'll have no problem executing it, I've overcome bigger problems than this, but it seems no one has tried this before so I've no frame of reference.
Basically, you'll need devx_XXX.sfs ("XXX" being a number corresponding to your Puppy version).
After installing that, it's getting the source, then do
# make clean
# make install
from the unpacked source's directory, and you're ready to use Puppy's tools to get a connection (NB. make clean's only a safety precaution to avoid conflicts - if you're sure there's no MadWifi version in the kernel, you don't have to do it). If there's no new device yet, do
Really appreciate the reply,I'm going to do as you say and get devxxx.sfs
as there are lots of things I can start using it for, but I'm afraid I found a madwifi '.pet' so I got it installed with no fuss in the end, I didn't use a terminal I just double clicked so no Make CLean was likely to have been performed.
Problem is, nothing changed. I'll be honest and say I'm not sure what madwifi is but I think it's just a set of drivers, and if this is the case there seem to be no new ones on my system and the problem persists.
If it functions as an app, where is it? It's still as if Network adapter AR5B91 doesn't exist when everything tells me that the driver I've loaded is the correct one.
Do you thinks it's my shitty SiS chipset?
Do you think 'Make Clean' would help update the drivers?
Any more help would be, once again Hugeley Appreciated
Are you using Puppy 4.0? What kernel version are you using? 4.0 is getting old. You would have to look for a madwifi pet that supports your particular kernel version.
You could also try Puppy 4.2, Fatdog 112, NewyearsPup, Unnamedpup, Slaxerpup or some of the 4.12 derivatives like Boxpup and Nop etc.
I have found Fatdog, Nyp, Unnamedpup, and Slaxpup to have excellent wireless support and I would be surprised if your wireless did not work out-of-box. They all have more recent kernels than stock Puppy.
Another problem is Network Wizard. It should be updated to the newest version (Apr.2) in any Puppy version. Rename the tar.gz to .pet and it will install normally.
make clean makes sure that old versions of the driver are removed - to avoid conflicts. I don't use Puppy a lot, and I don't have a version around to check, but if a version of MadWifi is in the kernel, it'll be cleanly replaced if you start the sequence with make clean (works on my box every time - on Ubuntu 8.04.2 LTS, I have to recompile after each kernel upgrade, never failed me, though a different version of the module is already present in the new kernel).