compiling a new linux kernel - facing problems scsi module not found

bhanuvrat · 2010-04-04 21:14:34

I am facing a lot of problems like non functional acpi etc which I have eventually found out that they can be solved by compiling a new kernel and setting them compiled into the kernel instead of being loaded as a module.

but while trying to compile a new kernel I am facing a problem which says sd[-_]mod not found (in the mkinitcpio step).

I tried to mkinitcpio with both scsi disk support built into the kernel and as a module both ways I am not able to make my system work with the new kernel.

I get the error if I try to run mkinitcpio with scsi disk support build into the kernel.
When the scisi disk sopport is left to be loaded later as a module, mkinitcpio works fine but later while booting the system complains that the partition was not found, i.e /dev/disk/by-uuid/"some kinda code" was not found.

I am not able to boot into my new kernel.
please help.

I took the help of these threads and pages

http://bbs.archlinux.org/viewtopic.php?id=43872
http://wiki.archlinux.org/index.php/Ker … rom_Source
http://bbs.archlinux.org/viewtopic.php?id=52847

ewaller · 2010-04-05 03:58:32

I am no expert on mkinitcpio, but if the driver is compiled into the kernel, why are you telling mkinitcpio to include the module in the initial ramdisk? If it is compiled into the kernel, there will no be kernel module to load at run time and therefore there will be no kernel module to copy into the initial ramdisk. The point being, it is not needed at all because it is intrinsic to the kernel and is always available.

Of course, I could be confused.

Marcel- · 2010-04-12 00:25:45

Indeed. I also compile SCSI disk support in the kernel and I get the same error "module 'sd[-_]mod' not found" (and I don't know how to stop mkinitcpio to look for that module, as there's no reference to it in mkinitcpio.conf). My kernel boots fine, though* (which is the expected behaviour).

Do you get the same error on boot ("partition /dev/disk/by-uuid/longString not found") when you build SCSI disk support in the kernel? I suspect that you misconfigured your kernel command line. Can you post the complete contents of /boot/grub/menu.lst (with the bootable stock Arch kernel instance), /etc/fstab and the output of "ls -l /dev/disk/by-uuid/"?

BTW, you shouldn't hijack an old topic like you did here, nor ask the same question in different places.

* I have to admit that I suffer from some other problem, but that's totally unrelated to the error message mentioned in this topic.

Last edited by Marcel- (2010-04-12 01:27:22)

ngoonee · 2010-04-12 06:02:35

You probably ask the module to load in /etc/rc.conf....

Marcel- · 2010-04-12 09:25:09

I can't find it there either:

#
# /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_US.UTF-8"
#HARDWARECLOCK="localtime"
HARDWARECLOCK="ntp"
TIMEZONE="Europe/Amsterdam"
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=()

# 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="brogain"

# 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="dhcp"
eth0="dhcp"
INTERFACES=(eth0)

# 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=(main)

# -----------------------------------------------------------------------
# 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 network netfs @ntpd @lighttpd @crond alsa)

ngoonee · 2010-04-12 15:08:19

I just noticed you're compiling your own kernel, from source, and not basing on one of the existing PKGBUILDs. May I ask why? It seems that the module just doesn't exist/doesn't get compiled for you.

Marcel- · 2010-04-13 00:07:52

Indeed. As I said, I compile the SCSI disk support into the kernel, so there simply is no sd_mod. Therefore the error is only cosmetic, I just wondered why mkinitcpio is looking for the module (i.e., which configuration file assigns sd_mod to the initial RAM disk).

There are a few reasons why I compile my own kernel:

1) I want to use the ZEN kernel patches (BFS and SCHED_ISO give me a far better responsive machine).

2) In the near future I want to include a kernel patch to make the zoom slider of my MS Natural Ergonomic Keyboard 4000* work as a scroll wheel (I know there are other solutions around to achieve this, like one using Key Touch, but it didn't feel smooth, so I want to give this a try).

3) It's nice to delve a bit into the inner workings of the Linux kernel this way.

4) [Very bad reason] I like to look at the logos that appear on boot and you have to compile the kernel yourself when using KMS to achieve this. :-P

* They actually make a very useful product at that company

Last edited by Marcel- (2010-04-13 01:16:44)

broch · 2010-04-13 00:56:30

