Bug 145168
Summary: | loop: Unknown parameter `' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stig Hackvan <stig-redhat-bugzilla> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | pfrields, sbuedenb, trondeg, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-16 14:29:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Stig Hackvan
2005-01-14 22:32:35 UTC
(/lib/modules/2.6.10-1.741_FC3/kernel/drivers/block/loop.ko): Unknown symbol in module, or unknown parameter (see dmesg) what does it say in dmesg ? well i rebooted, so you get before and after... before (kernel-2.6.9-1.724_FC3): Jan 14 19:16:18 usul kernel: loop: Unknown parameter `' Jan 14 19:16:18 usul kernel: loop: loaded (max 16 devices) NOTE: the loop module is loaded and the loopback filesystem is mounted. after (kernel-2.6.10-1.741_FC3): Jan 14 18:43:53 usul kernel: loop: Unknown parameter `' NOTE: the loop module doesn't load and the filesystem is not mounted. ---- so it may seem that the parameter checking is just more strict, but the error seems bogus in the first place! It appears even with the loop line in modules.conf commented out, and there don't seem to be any loop-oriented parameters coming from the kernel command line (via grub) or the fstab entry... and fstab's irrelevant when i attempt to load loop.ko with modprobe. This happens to the bttv module as well, in kernel-2.6.10-1.741_FC3 on x86_64 (from dmesg): bttv: Unknown parameter `' Removing the line "options bttv card=100" gets rid of the message. Running modprobe bttv with the same option on the commandline works. This has to do with trailing spaces in /etc/modprobe.conf. I found some in lines that has been migrated from modules.conf. Removing those fixes the problem. there are no trailing spaces in my /etc/modprobe.conf, so i beg to differ. Removing all the blank lines and comments from modprobe.conf does nothing either. (kernel 2.6.10-1.741_FC3) I find a few blank lines and a comment, so whitespace-in-general may be a problem, but it's not limited to trailing space... any improvement with the latest kernel(s) ? Works fine with the newest errata kernel. |