Bug 4802 - cannot blacklist firewire_core
Summary: cannot blacklist firewire_core
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO, Triaged
Depends on:
Blocks: 4301
  Show dependency tree / graph
 
Reported: 2012-03-05 14:15 CET by Chris Denice
Modified: 2012-05-26 13:19 CEST (History)
1 user (show)

See Also:
Source RPM: kmod
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Chris Denice 2012-03-05 14:15:05 CET 
Description of problem:

Adding firewire_core and firewire_ohci to blacklist files in /etc/modprobe.d does nothing. The modules are still loaded at boot time.


(The reason I want to blacklist them is

https://bugs.mageia.org/show_bug.cgi?id=4801)

Cheers,
Chris.
Comment 1 Manuel Hiebel 2012-03-06 00:18:34 CET 
Hi, thanks for reporting this bug.
Assigned to the package maintainer.
(we use kmod now)

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Blocks: (none) => 4301
Assignee: bugsquad => tmb
Source RPM: module-init-tools-3.16-15.mga2.src.rpm => kmod

Comment 2 Colin Guthrie 2012-04-29 15:51:05 CEST 
Out of curiosity, does adding modprobe.blacklist= to the kernel command line (with your module names) work?

CC: (none) => mageia

Comment 3 Chris Denice 2012-04-29 16:58:31 CEST 
Hi Colin
sorry, I had forgotten this report, it has been actually solved with your systemd updates; the blacklist file seems to be properly read and the modules not loaded.

You can close, unless you want me to test other stuff.

Cheers,
Chris.
Comment 4 Marja Van Waes 2012-05-26 13:03:08 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Chris Denice 2012-05-26 13:19:15 CEST 
no valid anymore for me; this has been fixed.

I am closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.