[Matt Devo]

I installed OpenELEC standalone, and would like to test KodiBuntu in a "Live" configuration. Is this possible? I tried booting off a USB image, but it hangs up on "Booting from USB...". I tried this with 2 USB drives.

If I decided to overwrite OpenELEC and install KodiBuntu, can I do this without reinstalling the stock firmware? The instructions on page 1 said that you can rerun the standalone setup, but how do you access the script without first booting into ChromeOS?

whatever method you are using to create the live USB sounds faulty then. I use/recommend UUI.

once you've run the standalone setup via the script, your ChromeBox becomes a normal PC. So you would just boot/install Kodibuntu off USB like you would on any other PC. Just be aware of all the manual configuration required after the fact to get Kodibuntu running properly (kernel update, sound config, etc) all of which is well outside the scope of this forum/thread.

[Reb313]

I'm sorry, but I followed the guide to duel boot Ubuntu and ChromeOS, I partitions, I installed Ubuntu... but I'm confused about the coreboot and Legacy BIOS

So the Legacy BIOS should have updated on it's own already, and with my setup I SHOULDN"T update my Coreboot right?

Thanks

[Matt Devo]

I'm sorry, but I followed the guide to duel boot Ubuntu and ChromeOS, I partitions, I installed Ubuntu... but I'm confused about the coreboot and Legacy BIOS

So the Legacy BIOS should have updated on it's own already, and with my setup I SHOULDN"T update my Coreboot right?

Thanks

correct. what part of the instructions were confusing / how can I make this more clear? The coreboot firmware update is under the standalone heading of the script menu, so it should be clear it doesn't apply to dual boot users...right?

[Reb313]

I'm sorry, but I followed the guide to duel boot Ubuntu and ChromeOS, I partitions, I installed Ubuntu... but I'm confused about the coreboot and Legacy BIOS

So the Legacy BIOS should have updated on it's own already, and with my setup I SHOULDN"T update my Coreboot right?

Thanks

correct. what part of the instructions were confusing / how can I make this more clear? The coreboot firmware update is under the standalone heading of the script menu, so it should be clear it doesn't apply to dual boot users...right?

Your guide was clear, it's what I read elsewhere that confused me.
The only other part that confuses me is the os verification is off screen - press space bar to re-enable.

From the guide I understood that if I press space there I will have to completely wipe chrome os and do the setup entirely over again? That's seems super risky... Did I misunderstand that? I have everything set but I'm slightly worried.

[Reb313]

Also, I thought I read it was possible to actually run Kodi within Chrome OS itself? But now I can't find anything how to.

[Matt Devo]

Your guide was clear, it's what I read elsewhere that confused me.
The only other part that confuses me is the os verification is off screen - press space bar to re-enable.

From the guide I understood that if I press space there I will have to completely wipe chrome os and do the setup entirely over again? That's seems super risky... Did I misunderstand that? I have everything set but I'm slightly worried.

If you hit [space] on the developer mode boot screen, it switches back to verified boot mode - so you can't use the legacy boot function to boot OpenELEC or Ubuntu. It shouldn't actually erase anything from the dual boot portion, it will just erase your ChromeOS user data. If you switch back to developer mode, everything should be how it was, but no guarantees. Don't hit [space] and you'll be fine.

Also, I thought I read it was possible to actually run Kodi within Chrome OS itself? But now I can't find anything how to.

it's possible, but it's not viable. You'd need to install Ubuntu (eg) and then Kodi in a chroot which would still be using all of the ChromeOS kernel/drivers etc. Pretty sure you don't get video acceleration (at least running it in a window).

[Reb313]

Your guide was clear, it's what I read elsewhere that confused me.
The only other part that confuses me is the os verification is off screen - press space bar to re-enable.

From the guide I understood that if I press space there I will have to completely wipe chrome os and do the setup entirely over again? That's seems super risky... Did I misunderstand that? I have everything set but I'm slightly worried.

If you hit [space] on the developer mode boot screen, it switches back to verified boot mode - so you can't use the legacy boot function to boot OpenELEC or Ubuntu. It shouldn't actually erase anything from the dual boot portion, it will just erase your ChromeOS user data. If you switch back to developer mode, everything should be how it was, but no guarantees. Don't hit [space] and you'll be fine.

Also, I thought I read it was possible to actually run Kodi within Chrome OS itself? But now I can't find anything how to.

it's possible, but it's not viable. You'd need to install Ubuntu (eg) and then Kodi in a chroot which would still be using all of the ChromeOS kernel/drivers etc. Pretty sure you don't get video acceleration (at least running it in a window).

So really, I should just go with Ubuntu or something and forget the Chrome OS entirely. Then I should update my Coreboot right?

[Matt Devo]

So really, I should just go with Ubuntu or something and forget the Chrome OS entirely. Then I should update my Coreboot right?

If all you want to do is run Kodi, then do a standalone OpenELEC setup. Ubuntu requires a bit more upfront setup (kernel updates, sound config), so unless you need/want to run additional app/services and are comfortable with linux, OE is the way to go. But either way, you would just follow the steps for a standalone setup from the first post (which includes installing the custom coreboot firmware). Only difference is with OE, the script has a function to create the install media for you (which isn't 100%, so if it doesn't boot for you, just re-create the install media from another PC).

