In Fedora 37 I have installed dkms for virtualbox but now wifi has stopped working

[computersavvy (Jeff V)]

I use virtualbox but I installed it as rpm from the rpmfusion repo. It does not require dkms and I have had no unexpected problems with running it.

Note that you seem to still be using F37 which is EOL in just a couple more weeks so there will be no further upgrades or bug fixes to any of the software you have. Solving the problem that seems to require you to remain on a 6.4 kernel would be the best suggestion I can make.

There are 2 ways to make a specific kernel default.
This thread provides one way and the most commonly used. Note that setting a kernel as default by using the index number only keeps that kernel active until the next kernel update is installed and a new kernel becomes index 0. A newly installed kernel becomes index 0 and older kernels are pushed down the list.

Changing the ID to boot from an older Kernel by default | grubby

I would like to know how dnf treats the default Index when I do the following changes. Will the older default kernel still be available after an update or do I have two newer kernels? I do use installonly_limit=2 in my /etc/dnf/dnf.conf. Before I test it on my selves I try to find out if somebody already made experience with it. grubby List all installed kernels To get the index number of all the installed kernels: sudo grubby --info=ALL | grep -E "^kernel|^index" The output should be som…

The second way is to edit /etc/default/grub and add an option in there.
Adding a line that reads GRUB_SAVEDEFAULT=true at the end of that file then running the command sudo grub2-mkconfig -o /boot/grub2/grub.cfg before rebooting will allow you to select any installed kernel and that kernel will then become the default until you select a different kernel to boot.