Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > Kernel Questions

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 31st January 2009, 19:06
anw anw is offline
Member
 
Join Date: Feb 2007
Posts: 53
Thanks: 0
Thanked 6 Times in 6 Posts
Default make-kpkg comes to work, but finds nothing to do

I am experimenting with different options for the kernel in preparation for ultimately trying to get a root-on-LVM installation working (and wondering what difference various preemption algorithms make), and am having some basic problems. I am using the 2.6.18 source with the P4 processor family and 4 gig memory. Here are the anomalies:

1. First and foremost, make-kpkg --initrd tells me there's nothing to do and won't build anything. It built the first time after I unpacked the source, and that was it. Spending a lot of google time only has shown me I'm not the only one to have this problem, but I've found no solution. I've tried make clean, make mrproper, and deleteing 'debian' in the source directory, and, in all cases, make-kpkg thinks for a while, spits out some stuff that doesn't *seem* to be relavant, then comes back and says nothing to do. make deb-pkg works, but I have to build the initrd separately and I have no idea what I may be missing by not using make-kpkg (although it does boot and I'm working under a new kernel now).

2. On boot, I get two messages, and can't find where in "make menuconfig" to fix them: "unknown file system type 'devfs'", and "sbp2 ieee1394 driver forced to serialize I/O". The first seems to be (according to google) because I'm using udev but have devfs compiled into the kernel. I can't find anywhere to get rid of it in the kernel (using "make menuconfig"). For the other message, it is, of course, the firewire, but I can't find any option that seems to "un-serialize" the I/O.

On question #2, it would be nice if there was an index somewhere that cross-referenced all the options with where they were in menuconfig, a la apropos. Is there such a thing? Although I'm beginning to think both of these may be module issues.

TIA!
anw
Reply With Quote
Sponsored Links
  #2  
Old 1st February 2009, 13:36
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,722 Times in 2,563 Posts
Default

Quote:
Originally Posted by anw View Post
I am experimenting with different options for the kernel in preparation for ultimately trying to get a root-on-LVM installation working (and wondering what difference various preemption algorithms make), and am having some basic problems. I am using the 2.6.18 source with the P4 processor family and 4 gig memory. Here are the anomalies:

1. First and foremost, make-kpkg --initrd tells me there's nothing to do and won't build anything. It built the first time after I unpacked the source, and that was it. Spending a lot of google time only has shown me I'm not the only one to have this problem, but I've found no solution. I've tried make clean, make mrproper, and deleteing 'debian' in the source directory, and, in all cases, make-kpkg thinks for a while, spits out some stuff that doesn't *seem* to be relavant, then comes back and says nothing to do. make deb-pkg works, but I have to build the initrd separately and I have no idea what I may be missing by not using make-kpkg (although it does boot and I'm working under a new kernel now).
How exactly did you try to build the kernel? Did you try this tutorial? http://www.howtoforge.com/kernel_com...on_debian_etch

Quote:
Originally Posted by anw View Post
2. On boot, I get two messages, and can't find where in "make menuconfig" to fix them: "unknown file system type 'devfs'", and "sbp2 ieee1394 driver forced to serialize I/O". The first seems to be (according to google) because I'm using udev but have devfs compiled into the kernel. I can't find anywhere to get rid of it in the kernel (using "make menuconfig"). For the other message, it is, of course, the firewire, but I can't find any option that seems to "un-serialize" the I/O.
I guess you need to build a ramdisk that you use for booting the system.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #3  
Old 1st February 2009, 16:36
anw anw is offline
Member
 
Join Date: Feb 2007
Posts: 53
Thanks: 0
Thanked 6 Times in 6 Posts
 
Default

Thanks for the help, Falko! It appears I left the target off my make-kpkg command:
Code:
make-kpkg --initrd
instead, should have been:
make-kpkg --initrd kernel_image
As for #2, in the process of continuing to research this, it came to my attention that the 2.6.18 kernel I'm on is several revs behind; so I'm upgrading to the 2.6.26 kernel, then see if I still have these problems.

Meantime, I got sidetracked on a different task, with a post coming imminently on the problem there!!

Again, thanks for the help.

anw
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Mail server using Postfix, Dovecot, Mysql... Postfix virtual maps doesn't work?? tarasbuljba HOWTO-Related Questions 33 28th May 2010 14:33
MAKE - not there in new install mspIggy Installation/Configuration 4 5th July 2008 16:08
ERROR: The PHP binary coming with ISPConfig does not work properly on your system! Th shadowspank Installation/Configuration 9 9th February 2008 18:55
ERROR: Could not make ClamAV chua_jose Installation/Configuration 1 3rd January 2008 16:47
'make : *** no rule to make target 'install'.Stop. dowell Installation/Configuration 1 30th August 2007 21:03


All times are GMT +2. The time now is 17:54.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.