Skip to contentSkip to conversation

LVM2 for kernels 2.4.20

linux-lvm Maximo Ramos 3 participants 3 messages Jan 26, 2003 – Feb 2, 2003

lore
Share & tools
lore
#0 lore raw

Hi!

sorry to bother you but I am trying to use LVM2 in my 2.4.20 kernel ...

the current device-mapper doesn't have a path for 2.4.20 so ...

I've got 2.4.20-dm-7.tar.bz2 but that's a lot of patch files with no README in it ...

I patch my kernel with those files, one-by-one (there are 40) but after the modules building, I've got:

[~]$modprobe dm-mod
/lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol mempool_destroy_Raf572a67 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol path_release_R8193b2f1 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol vmalloc_to_page_Raa214b41 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol bdput_Ra57a35a2 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol bdget_Rc89d026a /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol path_walk_Ra2e7eba5 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol vcalloc_R5c2c7068 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol blk_dev_Rffc56eca /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol blkdev_get_Ra638f186 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol mempool_free_slab_R8a99a016 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol set_bh_page_R294227b0 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol blkdev_put_Rccb77982 /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol _alloc_pages_R86a3f582

and more ... and some modules I've alread had, got some errors too:

[~]$depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/block/floppy.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/block/loop.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/cdrom/cdrom.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/char/agp/agpgart.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/char/busmouse.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/char/drm/mga.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/char/rtc.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/char/serial.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/md/dm-mod.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/net/ppp_async.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/net/ppp_generic.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/scsi/ide-scsi.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/scsi/scsi_mod.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/scsi/sd_mod.o
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/drivers/scsi/sg.o

more more more of this .....

now, what went wrong? :(

please help!!

#1 lore raw
Quoted 11 lines · Maximo Ramos

Hi!

sorry to bother you but I am trying to use LVM2 in my 2.4.20 kernel ...

the current device-mapper doesn't have a path for 2.4.20 so ...

I've got 2.4.20-dm-7.tar.bz2 but that's a lot of patch files with no README in it ...

I patch my kernel with those files, one-by-one (there are 40) but after the modules building, I've got:

for the hassle of patching i use this
#!/bin/sh
set -e
pname=basename $1
for i in $1/*.patch
do

       pnum=`basename $i`
       pnum=${pnum%.patch}
       patch -p1 -s -N -E -b -z .$pname.$pnum.orig < $i
       for j in `find . -name \*.$pname.$pnum.orig`
       do
               if [ -f ${j%.$pnum.orig}.orig ]
               then
                       rm -f $j
               else
                       mv $j ${j%.$pnum.orig}.orig
               fi
       done

done

to use cd into kernel source dir and run it vs /path/to/2.4.20-dm-7

Quoted 3 lines

[~]$modprobe dm-mod
/lib/modules/2.4.20/kernel/drivers/md/dm-mod.o: unresolved symbol mempool_destroy_Raf572a67

can you confirm you were running from a clean kernel source tree (i.e. you just untarred or made mrproper)

L.

Signature · 6 lines
Luca Berra -- [email protected]
       Communication Media & Services S.r.l.
/"\
\ /     ASCII RIBBON CAMPAIGN
 X        AGAINST HTML MAIL
/ \
#2 lore raw
Quoted 18 lines · Luca Berra

for the hassle of patching i use this
#!/bin/sh
set -e
pname=basename $1
for i in $1/*.patch
do

       pnum=`basename $i`
       pnum=${pnum%.patch}
       patch -p1 -s -N -E -b -z .$pname.$pnum.orig < $i
       for j in `find . -name \*.$pname.$pnum.orig`
       do
               if [ -f ${j%.$pnum.orig}.orig ]
               then
                       rm -f $j
               else
                       mv $j ${j%.$pnum.orig}.orig
               fi
       done
Quoted 3 lines

done

to use cd into kernel source dir and run it vs /path/to/2.4.20-dm-7

I just

cat /tmp/2.4.20-dm-7/*.patch | patch -p1

- Joe