ndiswrapper and wireless drivers with newer kernels... third time the charm?
FedoraThis forum is for the discussion of the Fedora Project.
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.
ndiswrapper and wireless drivers with newer kernels... third time the charm?
What I mean by "third time the charm" is that I've posted this problem on the ndiswrapper AND fedora forums and not gotten ONE answer. This'll be the third place I'm posting this. I hope you guys can help.
I have to use the 2.6.15-1.1831_FC4 kernel, because if I use any newer kernels, the driver's functions become useless.
iwlist wlan0 scan returns an error that the interface does not support scanning (when it actually does)
iwconfig wlan0 shows the correct configuration, except for the AP MAC address field, which is simply listed as "Invalid".
ifup just gives the error that I'd expect: that there's no link and I should check the link cable. This error doesn't mean much, since it occurs in my currently working kernel and wpa_supplicant and dhclient can still bring up the interface fully afterwards.
So what is it that I'm missing here? Is wireless support disabled in later kernels? Do I need to recompile wireless tools as well as ndiswrapper for new kernels?
This has been bothering me for more than a month. I'm ready to resort to violence here.
The strange thing is that I found the solution for this problem... I've only found it listed in one place!
My card is a linksys WMP54GS, which has a broadcomm chipset on it. What I needed to do was install bcm43xx-fwcutter and use it to get the proper missing files from wl_apsa.o. Apparently, kernels beyond that FC4 one need those files but don't provide them.
Now, I'm up to 2.6.17-1.2174_FC5!
My new problem is a common one... why am I getting this error when attempting to install kmod-nvidia?
Error: xorg-x11-drv-nvidia conflicts with selinux-policy < 2.2.29-2.fc5
The strange thing is that I found the solution for this problem... I've only found it listed in one place!
My card is a linksys WMP54GS, which has a broadcomm chipset on it. What I needed to do was install bcm43xx-fwcutter and use it to get the proper missing files from wl_apsa.o. Apparently, kernels beyond that FC4 one need those files but don't provide them.
Now, I'm up to 2.6.17-1.2174_FC5!
My new problem is a common one... why am I getting this error when attempting to install kmod-nvidia?
Error: xorg-x11-drv-nvidia conflicts with selinux-policy < 2.2.29-2.fc5
Firstly, because you have SELinux set to "enforcing"
Secondly, because the policy prohibits additions of "closed-source" code to the kernel since you have no way to verify that the code does not contain some "trojan."
If you don't care, try using the SELinux policy tools to set the security to report violations, but not prohibit them. (Um, that assumes your system does not need to be "super" secure.)
I am having a similar problem with my wireless NIC installation.
I have ndiswrapper installed, and it detects the NIC (The little light goes on) I have it set up in the configuration to obtain an IP address from the router/AP, but every time I boot up, I get a message that an IP address could not be obtained and that I should check the cable (duh...)
I'm running FC5 (2.6.15-1.2048) on a Compaq v2000 with a broadcom 4318 wireless NIC.
lspci return 05:02.0 0280: 14e4:4318 (rev 02)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.