Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19666 - [mkinitcpio] rc.conf fails to blacklist the 'floppy' module

Attached to Project: Arch Linux
Opened by Eric Toombs (ewtoombs) - Tuesday, 01 June 2010, 01:20 GMT
Last edited by Allan McRae (Allan) - Saturday, 19 February 2011, 01:46 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Very Low
Priority Low
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
MODULES=(!floppy) seems to have no effect. The floppy module gets loaded anyway. I don't know if it's udev or some other part of the init system, but I'm betting it's something to do with udev.

Additional info:
* package version(s)
udev-151-3
initscripts-2010.05-3

* config and/or log files etc.
=====BEGIN rc.conf=====
#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_CA.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Eastern"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(!snd_hda_intel !usblp !floppy !pcspkr)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="vault"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp" # PCI 10/100
#eth1="dhcp" # onboard 10/100/1000
#INTERFACES=(!eth1)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
#gateway="default gw 192.168.0.1"
#ROUTES=(!gateway)

# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(571network)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng dbus hal slim @crond iptables net-profiles !alsa @sshd @ntpdate @ddclient @openvpn cups samba)
=====END rc.conf =====

Steps to reproduce:
-add !floppy to MODULES in rc.conf
-reboot
-lsmod reveals that floppy gets loaded anyway.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 19 February 2011, 01:46 GMT
Reason for closing:  No response
Additional comments about closing:  Assuming fixed with patch in final comment
Comment by Jan de Groot (JGC) - Tuesday, 01 June 2010, 08:38 GMT
Does your initramfs image contain the floppy module?
Comment by Eric Toombs (ewtoombs) - Wednesday, 02 June 2010, 04:57 GMT
Yeah, it does. Do you think that's how it got loaded? I don't really know what the hell's going on during that stage of the boot process. Is there any way of keeping floppy.ko from getting into the initramfs?
Comment by Jan de Groot (JGC) - Wednesday, 02 June 2010, 06:33 GMT
Your initramfs module was generated before you blacklisted the floppy module. Regenerating the initramfs image should get rid of floppy.
Comment by Eric Toombs (ewtoombs) - Thursday, 03 June 2010, 01:53 GMT
I have regenerated it several times with !floppy in MODULES manually and through updates. It didn't get rid of floppy.ko. Is mkinitcpio supposed to read rc.conf's MODULES variable and blacklist modules using it? I didn't read anything like that in mkinitcpio's docs... If it doesn't, it would be a really good idea.
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 04 July 2010, 02:22 GMT
  • Field changed: Summary (rc.conf fails to blacklist the 'floppy' module → [mkinitcpio] rc.conf fails to blacklist the 'floppy' module)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Thomas Bächler (brain0)
Nop, mkinitcpio does not parse rc.conf to blacklist modules, and seems that there is no way to blacklist a module at build time. But there is a way to blacklist a module at runtime, just pass to kernel command line: disablemodules=floppy

Run mkinitcpio -v to see from what hook floppy module is detected.
Comment by Thomas Bächler (brain0) - Friday, 13 August 2010, 07:49 GMT
There is no reason why floppy should be added to the image. And I don't have a single system where it is added. Apparently it's the 'scsi' hook's fault.
Comment by Nevyansk (gardarea51) - Saturday, 21 August 2010, 06:19 GMT
Some problem.. i can't disable it:
:: Parsing hook [scsi]
adding dir /lib/modules/2.6.35-ARCH/kernel/drivers/cdrom
adding file /lib/modules/2.6.35-ARCH/kernel/drivers/cdrom/cdrom.ko
adding file /lib/modules/2.6.35-ARCH/kernel/drivers/scsi/sr_mod.ko
adding dir /lib/modules/2.6.35-ARCH/kernel/drivers/block
adding file /lib/modules/2.6.35-ARCH/kernel/drivers/block/floppy.ko
I need in use cd-rom =).. now, it's bug?
Comment by Thomas Bächler (brain0) - Saturday, 21 August 2010, 07:27 GMT

Loading...