[Sluggish/delayed mouse tracking w/USB mouse]

I am using a system I built from the trunk of Armbian for the pine64so.

 

After booting up the mouse does not do "smooth mouse tracking". The movement of the mouse lags behind where it should be and has to "catch up" which takes several seconds.

I consider it unusable doing this.

 

This is Version "20.04.1 LTS (Focal Fossa)"

Armbian 20.08.0-trunk Focal

5.7.17-sunxi64 #trunk

Mon Aug 24 03:00:31 PDT 2020 aarch64

 

[Ethernet not working on SOPINE module]

I think it has something to do with the embedded switch and a timing problem. The boards boot fine in the baseboard, bit don't get DHCP service in the clusterboard.

When you use a microSD with a modified device tree, it works on both, but apt update; apt upgrade can overwrite the device tree and on the next boot, no network.

If I were good with sed I could probably engineer an automatic fix to run aftewr upgrade that would decompile, patch and recompile the device tree.

[Ethernet not working on SOPINE module]

On 3/18/2019 at 4:47 AM, BryanS said:

 

That does seem to be the case. Hopefully this will change in the future - I really want to use this thing as a hardware docker-like device. If there's any information I can provide, please let me know.

I think the clusterboard is a great product. The only problem I have with it is this network issue and once solved, this will be a very easy integration.

Now that I have a provisionally working software load for the modules, it boots reliably and the modules are very responsive.

 

What I wish we had for now, is a script we can run after doing update and upgrade that will reinstall the device tree patch reboot rebooting.

If we had that, we could upgrade with an expectation that the system would come up after reboot.

[Ethernet not working on SOPINE module]

I was wondering if the Armbian distribution had a fix for this yet.  I downloaded the current sources and built

Armbian_20.08.0-trunk_Pine64so_buster_current_5.4.51.img

It does boot nicely in the baseboard but it does not appear to have any fix for the clustereboard networking problem.

 

I am able to use the 

Armbian_5.41_Pine64so_Ubuntu_xenial_next_4.14.20.img.xz

that I downloaded off the forum. It does have the fix, but if

I do the "apt update; apt upgrade" to bring in updates, I lose

the fix and the next boot fails to operate in the clusterboard.

 

Here is my Pine64 archive for community use.

see http://cloud.goodall.com/Pine64

 

The image I am using that has the fix (but cannot be updated) is

http://cloud.goodall.com/Pine64/ClusterBoard/Armbian_5.41_Pine64so_Ubuntu_xenial_next_4.14.20.img.xz

 

I will post updates in my archive as I have them so they will be available for use.

 

 

[Ethernet not working on SOPINE module]

I am finding it disappointing that after spending real money for the cluster, there is little or none

clear and straightforward information about reaching a botton line with this hardware. I have downloaded 

what appears to be good images and burned them to microSD and placed the module in the clusterboard

and powered it up. After waiting some minutes, there is no evidence at the router that any DHCP addresses

were allocated. I guess I assumed that there was a blessed configuration for us to start from and that each

of us wouldn't have to have a nearly base-metal experience just getting a basic linux running and an ssh

session up. I don't know whether to pack this kit back up and send it back or what.