martinayotte

The timer issue is present since the A64 SoC introduction, it is a silicon bug ! If you look at first post of this thread, I've faced it the first time 2 years ago in Feb 2017, so at that time, it was 4.10.y at that time ... If people still facing the issue, even after few workarounds, maybe those don't cover all test cases ...

BTW, some other fixes related to that in Mainline 5.0.y : CONFIG_SUN50I_A64_UNSTABLE_TIMER

I cannot explain why it is not working ...

Oh ! The CONFIG_FSL_ERRATUM_A008585 is present ... Then, I don't know ... For me, I've never faced the issue again since when that config has been added more than 2 years ago ...

I'm not fluent with HDMI since all my boards are headless, but I think you are wrongly use "video-mode". In the bootargs definition, it should be something like "disp.screen0_output_mode=1920x1080p60" .

Ah ! It is a PenDrive, not a eMMC ! (I've missed that in your previous post) But what "blkid" is reporting ?

Yes, the menu need to be fixed to say "(4.x -5.x)" instead of "(4.x)", because 5.0.y came only a week ago ... Not with Armbian build scripts ... For those "sdio/brcm" missing, my bad , I had some "un-committed" patches sitting on my desktop for about a week, not they are committed : https://github.com/armbian/build/commit/56c71fc2ba95b5feee0a6b8951b90aaee953a64c So, please, do another new build and report back ...

That is the reason for the boot loop ! Boot from SDCard, check the eMMC UUID with "blkid", mount the eMMC to /mnt, edit /mnt/boot/armbianEnv.txt and make sure the line with "rootdev=UUID=" has the good UUID, then check /mnt/etc/fstab to be sure the same good UUID is also there. Then, "umount /mnt", and do halt. Eject the SDCard and recycle the power ...

In this case, maybe it is better to purchase a new board like OPi+2E ...

Can you do a "grep ERRATUM /boot/config*" ?

Which kernel/image are you running ? Did you built it yourself ? With Armbian DEV branch with 5.0.y kernel, you should clearly see the following : [ 4.213027] mmc1: new high speed SDIO card at address 0001 [ 7.960498] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9 [ 8.088730] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 10.181048] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9 [ 7.960498] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9 [ 10.181048] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9 [ 10.472854] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84

I would rather install only the 32bits libraries needed as I explain above, leaving the rest of the OS to 64bits...

Without the full log, it difficult to see what is happening between these two lines ... Change /boot/armbianEnv.txt to have "verbosity=7" and "console=serial" and grab the log from a USB-TTL Serial dongle.

For networking, did you try it having the following in /etc/network/interface : allow-hotplug eth0 iface eth0 inet dhcp For USB, I've already asked you yesterday to provide output of "lsusb" ...

Then, no choice ... Use the above method as a workaround ...