Toshiba Satellite A105 - FC6 not recognising wireless card
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Toshiba Satellite A105 - FC6 not recognising wireless card
Hey, I have a Toshiba Satellite A105-S4014. I just installed Fedora Core 6 on a fresh hard drive, and everything seems to be working fine, except that it is not picking up my wireless device. It worked just fine on the same computer when I was using Ubuntu 6.06/6.10. I tried adding a new wireless device from the Networking tool, but when it comes time to pick which wireless device I am using mine is not on the list. There are 3 or 4 Intel devices on there, which is what mine is per the Satellite user manual, but none of them are the right one, and I have tried each of them to no avail. Any advice?
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Need to know what brand, model, and version it is.
Post output from /sbin/lspci command.
Might check out this site for help. http://www.linux-laptop.net/
It tells me the device is an Intel Corporation PRO/Wireless 3945ABG. I dunno if this is quite what you are looking for... I apologise for my lack of understanding -- networking is the one thing I have never had to figure out on my own, every distro in the past has automated it.
I found the source for the driver on Intel's website and I built it, and it said everything was fine, but it still doesn't recognise the actual hardware. I know I probably need to install something relating to the firmware, but that is where my knowledge stops.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I believe that module package is not installed as default FC6. Point us to the link you have for the driver and the info you used to install. This way we are all on the same page.
Grr... alright, now I have yet another issue. I found the installation instructions in the package, but when I followed them I installed, per the instructions, the IEEEE 802.11 network stack. Apparently when I installed it it tore apart the references and such to the original version (as would make sense) but it didn't replace them with the new stuff, so now when I try to use any of the commands in the IEEEE set it gives me a "command not found", and I don't have any idea what to do...
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I read the install and run the setup to the end with no problems. Not sure where you are at with the problem. Detail the steps you did and results from each step.
Alright... I did everything per the instructions, and it went fine, I suppose, up until it said to check the existence of the device with
%iwconfig eth0
I did this and it gave back that iwconfig was not a recognised command, nor is modprobe or any others that are related. Am I missing something?
Also, I bought a wireless card, a Netgear WPN511 PC card, because I needed it for Windows anyway. It was not recognised in the list of wireless cards, and there was no Linux driver support, so I turned to madwifi. For some reason MadWifi won't build... it gives me an error, and says that it's missing "linux/header.h".
The iwconfig, modprobe, and other similar commands are done with root privileges. You can do these ina terminal by using the "su" command or the "sudo" command.
So if you are running as your normal user inside a terminal or console, enter the following:
su
<You will be prompted for the root password>
enter the iwconfig, modprobe, etc.
When you are done enter:
exit
You will be returned to your normal user privileges.
As for the missing linux/header.h, that means that the madwifi build process is looking for the kernel source code files
I su'd and the same thing happened... it says the command was not found. Normally it would say that I do not have proper permissions, but it is telling me the command was not found.
Ah, of course... should I have pointed it at my source files with a flag of some sort?
I'll check out the RPM. Thank you very much.
Does your Linksys WPN511 card use the Atheros chipset? If is does not use the Atheros chipset the Madwifi drivers will not do you any good, as Madwifi is designed specifically to support the Atheros chipset devices.
Run /sbin/lspci from a terminal with the device installed (if it is a PCI device), and you should see an entry in the output listing with some information. You should see entries for both wired and wireless network cards if both are installed.
Once you determine the chipset your wireless card uses, you can research to determine which drive you need for that particular chipset. Before you do almost anything with wireless configuration, you need to know the wireless chipset if you are driving to get a wireless driver working.
Oh, I know it uses the Atheros chipset. I know madwifi will work, it's just a matter of getting there.
*sigh* I am so confused... unless I'm missing something, Ubuntu was way better. Ok, to start with, rpm packages associate themselves with Archive Manager - for some reason they don't install when you dbl-click them, at least not now. I know they used to, or is that just a Gnome thing? I'm using KDE... I don't see why it would make a difference though.
Second, I tried to install it from the command line with "rpm -i kmod-madwifi-whatever.rpm" and it said it needed a different kernel... I found another rpm package for it elsewhere on the internet, and I tried to install that with the same command, and it said it needs dkms. In short, I have no idea what is going on.
Alright, I installed the package with yum. It took some hunting, but I finally found out why I couldn't get the bugger in the first place - I didn't have the proper repository in my lists.
Now, the thing is, madwifi.org tells me to go with "modprobe ath_pci" but, as mentioned above, the command "modprobe" is "not found". What am I missing? Do I not have a certain package installed or something?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.