Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: After nvidia blob update, vboxdrv not found error

  1. #1
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,240

    Default After nvidia blob update, vboxdrv not found error

    openSUSE 13.2 KDE4, VBox 5.1.6 from (now defunct) http://download.opensuse.org/reposit...openSUSE_13.2/ repo.
    Nvidia blob updated from G03 to G04, see https://forums.opensuse.org/showthre...17#post2835617

    As part of the G04 "solution" I deleted all intermediary module folders, keeping only the first and last:

    Code:
    /lib/modules # ls
    3.16.6-2-desktop
    3.16.7-53-desktop
    Now when starting a VM I get the error dialog:

    Kernel driver not installed (rc=-1908)

    The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

    '/sbin/vboxconfig'

    as root.

    where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
    /sbin/vboxconfig does not exist. It appear to have been substituted by /sbin/rcvboxdrv. Some googling led to messages of missing vboxdrv module:

    Code:
    /etc/rc.d # ./vboxdrv setup
    vboxdrv.sh: Starting VirtualBox services.
    vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
    
    /etc/rc.d # ./vboxdrv force-reload
    vboxdrv.sh: Stopping VirtualBox services.
    vboxdrv.sh: Starting VirtualBox services.
    vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
    /etc/rc.d is a link to /etc/init.d. dmesg says absolutely nothing about this - maybe it's in a systemd log?

    Searching for vboxdrv results in:

    Code:
    /lib/modules/3.16.7-53-desktop/weak-updates/misc # ls -al
    total 8
    drwxr-xr-x 2 root root 4096 Dez 20  2016 .
    drwxr-xr-x 4 root root 4096 Dez 20  2016 ..
    lrwxrwxrwx 1 root root   46 Dez 20  2016 vboxdrv.ko -> /lib/modules/3.16.7-42-desktop/misc/vboxdrv.ko
    lrwxrwxrwx 1 root root   49 Dez 20  2016 vboxnetadp.ko -> /lib/modules/3.16.7-42-desktop/misc/vboxnetadp.ko
    lrwxrwxrwx 1 root root   49 Dez 20  2016 vboxnetflt.ko -> /lib/modules/3.16.7-42-desktop/misc/vboxnetflt.ko
    lrwxrwxrwx 1 root root   46 Dez 20  2016 vboxpci.ko -> /lib/modules/3.16.7-42-desktop/misc/vboxpci.ko
    The files above only appear in the weak-updates ../folder, not the ../misc folder. This only has:

    Code:
    /lib/modules/3.16.7-53-desktop/misc # ls -lsh
    total 4,1M
    1,8M -rw-r--r-- 1 root root 1,8M Dez 21  2016 vmmon.ko
    2,4M -rw-r--r-- 1 root root 2,4M Dez 21  2016 vmnet.ko
    /lib/modules/3.16.7.42-desktop was one of the deleted intermediary folders, so all *.ko links where orphaned (0 size). Restoring it from root's trash gives:

    Code:
    /lib/modules # ls
    3.16.6-2-desktop
    3.16.7-42-desktop
    3.16.7-53-desktop
    and

    Code:
    /lib/modules/3.16.7-42-desktop/misc # ls -lsh
    total 4,8M
    608K -rw-r--r-- 1 root root 608K Set 16  2016 vboxdrv.ko
     20K -rw-r--r-- 1 root root  18K Set 16  2016 vboxnetadp.ko
     48K -rw-r--r-- 1 root root  45K Set 16  2016 vboxnetflt.ko
     44K -rw-r--r-- 1 root root  41K Set 16  2016 vboxpci.ko
    1,8M -rw-r--r-- 1 root root 1,8M Ago 30  2016 vmmon.ko
    2,4M -rw-r--r-- 1 root root 2,4M Ago 30  2016 vmnet.ko
    Note that the restored intermediary folder also has older (but exactly the same byte size) vmmon.ko and vmnet.ko not linked in ../3.16.7-53-desktop/weak-updates/misc.

    However, after restoring /lib/modules/3.16.7-42-desktop and rebooting, the same error occurs, be it at VM start or running vboxdrv setup or vboxdrv force-reload.

    Lastly:

    Code:
    /etc/rc.d # modprobe -a vboxdrv.ko
    modprobe: WARNING: Module vboxdrv.ko not found.
    Perhaps because the modules should be somewhere else besides the ../weak-updates directory, like ../3.16.7-53-desktop/misc?

    Any ideas?

    Thanks,

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: After nvidia blob update, vboxdrv not found error

    And the devel files for the running kernel ??
    Code:
    rpm -qa | grep kernel | grep devel
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,240

    Default Re: After nvidia blob update, vboxdrv not found error

    I think that's OK. They were necessary to compile a bunch of other stuff the last couple of years.
    Code:
    ~> rpm -qa | grep kernel | grep devel
    kernel-devel-3.16.7-53.1.noarch
    kernel-desktop-devel-3.16.7-53.1.x86_64
    I've seen a package for oS 13.2 in obs called modulo-virtualbox to "Create menu command for Recompile Virtualbox module to be used in case of malfunctions without having to start the terminal procedure is especially useful for those who hate to use the terminal... ;-)"

    Anyone tried it?

  4. #4
    Join Date
    May 2012
    Location
    Finland
    Posts
    2,188

    Default Re: After nvidia blob update, vboxdrv not found error

    It just so happens that I have virtualbox-5.1.6 source rpm here (essentially the same that was in the Virtualization repo) that you could rpmbuild to produce the suitable kernel modules again.

    I would do this in OBS but you can't add 13.2 repos anymore.
    .: miuku @ #opensuse @ irc.libera.chat

  5. #5
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,240

    Default Re: After nvidia blob update, vboxdrv not found error

    More info:

    Code:
     # systemctl status vboxdrv
    vboxdrv.service - LSB: VirtualBox Linux module
       Loaded: loaded (/etc/init.d/vboxdrv)
       Active: failed (Result: exit-code) since Ter 2017-08-29 13:25:33 BRT; 1h 41min ago
      Process: 1630 ExecStart=/etc/init.d/vboxdrv start (code=exited, status=1/FAILURE)
    
    Ago 29 13:25:33 bruno-03 systemd[1]: Starting LSB: VirtualBox Linux module...
    Ago 29 13:25:33 bruno-03 vboxdrv[1630]: vboxdrv.sh: Starting VirtualBox services.
    Ago 29 13:25:33 bruno-03 vboxdrv[1630]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
    Ago 29 13:25:33 bruno-03 systemd[1]: vboxdrv.service: control process exited, code=exited status=1
    Ago 29 13:25:33 bruno-03 systemd[1]: Failed to start LSB: VirtualBox Linux module.
    Ago 29 13:25:33 bruno-03 systemd[1]: Unit vboxdrv.service entered failed state.
    # systemctl start vboxdrv
    Job for vboxdrv.service failed. See "systemctl status vboxdrv.service" and "journalctl -xn" for details.
    
    # journalctl -xn
    -- Logs begin at Ter 2017-08-29 13:25:27 BRT, end at Ter 2017-08-29 15:07:21 BRT. --
    Ago 29 15:07:16 bruno-03 vboxdrv[4708]: vboxdrv.sh: Starting VirtualBox services.
    Ago 29 15:07:16 bruno-03 vboxdrv.sh[4713]: Starting VirtualBox services.
    Ago 29 15:07:16 bruno-03 vboxdrv.sh[4718]: Recompiling VirtualBox kernel module, NOT. It has been packaged..
    Ago 29 15:07:16 bruno-03 vboxdrv.sh[4719]: .
    Ago 29 15:07:16 bruno-03 vboxdrv[4708]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
    Ago 29 15:07:16 bruno-03 vboxdrv.sh[4721]: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
    Ago 29 15:07:16 bruno-03 systemd[1]: vboxdrv.service: control process exited, code=exited status=1
    Ago 29 15:07:16 bruno-03 systemd[1]: Failed to start LSB: VirtualBox Linux module.
    -- Subject: Unit vboxdrv.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo /systemd-devel                                                                                                                                            
    --                                                                                                                                                                                                                 
    -- Unit vboxdrv.service has failed. --                                                                                                                                                                                                                 
    -- The result is failed.                                                                                                                                                                              
    Ago 29 15:07:16 bruno-03 systemd[1]: Unit vboxdrv.service entered failed state.

  6. #6
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,240

    Default Re: After nvidia blob update, vboxdrv not found error

    Quote Originally Posted by Miuku View Post
    It just so happens that I have virtualbox-5.1.6 source rpm here (essentially the same that was in the Virtualization repo) that you could rpmbuild to produce the suitable kernel modules again.

    I would do this in OBS but you can't add 13.2 repos anymore.
    I've never been good at compiling more complex stuff, but I'm willing to try. Is it possible to compile just the kernel modules and drop them in the pertinent directories or would it change other installed vbox components?

    I do have a vague recollection of seeing compiler warnings about these four vbox modules in one of my failed attempts to install G04, possibly like failed to compile or such. The last, successful G04 install with Yast SM, however, did not give any error or warning messages at all, so I (naively) assumed all was well...

  7. #7
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: After nvidia blob update, vboxdrv not found error

    Quote Originally Posted by brunomcl View Post
    I think that's OK. They were necessary to compile a bunch of other stuff the last couple of years.
    Code:
    ~> rpm -qa | grep kernel | grep devel
    kernel-devel-3.16.7-53.1.noarch
    kernel-desktop-devel-3.16.7-53.1.x86_64
    I've seen a package for oS 13.2 in obs called modulo-virtualbox to "Create menu command for Recompile Virtualbox module to be used in case of malfunctions without having to start the terminal procedure is especially useful for those who hate to use the terminal... ;-)"

    Anyone tried it?
    You have tried to use modules built agains a different kernel build ( the ....42... kernel ). Since this is a 64bit system, why not use Leap?. That would at least avoid repo issues etc .
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  8. #8
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,349
    Blog Entries
    15

    Default Re: After nvidia blob update, vboxdrv not found error

    Quote Originally Posted by Miuku View Post
    It just so happens that I have virtualbox-5.1.6 source rpm here (essentially the same that was in the Virtualization repo) that you could rpmbuild to produce the suitable kernel modules again.

    I would do this in OBS but you can't add 13.2 repos anymore.
    Hi
    Under repository overview, select expert mode and start typing openSUSE, or older ones start Discontinued
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #9
    Join Date
    May 2012
    Location
    Finland
    Posts
    2,188

    Default Re: After nvidia blob update, vboxdrv not found error

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Under repository overview, select expert mode and start typing openSUSE, or older ones start Discontinued
    Actually I got around this by just editing the metadata and adding <path project="openSUSE:13.2" repository="standard"/>

    Thanks for the hint!

    Op; I'm trying to build 5.1.6 in OBS for you - it should be the "least destructive" method of fixing your system and it (should) compile straight against the last kernel update released for 13.2.
    .: miuku @ #opensuse @ irc.libera.chat

  10. #10
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    3,240

    Default Re: After nvidia blob update, vboxdrv not found error

    That would be great, Miuku. Thank you!
    (and you, Malcolm, helpful as always )

    If all else fails, my second-to-last resort could be to remove vbox with yast and go with the Oracle rpm. If it still compiles.

    @Knurpht:
    My last resort would be switching to Leap, but I'm doing this now with on W10/Leap dual-boot secondary work machine and want to avoid upgrading both boxes at the same time. The idea is to test my most used software first, as something always go wrong/take some time to fix, then upgrade the main box.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •