mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: johann.pfefferl.jp@germany.agfa.com
To: linux-kernel@vger.kernel.org
Subject: loop Device doesn't work in kernel 2.4.14
Date: Mon, 12 Nov 2001 09:57:38 +0100	[thread overview]
Message-ID: <OFC9FBD042.EA509C88-ON41256B02.002FCAEC@bayer-ag.com> (raw)

Hello,

I have detected that the loop device mechanism can't be
used any longer in kernel version 2.4.14. I have compiled
the kernel with minimum features (ext2, initrd, ramdisk) compiled
into the kernel. The rest is all modules.

# cat /proc/version
Linux version 2.4.14 (root@pcls03) (gcc version 2.95.3 20010315 (SuSE)) #2 Wed Nov 7 11:34:01 CET 2001

# mount -o loop /tmp/DISK /mnt -v
mount: Could not find any loop device, and, according to /proc/devices,
       this kernel does not know about the loop device.
       (If so, then recompile or `insmod loop.o'.)

# modprobe -v loop
/sbin/insmod /lib/modules/2.4.14/kernel/drivers/block/loop.o
Using /lib/modules/2.4.14/kernel/drivers/block/loop.o
Symbol version prefix ''
/lib/modules/2.4.14/kernel/drivers/block/loop.o: unresolved symbol deactivate_page
/lib/modules/2.4.14/kernel/drivers/block/loop.o: insmod /lib/modules/2.4.14/kernel/drivers/block/loop.o failed
/lib/modules/2.4.14/kernel/drivers/block/loop.o: insmod loop failed

# find /usr/src/linux-2.4.14 -type f -name '*.[ch]' |xargs grep deactivate_page
/usr/src/linux-2.4.14/drivers/block/loop.c:             deactivate_page(page);
/usr/src/linux-2.4.14/drivers/block/loop.c:     deactivate_page(page);

# depmod -ae
depmod: *** Unresolved symbols in /lib/modules/2.4.14/kernel/drivers/block/loop.o
depmod:         deactivate_page
depmod: *** Unresolved symbols in /lib/modules/2.4.14/kernel/drivers/net/wan/comx.o
depmod:         proc_get_inode
depmod: *** Unresolved symbols in /lib/modules/2.4.14/kernel/drivers/telephony/ixj_pcmcia.o
depmod:         register_pccard_driver
depmod:         unregister_pccard_driver
depmod:         CardServices

There seems to be a problem with the routine deactivate_page, which is no longer present
in the 2.4.14 kernel but is used somehow in the loop device code.

Hans
--
Dr.-Ing. Johann Pfefferl       mailto:johann.pfefferl.jp@germany.agfa.com
Agfa-Gevaert AG                                    Tel.: +49 89 6207-3524
GF Laborgeraete, Entwicklung Software (LG-ESW)     Sek.: +49 89 6207-3362
Tegernseer Landstr. 161,  D-81539 Muenchen         Fax : +49 89 6207-7279
                      __
                     / /    __  _  _  _  _ __  __
                    / /__  / / / \// //_// \ \/ /           -o)
                   /____/ /_/ /_/\/ /___/  /_/\_\           /\\
                    ...for IQs GREATER than 98...          _\_v-



             reply	other threads:[~2001-11-12  8:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12  8:57 johann.pfefferl.jp [this message]
2001-11-12  9:11 ` DevilKin
2001-11-12  9:15 ` Adrian Bunk

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=OFC9FBD042.EA509C88-ON41256B02.002FCAEC@bayer-ag.com \
    --to=johann.pfefferl.jp@germany.agfa.com \
    --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

all inboxes | Powered by JetHome®