[SOLVED] failed to start network service LFS systemd 9.1

TheRealGrogan · 04-12-2020, 02:03 AM

Code:

CONFIG_ALX:  
  │
  │ This driver supports the Qualcomm Atheros L1F ethernet adapter,
  │ i.e. the following chipsets:
  │
  │ 1969:1091 - AR8161 Gigabit Ethernet
  │ 1969:1090 - AR8162 Fast Ethernet
  │ 1969:10A1 - AR8171 Gigabit Ethernet
  │ 1969:10A0 - AR8172 Fast Ethernet

Things to look at... can you tell from LSPCI exactly what Atheros ethernet you have?

What does dmesg say? Is the driver initializing? Is a network interface coming up? I assume by "same problem" you mean the systemd services not starting.

On your Kali Linux host that you used to build LFS, what does dmesg say as the driver is initializing?

extrimis · 04-12-2020, 02:06 AM

The Ethernet controller is Qualcomm atheros QCA8172 Fast Ethernet (rev 10)

extrimis · 04-12-2020, 02:20 AM

All interfaces appear when i type ifconfig -a

i think its not with the drivers

when i run systemctl status systemd-networkd.service this is the output

Click image for larger version

Name: Screenshot_2020-04-12_03-16-54.png
Views: 41
Size: 169.9 KB
ID: 32956

Click image for larger version

Name: Screenshot_2020-04-12_03-17-37.png
Views: 30
Size: 93.0 KB
ID: 32957

when i checked status=200/CHDIR in google it says the working directory is missing.

i tried a lot of techniques nothing works

the only thing that works is by disabling the service but that disables the network connectivity also

extrimis · 04-12-2020, 02:22 AM

Click image for larger version

Name: 5.jpg
Views: 24
Size: 112.0 KB
ID: 32958

lspci output

extrimis · 04-12-2020, 02:23 AM

plz help me

TheRealGrogan · 04-12-2020, 02:31 AM

Is all of that output from the bare metal install of your LFS on the host? It is not useful to show me things from Qemu. If that lspci output is from the Kali Linux host, we know it's working there.

On a LFS system that's got no X11 install yet, you probably can't copy and paste, but you can redirect to txt files and then copy and paste lines from there on a working system.

lspci -vv > lspci.txt
dmesg > dmesg.txt

extrimis · 04-12-2020, 02:55 AM

lspci output of host system (Kali Linux)

lspci-host.txt

lspci output of LFS System booted on Thoshiba Satellite Laptop

lspci-LFS.txt

dmesg output of host System (Kali Linux)

dmesg-host.txt

dmesg output of LFS System booted on Thoshiba Satellite Laptop

dmesg-LFS.txt

TheRealGrogan · 04-12-2020, 04:38 AM

Yes, it looks like the driver is loading and binding to the device.

So, your wired network adapter is enp3s0 (not enp0s3 as it is in the Qemu guest)

Try this:

Code:

[Match]
Name=enp3s0

[Network]
Address=192.168.43.12
Gateway=192.168.43.1
DNS=192.168.43.1

LinkLocalAddressing=no
IPv6AcceptRA=no

extrimis · 04-12-2020, 04:40 AM

Ok I'll try now

extrimis · 04-12-2020, 04:44 AM

No it doesn't work same issue

TheRealGrogan · 04-12-2020, 05:46 AM

Well, you needed to get your network configured correctly anyway.

I don't know exactly why but my guess would be that the 200/chdir error means the service's working directory is not present, or has wrong permissions/ownership. I think that's:

/run/systemd/network

extrimis · 04-12-2020, 05:48 AM

What permissions are required

extrimis · 04-12-2020, 06:25 AM

Do you know how to find the working dir

TheRealGrogan · 04-12-2020, 12:35 PM

I wonder about your kernel config. Under Filesystems -> Pseudo Filesystems, do you have Tmpfs POSIX Access Control Lists and Tmpfs extended attributes enabled?

extrimis · 04-12-2020, 12:37 PM

I have to check.do i have to enable that if it is disabled