No Xwindows after update when booting runit base inside Virtualbox

Forum Forums New users New Users and General Questions No Xwindows after update when booting runit base inside Virtualbox

  • This topic has 2 replies, 2 voices, and was last updated Sep 1-4:27 pm by BobC.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #87828
    Member
    Peter Linu

      Hiyall,
      I configured runit-base-64 inside VirtualBox. It opened without issue. I then used the update tool and when I next tried to login I get the attached. Can someone please advise.

      • This topic was modified 8 months, 1 week ago by BobC.
      Attachments:

      Live-USB = zzz-IceWM-antiX21-runit-64-base: static persistence
      VirtualBox= zzz-IceWM-antiX21-runit-64-base

      #87834
      Moderator
      BobC
        Helpful
        Up
        0
        ::

        Sorry, I don’t know, but I fixed your title for you. “bootup” is not really a good description, IMO.

        If I took a runit USB and updated it with persistence on your machine, my guess is it would boot. The only way to know would be to try it. If you have the same issue, then the cause is probably not virtualbox related.

        I think you have a lot of not so common permutations combined, there. It doesn’t mean it can’t be solved, just might not be something obvious. Maybe someone else might has had similar issues at some point and might know more than I.

        Since Xwindows is failing to come up, it might help if you post your output from a terminal under virtual box from:
        inxi -Fxz

        You could also research common causes of that under virtualbox.

        #87905
        Moderator
        BobC
          Helpful
          Up
          0
          ::

          To be clear, without knowing what hardware and software you have, its not likely anyone can guess what might fix your problem. That might be why there are no other replies.

          Did you try duplicating the problem on the same machine with a pure antiX flashdrive setup to see if the issue was virtualbox related like I suggested above?

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.