You probably ask the module to load in /etc/rc.conf....

then system would not boot at all...

@Marcel-
if you are building disk/fs in kernel, then you don't need initrd. skip it.

"module 'sd[-_]mod' not found"

so there is somewhere reference to scsi: scsi built in kernel, mkinitcpio.conf still looks for scsi module (MODULES array, and HOOKS), or you are using the same initrd for default kernel and custom.

if you really need initrd/mkinitcpio
make new custom:
save as mkinitcpio_custom.conf for example and run (after installing kernel):

mkinitcpio -k 2.6.33-zen -c /etc/mkinitcpio_custom.conf -g /boot/kernel-2.6.33-zen.img

remember now that your img name is different:
menu.lst
...........
initrd /kernel-2.6.33-zen.img

hope this will help

Last edited by broch (2010-04-13 00:57:11)

Marcel- · 2010-04-13 01:15:43

broch wrote:

if you are building disk/fs in kernel, then you don't need initrd. skip it.

I also thought of that. I'll get rid of it.

broch wrote:

"module 'sd[-_]mod' not found"
so there is somewhere reference to scsi: scsi built in kernel, mkinitcpio.conf still looks for scsi module (MODULES array, and HOOKS), or you are using the same initrd for default kernel and custom.

No, I'm apparently using the same mkinitcpio.conf for default and custom, as kernel26zen.preset also points to that file.

But you are right, it's in HOOKS:

HOOKS="base udev autodetect pata scsi sata filesystems"

 > Generating initial ramdisks using mkinitcpio
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.33-zen2-ARCH-20100413-stable-06378-g218eed9-dirty -c /etc/mkinitcpio.conf -g /boot/kernel26zen.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
error: /dev/sdb: No medium found
:: Parsing hook [pata]
ERROR: module 'sd[-_]mod' not found
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26zen.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.33-zen2-ARCH-20100413-stable-06378-g218eed9-dirty -c /etc/mkinitcpio.d/kernel26zen-fallback.conf -g /boot/kernel26zen-fallback.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [ide]
:: Parsing hook [pata]
ERROR: module 'sd[-_]mod' not found
:: Parsing hook [scsi]
ERROR: module 'sd[-_]mod' not found
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [mdadm]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26zen-fallback.img'...SUCCESS
==> SUCCESS

Ber · 2010-04-13 07:54:55

Just to be sure, did you "make modules_install" at the end of your kernel compilation?

Marcel- · 2010-04-13 11:51:32

Is this a question to me or to the OP? In the former case: as I wrote in post #7, I use the ZEN-git PKGBUILD, which indeed does do that. Moreover, if it didn't, other thing would break severely.

broch · 2010-04-13 12:53:15

The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.

make_modules does not mater for this error as SCSI (and I assume SATA) are build in kernel. Errors are referring to mkinitcpio. One more reason I prefer really custom setups instead of trying to weed out whatever differences between config files.

the same error is generated by zen and fallback mkinitcpio this should tell you something.

Arch Linux

#1 2010-04-04 21:14:34

compiling a new linux kernel - facing problems scsi module not found

#2 2010-04-05 03:58:32

Re: compiling a new linux kernel - facing problems scsi module not found

#3 2010-04-12 00:25:45

Re: compiling a new linux kernel - facing problems scsi module not found

#4 2010-04-12 06:02:35

Re: compiling a new linux kernel - facing problems scsi module not found

#5 2010-04-12 09:25:09

Re: compiling a new linux kernel - facing problems scsi module not found

#6 2010-04-12 15:08:19

Re: compiling a new linux kernel - facing problems scsi module not found

#7 2010-04-13 00:07:52

Re: compiling a new linux kernel - facing problems scsi module not found

#8 2010-04-13 00:56:30

Re: compiling a new linux kernel - facing problems scsi module not found

#9 2010-04-13 01:15:43

Re: compiling a new linux kernel - facing problems scsi module not found

#10 2010-04-13 07:54:55

Re: compiling a new linux kernel - facing problems scsi module not found

#11 2010-04-13 11:51:32

Re: compiling a new linux kernel - facing problems scsi module not found

#12 2010-04-13 12:53:15

Re: compiling a new linux kernel - facing problems scsi module not found

Board footer