by keithspg » Sun Jul 12, 2020 10:23 pm
Does anyone know why an nfs mount in my /etc/fstab does not mount at boot with this kernel/image? Does it have to do with uboot, somehow? I created this image by making a clean image with the aarch64 image:
$this->bbcode_second_pass_code('', 'http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-3-latest.tar.gz')
then build moonman's kernel and then installed it then built and installed the userland from this:
$this->bbcode_second_pass_code('', 'https://aur.archlinux.org/packages/raspberrypi-userland-aarch64-git/')
The line is:
$this->bbcode_second_pass_code('', '192.168.2.198:/mnt/stuff /mnt nfs _netdev,rw,vers=4.1 0 0
')
This same line works when I boot the same device on the same network as armv7, but fails when I boot it as aarch64.
After I get a prompt, I can always 'mount -a' and it mounts, so I do have everything needed (nfs wise) installed, it is just strange to me that I cannot get it to do this at boot. I am running a kernel compiled with moonman's PKGBUILD but with 1 mod:
$this->bbcode_second_pass_code('', 'diff config8 ../moonman/linux-raspberrypi4/config8
7321c7321
< CONFIG_PKCS8_PRIVATE_KEY_PARSER=m
---
> # CONFIG_PKCS8_PRIVATE_KEY_PARSER is not set
')
I made this mod to the kernel config to get iwd running. It is:
$this->bbcode_second_pass_code('', 'Linux build64 5.4.45-1-ARCH #1 SMP PREEMPT Wed Jul 1 20:34:37 CDT 2020 aarch64 GNU/Linux
')
Other than this minor issue, everything I need seems to work. I have an i2s card and a 3.5" tft resistive touchscreen loaded as dtoverlays and have connman/iwd managing the ethernet connections.