Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
05-06-2006, 04:40 AM
|
#1
|
Member
Registered: Feb 2002
Posts: 393
Rep:
|
This makes no freaking sense! Can't isntall Kernel?
Hi I compiled a kernel on Ubuntu Debian in the normal way:
make-kpkg clean && make-kpkg --initrd --revision=custom.1.0 kernel_image
However after the kernel had compiled without errors and I had navigated to the upper level directory containing my new kernel and try to install it using
dpkg -i kernel-2.6-16.deb I get a complaint that the kernel-2.6-16.deb already exists - which is just a standard warning as I had already compiled a previous version of this kernel (although I hadn't used it yet - as I had to go back and add some modules I had missed). The message warned me that if I went ahead and installed in that directory that this might cause me some problems. So I quit the install/dpkg process and renamed the folder to kernel-2.6.16.old and then I ran dpkg -i kernel-2.6-16.deb again. However this time I got another error message saying 'error can't find directory /lib/modules/kernel-2.6.16.' The process then dies and refuses to continue. So I get an error whether the /lib/modules/kernel-2.6.16 directory is present or whether it isn't. It's a totally nonsensical condition.
I also get an error message when trying to install that says can't locate module dm.mod - which as it appears to be the device mapper module would seem to be quite important. (Although I'm still not quite clear what it is?)
It may or may not be significant - but I am trying to compile and install a 2.6.16 kernel on a system that is currently running a recent 2.4x kernel version. It is much too complicated and irrelevant to go into detail on why I am running a 2.4x kernel, execpt to say that this really is currently my only option). I have (I think) all of the required tools installed - so the question is what on earth is going on?
If I create an empty directory (since this is what dpkg appears to expect to find) at /lib/modules/linux-2.6.12 the kernel will install - but there is no modules created in the /lib/modules/linux-2.6.12 folder.
Obviously I must still be missing some important stuff - but the question is what? And why would the kernel compile cleanly if I was missing some files/modules that dpkg expects to find?
GJ
|
|
|
05-06-2006, 07:19 AM
|
#2
|
Senior Member
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: Gentoo, LFS, Debian,Ubuntu
Posts: 1,537
Rep:
|
The file /lib/modules/<kernel version> is created when you compile a new kernel namely the make modules_install part. If you remove this directory then the kernel will not know where to find its files. Im not famillair with your particular distro but from what i can gather rename that back to what it was and just overwrite it anyway.
hope this helps.
PS. You can always just manually install the kernel by moving the file bzImage usaully located for x86 in arch/i386/boot/ and modifying ither lilo.conf in /etc or menu.lst in /boot/grub to point to the new kernel. And of cource the make modules_install in the kernel to install the modules.
|
|
|
05-06-2006, 10:40 AM
|
#3
|
Member
Registered: Feb 2002
Posts: 393
Original Poster
Rep:
|
Are you sure? kpkg by rights should install it's own /lib/medules/kernel-xxxx version in that directory. It not only builds the kernel - but it builds all the needed modules too. (Or at least it should).
The problem is that it hasn't done that - and the process isn't working properly at all.
GJ
|
|
|
05-06-2006, 04:14 PM
|
#4
|
Senior Member
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: Gentoo, LFS, Debian,Ubuntu
Posts: 1,537
Rep:
|
Not sure but the make file that comes with the kernel builds all the modules as well. Ive never used a automated kernel builder ive always built the kernel manually. So maybe im the wrong person to ask about this. I just wanted to give you an alternative.
|
|
|
All times are GMT -5. The time now is 12:21 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|