Re: Module problems
You forget to do a couple important steps if you're using modules. 1. After make-kpkg -revision... kernel_image do make-kpkg modules_image . 2. Then either: a) mv /lib/modules/[kernel version] \ /lib/modules/[kernel version]-old or b) rm -rf /lib/modules/[kernel version] 3. Then do dpkg -i ../kernel-source... -- Eric G. Miller Powered by the POTATO (http://www.debian.org)!
Re: Module problems
Eric G . Miller wrote: You forget to do a couple important steps if you're using modules. 1. After make-kpkg -revision... kernel_image do make-kpkg modules_image . Actually 'make-kpkg kernel-image' also compiles any modules you configured. So it is not necessary to do this extra step. I never have. -- Paul Miller [EMAIL PROTECTED] Where do all the bits go when the computer is done with them?
Re: Module problems
| You forget to do a couple important steps if you're using modules. | 1. After make-kpkg -revision... kernel_image do | make-kpkg modules_image . | | Actually 'make-kpkg kernel-image' also compiles any modules you | configured. So it is not necessary to do this extra step. I never have. Correct. I was thinking of add-on modules that live under /usr/src/modules. -- Eric G. Miller Powered by the POTATO (http://www.debian.org)!
Re: Module problems!
On Mon, Jul 05, 1999 at 09:06:23AM +0530, Ramakrishnan M wrote: hello, I had been reading the Linux Device Drivers,and tried running the first program. #define KERNEL #include ... ...init_module(...) . when I do insmod prog.o it says the program has been compiled to run on kernel 2.2.5 and the running kernel is 2.2.10. Sure! I have 2.2.10 kernel running but I am not able to understand the 2.2.5 business. Itried installing an older kernel and recompiled it,with no useful result.Please help! TIA Ramakrishnan M World Wide Web: http://www.ee.iitm.ernet.in/~ee98m09 -- A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null /usr/include/linux is usually a symbollic link to /usr/src/linux/include/linux But, in Debian, for reasons I've forgotten, /usr/include/linux is a copy of the headers for whatever kernel the package maintainer had installed at the time. I think the line of reasoning is that very few programs really care about the version of the kernel headers. Unfortunately, you've got module versioning as an option in the kernel, so it is going to check the version.h the module was compiled against with the one in the kernel. I'd suggest recompiling your module with -I/usr/src/linux/include/linux, provided you have the kernel source installed. -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
Re: Module problems!
Quoting Ramakrishnan M ([EMAIL PROTECTED]): hello, I had been reading the Linux Device Drivers,and tried running the first program. #define KERNEL #include ... ...init_module(...) . That first line is wrong, but I guess you copied into the email wrongly. when I do insmod prog.o it says the program has been compiled to run on kernel 2.2.5 and the running kernel is 2.2.10. Sure! I have 2.2.10 kernel running but I am not able to understand the 2.2.5 business. Itried installing an older kernel and recompiled it,with no useful result.Please help! I compile modules with something like gcc -DMODULE -D__KERNEL__ -I. -I/usr/local/src/linux/include \ -O2 -m486 -g -Wall -c $@ -o foo.o foo.c where linux is a link to the kernel source tree. Now that kernel-source packages just install a .tgz file rather than the tree, and you have to untar the tree yourself, you have to make sure that link is correct (or use the full name -I/usr/local/src/kernel-source-2.2.10/include instead). Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
