-------- Forwarded Message --------
Subject: Re: [lfs-support] Where Do I Go From Here on Booting systemd
Development?
Date: Wed, 17 May 2017 21:39:59 -0600
From: Alan Feuerbacher <[email protected]>
To: Ken Moffat <[email protected]>
On 5/17/2017 9:00 PM, Ken Moffat wrote:
On Wed, May 17, 2017 at 07:59:57PM -0600, Alan Feuerbacher wrote:
Hi,
I managed to get LFS Development systemd "Version 20170513-systemd" to boot
to the point that a number of the usual Linux startup lines appear on the
screen. Then things hang completely. I don't know where to go from here.
Help!
I haven't tried to boot a systemd version for a long time, so I
can't offer many suggestions - but nevertheless, here are a few
random comments :
Last lines upon startup:
#######
. . .
[ OK ] Started Update UTMP about System Runlevel Changes.
That sounds as if systemd is running. That would mean that
filesystems and disk drivers are successfully loaded.
That's what I also concluded, from the fact that a login prompt appeared.
For sysv I would suggest starting with init=/bin/bash and stepping
through the initscripts, but I don't think you can do that in
systemd. For sysv I would also suggest looking at the logs (if any)
from chroot, but again I think your binary logs will prevent that.
Oy! The reason I'm going for systemd is the challenge. Also to get a
full UEFI boot working.
<machine-name> login: [14.278504] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: rx/Tx
[ 14.281052] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
#######
Then the machine completely hangs and I have to power cycle.
Are you relying on nfs or another sort of network filesystem such as
samba ? I can recall that getting nfs to work in systemd was a
PITA.
No.
Host distribution: Fedora 25
Host system requirements all met
Booting using RodsBooks rEFInd boot manager
ASUS TUF Mark I MB
Bios set to UEFI boot, Secure Boot disabled
Using kernel EFI boot stub
initrd image made using mkinitramfs script from BLFS chapter 5
Do you need an initrd ?
Everything I've read indicates Yes: BLFS, ArchLinux, RodsBooks.
Generally it is easier to build in what
needs to be built in (filesystems, disk drivers) and make everything
else modules. Once it boots, you may well need to add extra things
as built-in, and therefore rebuild the kernel/modules (ideally with
a different extraversion so that you don't trash the previous
version).
Part of the reason I'm going to this trouble is to end up with a hard
drive containing LFS that I can put in another computer and expect to
run Linux with minimal changes. Again this is a learning exercise.
For deciding what needs to be built in, look at lsmod on a running
(distro) system and assume all used modules are needed.
There are upwards of 100 modules listed, which I have no clue about.
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
