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

Thread: HOWTO: Install Xubuntu on HP Chromebook 14

  1. #11
    Join Date
    Mar 2015
    Beans
    1

    Re: HOWTO: Install Xubuntu on HP Chromebook 14

    You can change some of the flags in the HP Chromebook 14 seabios using the gbb utility. This enables default boot in legacy mode and a minimal time at the chromeos white screen.
    See the links here:
    http://johnlewis.ie/how-to-make-seab...our-acer-c720/
    and end of page here:
    https://wiki.archlinux.org/index.php/HP_Chromebook_14

    Also someone complains about a long boot time and usb something something error messages. A little googling suggests this is a misleading message and can be fixed by addressing the suspend (UEFI) issue like so: ( from http://realityequation.net/installin...-chromebook-14 among other places). Sorry, I lost my main sources for this error rebooting trying to address the issue.


    1. Edit /etc/default/grub, comment out the line withGRUB_CMDLINE_LINUX_DEFAULT and add this instead:

      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic"


    Hope this helps. I know your post is a little old at this point.

  2. #12
    Join Date
    Mar 2015
    Beans
    3

    Re: HOWTO: Install Xubuntu on HP Chromebook 14

    Thanks so much

  3. #13
    Join Date
    Jul 2015
    Beans
    1

    Re: HOWTO: Install Xubuntu on HP Chromebook 14

    I have problems in step 4. When i press ctrl+L i only get some bib sounds and nothing else happens. what to do?

  4. #14
    Join Date
    Jan 2011
    Location
    USA
    Beans
    28
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: HOWTO: Install Xubuntu on HP Chromebook 14

    I know I'm reviving an old thread, but I'd like to make a pointer. When I updated after this worked for me (several weeks actually) I believe a kernel update kind of broke my trackpad. What I personally did was just follow Step 5 again and it worked. That's all. Oh and it's worth noting that for me changing how the script gets the kernel source didn't seem to work for me particularly, so I left it how it came in the script and it worked completely flawlessly for me.

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

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