Hp pavilion x2 (again)

Comments

11 comments

  • Dondre Johnson

    It can be the processor. It may not be compatible with CloudReady. Which processor did x2 have, and the other laptops? I may be able to help.

    1
    Comment actions Permalink
  • Forrest Smith

    You may need ot boot in UEFI mode - maybe even specify the boot path

     

    [Your USB] > efi > boot > bootx64.efi

    1
    Comment actions Permalink
  • Enrico Fermi

    Tried UEFI and bootx64. Maybe it really is the problem with processor. x2's processor is atom. Other one was not mine so I don't know

    0
    Comment actions Permalink
  • Forrest Smith

    Try selecting not bootx64, but bootia32

    0
    Comment actions Permalink
  • Enrico Fermi

    Also done that.. Changed my USB, re-imaging, srsly every thing that I thought it might be work that i saw on forum, it's already done.. Something new or Guess I should just give up.. Thanks for your time Sir

    0
    Comment actions Permalink
  • Forrest Smith

    Sounds like a graphics issue, ultimately. I'd encourage you to come back and check v51 when we release later in July.

    1
    Comment actions Permalink
  • Enrico Fermi

    That's relief to me! I will certainly wait for that. If you can, mail me when the next update comes out, I'm a student so I don't have much time for checking out right now.

    0
    Comment actions Permalink
  • Kristoffer kortsen

    I also have this exact hp x2 mini laptop convirtible. Has anyone actually got chromium onto this device?
    I have a few other old laptops (dell and samsung) that I'm running cloudready on, but can't get it going on this one...

    0
    Comment actions Permalink
  • diego de brasi

    is there any news?

     

    0
    Comment actions Permalink
  • Forrest Smith

    We've made massive improvements to driver support for modern chipsets and for tablet functionality since this thread was started 3+ years ago.

    I would recommend just giving it a shot with the 64bit installer.

    0
    Comment actions Permalink
  • Kristoffer kortsen

    @forrest smith: just wasted another few hours trying again, nothing has changed...

    0
    Comment actions Permalink

Please sign in to leave a comment.