Jump to content

Recommended Posts

Posted

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

Posted

Did you check with OMV people to understand what this plugin does? Or perhaps try to see if there is something in the system or omv logs when you do that. That might help us to understand what is going on.

Posted

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.

Posted
51 minutes ago, 0jay said:

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.


Purely blind speculation. The problem could be as we are providing Wireguard module and tools by default, while OMV could be trying to install dkms package which re-compiles it on demand ... 

Posted

The problem could be as we are providing Wireguard module and tools by default


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
Posted
3 minutes ago, 0jay said:

Ahh ok, so would you think it might help for me to uninstall those Armbian packages before attempting an install of the plugin?


Well, this should be determined by someone that is closer to OMV. More looks like a bug in their modules as they should cover such case / circumstances.

Posted
this should be determined by someone that is closer to OMV. More looks like a bug in their modules as they should cover such case / circumstances.

Ok, thanks again for your input.

I’ll follow up in the OMV forums.
  • Solution
Posted

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.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines