Stuck at CloudReady Splash screen on MacBook Pro

Comments

13 comments

  • JCloud

    How are creating the USBs? There are two ways so try both, there USB maker and Chromebook recovery tool way.

    Think CR doesn't like macs with ATI graphics though.

    0
    Comment actions Permalink
  • Philip Panic

    I used the Chromebook recovery tool to create the USB. And no this is not an ATI graphics mac, it has Nvidia inside.

    0
    Comment actions Permalink
  • Philip Panic

    And sadly I cannot try the USB Maker way since I have no access to Windows machine.

    0
    Comment actions Permalink
  • Philip Panic

    So I fixed this yesterday evening. 

    What went wrong?

    So my Mac clearly has some issues with the graphic card or something (I guess) which was also present on basically any Linux distribution I would try. So instead of having one monitor listed, because it's a laptop I got two listed. I was so confused until I realised that the second monitor was a virtual LVDS (a monitor that basically does not exist?!) 

    So when I booted from the USB I only saw the CloudReady logo and nothing else, but I heard the startup sound that CR gives so I knew that it was actually running but on that virtual monitor so I had no idea what was going on. Then I went in the tutorial for installing on uncertified devices and I saw that there were also instructions on how to install it via TTY. After I rebooted with CR now installed via TTY it just started working.

    However Linux Environment still does not seem to work in release 89 on my machine... Just me or is this a version bug?

    0
    Comment actions Permalink
  • JCloud

    Weird stuff, good work.

    Linux should work, but not all machines.

    0
    Comment actions Permalink
  • JCloud

    Machine needs to support virtualisation, there's various tech requirements. It's buggy even when does work.

    Also if your machine is not high spec the performance will disappoint you anyway.

    0
    Comment actions Permalink
  • Philip Panic

    So basically the error I encounter is:

     

    Error: routine at frontends/vmc.rs:243 `vm_start(vm_name,&user_id_hash,features,user_disks,!matches.opt_present("no-start-lxd"))` failed: bad VM status: `VM_STATUS_FAILURE`: VM failed to start in time

    0
    Comment actions Permalink
  • Philip Panic

    and yes my Mac's CPU does support VT-x by default and I reset PRAM just to make sure it isn't disabled.

     

    0
    Comment actions Permalink
  • JCloud

    Ok well you machine might just fall under the buggy side of things for Linux beta. This is beyond my tech levels anyhow.

    0
    Comment actions Permalink
  • Philip Panic

    Hmm... Thank you for help anyways, appreciate it!

    0
    Comment actions Permalink
  • JCloud

    The official Tech guys from neverware who help on the forum are really busy since the Google deal.

    I have a Lenovo flex 5 Chromebook i5, 8gb RAM, Linux is pretty much the only things that get the fans going on it.

    0
    Comment actions Permalink
  • Philip Panic

    Well yeah that is understandable since you are allocating your CPU to another machine that is running (even though you're chrooted).

     

    Guess I'll wait for firmware update to v90 and maybe it does fix something, which from my POV may not be a part of updates...

     

    0
    Comment actions Permalink
  • JCloud

    I mainly use Linux Beta for extra browsers, the two best that work are Chrome Linux and Edge.

    It's actually really reliable on that Chromebook, just resource hungry.

    0
    Comment actions Permalink


ChromeOS Flex is replacing CloudReady, so this community is no longer accepting new comments.

Please visit the ChromeOS Flex Help Community to post any new questions or thoughts! You can still link back to this or other pages in this community in order to reference past conversations.

Please sign in to leave a comment.