From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Subject: Check dependencies for modules "dm-snapshot" and "sd_mod" in kernel 2.6.23.1
Date: Sun, 28 Oct 2007 16:52:06 +0100 [thread overview]
Message-ID: <fg2b7g$1hj$1@ger.gmane.org> (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
next reply other threads:[~2007-10-28 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 15:52 Markus Elfring [this message]
2007-10-28 16:02 ` Check dependencies for modules "dm-snapshot" and "sd_mod" in kernel 2.6.23.1 Jan Engelhardt
2007-10-28 17:05 ` Markus Elfring
2007-10-28 17:15 ` Jan Engelhardt
2007-10-28 18:51 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fg2b7g$1hj$1@ger.gmane.org' \
--to=markus.elfring@web.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox