On Sun, 28 Nov 2021 00:11:57 +, Wols Lists wrote:
> > Strange. try: emerge virtualbox-modules
> >
> > That should be rebuild after everuy kernel upgrade and that happens
> > normally with emerge @module-rebuild
> >
> "nothing to rebuild"
emerge pkg should always emerge it, whether it is
On Tue, 2021-11-23 at 20:43 +0100, Branko Grubić wrote:
> Hi,
>
> I have few applications which use webkit-gtk and gnutls behind as far
> ...
Filed a bug report[1]
[1] https://bugs.gentoo.org/827718
quickpg the existing modules then try the remove/reinstall fix. You can
then use "emerge -K =package" or even a manually reinstall (by coping
them over the newer ones) to replace the modules if things don't work out.
I would think in your case needing to keep kernel specific modules
around th
On 27/11/2021 22:15, Kees wrote:
>The docu says "emerge @module-rebuild".
>Both of these terminate with "nothing to rebuild".
Strange. try: emerge virtualbox-modules
That should be rebuild after everuy kernel upgrade and that happens
normally with emerge @module-rebuild
"nothing to reb
>The docu says "emerge @module-rebuild".
>Both of these terminate with "nothing to rebuild".
Strange. try: emerge virtualbox-modules
That should be rebuild after everuy kernel upgrade and that happens normally
with emerge @module-rebuild
On Sat, Nov 27, 2021 at 7:29 AM Wols Lists wrote:
>
> Simple problem, after a kernel upgrade, virtualbox no longer works. This
> is to be expected, of course, BUT ...
>
I can't offer any VirtualBox-specific solutions but I would try
reinstalling it as others have suggested (emerge -1
virtualbox-m
On Tue, 2021-11-23 at 18:14 -0500, Jack wrote:
> OK, here's something.
>
> I changed my stable version of ca-certificates from -cacert to
> cacert,
> and now I get the same failure you do. So - it's due to either
> something in nss-cacert-class1-class3-r2.patch which only gets
> applied
> i
I mean that as: just reinstall Virtualbox as a first troubleshooting step.
If that works, great. If it doesn’t, then that can be marked off the list
as something that was tried.
On Sat, Nov 27, 2021 at 8:21 AM Wols Lists wrote:
> On 27/11/2021 13:03, Jeremy Hendricks wrote:
> > I’d recommend eme
On 27/11/2021 13:03, Jeremy Hendricks wrote:
I’d recommend emerging Virtualbox again. It should just work with emerge
@module-rebuild unless Virtualbox isn’t compatible with the newer
version of kernel.
HOW !?!?
The problem is that they are already installed, so any attempt to emerge
them fa
On Saturday, 27 November 2021 12:59:49 GMT Wols Lists wrote:
> On 27/11/2021 12:41, Peter Humphrey wrote:
> > On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:
> >> Simple problem, after a kernel upgrade, virtualbox no longer works. This
> >> is to be expected, of course, BUT ...
> >>
>
I’d recommend emerging Virtualbox again. It should just work with emerge
@module-rebuild unless Virtualbox isn’t compatible with the newer version
of kernel.
On Sat, Nov 27, 2021 at 8:00 AM Wols Lists wrote:
> On 27/11/2021 12:41, Peter Humphrey wrote:
> > On Saturday, 27 November 2021 12:29:10
On 27/11/2021 12:41, Peter Humphrey wrote:
On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:
Simple problem, after a kernel upgrade, virtualbox no longer works. This
is to be expected, of course, BUT ...
How do I fix it !!!
What I always did on my old system was to re-emerge the mod
On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote:
> Simple problem, after a kernel upgrade, virtualbox no longer works. This
> is to be expected, of course, BUT ...
>
> How do I fix it !!!
>
> What I always did on my old system was to re-emerge the modules.
>
> The docu says "emerge @
Simple problem, after a kernel upgrade, virtualbox no longer works. This
is to be expected, of course, BUT ...
How do I fix it !!!
What I always did on my old system was to re-emerge the modules.
The docu says "emerge @module-rebuild".
Both of these terminate with "nothing to rebuild".
What
14 matches
Mail list logo
