Skip to contentSkip to conversation

Check dependencies for modules "dm-snapshot" and "sd_mod" in kernel 2.6.23.1

DISCUSSION Markus Elfring 2 participants 5 messages Oct 28, 2007

lore
Share & tools
lore
#0 lore raw

Hello,

I get the following output from the command "make install" after the source files were successfully compiled for my personal configuration.

if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 2.6.23.1-default; fi
sh /usr/src/linux-2.6.23.1/arch/i386/boot/install.sh 2.6.23.1-default arch/x86_64/boot/bzImage System.map "/boot"

Kernel image:   /boot/vmlinuz-2.6.23.1-default
Initrd image:   /boot/initrd-2.6.23.1-default
Root device:    /dev/system/root (mounted on / as ext3)
Resume device:  /dev/sdb5

WARNING Cannot determine dependencies of kernel module 'dm-snapshot'.
Does it exist? If it does, try depmod -a. Continuing without dm-snapshot.
WARNING Cannot determine dependencies of kernel module 'sd_mod'.
Does it exist? If it does, try depmod -a. Continuing without sd_mod.
Kernel Modules: processor thermal libata pata_amd sata_nv sata_sil24 fan jbd mbcache ext3 dm-mod edd usbcore ohci-hcd uhci-hcd ehci-hcd hid usbhid linear

Features:       keyboard-blink dm block usb lvm2 resume.userspace resume.kernel
Bootsplash:     SuSE (1024x768)

20893 blocks

Is anything wrong here with the executable generation for these modules? Are there any open issues with dependency management for (LVM) snapshots and SCSI devices?

Regards,
Markus

#1 lore raw
Quoted 20 lines · Markus Elfring

Hello,

I get the following output from the command "make install" after the source files were successfully compiled for my personal configuration.

if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 2.6.23.1-default; fi
sh /usr/src/linux-2.6.23.1/arch/i386/boot/install.sh 2.6.23.1-default arch/x86_64/boot/bzImage System.map "/boot"

Kernel image:   /boot/vmlinuz-2.6.23.1-default
Initrd image:   /boot/initrd-2.6.23.1-default
Root device:    /dev/system/root (mounted on / as ext3)
Resume device:  /dev/sdb5

WARNING Cannot determine dependencies of kernel module 'dm-snapshot'.
Does it exist? If it does, try depmod -a. Continuing without dm-snapshot.
WARNING Cannot determine dependencies of kernel module 'sd_mod'.
Does it exist? If it does, try depmod -a. Continuing without sd_mod.
Kernel Modules: processor thermal libata pata_amd sata_nv sata_sil24 fan jbd mbcache ext3 dm-mod edd usbcore ohci-hcd uhci-hcd ehci-hcd hid usbhid linear

Quoted 6 lines
Features:       keyboard-blink dm block usb lvm2 resume.userspace resume.kernel
Bootsplash:     SuSE (1024x768)

20893 blocks

Is anything wrong here with the executable generation for these modules? Are there any open issues with dependency management for (LVM) snapshots and SCSI devices?

Perhaps your personal configuration is missing the modules SUSE 10.3 requires. I'd use one of their rpms anyway.

#2 lore raw
Quoted 2 lines

Perhaps your personal configuration is missing the modules SUSE 10.3 requires. I'd use one of their rpms anyway.

I have assumed that my Linux distribution is clean enough to try out a current kernel. Would you like to recommend anything to get rid from these warnings about unresolved dependencies?

Regards,
Markus

#3 lore raw
Quoted 7 lines · Markus Elfring
Quoted 3 lines

Perhaps your personal configuration is missing the modules SUSE 10.3 requires. I'd use one of their rpms anyway.

I have assumed that my Linux distribution is clean enough to try out a current kernel. Would you like to recommend anything to get rid from these warnings about unresolved dependencies?

If you really have to roll your own kernel (often this is not the case-YMMV), I suggest you enable dm-snapshot and sd_mod.

#4 lore raw
Quoted 2 lines

If you really have to roll your own kernel (often this is not the case-YMMV), I suggest you enable dm-snapshot and sd_mod.

I intentionally omitted the configuration option "DM_SNAPSHOT" because it is marked as "EXPERIMENTAL".
Snapshot target:
"Allow volume managers to take writable snapshots of a device."

I intentionally checked the option "BLK_DEV_SD". I do not want to build it as a module. SCSI disk support:
"If you want to use SCSI hard disks, Fibre Channel disks,
Serial ATA (SATA) or Parallel ATA (PATA) hard disks,
USB storage or the SCSI or parallel port version of
the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
the Disk-HOWTO and the Multi-Disk-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
CD-ROMs.

To compile this driver as a module, choose M here and read <file:Documentation/scsi/scsi.txt>.
The module will be called sd_mod.

Do not compile this driver as a module if your root file system (the one containing the directory /) is located on a SCSI disk. In this case, do not compile the driver for your SCSI host adapter (below) as a module either."

Do I expect more from the dependency management than it is provided at the moment?

Regards,
Markus