Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel.

[Cy Schubert]

In message <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5
FMckEUy

see subject

Try rebuilding and reinstalling virtualbox-ose-kmod.

[Taavi]

Hi

Not really wanting to do that. Using pkg binary system for purpose

That would lead to question why binary package driver crashes kernel?

regards,
Taavi
​
Sent with ProtonMail Secure Email.
​

-------- Original Message --------

Post by Cy Schubert
In message <1JOKDx2CeRUWS-ZzfU-7hCpDv4Yb0eMqlfrGzV-DnL89_Qg9MMxTZqdZJNu5
FMckEUy

see subject

Try rebuilding and reinstalling virtualbox-ose-kmod.
Cheers,
The need of the many outweighs the greed of the few.

[Kevin Oberman]

Post by Taavi
Hi
Not really wanting to do that. Using pkg binary system for purpose
That would lead to question why binary package driver crashes kernel?
regards,
Taavi

This is a real problem with kmod packages. If hte kernel is modified in any
way, modules must be re-built. It may take a while for the package to get
re-built for a given change as the port has not been modified. The
recommended method is to put port modules into /etc/src.conf PORTS_MODULES
list so that kernel rebuild will always rebuild the modules, but that only
works if the kernel IS built from sources and re-installed. It will be a
bigger issue when more people start doing binary updates to the kernel.more
routinely.