Hello,
I use MDK 10 and I have a wireless card that uses a module called 'ndiswrapper' as its driver. By default, MDK loads a driver called 'prism54' which does not work with this card and conflicts with ndiswrapper. So, every time I start up Linux, I have to run

modprobe -r prism54
modprobe -r ndiswrapper
modprobe ndiswrapper

as root and this all works fine. I would like to know, how can I permanently get rid of this annoying module called 'prism54' and make sure that MDK doesn't load it automatically? A GUI tool is preferable but I'm grateful for command line methods too. I would also like some way to make MDK load the correct driver when the wireless card is detected.
Thanks!

the man pages are your friend.............

man rmmod


http://man.linuxquestions.org/index....pe=2&section=8

Thank you for your reply!
However I do not believe this particular module can be removed using this tool, since I had to patch the kernel to put it in, and the darn source doesn't have anything for "make uninstall". What I have instead is something that is located in the following directory:

/lib/modules/2.5.3-7mdk/kernel/3rdparty/prism54/

and it's a file called prism54.ko.gz. If I type

#rmmod prism54

It tells me 'Module prism54 does not exist in /proc/modules'. I don't understand. It probably isn't safe to just delete this fellow, so should I just recompile my kernel? Can I do everything with RPM's maybe?
Thanks!

Your best bet is to look at your modules.conf file or its moral equivalent, and delete the line that loads that module on boot.

Hrmm. Both my 'modules' and my 'modules.conf' files don't seem to contain any line that loads this driver. I search for all the files in my /lib/modules/ directory that contain the phrase 'prism54' and there are three files:

2.6.3-7mdk/modules.alias
2.6.3-7mdk/modules.dep
2.6.3-7mdk/modules.pcimap

is it safe to delete lines from these files? Would that accomplish anything? Sorry I'm so new to this, and thanks a lot for all your help!

Also,
When I start up my machine and it's not plugged into the network, it takes FOREVER to register that I'm not plugged in. That is, at bootup, the line
'Bringing up interface eth0...'
sits there for like five minutes. Does anybody know how I can speed this up? Thanks a lot!

Well I think the major thing is that you compiled it INTO the kernel rather than as a module. As such I think you would have to recompile your kernel.

As for the network thing....its probably looking for a DHCP server. If you want you can always ctrl-c out of it and then after you login as root you can bring up the interface with an ifup eth0 after you are plugged into the network.

I see. But there's no place where I can tell the machine to give up bringing up that particular interface if it takes longer than, say five minutes? Like how you can specify how long to wait until a server times out?
Thanks!

Well you can always tell the interface not to auto up or just not start networking on boot up. Just rename your rc file so networking isn't started up. Then when you are ready to start networking just use the /etc/init.d script to start it up.