Login at Kodi Home

hockeycoach · 2015-02-17, 21:20

(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

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.

**VanillaXtract** · 2015-02-17, 21:33

I just assumed it wasn't installed by default and added the repo and installed it. It didn't appear installed, but then again neither does LibreOffice when looking in the package manager even though it clearly is.

Matt Devo · 2015-02-17, 22:20

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

Soli · 2015-02-17, 23:18

Crystal HD with Kodibunti/Chrome. I should probably try it first, then post my impressions in this thread... But I just realized the wifi card in the Chromebox use a regular minipcie slot, so it should be possible to fit a Crystal HD card there. That should let me watch 1080p in both HTML5 and flash (if I deactivate the pepperflash plugin inside Chrome). Incidentally Kodi has removed support for Crystal HD, but I'd use VAAPI anyways. I wonder if this would be a win-win?

**fritsch** · 2015-02-17, 23:19

Crystalhd ... that must be a joke ...

oh man, you are killing me.

Soli · (This post was last modified: 2015-02-18, 00:06 by Soli.)

Not surprising coming from you Wink

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 Smile

**fritsch** · (This post was last modified: 2015-02-18, 00:21 by fritsch.)

(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

There is a gl vdpau wrapper which works great and is btw. the default on newer intel drivers [1]. Installation is a bit of a hazzle, but works okayish.

[1] http://cgit.freedesktop.org/xorg/driver/...dcfb15b704

Btw. I removed crystalhd from kodi, cause the kernel drivers are not maintained anymore (were removed from the linux kernel (staging)) and the integration into kodi was a real nightmare at the end - the original author had really bad feeling seeing this ancient code die that slow without any support of the community and "crystal" distributions ... we still wait for it to come back, as some volunteers volunteered, but nothing ever happened.

Edit: http://www.webupd8.org/2013/09/adobe-fla...dware.html <- the systemwide stuff (4. second part) is enough, the driver is already included in trusty and can be installed with: sudo apt-get install libvdpau-va-gl1

For completeness: Kodi will still use VAAPI (which this gl thingy tunnels through).

Soli · 2015-02-18, 00:41

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.

meeotch · 2015-02-18, 08:12

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?

**fritsch** · 2015-02-18, 08:47

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

2) Please see the wiki. It all depends on the Range of your TV.

meeotch · 2015-02-18, 09:00

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.

**fritsch** · 2015-02-18, 09:00

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

**fritsch** · (This post was last modified: 2015-02-18, 09:04 by fritsch.)

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

Which kind of ramp do you display? Is it a full range, like, e.g. https://dl.dropboxusercontent.com/u/5572...172435.png or Limited. When you force your GPU to full, what can you still see on this image: https://dl.dropboxusercontent.com/u/5572...b_test.jpg

We need to find out what your TV does ... it should do "Limited" by default, but from what you say - yours is full. Try setting it to limited, force your gpu to full and use kodi's "Use Limited Range". Furthermore turn off "Prefer VAAPI Render Method" and don't use "VAAPI Postprocessing".

Matt Devo · 2015-02-18, 10:20

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

Soli · (This post was last modified: 2015-02-18, 14:10 by Soli.)

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

Just found out the latest Chrome already has disabled npapi plugins, they even removed the override option, so no more adobe flash in chrome. I can't be bothered to install Firefox to just get this going, I am terrified to f*** up my really smooth Kodibuntu install. To be honest, I don't really care that much for flash acceleration, but it would be nice to have html5 acceleration. A review on amazon says it's possible, but I kinda doubt that.

I just got a second HP Chromebox, so I might just clone my existing Kodibuntu and try it after all, though. Or not, we'll see Wink