On 26 Dec 2022 at 8:37, John Mellor wrote:
From: John Mellor
Date sent: Mon, 26 Dec 2022 08:37:42 -0500
Subject:Re: Upgraded from 35 to 36, and noticed that VirtualBox wasn't
working with 6.0.15, but would with 6.0.14?
To: users@lists.fedoraproject.org
Send reply to:
On 11/3/22 3:51 PM, home user wrote:
This problem was solved by the "dnf upgrade" that I did on Dec. 14.
Details can be viewed in the follow-up thread "need perm. fix for
monitor/display problem.", launched on Dec. 14.
My thanks to everyone who tried to help.
(f36)
Good afternoon,
A
On 12/17/22 9:46 AM, home user wrote:
On 12/17/22 12:54 AM, Samuel Sieb wrote:
On 12/16/22 10:33, home user wrote:
I shut down nightly. So I do notice the long time. I hear at least
3 long surges of the cooling fans during shutdown. But I don't know
of a way of knowing what's really going
On Sun, 25 Dec 2022 08:04:22 +0100
lejeczek via users wrote:
> Specs, rfcs & howtos are what we all can sroogle relatively
> easily - as I had - still, thank you.
> What I was hoping was for someone who had more of hands-on
> experience(with the hardware) - if I was not clear
> absolutely
On Mon, Dec 26, 2022 at 7:30 AM Michael D. Setzer II via users
wrote:
>
> Appears there is kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64
> but not a version for 6.0.15 yet?
> Gave message the vboxdrv wasn't loaded, but ran the commands it said, but
> guess without the package, it
On 2022-12-26 07:29, Michael D. Setzer II via users wrote:
Appears there is
kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64
but not a version for 6.0.15 yet?
Gave message the vboxdrv wasn't loaded, but ran the commands it said,
but guess without the package, it couldn't build the
Appears there is
kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64
but not a version for 6.0.15 yet?
Gave message the vboxdrv wasn't loaded, but ran the
commands it said, but guess without the package, it
couldn't build the module.
But was able to boot with 6.0.14, and do the testing
