-----Oprindelig meddelelse-----
Fra: lfs-support-boun...@linuxfromscratch.org
[mailto:lfs-support-boun...@linuxfromscratch.org] På vegne af Bruce Dubbs
Sendt: 21. marts 2013 20:06
Til: LFS Support List
Emne: Re: [lfs-support] Kernel can not boot

Niels Terp wrote:
> Hi there,
>
> I have build LFS several times now, and I wanted to upgrade to the new 
> kernel 3.8.3.
>
> I started out from scratch, the only change I made from the book was 
> the new kernel. Since I have a quad-core processor in my laptop, I 
> made all the builds whith the make flag '-j 4'. And because I had made 
> the build several times on the same hardware, I skipped most of the 
> tests. It didn't work :-(
>
> Then I repeated the whole thing, this time without the make flag. It 
> still didn't work.

What didn't work?  Boot?  What happened?

> Is there anything special I should do, to use the 3.8.3 kernel ? And 
> now
> 3.8.4 is out, what about that one ?

Use the latest.

> And by the way, what is the correct procedure if I want to upgrade the 
> kernel after an installation is finished ? I guess I would have to 
> extract the headers, and rebuild GCC and GLIBC ? What about the other 
> programs, is any of them using the kernel headers ?

Just build the kernel and copy to /boot.  Then update grub.cfg.  Do
*not* change the headers.  They need to be the same as used for building
glibc.  The is no need to update gcc or glibc.

   -- Bruce

--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Thank you Bruce,

What happened was, that the boot started, but ended in kernel panic, then
the screen scrolled on very fast, obscuring what exactly happened.

If I understand you right, I can just rebuild the kernel, copy the files to
/boot and then update GRUB, so I think I will go for that solution.

Niels

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to