Thank you! (as always) a thorough report which makes it better for the future!
According to a quick search the (early stage) Fast Interrupt (FIQ) warnings can be ignored.
I see urandom running out of entropy all the time while the kernel still runs in the initramfs. And because it occurs during this stage installing haveged does not help…
Can not reproduce this @mrmarkuz does systemctl status systemd-tmpfiles-setup.service give any clue’s?
With both images the kdump.sercice fails for different reasons. On NS x86_64 the service is disabed by default. I’m considering to even mask ( systemctl mask kdump ) the service on armhfp. tagging this as Bug (thanks)
Here is a qcow image for qemu emulation/virtualization of armhfp on x86_64 with a large address space lpae kernel included.
On Fedora 28 (can not get it to work on Centos) it is possible to emulate armhfp. On my hardware it’s dead slow (boot takes about 70 sec…) but is seems to work.
sudo dnf install qemu-system-arm virt-install libvirt libvirt-python libguestfs-tools
(above is deducted from bash_history ; not sure if I installed more in the past )
Download the image and unpack it on a convenient place xz -vdk -T 0 Centos-Qemu-lpae-armhfp.qcow2.xz
Extract the kernel from the image: virt-builder --get-kernel Centos-Qemu-lpae-armhfp.qcow2
^] > leave the console of the VM (=“CNTRL + ]”, like telnet… )
virsh destroy centos7_armhfp > stop the VM virsh edit centos7_armhfp > edit libvirt configuration of VM virsh start centos7_armhfp > start the VM virsh console centos7_armhfp > get a console for the started VM virsh undefine centos7_armhfp > delete/remove the VM
Your post post was actually one of the references for the implementation we are testing now.
In the arch linux philosophy we made it simpler… AFAIK zram is multi threading in modern kernels and you do not need to dispatch it over the (cpu)cores…?..
Yes, I have read about that, yet I prefer to dispatch it over cpu cores because I can’t tell whether zram on my kernel is coded for multi-thread or not, safety first.
For the wiki, a page called ‘Nethserver on Raspberry PI’ would be a nice thing to have. Very few people know about ‘ARM’ or other tech details, al they need to know how a $30 computer can run Nethserver
I like to do an other proposal:
Start writing first chapter, getting started, of the documentation on github.
The simple fact there is an outdated “How to install Nethserver 7 on a RaspberryPI2/3” wiki page a kind of proves wiki’s don’t work … Oke biased, I think wiki’s don’t work (and this is a mild description of my opinion…)
Most of all i’d like to prevent keeping several different information sources up to date.
also see and comment on : ARM development: next steps : “Documentation”
Wiki is simple, people with a low level of knowledge could start to write, others could correct the bad syntax…write the documentation on readthedoc, it is like coding, I think it is not so easy, and you must follow good practices.