You are not logged in.
Pages: 1
[deleted]
Last edited by girlbythesea (2023-01-28 01:34:37)
Offline
Downgrading to 5.2.0-2 fixed it for me.
Offline
Rebuild against currently installed kernel and try again.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
virtualbox-host-modules-arch-5.2.0-3 in [community] is a rebuild against 4.13.12 kernel, which is still in [testing]. Therefore my guess is that virtualbox maintainer prematurely pushed the rebuilt modules to stable repo, or something else is going on..
I suppose you should open a bug, although this should get fixed by itself once linux-4.13.12-1 hits [core]. Before that happens you could downgrade to virtualbox-host-modules-arch-5.2.0-2 or use dkms.
Rebuild against currently installed kernel and try again.
This is not about virtualbox-host-dkms, although switching to dkms modules should work around the issue as well.
EDIT: This should be fixed now with virtualbox-*-modules-arch-5.2.0-4
Last edited by ooo (2017-11-09 16:58:48)
Offline
Pages: 1