From: cestjihef@free.fr   
      
   Aragorn wrote:   
      
      
   > I have no experience with "eselect", but my recommendation would be to   
   > build your kernel with all the required drivers statically linked, i.e.   
   > use "Y" instead of "M" in the kernel configuration.  First write down   
   > what drivers you need, based upon the hardware in the machine and any   
   > potential hardware you plan on connecting to the machine for which an   
   > in-tree driver exists, plus of course all the filesystems that you want   
   > to have support for.  For instance, if your root filesystem is on ext3,   
   > then you should definitely have ext3 statically linked into the kernel,   
   > or otherwise you're going to need an /initrd/ with ext3 support.   
   >   
   > Since you're already using "menuconfig", it's trivial to select all the   
   > required drivers to be built in.  The advantage is that you won't need   
   > an /initrd/ anymore and that the kernel will boot a little bit faster -   
   > not that this is really noticeable.   
   >   
   > Do however remember to leave the option for loading kernel modules   
   > enabled if this is a kernel for a desktop/workstation machine and you   
   > are going to use proprietary video and/or wireless drivers on it.  As   
   > those drivers come as binary blobs only, you cannot build them into the   
   > kernel image directly.  (It would also be a violation of the GPL.)   
   >   
   Thanks for your answer :)   
   That is what I do : "Y" for modules that work, an "M" for others ( nvidia,   
   ...) .   
   Now, the boot is OK, and indicates   
   "This is jf_hp at chez.moi ( linux i686 2.6.31.gentoo-r6 )"   
   which matches the kernel   
   But I can't build the dvb modules I need, they still build in "2.6.30-r8"   
   I've had a look at makefile, but I can't see what to chage there.   
      
   jf   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)