If I need to make two separate posts instead of just this one let me know. I would like to bring up two significant issues I am still experiencing with my LFS 9.0 (systemd) build that I hope to get resolved somehow.
The first issue is that my system will not create the necessary network interfaces during boot. The only interfaces detected by '*ip a*' are '*lo*' and a '*sit0*' interface for stunnel that I hoped to experiment with once I got everything up and running. I first followed the method in the LFS book of creating .link files for *eth0* and *wlan0* followed by disabling systemd-networkd for use with Network Manager instead since I was building for GNOME. I also have ISC DHCP Client (dhclient) for DHCP use. The only indication I get during boot about the network interfaces are the following messages: *A start job is running for sys/subsystem/net/devices/eth0.device (1 min / 1 min 30 sec)*** *A start job is running for sys/subsystem/net/devices/wlan0.device (1 min / 1 min 30 sec)*** The start jobs will both run until the 1:30 mark at which point they time out and the boot process finishes with no network interfaces. So far I have tried removing the .link files in favor of the udev symlink and trying to use systemd-networkd service instead, but the same error at boot continues. I know for a fact that the kernel is built with the necessary drivers for my Atheros ath10k wireless card and Ethernet. Meanwhile, the other issue I have is in the GNOME desktop where I try to "unlock" settings or mount drives, but when given the "Authentication Required" prompt neither my user password or the root password will work. I can't figure out if the issue is with needing to add my user to a certain group (it is already in wheel for Sudo) or if there is an issue with PAM. Thanks, -- Jared
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
