On Sat, Oct 26, 2019 at 03:28:06PM -0400, Jared Stevens via blfs-support wrote:
> 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.
>
Does ifconfig -a show any interfaces of the form enp* (wired) or wl*
(wireless). If it does, it turns out to be easier in the long run
to just use that naming. On my laptop I have enp1s0f1 and wlp2s0,
on my latest desktop the wired connection is enp8s0.
More generally, for wired ethernet the main requirement is to get
the correct driver. Wireless also usually needs other modules and
firmware. And then getting it to login to your wifi is a painful
process until everything has been built.
From a system running LFS, try lspci -vv and look for the Ethernet
Controller and anything described as Wireless. Or better, do that
on a distro kernel to see what the 'Kernel modules:' information in
lspci says, followed by using lsmod and attempting to track down the
dependant modules.
> I know for a fact that the kernel is built with the
> necessary drivers for my Atheros ath10k wireless card and Ethernet.
>
Ah, I didn't initially see that. I happen to have ath10k on this
laptop.
You may need to rebuild / reboot several times, particularly when
firmware is needed. Using modules (to save building the firmware
in, i.e. just find and download the next blob, install it in the
appropriate /lib/firmware/ subdirectory, reboot) is the more
productive approach.
While trying to load the atheros, looking at either the system
journal or dmesg should hopefully tell you about missing modules or
missing firmware.
For my ath10k (yours might be different, the driver covers many
variants) I have /lib/firmware/ath10k/QCA9377/hw1.0/ with several
blobs, and also /lib/firmware/qca with a couple of blobs (not sure
if those are for the wifi, or for a dependant module).
FWIW, my own laptop still has a metric shed-load of modules I'm
fairly sure I don't really need, simply because identifying what
kernel config options select some of the modules is a very
non-trivial business. And I haven't attempted to update it to
LFS-9.0 yet because I need to take time to remind myself about all
the details of getting the wifi working with wpa_supplicant for the
time when network-manager-applet has not been installed.
Therefore, getting the wired ethernet working is probably the
quickest way forward.
ĸen
--
Trogdor wæs un mann, On hsendlio he wæs un Draca-mann,
On hsendlio he wæs un Draca, Ac he wæs níwene TROGDOR! TROGDOR!
~ Trogdur þæm Bærnettamber (Trogdor the Burninator)
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
