(2015-02-18, 10:20)Matt Devo Wrote:

(2015-02-18, 08:12)meeotch Wrote: Just got my Asus Chromebox, and installed Ubuntu/Kodi dual-boot. Relatively painless, except...

1) My wifi link seems slow. On first boot after the script updated my firmware, I couldn't connect to my wifi network at all for about 10min - kept getting the "out of range" error in chromeos. After I managed to connect & finish installing ubuntu, my link speed (as given by iwconfig) never seems to get above ~120Mbps (802.11n), or ~300Mbps (802.11ac). By comparison, my ancient laptop, sitting at the same location, gets a 200-450Mbps 802.11n link. Before flashing back to the stock firmware to see if it's any better, I thought I'd post here.

when running a dual boot setup, you're running the stock firmware, just with a fixed/modified legacy boot payload. This has absolutely no effect on networking, wired or wifi, under ChromeOS or any other OS. Any issues you are having with wifi are due to something else - your router, RF environment, wifi card hardware/firmware/drivers, etc. Also, unless Asus changed components, the included Atheros wifi/BT module is dual-band (2.4/5GHz) abgn, not ac. Also, the reported link speed and actual transfer speed are loosely correlated at best.

(2015-02-17, 22:20)Matt Devo Wrote:

(2015-02-17, 21:20)hockeycoach Wrote: Thanks for the reply!
Due to "personal malloc errors" (aka brain cramps) I had done a bunch of screen grabs during the installation... just in case, and I just looked, and yes I did answer 'y' to the install Kodi question.

I will try your search suggestion.
It was very late last night when I finished the install and I had been scratching my head on another issue when I noticed the Kodi thing.

if it didn't install automatically as it should have (I'll check that here shortly, just LMK what options you chose for version and metapackage), you can just follow the instructions on the Kodi wiki for linux/Ubuntu installation and all should be fine.

(2015-02-18, 17:40)hockeycoach Wrote: Hi Matt
So I did the search for kodi as you suggested and found it! Thanks ! Added it to the menu, all is good.
The other issue I was fighting, where it would not automount a 32G sd card seems to have cleared itself up after rebooting.

Now I'm playing with the colour levels between the asus chomebox and my sharp aquos , (xrandr) but not too worried I'll get it the way I want it... eventually

The only thing left to sell this setup to my wife is to have Kodi start automatically after power up and Ubuntu boot. I'm going to look into the RC scripts and add it there... unless there is another way you might suggest.

Quote:-------------------------------------------------------------
Updating the coreboot Firmware (standalone)
-------------------------------------------------------------
As of version 3.0 of the script, you can simply re-download/re-run the script under any Linux distro with a full bash shell. The dual-boot related options will be disabled, but the Standalone Setup / coreboot firmware update option will be available.

If you are running a Linux distro which does not have a full bash shell, such as OpenELEC, you should use my standalone firmware updater script from an SSH terminal. This script is only intended to update a ChromeBox already running my custom coreboot firmware (via the EZ setup script), and will not work under ChromeOS/ChromiumOS.

Code:
curl -L -O http://goo.gl/HSZer4
bash HSZer4

Note: the bash command will require using the 'sudo' prefix if not running OpenELEC (since with OE, you are always logged in as the root user). Additionally, this script must be run immediately after booting, otherwise it may fail to detect the current firmware version.

Quote:You already have the latest firmware (20150129)

(2015-02-18, 09:03)fritsch Wrote: Which kind of ramp do you display?
When you force your GPU to full, what can you still see on this image: https://dl.dropboxusercontent.com/u/55728161/fullrgb_test.jpg

(2015-02-18, 10:20)Matt Devo Wrote: unless Asus changed components, the included Atheros wifi/BT module is dual-band (2.4/5GHz) abgn, not ac. Also, the reported link speed and actual transfer speed are loosely correlated at best.

(2015-02-19, 00:16)meeotch Wrote: So xbmc assumes that input video files have preserved the 16-235 range from the original source material, and by default scales this to 1-255, which is then either re/de-scaled to 16-235 (Limited) for output to a t.v. or left alone (Full) for output to a monitor. So when viewing on a monitor, you're stuck with either banding (if you expand) or incorrect levels (if you don't).

(2015-02-19, 03:34)Soli Wrote: there is no such thing as an unscaled YUV 16-235 to RGB (or RGB 16-235/limited for that matter)