On 2 Sep 2023 at 16:05, Francis.Montagnac@xxxxxxxx wrote: From: Francis.Montagnac@xxxxxxxx To: mikes@xxxxxxxx, Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: Virtual Box not working after upgrade to Fedora 38 Date sent: Sat, 02 Sep 2023 16:05:21 +0200 > Hi. > > On Sat, 02 Sep 2023 22:53:59 +1000 "Michael D. Setzer II via users" wrote: > > >> Did the install and created the new driver as it says, and it seems > >> to have the vboxdrv in the same relative place as it did with fc37, > >> but gives message that not found, but file is there?? > > >> modprobe vboxdrv > >> modprobe: FATAL: Module vboxdrv not found in directory > >> /lib/modules/6.4.12-200.fc38.x86_64 > > >> # find . | grep vboxdrv > >> ./6.4.11-100.fc37.x86_64/extra/VirtualBox/vboxdrv.ko.xz > >> ./6.4.12-100.fc37.x86_64/extra/VirtualBox/vboxdrv.ko.xz > >> ./6.4.12-200.fc38.x86_64/extra/VirtualBox/vboxdrv.ko.xz > > >> Any ideals why modprobe isn't seeing the driver that does exist?? > > The depmod done by the kmod-VirtualBox-KERNELVER RPM may have been interrupted > during its installation. This ia a know problem. > > What is the release of it ? > Finally got it working again, but took a new kernel release to totally fix it. First attempt was to remove all VirtualBox packages and then reinstall them. That got most things working, but attempted to use bridged nick or anything but the NAT option would cause failure. NAT option would work, but getting a 10.0.2.x IP. rather than a 192.168.16.x which was with the bridge adapter. Didn't matter if use ethernernet or wifi device only NAT would boot image. Think if may have been because it was using the exact same kernel as had been used with the Fedora 37. Only different was FC37 had -100, while the FC38 had -200?? dnf update just had the kernel so now have. 14377960 Aug 23 10:00 /boot/vmlinuz-6.4.12-200.fc38.x86_64 14384360 Aug 24 04:07 /boot/vmlinuz-6.4.12-100.fc37.x86_64 14401832 Aug 30 10:00 /boot/vmlinuz-6.4.13-200.fc38.x86_64 Interesting that the fc37 kernel has a newer date than the fc38 for 6.4.12?? But after the 6.4.13 kernel installed and system reboot, was able to put it back to bridged option and it boots fine. Interesting glitch.. But now working like expected. Thank. > For example with: > > dnf list installed kmod-VirtualBox-$(uname -r) > > or: > > rpm -qf /lib/modules/6.4.12-200.fc38.x86_64/extra/VirtualBox/vboxdrv.ko.xz > > > Latest atempt shows failure in build process? > > > The installation of packages shows already installed. > > > dnf install akmod-VirtualBox kernel-devel-6.4.12-200.fc38.x86_64 > > Last metadata expiration check: 1:51:24 ago on Sat 02 Sep 2023 08:49:43 PM ChST. > > Package akmod-VirtualBox-7.0.6-1.fc38.x86_64 is already installed. > > Package kernel-devel-6.4.12-200.fc38.x86_64 is already installed. > > I am using the same kernel but a slightly newer version of akmod-VirtualBox > from rpmfusion that works: > > rpm -q akmod-VirtualBox; rpm -q --changelog akmod-VirtualBox | head > akmod-VirtualBox-7.0.10-2.fc38.x86_64 > * Sat Aug 12 2023 Sérgio Basto <sergio@xxxxxxxxxx> - 7.0.10-2 > - Add fix for kernel-6.4.10 > > * Wed Jul 19 2023 Sérgio Basto <sergio@xxxxxxxxxx> - 7.0.10-1 > - Update to 7.0.10 > > -- > francis +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@xxxxxxxx mailto:msetzerii@xxxxxxxxx Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+ _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
