LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva
User Name
Password
Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux.

Notices

Reply
 
Search this Thread
Old 11-30-2005, 06:50 PM   #1
JerryP
Member
 
Registered: May 2005
Location: Hells Kitchen, New York
Distribution: PCLinuxOS 2007
Posts: 72

Rep: Reputation: 15
'blacklist' WARNING


I am running Mandriva 2006. While the system is loading I get the following message:

WARNING: /etc/modprobe.conf line 8 ignoring bad line starting with 'blacklist'
WARNING: /etc/modprobe.conf line 9 ignoring bad line starting with 'blacklist'

This is �said� many times during the loading.

Following is the contents of my etc/modprobe.conf:

+++++++++

# This file is autogenerated from /etc/modules.conf using generate-modprobe.conf command

alias sound-slot-0 cmpci
remove snd-cmipci /sbin/modprobe --first-time -r --ignore-remove snd-cmipci
install snd-cmipci /sbin/modprobe --first-time --ignore-install snd-cmipci
install usb-interface /sbin/modprobe uhci-hcd; /sbin/modprobe ehci-hcd; /bin/true
alias eth0 8139too
blacklist audio
blacklist snd-usb-audio
remove cmpci /sbin/modprobe --first-time -r --ignore-remove cmpci
install cmpci /sbin/modprobe --first-time --ignore-install cmpci

+++++++++

If I put # in front of both of the 'blacklist' lines the system just puts them back and the warning is repeated except for the bad line having a different number.

moduals.conf is an empty file.

I have tried to reinstall and install the alternate drivers for my sound card but this doesn't change anything with the warning. My audio is fine with either.

Any suggestions to get rid of this 'blacklist' thing? I've had no luck Googling it. I just want to get rid of it.

Thanks, Jerry
 
Old 12-01-2005, 02:26 PM   #2
springshades
Member
 
Registered: Nov 2004
Location: Near Lansing, MI , USA
Distribution: Mainly just Mandriva these days.
Posts: 304

Rep: Reputation: 30
I doubt this will help you, but I'm just a little curious. Have you tried running the generate_modprobe.conf command manually yet? I'd be interested in whether that changes anything in your modprobe.conf line.
 
Old 12-01-2005, 04:56 PM   #3
JerryP
Member
 
Registered: May 2005
Location: Hells Kitchen, New York
Distribution: PCLinuxOS 2007
Posts: 72

Original Poster
Rep: Reputation: 15
That's a fair idea. I tried it and it didn't do anything although that wasn't too surprising since modules.conf is an empty file. I also thought I would cleverly backup and then delete modprobe.conf and let Linux re-create it by whatever means it does this. The modprobe created only had two lines:

blacklist audio
blacklist snd-usb-audio

and I got the same warning through booting except the bad lines were now (naturally) 1 and 2. When the system came up I had no sound and no LAN card which is eth0. My sound driver is cmpci so this file points to these.

Any other curiosities? I'm stumped.
 
Old 12-01-2005, 06:09 PM   #4
springshades
Member
 
Registered: Nov 2004
Location: Near Lansing, MI , USA
Distribution: Mainly just Mandriva these days.
Posts: 304

Rep: Reputation: 30
Well I didn't have any really great ideas to start with. The next thing I think I'd do in your situation is look at the contents of other related files. For me, ls /etc/mod* shows that I have 4 files that start with mod and all appear to be related. I've got modules, modprobe.conf, modprobe.devfs, and modprobe.preload. If I were you I might look at those files and see if they have anything that might give you a clue. In particular, pay attention to anything having to do with sound.

If I were desperate I might do something like,

grep blacklist /etc/rc.d/*
grep blacklist /etc/init.d/*
grep blacklist /var/log/*

but this is that desperation maneuver when you have no idea what the heck to do, and you're just trying to get some clues.

If you're unfamiliar with grep, it searches the text of the files listed for any occurance of the "pattern". The pattern is blacklist. So those commands will check your initialization scripts and the majority of your log files for the occurance of the word. The next step would be to check out any files that it finds... I'd suggest something like kate with an easy to use "find" function so that you can track down the proper part of the file quickly (some of these text files might be hundreds or thousands of pages long). Also, grep will take a LONG time when used on this many files. That's a lot of text to search through. This may not really help you at all, but like I said, I don't really have any "good" ideas.
 
Old 12-01-2005, 06:35 PM   #5
JerryP
Member
 
Registered: May 2005
Location: Hells Kitchen, New York
Distribution: PCLinuxOS 2007
Posts: 72

Original Poster
Rep: Reputation: 15
Thanks. I looked in the files and didn't get any clues. I tried the desperation action and didn't get any clues from that either.

But I now have a question -

What are these files /etc/rc.d/*, /etc/init.d/* and /var/log/*? What led you to suggest looking in these?
 
Old 12-01-2005, 06:47 PM   #6
springshades
Member
 
Registered: Nov 2004
Location: Near Lansing, MI , USA
Distribution: Mainly just Mandriva these days.
Posts: 304

Rep: Reputation: 30
Quote:
What are these files /etc/rc.d/*, /etc/init.d/* and /var/log/*? What led you to suggest looking in these?
Actually, they are folders, not files. The * is the wildcard that means look at everything inside basically. I suggested those because your initialization scripts (basically everything that runs while your computer is booting) are mainly contained in either /etc/rc.d or /etc/init.d. I suggested /var/log because that folder contains most of the logs made by your computer. Kernel logs, boot logs, etc. I should have mentioned, to grep in those places you might have to be root because only root has permissions to read some of the files.

Crap! Just realized I made a mistake. You'll have to do grep -r blacklist /var/log/* actually. You need that -r to look at the files in the sub-folders. Sorry about that. You should be fine without the -r for the rc.d and init.d files because their subfolders shouldn't contain anything all that interesting. Again, if you get a permission denied error for the output, it means that you need to be root to read those files most likely.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
a blacklist for hal? evans0409 Linux - Software 12 02-05-2006 09:29 PM
what is /etc/hotplug/blacklist for? slinky2004 Linux - Software 1 09-10-2005 11:44 PM
using the squidguard blacklist myheart Linux - Security 4 02-01-2005 11:05 AM
hotplug blacklist doesn't quite work ? aherrys Slackware 5 01-13-2005 11:09 AM
WARNING to all those using Osirusoft blacklist. Pcghost Linux - General 0 08-28-2003 02:39 PM


All times are GMT -5. The time now is 12:18 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration