MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
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.
Hello,
I have a specific module compiled in my kernel which I would like to get rid of, and it is not loadable so I cannot use rmmod to delete it. I assume that I have to recompile my kernel to get rid of it. I downloaded the source RPMs from a mandrake repository, but I cannot find any guides for recompiling my kernel, keeping everything the same except for this one module. Can anybody help me with such a problem?
Thank you very much!
I have a wireless card which uses a module called 'ndiswrapper'. In order to use this module I had to download the kernel source RPM. However, there is also a module called 'prism54' included in the kernel source which wants to act as the driver for this wireless card, even though it does not work. In fact, 'prism54' prevents 'ndiswrapper' from functioning properly. So, every time I start up, I have to do
and everything works fine. The reason I want to completely remove 'prism54' is for two reasons:
\it's annoying to have to type that every time
\it makes my bootup sequence last an additional 3 minutes, because the startup screen takes that long at the line 'bringing up interface eth1...' to give me an error message.
The problem comes from the fact that the source that I get in
urpmi kernel-source
already contains both 'ndiswrapper' (although an outdated version) and 'prism54', so I believe I must remove it by hand.
Thanks a lot!
Last edited by johngcarlsson; 12-05-2004 at 03:37 PM.
Hello,
Hmm, I don't see any lines mentioning prism54 or ndiswrapper in the four files you mentioned. I see lines that modprobe all the USB devices, but I do not see anything for PCMCIA. Google hasn't been very helpful with these files either; should I add in a 'remove' line or something? I have, in modules.conf, the line
probeall usb-interface usb-ohci ehci-hcd
but these all look like they're USB related.
Thanks!!!
Last edited by johngcarlsson; 12-05-2004 at 10:42 PM.
I don't think I have any packages with that in their name...I thought that the only time I saw any prism54 driver was in installing the kernel source. Maybe I'm wrong?
Evey time I do an update it wants to update the file prism54-firmware. I don't have anything that requires such firmware. So I just did a urpme prism54-firmware and it stop trying to update something I wasn't using.
Originally posted by johngcarlsson Hello,
Hmm, I don't see any lines mentioning prism54 or ndiswrapper in the four files you mentioned. I see lines that modprobe all the USB devices, but I do not see anything for PCMCIA. Google hasn't been very helpful with these files either; should I add in a 'remove' line or something? I have, in modules.conf, the line
probeall usb-interface usb-ohci ehci-hcd
but these all look like they're USB related.
Thanks!!!
If so then it's NOT being loaded at boot by the kernel.
Rather you may have a script trying to load these files, if it's happening at all.
In all likelyhood it's the configuration you have selected for eth1.
I'd start by NOT having it come up at boot so you can manage it directly or invoke it from rc.local if required.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.