2014-12-21, 20:51
(2014-12-21, 11:58)nolight Wrote: Hi, I recently installed dual boot Chrome OS/OpenELEC on Asus Chromebox with OpenELEC as default OS.
On my Sharp LCD TV LC-32M400M-BK (native resolution 1366x768) it is able to display the OpenELEC on boot up. Connection is direct HDMI.
On my Panasonic plasma TV TH42PV70H (native resolution 1024x768) it is showing up as if no signal. Tried both direct HDMI connection and HDMI connection through chromebox -> AVR -> TV.
Pls help on how I can fix the no display on Panasonic TV. Thanks.
I can only guess that for some reason it's not setting the proper output resolution on startup. That's going to require a bit of debugging, and is probably most easily dealth with on the OpenELEC IRC channel.
(2014-12-21, 14:45)toadleyb Wrote: I just purchased the Asus Celeron Chromebox as a gift for someone for Christmas. I have Ubuntu and ChromeOS setup as dual boot.
I have a Logitech keyboard and mouse that I am having major issues with. I have no problem with the keyboard as far as selecting Ctrl D or Ctrl L but once I am booted into ChromeOS or Ubuntu the mouse and keyboard become completely unresponsive. The keyboard will work sometimes in Ubuntu but the mouse is unusable. This same mouse and keyboard work fine on my Home Theater Computer in the same room in both Windows and Ubuntu.
Is it worth me buying another Mouse and Keyboard and trying it or could it be an issue with the Chromebox. I do not own a wired mouse or keyboard to try (Can you even buy them anymore?).
Any troubleshooting tips?
that's certainly not an issue I've seen before - what model keyboard/mouse? do they use a unifying receiver?
(2014-12-21, 15:50)Jpopgt Wrote: Hello again,
I have followed the tutorial again on the first page and finished the setup and i still can't dual boot ChromeOS and OpenElec, when my machine boots up it is still on the 1 second boot option to boot into Chrome.
I must be missing something somewhere and can't figure out where i'm going wrong.
The only thing that i done different was remove the screw before i powered on the chromebox.....could this possibly be something to to with it?
Appreciate some help again.
cheers.
removing the screw first is fine, has nothing to do with anything. What exactly is your issue? does it not boot into OpenELEC when you press [CTRL-L] on the dev boot screen? If not, what happens? If you just want a longer delay, then use the script to set it as such.
(2014-12-21, 20:04)paintmecyanide Wrote: Posting here because this script is among the top Google results for Chromebox Ubuntu.
The current version does not enable i386 by default. As a result, a number of packages will not install, particularly pipelight - needed to get Amazon Prime Video, among other things, working. This triggers errors that don't make it apparent that the problem is related to the architecture. This can be fixed, post install, by running the commands shown below.
sudo dpkg --add-architecture i386
sudo apt-get update
You might also want to consider not hard coding the Ubuntu version to "latest," and making Kodi installation optional. I am likely not the only person using this script as a starter for a general purpose Ubuntu box. I manually switched to lts, and deleted out Kodi while troubleshooting this problem, but they obviously ended up being unrelated.
If you're using it as dedicated Ubuntu box, just install from a Ubuntu ISO on a USB stick (after installing the coreboot firmware).
If you want to dual boot but don't want Kodi or the latest release, then use Jay Lee's ChrUbuntu script.
I've added i386 to the build script - thanks for the heads up
