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.
Here is what I typically see on the screen:
######
[ OK ] ...
...
[ OK ] Started Update UTMP aout System Runlevel Changes.
komodo login: [ 19.630871] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps
Full Duplex, low Control: Rx/Tx
[ 19.6313941] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
_ BLINKING CURSOR
BLACKED OUT KEYBOARD AND MOUSE; NO RESPONSE
CAN RESTART 10 MINUTES LATER TO HOST SYSTEM
######
If I wait for about 10 seconds after getting the above, and hit the soft
power button, a bunch of normal-appearing shutdown messages appear, and
the system shuts down normally. The keyboard and mouse are blacked out the
entire time after hitting Enter in the grub selection menu. This is
consistent with what I see in the journalctl log.
I can get a grub prompt by using the RodsBooks boot manager rEFInd
. . .
I copied /boot/grub/grub.cfg from the non-systemd LFS that I finished
building a few days ago, to this new systemd /boot/grub (it did not exist
up to this point), and modified it to work with the appropriate /dev/sdX
numbers (why is the documentation on grub.cfg so poor?) and hdX and gptX
numbers, as well as the UUID numbers. Then I got a normal grub menu after
selecting the appropriate startup icon in the rEFInd boot menu. The first
selection is what you expect: GNU/Linux_SystemD, since that's what I put
in the grub.cfg menu entries. Hitting Enter starts Linux normally, after
immediately blacking out the keyboard and mouse in the normal way. After
the usual [ OK ] messages, the system hangs up, as I described earlier.
So for some reason, grub does not see the vmlinux... image as bootable
without manual intervention. I'm not very clear on what's going on here.
Is the system expecting an initrd?
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.
I found that grub is *extremely* picky about the syntax in grub.cfg. For
example, the line "set root=(hd2,gpt3)" must NOT have a space like this:
"set root=(hd2, gpt3)", or grub boots into its default mode. This example
comes from the EFI booting hint at
http://www.linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt
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.
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?
-- Bruce
--
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
