On Mar 8, 2016 11:19 AM, "Ken Moffat" <[email protected]> wrote: > > On Tue, Mar 08, 2016 at 06:01:31AM -0700, Roger Koehler wrote: > > > > Yes. I tried that. I downloaded a bunch of kernels. I am going to build LFS > > with each one until I find the one that breaks it and then look through the > > release notes. > > I hope you do not mean that the way I am reading it (rebuild LFS on > each). > > Just build the initial version of each kernel release (e.g. 3.18.0, > 4.1.0, 4.4.0) to see where it broke. Also, review the options which > 'make oldconfig' offers you, and check any help for that option. > > If you find a kernel option which does not do what you thought it > would, all well and good (been there, reduced the box to running on > one core). If it is still broken, you can then bisect and take it > to the kernel list (fun!). > > If 4.4.0 turns out to be ok, try the latest 4.4 and if that is still > broken, bisect the stable tree between 4.4.0 and that kernel - use > the stable tree for that.
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.
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
