On Sun, May 15, 2016 at 03:46:02PM -0400, Nathan Bibb wrote: > On Sun, May 15, 2016 at 3:37 PM, Bruce Dubbs <[email protected]> wrote: > > > If we are relatively confident that 'make defconfig' should boot, and I get > the same issue, I am thinking that we can narrow down the issue to how > Debian constructs the GRUB entry when using 'update-grub' from the host. > Does that sound reasonable, or is there something I'm missing? >
Bruce is confident because it works on his hardware :) On older, or different, machines the defaults might not be adequate - e.g. almost everything which has been separated in the last few years will default to N. There are two issues here - 1. The grub entry that you let debian create. From time to time I have let debian-derived distros keep /boot, but since I did not intend to keep debian I edited grub.cfg myself. What we do not know is what that generated debian entry looks like : it might have oddities - please consider posting it if the suggestion below does not help. 2. The kernel config. I strongly suggest that you rerun 'make menuconfig' in chroot, and check whether ALL of the likely libata drivers have been selected. lspci and google will help identify which drivers your motherboard needs. If you need to change the config, rebuild in chroot and then copy (from debian) the bzImage onto the previous LFS kernel. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
