0jay

the tools package is part of a default install, there's no need to install it manually

I did try this Werner, it still installed a vanilla debian kernel Tools is installed by default, it's the meta package that's the problem and the OMV plugin requires the meta package

I intend getting to this in time (also with OpenWRT) but for the moment I'm not in a position to do it. If there's an image that'll boot on a renegade board then at least I can explore

I think I know how to do it. Install wireguard, then goto arbian-config and install the kernel and headers, that way you overwrite the kernel from the wireguard installation.

Thanks SteeMan, wireguard-tools show as installed, I think the metapackage needs installation (which I'd guess is why I can actually install the package without getting a message it's already present). My issue is that the OMV plugin installation results in the same unbootable state. I'm trying to save myself the time of reinstalling OMV every time and work out why a wireguard install renders Armbian unbootable. Igor (and Werner) have observed it probably has to do with dkms packages which I suppose is why wireguard installation defaults to installing a linux package which I guess installs an incompatible kernel. I'd been hoping that the pre-rolled Arbian/OMV images might solve this problem but it's looking unlikely unless the OMV-Extras team can suggest a solution.

Unfortunately apt install --no-install-recommends wireguard doesn't help. I started by installing headers first which seemed to skip a kernel install (at least I got a – autoinstall for kernel 6.1.0-23-rt-arm64 was skipped since the kernel headers for this kernel do not seem to be installed – message) but still no boot on restart. I even tried installing edge kernel and headers which worked for me last time but as soon as Wireguard's installed it refuses to boot.

Would any of these OMV images run on a 3328 Renegade? I can run the Libre portability script so figure I just need it to boot

I'll hook into this in the next few days, thanks for your time nutting it out it'll be great to finally have it sorted Best regards, Oscar

Thank you! Can I just apt uninstall those packages? Are there only the two that can cause this issue that I need to remove?

Hi Werner, thanks for your reply. I tried again several times today, including with the latest server image and am still unable to boot following installation (though no errors are reported). It occurred to me I should've tried installing headers first but I've spent another day trying to nut it out so I'll have to leave it for another day. Really frustrating not knowing what I'm doing wrong. I'll give this a try next time, thanks.

This is great, thanks for this it's exactly what I wanted! Will this play nice with armbian-config eMMC install? I once tried after installing OMV on an sd card and the emmc transfer wouldn't boot (armbian-config's the only tool I've found to do an emmc install)

Hi, just to be clear I've zero doubt the problem is me but this is a recurring issue and I've been unable to nut it out on my own. I've found (both with bullseye and bookworm) that installing Wireguard borks my system - ie I am unable to boot after install. I'm running headless and therefore am limited diagnostically (I can't say what errors are occurring when attempting to reboot) I realise this'll make my problem frustrating for a lot of folks to engage with but any ideas at all'd be helpful. When first using Armbian a few years back it seemed as though the issue was that the LTS kernel did not include wireguard support and I discovered installing an edge kernel allowed me to install and use Wireguard successfully. I'm now getting the issue with Bookworm though so clearly my problem was not the kernel and whatever allowed me to install Wireguard was just incidentally triggered by the process I followed to install the edge kernel. I've done seven fresh installs in the last few days just to get my system bedded down and am a bit nervous about experimenting too much given cellular internet with limited data allowance. I'm hoping to swing into this with at least some idea about what the problem might be and how I might resolve it so I can minimise danger of another time consuming reinstallation. System is a Libre Renegade board (Rockchip 64) Thanks in advance for any ideas. Oscar

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.