Hi guys,
I'm back to building LFS stable systemd, and having problems getting
it to boot.
I'm trying to debug the boot problems as much as I can on my own, since
that's a good way to learn.
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
######
When grub starts up normally (like when booting the host system), the
mouse and keyboard lights turn off, then turn back on again after a
second or two. In my case with this new systemd, the lights never turn
back on, even though systemd is putting out normal kernel messages.
I know that the system is still running because the computer's soft
power button successfully shuts down the system. The apparently
running systemd goes through a full shutdown procedure, as shown in the
journalctl log. However, the keyboard and mouse are dark and not
functional, so there is no way to respond to the login prompt.
I can get a grub prompt by using the RodsBooks boot manager rEFInd
(this
works quite well for booting all other working OS's on my system,
including LFS non-systemd version 8.0 and Fedora. rEFInd is installed
on
a non-used drive /dev/sdb). Once I get the grub prompt, the session
goes
like this:
###
grub > linux /vmlinuz-4.9.9-lfs-8.0-systemd root ro
grub > boot
###
Then the mouse/keyboard lights turn off, systemd starts booting, and
eventually appears to quit working after putting out the boot prompt.
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?
Systemd keeps a boot log via journalctl, which I'm learning to use.
Using this command in the Fedora host system, I can read the boot log of
the new systemd, like this (after mounting the systemd hard drive root
partition on /lfssdc/root):
###
journalctl -D /lfssdc/root/var/log/journal -x > journal.1x
###
The "-x" adds a bunch of explanatory messages to the output.
There seem to be no fatal error messages in the output.
The log begins, after the first reboot, with:
###
-- Reboot --
Jun 06 14:37:59 komodo kernel: Linux version 4.9.9 (lfs@komodo) (gcc
version 6.3.0 (GCC) ) #1 SMP Mon Jun 5 14:39:00 MDT 2017
Jun 06 14:37:59 komodo kernel: Command line: BOOT_IMAGE=/vmlinuz-4.9.9-
lfs-8.0-systemd root=/dev/sdc4 ro
###
The 2nd line above is what I would expect, given that it's what I gave
to grub.
After removing all of the old journalctl log files from the journal
directory (you must set ownership like this:
###
drwxr-sr-x 3 root systemd-journal 4096 Jun 6 16:22 journal)
###
I uninstalled all of the "make install-XXX" programs in
blfs-systemd-units-20160602 and rebooted systemd. I saw the same
behavior as described above. Then I recompiled the GPM service and
restarted it with "make install-gpm", then rebooted the system again.
This time the gpm daemon startup appeared to work ok, but I saw this
message in the log which I don't understand:
###
Jun 06 14:37:59 komodo systemd[1]:
[/etc/systemd/system/gpm.service.d/99-user.conf:1] Assignment outside
of section. Ignoring.
###
It appears that GPM started ok, because these messages appear in the
log:
###
Jun 06 14:38:06 komodo systemd[1]: Starting Virtual console mouse
server...
-- Subject: Unit gpm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gpm.service has begun starting up.
Jun 06 14:38:06 komodo /usr/sbin/gpm[2454]: *** info
[daemon/startup.c(136)]:
Jun 06 14:38:06 komodo /usr/sbin/gpm[2454]: Started gpm successfully.
Entered daemon mode.
Jun 06 14:38:06 komodo systemd[1]: Started Virtual console mouse
server.
-- Subject: Unit gpm.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gpm.service has finished starting up.
--
-- The start-up result is done.
Jun 06 14:38:06 komodo /usr/sbin/gpm[2454]: *** info [mice.c(1990)]:
Jun 06 14:38:06 komodo /usr/sbin/gpm[2454]: imps2: Auto-detected
intellimouse PS/2
###
After powering the computer down and back, these messages appear toward
the end of the log:
###
Jun 06 14:48:28 komodo systemd[1]: Stopping Virtual console mouse
server...
-- Subject: Unit gpm.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gpm.service has begun shutting down.
Jun 06 14:48:28 komodo systemd[1]: Stopped Virtual console mouse
server.
-- Subject: Unit gpm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gpm.service has finished shutting down.
###
So the GPM service has clearly been started and stopped by the kernel.
The last few lines in the log before reboot are:
###
Jun 06 14:38:12 komodo systemd[1]: Started Hostname Service.
-- Subject: Unit systemd-hostnamed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hostnamed.service has finished starting up.
--
-- The start-up result is done.
Jun 06 14:38:12 komodo systemd-networkd[2437]: enp0s31f6: Configured
Jun 06 14:38:12 komodo systemd-timesyncd[2433]: Network configuration
changed, trying to establish connection.
Jun 06 14:38:43 komodo systemd-timesyncd[2433]: Synchronized to time
server [2001:4860:4806:8::]:123 (time3.google.com).
###
It's at this point where the login prompt seems to show up on the
screen. I see no indication of why the system does not power up the
keyboard and mouse.
After waiting about ten minutes, I power cycled the computer using the
soft power button. Here's what's the journal log shows:
###
Jun 06 14:38:43 komodo systemd-timesyncd[2433]: Synchronized to time
server [2001:4860:4806:8::]:123 (time3.google.com).
Jun 06 14:48:28 komodo systemd-logind[2435]: Power key pressed.
Jun 06 14:48:28 komodo systemd-logind[2435]: Powering Off...
Jun 06 14:48:28 komodo unbound[2455]: [2455:0] info: service stopped
(unbound 1.6.0).
Jun 06 14:48:28 komodo systemd-logind[2435]: System is powering down.
-- Subject: System shutdown initiated
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Systemd shutdown has been initiated. The shutdown has now begun and
-- all system services are terminated and all file systems unmounted.
###
So clearly, the system stopped in some odd state, but was still able to
shut down normally.
Ideas?
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
