FriendlyELEC-Forum

ejolson wrote:
Note that I've successfully build Wireguard on x86 PCs running Artix linux and successfully on the Raspberry Pi 4 running Raspbian as well as Gentoo

igorp wrote:

ejolson wrote:
Note that I've successfully build Wireguard on x86 PCs running Artix linux and successfully on the Raspberry Pi 4 running Raspbian as well as Gentoo

- best 8812AU driver
- wireguard
- dkms
- kernel headers

= Armbian

ejolson wrote:
Is it possible and how do I install the Armbian Buster minimal distribution to eMMC? I see the download link here

https://www.armbian.com/nanopc-t3/

igorp wrote:

ejolson wrote:
Is it possible and how do I install the Armbian Buster minimal distribution to eMMC? I see the download link here

https://www.armbian.com/nanopc-t3/

Ofc its possible.
https://docs.armbian.com/User-Guide_Get ... d-sata-usb

If you have eMMC model with 2G memory, you need to choose this board:
https://www.armbian.com/nanopc-t3-plus/

Or it wont't work.

Mar 15 03:07:13 matrix iscsid[2207]: iSCSI logger with pid=2208 started!
Mar 15 03:07:13 matrix systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument
Mar 15 03:07:13 matrix iscsid[2208]: iSCSI daemon with pid=2209 started!
Mar 15 03:07:13 matrix iscsid[2208]: can not create NETLINK_ISCSI socket
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Start operation timed out. Terminating.
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Failed with result 'timeout'.

ejolson wrote:

igorp wrote:

ejolson wrote:
Is it possible and how do I install the Armbian Buster minimal distribution to eMMC? I see the download link here

https://www.armbian.com/nanopc-t3/

Ofc its possible.
https://docs.armbian.com/User-Guide_Get ... d-sata-usb

If you have eMMC model with 2G memory, you need to choose this board:
https://www.armbian.com/nanopc-t3-plus/

Or it wont't work.

Thanks! I've got Armbian installed on my NanoPC T3 now and WireGuard installed without any difficulties. Unfortunately, it would appear the Armbian kernel is not compiled with full iSCSI support, so I get something like

Code: Select all

Mar 15 03:07:13 matrix iscsid[2207]: iSCSI logger with pid=2208 started!
Mar 15 03:07:13 matrix systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument
Mar 15 03:07:13 matrix iscsid[2208]: iSCSI daemon with pid=2209 started!
Mar 15 03:07:13 matrix iscsid[2208]: can not create NETLINK_ISCSI socket
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Start operation timed out. Terminating.
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Failed with result 'timeout'.

a 90 second delay when booting and, of course, no iSCSI either.

I'm not looking forward to building my own kernel. If I had wanted to do that, I would have stuck with the original FriendlyARM distribution. Any thoughts what to do next?

igorp wrote:

ejolson wrote:

igorp wrote:
Build system for creating your own Armbian kernel https://github.com/armbian/build is so simple that my mother could do that. You need a PC with Linux.

You can modify https://github.com/armbian/build/blob/m ... acy.config config (I would enable things but don't know exactly what you miss) and ask someone to build the kernel for you ... or wait for next release. Or download .deb build artefacts from Jenkins (if works) when making a PR.

Sticking to outdated FA distro is not what you want.

And this is possible only if you help https://www.armbian.com/donate/

ejolson wrote:

igorp wrote:

ejolson wrote:

I wonder if your mother has a computer science degree. Mine does, but even so, I'm pretty sure in her retirement she has not kept up with docker and other virtualized environments on Linux. Though not retired, neither have I. Will access to QEMU through a remote ssh session be sufficient?

While I understand the FriendlyARM distro is based off an earlier Ubuntu distribution, my only difficulty was lack of kernel headers for the default kernel. Obviously, building my own kernel would have solved that.

My understanding is that

CONFIG_INET=y
CONFIG_BLK_DEV_SD=y
CONFIG_SCSI_LOWLEVEL=y
CONFIG_ISCSI_TCP=M
CONFIG_SCSI_ISCSI_ATTRS=M

are needed for iSCSI support. See, for example,

https://wiki.gentoo.org/wiki/ISCSI/Initiator

Many of the Armbian kernels already have the iSCSI drivers built as modules and it is surprising the NanoPC T3 kernel does not. Note again that I somehow accidentally started this thread in the RK3399 forum rather than the S5P6818 section, so we are, in fact, talking about the 4.14.171-s5p6818 kernel here.

If you were able to change the above flags so the next automatic kernel build for the NanoPC T3 includes iSCSI support, I would greatly appreciate this. Unfortunately, I have never and don't know how to set up a forked GitHub repository and then issue a pull command for the needed changes.