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.
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
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.
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:
and it's a file called prism54.ko.gz. If I type
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?
Last edited by johngcarlsson; 12-05-2004 at 01:30 AM.
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:
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?
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.