• Ubuntu and VirtualBox

    From Barry Martin@454:1/1 to All on Thursday, March 29, 2018 18:45:00
    Hi Folks! March 29. 2018

    Just had an issue with a one of the Ubuntu Updates clobbering my
    VirtualBox -- great! there goes the BBS and ILink!!

    Error messages included:

    - Virtualbox kernel module not match; try 'modprobe vboxdrv'
    (Didn't appears to do anything except to return to Terminal
    immediately.)

    - RTR3InitEx failed with rc=-1912 (rc=-1912). The installed support
    driver doesn't match the version of the user. (I've heard about
    these cryptic error messages on Macs!)

    - Error: NS_Error_Failure (0x80004005) (So the 80004005 code says to
    go to Sun's website and download the Linux installer. I don't want
    to clobber what had been working!)

    So rebooted. SOS.

    Rebooted and went back to the previous version (the new and improved
    everything except VirtualBox was 4.4.0-116, went back to 4.4.0.112.
    That got the SOS too. Grr.

    Rebooted to go back to the current version; not sure if I want to try to
    fix or wait for a correct that may not occur: had looked around the web
    for a simple and non-destructive fix; the issue has popped up for
    several years, with dozens of proposed corrections, so of which stated
    works, others stated did not work. Among them:

    - sudo modprobe vboxdrv ==> the original trial was without sudo.
    This trial worked as well as the original.

    - sudo apt-get update
    sudo apt-get install --reinstall virtualbox
    Got the same errors.

    Fiddle-fiddle, search, search. Dawns on me there's potentially a step missing, so:
    sudo apt-get update
    sudo apt-get upgrade

    Was going to go on with with the --reinstall step but decided to check,
    maybe because I had noticed a 'response line' re: 'virtualbox dkms'
    scroll by. VirtualBox works (yeaaaa!!) and did upgrade as the screen
    looks slightly different.

    Hopefully this can help someone else.





    ¯ ®
    ¯ Barry_Martin_3@ ®
    ¯ @Q.COM ®
    ¯ ®


    ... There is a chasm
    of carbon and silicon
    the software can't bridge.
    --- MultiMail/Win32 v0.47
    þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.dtdns.net | 856-933-7096 (454:1/1)
  • From Ky Moffet@454:1/1 to Barry Martin on Sunday, April 01, 2018 18:00:00
    BARRY MARTIN wrote:
    Hi Folks! March 29. 2018


    - sudo modprobe vboxdrv ==> the original trial was without sudo.
    This trial worked as well as the original.

    - sudo apt-get update
    sudo apt-get install --reinstall virtualbox
    Got the same errors.

    Fiddle-fiddle, search, search. Dawns on me there's potentially a step missing, so:
    sudo apt-get update
    sudo apt-get upgrade


    Well, that's intuitive! ;)
    þ RNET 2.10U: ILink: Techware BBS þ Los Angeles, Ca þ www.techware.dynip.com

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.dtdns.net | 856-933-7096 (454:1/1)
  • From Barry Martin@454:1/1 to Ky Moffet on Monday, April 02, 2018 07:46:00

    Hi Ky!

    - sudo modprobe vboxdrv ==> the original trial was without sudo.
    This trial worked as well as the original.

    - sudo apt-get update
    sudo apt-get install --reinstall virtualbox
    Got the same errors.

    Fiddle-fiddle, search, search. Dawns on me there's potentially a step missing, so:
    sudo apt-get update
    sudo apt-get upgrade

    Well, that's intuitive! ;)

    Thanks! I'm still learning and so 'cookbooking' projects and solutions. Figured adding the 'upgrade' step wasn't going to cause a problem.

    Not what 'install' does different from 'upgrade' but apparently was the missing step my system wanted.

    ¯ ®
    ¯ Barry_Martin_3@ ®
    ¯ @Q.COM ®
    ¯ ®


    ... Writing Rules: Analogies in writing are like feathers on a snake.
    --- MultiMail/Win32 v0.47
    þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.dtdns.net | 856-933-7096 (454:1/1)
  • From Mike Powell@454:1/105.2 to Barry Martin on Saturday, June 09, 2018 18:17:00
    Not what 'install' does different from 'upgrade' but apparently was the missing step my system wanted.

    I am guessing the package you were trying to install
    was not compatable with an older version of another package it depends on.

    Upgrade may have picked up a newer version of a package that it was
    dependent on, where install would not have picked up the newer version of
    the other package.

    At least I think that is how it works (and how I have run into trouble with
    it before!).

    Mike

    ---
    # SLMR 2.1a # ....we came in?


    --- GTMail 1.26
    * Origin: ILink: moe's * 15028758938 * moetiki.ddns.net:27 (454:1/105.2)