[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Custom Kernel Won't Boot

On 9/13/05, Alvin Oga <aoga@mail.linux-consulting.com> wrote:

- when you build a kernel:

        - why ??

        - where did you get the kernel source code from

I got the source from stable(sarge)repository which says 2.6.8. But my sarge default kernel is 2.6.8-2-386.

        - where did you get the *.h ( headers ) for your current

from cds.

          kernel you are using in order to build the new kernel


        - do you know the chipset used in your hardware ?

        - the 4 important questions:

                which svga chipset
                which nic chipset
                which sound chipset
                which dma chipset

How to find out svga, dma chipset

                ( see the output of lspci .

                - i assume you know exactly what cpu you have

pentium m 1.4 ghz

                and all the cpu flags it uses

How to know?
Should I use any patch to the source installed so that 2.6.8 becomes 2.6.8-2-386?

        - make xconfig and start clicking away ..

                - if you donno what that option is for .. turn it off
                - most of the defaults in the kernel source
                from kernel.org is wrong ( left on for the wrong reasons )
                        - tons of kitchen sink stuff you dont need
                        in your otutdoor tent  ( your own hw )

- you're allotted 10 minutes to click things on and off to
  define your kernel ... and you're done after that making
  your custom kernel, install /vmlinuz and running lilo is 30 seconds

- if you build all the chipset drivers into the kernel:
        - you do NOT need an initrd
        - you have built your own kernel if it boots and works

- see the kernel-howto for all the itty bitty details

- and if you wanna start to play ..
        - harden your kernel with the gazillion kernel security patches

Kindly let me know further how to proceed in debian for compiling kernel?

linux user No.205042
Reply to: