Error Inserting Cloop
a SuSe 9.1 box with kernel version2.6.5 . I followed all the instructions inhttp://www.knopper.net/download/knoppix/cloop.READMEand sucessfully went through compilation, depmod -a and mknod.I don't know how to create a compressed filesystem with cloop yet. Butwhen I tried to load the module into kernel, 'insmod /path/to/cloop.o",there is an error:insmod: error inserting 'cloop.o': -1 Invalid module formatWhat should I do with it? Could anyone help me?I am no expert in kernel modules and really appreciate any hints!Thanks!Lei--Kernelnewbies: Help each other learn about the Linux kernel.Archive: http://mail.nl.linux.org/kernelnewbies/FAQ: http://kernelnewbies.org/faq/ Michel Hubert 2004-07-30 16:02:20 UTC PermalinkRaw Message Starting with kernel 2.6, kernel modules have some versions infosattached to them. Thats the '*.ko' files. That's the one you shouldinsmod.On my side, I have a different problem, specific to SuSE 9.1. It workson other distros with kernel 2.6. When linking, I have the followingwarning: "xxx is COMMON symbol". And then when I try to load themodule: "invalid module format"I know SuSE uses a special branch of gcc 3.3 which includes somefeatures of gcc 3.4. But what could cause that ? The common symbolsare static members attributes of classes which are no different thanmany other similar static members....Any clue ?Post by Lei YangHello,I've got a problem here on installing cloop. I was trying to getcloop-2.0.1 built and installed on a SuSe 9.1 box with kernel version2.6.5 . I followed all the instructions inhttp://www.knopper.net/download/knoppix/cloop.READMEand sucessfully went through compilation, depmod -a and mknod.I don't know how to create a compressed filesystem with cloop yet. Butwhen I tried to load the module into kernel, 'insmod /path/to/cloop.o",insmod: error inserting 'cloop.o': -1 Invalid module formatWhat should I do with it? Could anyone help me?I am no expert in kernel modules and really appreciate any hints!Thanks!Lei--Kernelnewbies: Help each other learn about the Linux kernel.Archive: http://mail.nl.linux.org/kernelnewbies/FAQ: http://kernelnewbies.org/faq/--Michel Hubert <***@matrox.com>Matrox Graphics Inc.--Kernelnewbies: Help each other learn about the Linux kernel.Archive: http://mail.nl.linux.org/kernelnewbies/FAQ: http://kernelnewbies.org/faq/ Lei Yang 20
does not exist. Board index http://forum.linhes.org/viewtopic.php?f=1&t=4307 All times are UTC - 6 hours Powered by phpBB Forum Software © phpBB Group Theme Created By ceyhansuyu Hosting provided by : Linode Cloud Hosting Hosting provided by : Open Source Lab Sponsored by: Ermine Tools for Professional Software Deployment
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack http://unix.stackexchange.com/questions/25421/how-much-strip1-ing-is-okay-for-kernel-modules Overflow the company Business Learn more about hiring developers or posting ads with us Unix https://bugs.launchpad.net/bugs/120512 & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up error inserting and rise to the top How much strip(1)-ing is okay for kernel modules? up vote 7 down vote favorite 1 I regularly create packages for Slackware Linux and part of the process is stripping binaries so that they take up less space. I find that if I strip --strip-all (or strip with no options) kernel modules, they often fail to insert: FATAL: Error inserting cloop (/lib/modules/2.6.38.7-smp/kernel/fs/cloop/cloop.ko): Invalid module format What level of stripping is error inserting cloop recommended for kernel modules? If I use --strip-debug, will I remove debugging symbols that will negatively affect system performance and/or error logging? kernel-modules strip share|improve this question edited Nov 27 '11 at 0:29 asked Nov 26 '11 at 21:16 amphetamachine 2,99711533 add a comment| 2 Answers 2 active oldest votes up vote 8 down vote accepted Stripping all symbols removes the names of the symbols that the module calls. It's not going to work. Stripping debugging symbols with strip --strip-debug *.ko (= strip -g *.ko) is safe. The kernel makefile does it for you if you run make INSTALL_MOD_STRIP=1 modules_install. You can prevent debugging symbols being inserted in the first place by configuring your kernel with CONFIG_DEBUG_INFO not defined. See also How do I strip local symbols from linux kernel module without breaking it? share|improve this answer answered Nov 26 '11 at 23:46 Gilles 371k686741125 add a comment| up vote 2 down vote I believe the safest approach is strip --strip-unneeded. share|improve this answer answered Nov 27 '11 at 1:56 David Schwartz 3,234922 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting
linux-source-2.6.20 (Ubuntu) Edit Won't Fix High Unassigned Edit You need to log in to change this bug's status. Affecting: linux-source-2.6.20 (Ubuntu) Filed here by: enthos When: 2007-06-15 Completed: 2008-03-25 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Won't Fix High Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description md5sum ubuntu-7.04-desktop-amd64.iso a2b159599b69cea51371eee1ec5feda6 *ubuntu-7.04-desktop-amd64.iso boot with usb-cdrom ctrl-alt-f6 sudo su cat /proc/cmdline BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.gz quiet splash -- uname -a Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux mkdir /s3 # /dev/hda3 is ext2 mount /dev/hda3 /s3 modprobe cloop # mknod /dev/cloop1 b 240 1 (cloop1 is exist) # KNOPPIX file is copied from knoppix 5.1.1 losetup /dev/cloop1 /s3/KNOPPIX/KNOPPIX losetup /dev/cloop1 /s3/KNOPPIX/KNOPPIX >err1.txt 2> err2.txt cat err2.txt ioctl: LOOP_SET_FD: Cannot allocate memory dmesg [ 185.562396] cloop: Initializing cloop v2.02 [ 185.570195] cloop: loaded (max 8 devices) [ 192.488850] cloop: out of kernel mem for block buffer (0 bytes) [ 194.886974] cloop: out of kernel mem for block buffer (0 bytes) rmmod cloop modprobe cloop file=/s3/KNOPPIX/KNOPPIX >err3.txt 2> err4.txt cat err4.txt FATAL: Error inserting cloop (/lib/modules/2.6.20-15-generic/kernel/ubuntu/misc/cloop.ko): Cannot allocate memory dmesg [ 331.935216] cloop: unloaded. [ 335.176826] cloop: Initializing cloop v2.02 [ 335.178830] cloop: loaded (max 8 devices) [ 335.178874] cloop: out of kernel mem for block buffe