0jay

Armbian-config has a transfer to eMMC tool Sent from my iPhone using Tapatalk

Actually anyway of disabling HDMI, preferably persistent There are some methods online but the ones I’ve found are oriented to Raspberry Pis and nothing has any effect on my Renegade board

Hey, I’ve read you can save 40Ma, can anyone tell me what is the best way of disabling HDMI? TIA

Hey, I've had issues using Wireguard in Armbian. I worked out a method to install but on reinstalls this method has run into problems. I've since developed a new method but am getting a strange error as below. Can anyone interpret this and tell me if it's likely to be problematic and if so is there a way forward? I've searched the Wireguard repository and there doesn't seem to be an arch specific buildset. TIA The /var/lib/dkms/wireguard/1.0.20210219/6.1.11-rockchip64/aarch64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped.

In case anyone has a similar problem, the plugin depends on the wireguard meta package and on a 6.x kernel and headers (at least the >5.5 kernels I tried were unstable except the 6.1.11). So unfreeze in armbian-config and select the 6.1.11 kernel, apt install linux-headers-edge-rockchip64 to install the headers then manually install the wireguard meta package then OMV from there. Thanks for your time Igor.

Thank you. I think I’ve worked it out – the wireguard meta package is required as well as headers (neither of which are part of a cli install). I’ve got the plugin installed and working just dealing with some weird issues with kernel packages failing to install. I’m guessing it’s to do with the edge kernel so will try updating from a clean install after an unfreeze and see what happens. Thanks for your time. Sent from my iPhone using Tapatalk

Thanks Igor. Is this the same as nightly builds? Sent from my iPhone using Tapatalk

Thanks Igor!

Hi, trying to nut out the problem of being unable to restart after installation of the OMV Wireguard plugin. I have removed the wireguard-tools package and installed the 4 rockchip64 edge 6.1.11 packages. It took me a while to realise that armbian-config was not installing the headers when selected but wondering if there's a necessary order for installation ie linux-source-6.1.11-edge-rockchip64 first maybe? Sorry I realise how tedious it is supporting folks who are feeling around in the dark but I've wasted so many hours starting from scratch I either have to give up or ask for a tip. TIA

Ok, thanks again for your input. I’ll follow up in the OMV forums.

Ahh ok, so would you think it might help for me to uninstall those Armbian packages before attempting an install of the plugin? I guess it might be best to leave it until there’s an Armbian kernel update but I’m a bit of a dog with a bone when there’s a puzzle to solve

Thanks Igor, I've posted up a question in the OMV forum. I just thought it was likely to do with the older kernel but I guess given it's breaking the 6.1.11 kernel too it might be a bit more complicated. Armbian runs so much better than the Libre builds btw, thanks for your work.

Is nobody else having this problem?

I’m assuming this is to do with the kernel but otherwise have no idea. I’ve had no problems with this Wireguard plugin on a 32bit Libre Bullseye install on a Renegade but was unable to get 64bit Bullseye to accept login creds so opted for Armbian. Now unable to use the plugin at all. Anyone have any ideas? I’ve tried the 6.1.11 edge kernel but Wireguard broke this too. Not sure what else to try. Attempted to get Libre kernels to load without success - way above my skillset for now. TIA