Neversoft cloudready stopping on cloudready logo

Comments

10 comments

  • Forrest Smith

    Hi kenneth,


    https://www.amazon.com/Dell-Inspiron-Touchscreen-Bluetooth-MaxxAudio/dp/B07CT7FX7Z

    Does that look like your device?

    If so - I think what you're running into is a graphics support bug. CloudReady has a known issue with some newer AMD graphics which we think we have a handle on - I would guess that it will work in versions v73.1 and newer. I'd recommend you keep an eye on our blog/social media and, when you see v74.3 released (that's our next stable release that you can put on a USB) you should try again.

    0
    Comment actions Permalink
  • Kenneth

    Yes this is my laptop. I will be on the lookout for the next release and will update on what happens with it.

    0
    Comment actions Permalink
  • Patrick

    When will that update be out?

    0
    Comment actions Permalink
  • Kenneth

    On the latest update as of writing this cloudready now works on my device. I still get a distorted picture right before cloudready logo but it works. The linux beta installs but refuses to start. I don't know if i need to enable a chrome://flags setting or if its just broken.

    0
    Comment actions Permalink
  • Forrest Smith

    Kenneth - 

     

    You might need to enable a bios setting for virtualization or "vtx" - do you see anything like that?

    0
    Comment actions Permalink
  • Kenneth

    Virtualization is enabled on my system as seen in this photo. https://cdn.discordapp.com/attachments/423286561355071499/574382387358728202/IMG_20190504_130621.jpg
    Could it be because of my AMD based laptop?

    0
    Comment actions Permalink
  • Forrest Smith

    Could be? You could try reinstalling - I've seen one or two cases where the install state of Crostini was brittle enough to need a fresh start.

    0
    Comment actions Permalink
  • Kenneth

    I have tried reinstalling Linux and just tried a full oOS reinstall with the same issue.

    0
    Comment actions Permalink
  • Forrest Smith

    I would guess then that you're right - Linux container support is made by Google and may assume some things that cause bugs on your particular amd machine.

    Try again on v75 or higher, once out in the next month or two. That will have an upgraded kernel with closer adherence to Chrome OS 's settings, so hopefully it will lead to better support.

    0
    Comment actions Permalink
  • Forrest Smith

    Hi Kenneth 

    If you're interested in continuing to try, we have an unstable preview of v75.1 available for you to install:

    https://go.neverware.com/previewrelease

    0
    Comment actions Permalink

Please sign in to leave a comment.