Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
Right Now Im Running a Dual Boot System (WinXP and Fedora Core 5) with GRUB installed as my boot.
I boot into FC5, and ran: u name-rm to find out what kernel devel headers I needed and installed the correct ones using the .rpm package.
After installing the kernel headers located in (/usr/src/kernels/2.6.15-1.2054_FC5/) I proceeded to install NDISWRAPPER so I could get my D-Link DWL G132 Wireless Adapter Working.
Ok so back to NDISWRAPPER. I extracted the tar file and then changed to that directory in the Terminal. Then I ran the following commands, having no errors throughout the installation:
make dist clean
make install KSRC=/usr/src/kernels/2.6.15-1.2054_FC5/
After Installing NDISWRAPPER successfully, I shut down the comp. for the night. This morning when I went to boot into FC5 it does the usual..
Uncompressing Linux Kernel etc..
Starting UDEV.. Then all of a sudden I get this huge page of error code with paths having ndiswrapper in them, then it says: Continuing in 120 Seconds and countsdown...then nothing...with all of this error code and it will boot no further, so I just have to shut down. Please help me.!!! I can only guess this has to do with NDISWRAPPER because it is the only installed prog. off a fresh FC5 install, with proper kernal and kernel headers. What is wrong?
If you still need to be able to get access to the machine, try booting into single mode (at the GRUB boot prompt, select the kernel you want to use and add the word single or the number 1 after the name. Single mode loads only the very basic stuff necessary to run the computer, so you should be able to get to a command prompt and uninstall ndiswrapper.
As far as what is going wrong with ndiswrapper, we're going to need to see the error getting spit out in order to give any sort of guess.