You are not logged in.

#1 2017-11-09 09:02:27

girlbythesea
Member
Registered: 2016-12-19
Posts: 9

[deleted]

[deleted]

Last edited by girlbythesea (2023-01-28 01:34:37)

Offline

#2 2017-11-09 09:17:20

dunek
Member
Registered: 2010-05-15
Posts: 23

Re: [deleted]

Downgrading to 5.2.0-2 fixed it for me.

Offline

#3 2017-11-09 09:50:41

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,597
Website

Re: [deleted]

Rebuild against currently installed kernel and try again.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#4 2017-11-09 12:39:11

ooo
Member
Registered: 2013-04-10
Posts: 1,638

Re: [deleted]

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.

graysky wrote:

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

Board footer

Powered by FluxBB