(2015-02-17, 19:44)Matt Devo Wrote: you should just be able to type 'kodi' into the program search at the top left. I assume you selected 'y' when asked if you want to install Kodi?

there's nothing ChromeBox-specific about the Ubuntu/Kodi installation (outside of the partition setup when dual booting), it's just automated for your convenience

(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.

(2015-02-18, 00:05)Soli Wrote: Not surprising coming from you
Well, the the dual core 1.4ghz celeron in the chromebox isn't powerful enough to do 1080p (although it is just about enough to do 1080p in youtube/html5 99% of the time), and using VDPAU is not really working with the Intel drivers, and VAAPI support is nowhere to be seen. I think it's worth a try

(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.

2) Color range: the grayscale ramp test video looked steppy at default settings, so I turned on Limited Color Range in kodi settings. Ramp looked smoother, but the blacks were washed out. Ran "xrandr --output HDMI1 --set "Broadcast RGB" "Full" with some improvement, but the blacks are still very grey ("Limited 16:235" was worse). The only way to get them looking "right" was to turn OFF Limited Color Range, and *also* use the "Full" setting via xrandr. Am I missing something? How can I get the correct range processing in kodi to avoid banding, but still have the range go all the way down to black?

(2015-02-18, 00:41)Soli Wrote: Yeah I tried the vdpau wrapper, deactivated the gpu whitelist in chrome. I also managed to confirm gpu accel. in flash by deactivating pepper flash and overriding the white list in adobe flash. I think flash worked a little better, but not anywhere stable without dropping frames. (With the *15 card). But this was with a pretty bloated linux mint, i'll have another go with Kodibuntu. As for html5 , i dont think there was any difference. Does Chrome for Linux even support VDPAU?

Btw, I always believed the crystal hd kernel code was useless, thats it was reccomended that you build the drivers from git yourself. And I'm not really disagreeing with you at anything at all. My only question is: will it work with crystal hd in Chrome or not? I guess I'll have to find that out for myself.

(2015-02-18, 09:00)meeotch Wrote: The wiki is where I got the xrandr command / limited color range settings. My understanding is that you would either handle the limited range in kodi (Limited in kodi + Full via xrandr), or the opposite. In my case, the combination that produces correct black levels (Non-limited kodi + Full xrandr) also produces a quantized grayscale ramp test image. If there's a section of the wiki that I'm missing, other than the Chromebox page where I got this info, definitely hit me with a link.

Oh, and I should mention that the grayscale ramp is also quantized on the ChromeOS side.

As for the network link, I don't know how to get ChromeOS to display the link speed in Mbps - if anyone knows, please let me know. Link speed on the ubuntu side is given above.

(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.

(2015-02-18, 09:00)fritsch Wrote:

(2015-02-18, 00:41)Soli Wrote: Yeah I tried the vdpau wrapper, deactivated the gpu whitelist in chrome. I also managed to confirm gpu accel. in flash by deactivating pepper flash and overriding the white list in adobe flash. I think flash worked a little better, but not anywhere stable without dropping frames. (With the *15 card). But this was with a pretty bloated linux mint, i'll have another go with Kodibuntu. As for html5 , i dont think there was any difference. Does Chrome for Linux even support VDPAU?

Btw, I always believed the crystal hd kernel code was useless, thats it was reccomended that you build the drivers from git yourself. And I'm not really disagreeing with you at anything at all. My only question is: will it work with crystal hd in Chrome or not? I guess I'll have to find that out for myself.

You will need to find, port and get kernel drivers and userspace compiled ... was no fun the last time.