| Summary: | cannot blacklist firewire_core | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Chris Denice <eatdirt> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia |
| Version: | Cauldron | Keywords: | NEEDINFO, Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kmod | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 4301 | ||
|
Description
Chris Denice
2012-03-05 14:15:05 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 Out of curiosity, does adding modprobe.blacklist= to the kernel command line (with your module names) work? CC:
(none) =>
mageia 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. 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 no valid anymore for me; this has been fixed. I am closing. Status:
NEW =>
RESOLVED |