(03-17-2019, 08:48 AM)BryanS Wrote: There appears to be a thread about this issue in the Armbian forums. It talks about some changes that weren't carried through to the newest kernel, that of timing issues with the Realtek devices. I assume that's the same whispers I saw regarding timing elsewhere.
https://forum.armbian.com/topic/9402-eth...ne-module/
I'm out of my league at the moment doing kernel recompiles, but I'll try and provide any information that is needed to get this resolved.
(edit: I tried to post my findings in the Armbian forum, but I've forgotten my password and the email reset appears to be broken...)
That is the exact issue you are fighting against. You can fix it on the newer kernels - one module at a time - by modifying one of the boot files as described in that other thread. But it requires a serial console and is a PITA.
I appreciate all the work that Armbian does, but there really is no excuse for this issue remaining open and untouched by them for this long.
Once you get past that one the next hurdle to get over is the "won't reboot without power cycle, which required power cycling the whole cluster" issue. This one really needs to get fixed if the Clusterboard is ever going to be really useful. At is is mine is back on a storage shelf because its just not worth fighting it.
In fact, if anyone wants a Clusterboard and 8 so-pines at a good discount you could PM me...
