On Wed, Mar 09, 2016 at 11:37:12AM -0700, Roger Koehler wrote: > On Wed, Mar 9, 2016 at 11:34 AM, Roger Koehler > <[email protected]> wrote: > > On Mar 9, 2016 11:22 AM, "Ken Moffat" <[email protected]> wrote: > >> > >> On Wed, Mar 09, 2016 at 08:48:27AM -0700, Roger Koehler wrote: > >> > > >> > This is very disturbing. I built the 3.16.7 kernel as a baseline using > >> > the > >> > LFS-7.9 tool chain, and it doesn't boot. My grub just sits there, but > >> > when > >> > I load the same kernel built with the LFS-7.6 tool chain, it works fine. > >> > I > >> > built LFS-7.9 using jhalfs with the 3.16.7 headers per Pier's > >> > instructions > >> > in the README.CUSTOM file. > >> > > >> > I guess I'll start with 4.2 and work my way backwards. > >> > >> If *grub* just sits there, that is not a kernel problem - those only > >> start once grub transfers control to the kernel. > > > > So why does it work when I just change the name of the kernel? > >
But are you sure that it is grub that is hanging ? If you get a message about it loading vmlinuz-whatever (I forget the text, and on a normal boot there is not time to read it) then the kernel has started, but perhaps not got very far. And rebuilding LFS with different kernel headers is wasting your time : the book builds glibc with --enable-kernel=2.6.32 so *any* kernel newer than that should be able to run. If the 3.16.7 kernel built with current LFS does indeed fail to boot (I would expect you to see at least a few lines of kernel output before it dies) then that could perhaps be caused by old kernel code which got miscompiled by newer gcc - that is possible, 3.16 has not been maintained for ages. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
