Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-28-2003, 06:48 PM
|
#1
|
|
Member
Registered: Nov 2002
Location: Cary, NC
Distribution: Red Hat
Posts: 76
Rep:
|
How to PERMANENTLY Remove a KLM?
Somehow I got a Cyclades multi-port serial module installed. It is a major interference in trying to log on but I cannot get rid of the damned thing. I have tried /sbin/moprobe -r cyclades and /sbin/rmmod -r cyclades. Both temporarily remove it from memory but on reboot, it's back.
I have some small cron files but crontab tells me that there are no cron files for any user on the system.
How do I find the Cyclades module and how do I get rid of it PERMANENTLY for all users?
|
|
|
|
07-28-2003, 06:53 PM
|
#2
|
|
Member
Registered: May 2002
Location: AK - The last frontier.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
|
Do you have it in your /etc/modules.conf?
|
|
|
|
07-28-2003, 07:19 PM
|
#3
|
|
Member
Registered: Nov 2002
Location: Cary, NC
Distribution: Red Hat
Posts: 76
Original Poster
Rep:
|
No - nothing there about the Cyclades module.
|
|
|
|
07-28-2003, 07:50 PM
|
#4
|
|
Member
Registered: May 2002
Location: AK - The last frontier.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
|
The next thing I would do is to grep my rc directories for the string 'cyclades' to see if it is being modprobed at all. To be safe, I would grep /etc itself recursively, redirect output to a file and check every occurance.
|
|
|
|
07-28-2003, 07:56 PM
|
#5
|
|
Member
Registered: May 2002
Location: AK - The last frontier.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
|
Code:
#!/bin/bash
# fts - full text search
if [ $# -lt 1 ]; then
echo "fts - Full Text Search"
echo "Usage: $(basename $0) <searchText>"
exit 1
fi
for i in $(find . -type f -print); do
if [ -r $i ]; then
grep -Hi -e "$1" $i;
fi
done
exit 0
A bare-bones script like the one I use may be used to do the text-search regular files starting from the current directory. A word of warning: the script assumes non-space-delimited filenames, does not check for file types etc.
Last edited by nxny; 07-28-2003 at 07:59 PM.
|
|
|
|
07-28-2003, 08:24 PM
|
#6
|
|
Member
Registered: Nov 2002
Location: Cary, NC
Distribution: Red Hat
Posts: 76
Original Poster
Rep:
|
Did cd /etc and then things of the form grep -R "cyclades" rc0.d/*.
Got not hits. Getting blerry-eyed, tired, and hungry. Must consume calories and snooze.
|
|
|
|
07-29-2003, 11:20 AM
|
#7
|
|
Member
Registered: May 2002
Location: AK - The last frontier.
Distribution: Red Hat 8.0, Slackware 8.1, Knoppix 3.7, Lunar 1.3, Sorcerer
Posts: 771
Rep:
|
Chances are that youw won't find it by looking rc0.d , that being the HALT runlevel. I would look under /etc/rc.d/init.d specifically. Or comb the entire /etc since it usually isn't too big for a recursive grep to comeback in under 20-30 seconds.
|
|
|
|
08-31-2003, 11:54 AM
|
#8
|
|
Member
Registered: Nov 2002
Location: Cary, NC
Distribution: Red Hat
Posts: 76
Original Poster
Rep:
|
Finally got to work on this Cyclades pain some more. Found a much of different cyclades.o files that apparently get generated automatically each time I use RedHat Network to update my kernel. When I do modprobe -c, I see
alias char-major-19 cyclades
alias char-major-20 cyclades
cat /etc/modules.conf yields many fewer lines - a bunch of blank ones and then some stuff having to do mainly with sound drivers.
In addition to the module files, there is an include file and a Perl script. Doing rpm -qf on the modules (RH 8) and other two files doesn't give anything useful in finding a package that installed the cyclades modules in the first place.
I still haven't found anything that tells me how to permanently prevent the module from loading on boot for the current kernel. How can I do this?
Looks like I need to find some kind of kernel configuration file to ensure that the module does not get built for future kernels. Pointers? Clues for the clueless?
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 04:19 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|