[Reb313]

So really, I should just go with Ubuntu or something and forget the Chrome OS entirely. Then I should update my Coreboot right?

If all you want to do is run Kodi, then do a standalone OpenELEC setup. Ubuntu requires a bit more upfront setup (kernel updates, sound config), so unless you need/want to run additional app/services and are comfortable with linux, OE is the way to go. But either way, you would just follow the steps for a standalone setup from the first post (which includes installing the custom coreboot firmware). Only difference is with OE, the script has a function to create the install media for you (which isn't 100%, so if it doesn't boot for you, just re-create the install media from another PC).

I'm not going to be doing just Kodi. So I think Ubuntu is the way to go for me.

No point in keeping Chrome OS around that I can think of.

[denz13]

Hi all,

I've currently got a dual boot setup (ChromeOS + Ubuntu 14.10 (Desktop) and unfortunately it looks like I've ran out of disk space on my Ubuntu disk - I've only installed Transmission-Daemon, SortTV & Upgraded the Kernal. What are my options for increasing the disk for Ubuntu to use without trashing everything?

Looking at 'Disks' there're 2 ROOT-A partitions, 2.1GB each partition, can these be resized?

Any advice would be appreciated.

the only partitions you should be resizing are the ChromeOS stateful partition (userdata), which is /dev/sda1, and the Ubuntu partition (KERN-C) which is /dev/sda7. You should do this from a bootable USB utility like PartedMagic, but be aware it will cause ChromeOS to "repair" itself on next boot, which will erase all existing userdata. If it goes south, just be prepared to do a factory reset and start from scratch.

Thanks for the response Matt.

I've decided to scrap ChromeOS completely in order to make use of the extra 9GB, and instead use the standalone firmware and Kodibuntu.

[Reb313]

I am currently installing Xubuntu.

Following this guide to make it look like Chrome OS.

http://linuxthemer.blogspot.com/2014/06/...art-1.html

Is there anything that needs to be done with a single install otherwise?

[Matt Devo]

I am currently installing Xubuntu.

Following this guide to make it look like Chrome OS.

http://linuxthemer.blogspot.com/2014/06/...art-1.html

Is there anything that needs to be done with a single install otherwise?

yes, as per the wiki:

Note: If installing a Linux-based OS other than OpenELEC, you will most likely need to manually update the kernel for optimal operation. Kernel version 3.14 is the minimum recommended; 3.16 has a fix for most MCE remote controls, and 3.18.4 has a fix for an Intel GPU bug that can cause hanging during video playback.

[Reb313]

I am currently installing Xubuntu.

Following this guide to make it look like Chrome OS.

http://linuxthemer.blogspot.com/2014/06/...art-1.html

Is there anything that needs to be done with a single install otherwise?

yes, as per the wiki:

Note: If installing a Linux-based OS other than OpenELEC, you will most likely need to manually update the kernel for optimal operation. Kernel version 3.14 is the minimum recommended; 3.16 has a fix for most MCE remote controls, and 3.18.4 has a fix for an Intel GPU bug that can cause hanging during video playback.

Is that different than updating the Coreboot ?

[denz13]

I installed OpenELEC standalone, and would like to test KodiBuntu in a "Live" configuration. Is this possible? I tried booting off a USB image, but it hangs up on "Booting from USB...". I tried this with 2 USB drives.

If I decided to overwrite OpenELEC and install KodiBuntu, can I do this without reinstalling the stock firmware? The instructions on page 1 said that you can rerun the standalone setup, but how do you access the script without first booting into ChromeOS?

whatever method you are using to create the live USB sounds faulty then. I use/recommend UUI.

once you've run the standalone setup via the script, your ChromeBox becomes a normal PC. So you would just boot/install Kodibuntu off USB like you would on any other PC. Just be aware of all the manual configuration required after the fact to get Kodibuntu running properly (kernel update, sound config, etc) all of which is well outside the scope of this forum/thread.

Matt, I've just installed Kodibuntu in a standalone setup myself. Are you able to give any pointers to guides which provide details on the additional configuration you speak of? I've already updated the kernal with no issues.

Thanks in advance (again)

[Matt Devo]

yes, as per the wiki:

Note: If installing a Linux-based OS other than OpenELEC, you will most likely need to manually update the kernel for optimal operation. Kernel version 3.14 is the minimum recommended; 3.16 has a fix for most MCE remote controls, and 3.18.4 has a fix for an Intel GPU bug that can cause hanging during video playback.

Is that different than updating the Coreboot ?

coreboot is the firmware (BIOS); the kernel is the "core" of the OS. So yes

Matt, I've just installed Kodibuntu in a standalone setup myself. Are you able to give any pointers to guides which provide details on the additional configuration you speak of? I've already updated the kernal with no issues.

Thanks in advance (again)

none of it's ChromeBox-specific. There's probably some info in the Linux/Live support forum, but I don't think anyone has made a complete list/guide of what's needed post-install on an Intel-based setup