Success booting systemd!
On 6/7/2017 10:47 AM, Bruce Dubbs wrote:
Alan Feuerbacher wrote:
On 6/6/2017 6:19 PM, Alan Feuerbacher wrote:
A quick update on debugging booting of systemd.
Systemd appears to boot ok up to a point, but then, after putting
out a login prompt and a bit of other stuff, puts out no more messages.
However, the system still appears to be running.
Grub seems to have been expecting /boot/grub/grub.cfg.
After looking over the LFS book's notes on grub again, I found that a
simple grub.cfg, based on section 8.4.4 "Creating the GRUB Configuration
File" in the LFS book, can be used, with slight modifications. The trick
is exactly what to modify.
...
The LFS book also mentions the command grub-mkconfig, which I believe I
ran in the running non-systemd system I got running a few days ago, in
order to create the complicated grub.cfg that now resides on that system
in /boot/grub. Unfortunately that command does not run in the chroot
environment I still have to use. It gives this error:
/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
We recommend that you not use grub-mkconfig. You are on your own if you
use it. It is actually a lot easier to modify grub.cfg manually. There
are only about 7 lines to be concerned about. If adding a new build,
there are on;t 2 or 3 lines: menuentry, linux, and possibly initrd.
Yes, I've more or less sorted that out. The only reason I ran
grub-mkconfig when building LFS-8.0 was out of desperation, because I
could not get the picky syntax right. Running grub-mkconfig helped me
sort that out.
For your input problems on boot, it really sounds like a kernel driver
issue. Use a known good kernel. If you use modules, be sure
/lib/modules/<version> is copied to the new system.
BTW, you did run make modules_install when you built the kernel you are
having problems with, right?
Yes, I had done that.
But your comments got me to look over the .config file in linux-4.9.9
again. Turns out it was messed up, not even having the EFI stub module
set. I had copied the .config from the earlier, successful LFS-8.0
build, but I must have royally screwed it up, and the .config that the
systemd build was using was essentially the default. So I copied it
again, made sure the EFI stub module was set, recompiled, and now
systemd boots up normally. Now I have some cleanup to do.
Thanks!
Alan
--
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
