Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
the debug-option is turned on in the Makefile of the the driver-source, there is no command-line-option as far as I know (simply remove # in front of DEBUG,
do this before you try any make command).
Modprobe will not find the module if it is not fully installed(and you need the alias command in modules.conf). Please download latest CVS(best working I think) and do a 'make clean && make install' after(!) cding to the source directory of ndiswrapper....
than install your driver ...
-ndiswrapper -i <inf-path>
add the module alias...
try to load the module
if that does'nt work you may try
-insmod ndiswrappper(sometimes worked for me)
you may add your init commands (iwconfig,ifconfig route etc) to /etc/init.d/boot.local or what ever the requirements of your distro are....
I couldn't get the cvs...I tried re installing and i got errors. I turned on debug and I got even more! I give up....Ndiswrapper just won't work with my computer. I will never get anything to work. Ever. I'll keep checking back here but I doubt anything will ever get this computer to work.
If its any consolation, ndiswrapper seems to be one of the more difficult pieces of software to get working. It seems to either work right off the bat or it is a real struggle to get it working. By the way, turning on the debug is supposed to give you more errors. If you feel like it, post the errors and we can see if anything makes sense.
BTW, are you sure this is one of the Linksys cards that uses the Broadcom chipset? I've been assuming so, but you might check the output of lspci just to be sure. If it is an older WMP11 card, we may be barking up the wrong tree with ndiswrapper.
I really don't know. Supposedly the broadcom chipset is only on a card that serial number starts with BB727 and this one doesn't I was trying linux-wlan-ng but when I got to the linux source tree question in the config, it shot out tons of errors. I was going to upgrade my kernel, but I burnt the kernel to a cd on a windows computer and it turned out nothing was on it!
Oh--I just didn't feel like putting the errors on a floppy again..I had tried with the darn .RPM and it said that it needed some file called VMLINUZ.EL I searched google for it and I couldn't get anything. I even searched freshrpms.net
OK, to check on the card chipset you can use the lspci command. Post the output if you can't spot your wireless card.
The other question I have is this: Is your kernel source code installed? In order for ndiswrapper to compile properly, you need to have the source code for your version of kernel installed. If it isn't, you can install it from either your original CDs or from the RH website. I'm suspicious about the errors starting with questions about the source tree. I'm also going to guess that VMLINUZ.EL is a kernel related file. VMLINUZ is the name given to the kernel file. All of this suggests to me that the source code isn't there. By default kernel source code usually isn't installed since it takes up a chunk of disk space.
Dang. I was hoping that would be a bit more informative. However in digging around, it looks like Linksys started using the Broadcom chipset when they started making the WMP11 compatible wiht 802.11g. So if your card is compatible with g, then we have to take the ndiswrapper route. If your card is only capable of 802.11b, then the Prism drivers are the way to go.
it spit out errors no matter what i answer at the linux source tree question in the config...
Well, it is probably going to do that if you don't have the proper kernel sources installed. In fact absolutely ANY modules you try to compile aren't going to work unless there is kernel source code installed. So as a first step you need to get that installed. In fact if you can't get the kernel source installed then we might as well give up now because that is an absolute requirement for moving on.
Once you have that done, you may need to upgrade the firmware on the card. According to this site you need the latest firmware for it to work with Linux. The downside is that you have to be in Windows to run the Linksys update software. Do you have a Windows box that you can put this card in?
I'm not sure you want to go the prism54 route. Looking over their list of supported chipsets, it looks like this card isn't supported. I think that we stand a greater chance of success with the linux-wlan drivers.