PigLover

Kind a like this: https://github.com/armbian/build/pull/4611 Guess I was a bit slow to the punch - but at least somebody else was on top of it!

If somebody is willing to a) test this scenario and b) then provide a PR that enables the requested module across all configs, then yes, we could ship it by default. Now that the crazyness of the last few weeks have settled down I can finally pay attention to this again. Is there any chance you could point me to an example of a good/successful PR to enable a feature that I could use to model against? Would rather get it right the first time rather than wasting time doing it wrong, responding to PR comments, doing it again, rinse, repeat...

Thank you. I built it last evening. It appears stable, iscsid now starts (fixed the key symptom) and does allow Longhorn to work. I also included the Ceph kernel modules due to future testing plans. I'd like to run with it for a few days to see if there are any problems and, barring any problems, will submit the PR in a week or so.

Is there any chance we could get kernel support for open-iscsi built into this kernel (I believe this requires module iscsi_tcp)? I'm doing some Kubernetes testing and this is required for Longhorn. I know I could build my own kernel and probably will if this is a request that will take a long time. But I believe this will be a common use case for this board and it would be nice to have it in the base kernels. Thanks!

On the above - forgot to mention - the dtb file that needs to be edited is "sun50i-a64-sopine-baseboard.dtb"

This appears to be the same issue that was fixed for the Legacy kernel, but not carried forward. Two fixed are possible - add a "tx-delay" in the DTB or a fix some constants in the Realtek driver. I've confirmed that the DTB fix corrects the issue. Add allwinner,tx-delay-ps = <500>; to the ethernet device and it works. Continues to work when soPine is plugged into the baseboard instead of the clusterboard. Detail on the more complex fix here: https://patchwork.ozlabs.org/patch/873752/ ethernet@1c30000 { compatible = "allwinner,sun50i-a64-emac"; syscon = <0x2d>; reg = <0x1c30000 0x10000>; interrupts = <0x0 0x52 0x4>; interrupt-names = "macirq"; resets = <0x2 0xd>; reset-names = "stmmaceth"; clocks = <0x2 0x24>; clock-names = "stmmaceth"; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <0x2e>; phy-mode = "rgmii"; phy-handle = <0x2f>; phy-supply = <0x30>; phandle = <0x6f>; allwinner,tx-delay-ps = <500>; mdio { compatible = "snps,dwmac-mdio"; #address-cells = <0x1>; #size-cells = <0x0>; phandle = <0x70>; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x1>; phandle = <0x2f>; }; }; };

This restriction does make it difficult to create a dialog about issues. I have comments I'd like to reply regarding the SoPine Clusterboard network issue reported recently but replies are blocked. Starting a new topic for every reply doesn't seem very productive. I understand the spam issue - but treating the disease by shooting the patient seems a bit extreme.