Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Update Virtualbox conflicts with Virtualbox ...

  1. #11
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,381

    Default AW: Update Virtualbox conflicts with Virtualbox ...

    @DocB
    Maybe you open a new thread with all your errors and also your running openSUSE Version.
    Because this problem was about switching from Virtualbox Version 6.14 to 6.16.

  2. #12
    Join Date
    Jun 2008
    Location
    Düsseldorf/Germany
    Posts
    283

    Default Re: AW: Update Virtualbox conflicts with Virtualbox ...

    Quote Originally Posted by Sauerland View Post
    @DocB
    Maybe you open a new thread with all your errors and also your running openSUSE Version.
    Because this problem was about switching from Virtualbox Version 6.14 to 6.16.
    I just had a fresh test installation of Leap 15.2.
    The virtualbox-kmp-default-6.1.16 could not be updated automatically from 6.14, as some dependencies needed to be resolved manually, as well w/o the preempt kernel. So somewhat as described in https://bugzilla.opensuse.org/show_b...?id=1180625#c2

  3. #13

    Default Re: AW: Update Virtualbox conflicts with Virtualbox ...

    Quote Originally Posted by DocB View Post
    I just had a fresh test installation of Leap 15.2.
    The virtualbox-kmp-default-6.1.16 could not be updated automatically from 6.14, as some dependencies needed to be resolved manually, as well w/o the preempt kernel. So somewhat as described in https://bugzilla.opensuse.org/show_b...?id=1180625#c2
    THESE ARE THE STEPS TO CLEAN UP ALL THOSE UNWANTED “PREEMPTS”:
    In Yast, you first UNINSTALL virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel (with this last one, you choose the third alternative: “keep kernel-syms with broken capacities”)
    THEN YOU REBOOT
    Then, in Yast again, you put a TABU option (with right mouse) on these three: virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel ; that way these three won't bother you anymore, never: they're "tabu" now.
    THEN YOU REBOOT AGAIN
    Then, in Yast again, you UPDATE kernel-syms (with this, you choose the third alternative option: “keep kernel-syms with broken capacities”) Don't bother about those “broken capacities”: they refer to the unwanted preempts.
    THEN YOU REBOOT AGAIN
    And now your computer works fine, your kernel-default updates will not prompt you anymore to install those ********** “preempts”, and your VirtualBox (or what it was that pulled in those “preempts”) works like a charm.
    The first reboot is needed so that you can put the “tabu” option on the three “preempts”;
    the second reboot is needed so that the three tabus are fixed and so that you can update your kernel-syms with the right version;
    the third reboot is needed to finalize all the steps you've taken and to clean up your computer for good.
    Have a nice day!

Page 2 of 2 FirstFirst 12

Posting Permissions

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