I followed mostly the howto https://gist.github.com/pezz/5310082 (differences being that yaourt does not work any more, that the manual was not for Raspberry Pi 3, that it uses /boot/cmdline.txt and /boot/config.txt, not /boot/boot.txt).
The relevant line of boot.txt is:
$this->bbcode_second_pass_code('', 'setenv bootargs earlyprintk console=ttyGS0,115200 console=${console} ip=192.168.0.10::192.168.0.1:255.255.255.0:pi:eth0:none cryptdevice=/dev/mmcblk0p3:root root=/dev/mapper/root rw rootwait loglevel=5')
The /etc/mkinitcpio.conf is (non-commented lines only):
$this->bbcode_second_pass_code('', 'MODULES="dm_crypt dm_mod ext4"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block keyboard netconf dropbear encryptssh filesystems fsck"')
The error is the following (note that the left margin of the screen is not readable):
$this->bbcode_second_pass_code('', '...
...0.000000] arm_arch_timer: WARNING: Please fix your firmware
...0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ2, assuming level
[This message is repeated 7 times for IRQ1 and IRQ2 with the time index increasing, otherwise nothing changed]
...0.145404] dmi: Firmware registration failed.
...0.772865] kvm [1]: Invalid trigger for IRQ4, assuming level low
...1.712142] cacheinfo: Unable to detect cache hierarchy for CPU0
...1.789492] dmi-sysfs: dmi entry is absent.
...1.923932] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not fount, using dummy regulator
...1.924363] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not fount, using dummy regulator
...unning early hook [udev]
...ting version 232
...unning hook [udev]
...riggering uevents...
...unning hook [netconf]
...nfig: eth0: SIOCGIFINDEX: No such device
...nfig: no devices to configure
...onfig: eth0: /
...onfig: eth0: gw: dns0: dns1:
...unning hook [dropbear]
...ting dropbear
...] Jan 01 00:00:01 Running in background
...unning hook [encryptssh]
[Followed by the LUKS password prompt to which I cannot respond since I have no input devices]')
The device does never appear on the LAN (which is perhaps not surprising as it failed to configure eth0). What I do not understand is, why or how to solve it.
What did not work is:$this->bbcode_list('1')
Also note that without disk encryption, the system (with even the same kernel and initrd) starts quite normally; the network is configured properly and the system cones online under the specified IP with the network device being named eth0.
I gather that this is not a problem of missing modules but rather either one of the hooks being in the wrong order or one of the network device (eth0) not being named correctly.
The IRQ[124] firmware warnings are somewhat odd, but, I assume, unrelated to this network issue.
Any help is appreciated...