[Soli]

I took it you meant unscaled as in "untouched/bypassed". So what I said was basically that you cannot directly substitue YUV/RGB values even though they seem the same (16-235), there is a lossy colorspace conversion involved. It may seem illogical at first, if you don't know the basic difference between the 2 colorspaces, but that's how it is.

Yes, you can convert YUV to any arbitrary RGB encoding/mode. I never said or remotely implied otherwise. In fact I implied the opposite by writing what you just quoted.

[meeotch]

Ah - just a miscommunication then. I meant "unscaled", not "untouched". Again, thanks for your help.

Believe it or not, I've been working in film / t.v. for roughly 20 years - so no stranger to colorspace transforms. It just happens that the part of the chain where I'm at never really deals with YUV. In fact, these days we're all floating point. No more logspace, no more 8-bit, everything as God intended. ;-)

[AttacktheCow]

@AttacktheCow,

- there's no need to update the firmware unless you are having issues that a new version fixes
- if you look at the change log, 2015-01-29 is the latest/current firmware version. The firmware isn't always updated every time the script is
- the firmware and OpenELEC are not coupled in any way, so you can (should) just update OpenELEC in the future
- a dirty install is ok for the 4.x -> 5.0 update as long as you don't run into issues; if you do, then a clean install is recommended. Or just use the 'Hard Reset' function under the OpenELEC General settings.

Thank you. It seems like i did not know many things about this

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

[Vlaves]

Hi all,

I don't know if this has been asked before. My HP Chromebox (running under Openelec 5.0.2) is waking up from standby when it shouldn't.
I already turnd of WOL for the Ethernet adapter and I have putted that command in the autostart.sh as I have been reading that in some other Forum/Thread.

Where can I have a look, what is waking up my Chromebox?

Thanks for any help.

Regards
Vlaves

[Soli]

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.

If you did an non-advanced install, then you probably have a swap partition. This can safely be deleted. ( I take it you only use it for light webrowsing and Kodi). The 16GB SSD is probably too small to "comfortably" dual boot Chrome OS and Ubuntu.

[Lambada123]

Hello Matt,

thanks for your work with that Firmware. But in moment there are an little issue with the lastet one 20150129 for my Asus Chromebox i3...

The Problem comes with my last Firmware Update from 20141202 to 20150129, at the same time i have made an OpenELEC Update (Plex Version)... now the BlueTooth WakeUp works... but when i do this my Chromebox are very noise for 1 minute or longer. The Fan an runs FullPower. Some Times it runs for minutes...

It this an Firmware Problem or an OpenELEC Problem?

Thanks
Lambada

[AttacktheCow]

Oh boy, its me again.
It seems like i kinda soft bricked my openelec install.
I just tried out some skins and addons, didn't change anything in systems folders or something. Then i played a movie, stopped it and then it blackscreened on me. I restarted it, but it keeps blackscreening.
Upon restart (does not make a difference between powerbutton and plugging), it shows the openelec screen, and then a brief Kodi intro video which then freezes as its almost over. The screen stays black.
I can access it remotely via ssh and also can access it via the networkshare.
I tried pushing openelec onto it via the networkshare update folder, and upon reboot, it does indeed install it, yet it keeps freezing at this video.


Does anyone have a workaround for that?
Thanks

[theslime]

I can't help you, but calling a black screen you can access through ssh and network shares a softbrick feels like pushing it.

[Soli]

*facepalm* If you can ssh, then why don't you delete the .kodi (or similar, I dont use OE) directory.

[hockeycoach]

Hockeycoach, If you apt-get Kodi then the standalone option xsession gets added automatically. You basically only need to set autologin. Would be easier to just install Kodibuntu, though, if you don't need to run full blown Ubuntu/Unity. I did post my steps a few pages back. Works really good. I'm using a PS3 remote and the waf factor is superhigh, including playback of Netflix through netflixbmc. In fact it works so good that I'm going to give away a box to my sister, and that is saying a lot!

Soli, thanks for the reply. Interesting suggestions, I'll look into the apt-get Kodi with autologin. I like the full blown Ubuntu installation, I'm a Linux bigot from way back and like to 'play'.
btw ... what is the "waf factor"? the fact that it is superhigh intrigues me

edit..
wait... WAF factor... is it Wife Acceptance Factor ?

[Matt Devo]

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.

Hi all,

I don't know if this has been asked before. My HP Chromebox (running under Openelec 5.0.2) is waking up from standby when it shouldn't.
I already turnd of WOL for the Ethernet adapter and I have putted that command in the autostart.sh as I have been reading that in some other Forum/Thread.

Where can I have a look, what is waking up my Chromebox?

Thanks for any help.

Regards
Vlaves

look at the kernel log (dmesg) via ssh right after it wakes up

If you did an non-advanced install, then you probably have a swap partition. This can safely be deleted. ( I take it you only use it for light webrowsing and Kodi). The 16GB SSD is probably too small to "comfortably" dual boot Chrome OS and Ubuntu.

a dual boot Ubuntu install doesn't use swap, just a single data partition - see above.

Hello Matt,

thanks for your work with that Firmware. But in moment there are an little issue with the lastet one 20150129 for my Asus Chromebox i3...

The Problem comes with my last Firmware Update from 20141202 to 20150129, at the same time i have made an OpenELEC Update (Plex Version)... now the BlueTooth WakeUp works... but when i do this my Chromebox are very noise for 1 minute or longer. The Fan an runs FullPower. Some Times it runs for minutes...

It this an Firmware Problem or an OpenELEC Problem?

Thanks
Lambada

Last I checked, the Plex version of OpenELEC is based on an ancient version of OpenELEC (3.2.4) using a much older kernel version which does not have full support for the ChromeBox's hardware. It's not a firmware issue, it's a kernel/driver issue.

Oh boy, its me again.
It seems like i kinda soft bricked my openelec install.
I just tried out some skins and addons, didn't change anything in systems folders or something. Then i played a movie, stopped it and then it blackscreened on me. I restarted it, but it keeps blackscreening.
Upon restart (does not make a difference between powerbutton and plugging), it shows the openelec screen, and then a brief Kodi intro video which then freezes as its almost over. The screen stays black.
I can access it remotely via ssh and also can access it via the networkshare.
I tried pushing openelec onto it via the networkshare update folder, and upon reboot, it does indeed install it, yet it keeps freezing at this video.


Does anyone have a workaround for that?
Thanks

ssh in, rm -rf /storage, reboot.

*facepalm* If you can ssh, then why don't you delete the .kodi (or similar, I dont use OE) directory.

see above

[Soli]

Hockeycoach, If you apt-get Kodi then the standalone option xsession gets added automatically. You basically only need to set autologin. Would be easier to just install Kodibuntu, though, if you don't need to run full blown Ubuntu/Unity. I did post my steps a few pages back. Works really good. I'm using a PS3 remote and the waf factor is superhigh, including playback of Netflix through netflixbmc. In fact it works so good that I'm going to give away a box to my sister, and that is saying a lot!

Soli, thanks for the reply. Interesting suggestions, I'll look into the apt-get Kodi with autologin. I like the full blown Ubuntu installation, I'm a Linux bigot from way back and like to 'play'.
btw ... what is the "waf factor"? the fact that it is superhigh intrigues me

edit..
wait... WAF factor... is it Wife Acceptance Factor ?

Yeah except it would actually be Wife Acceptance Factor Factor. Kinda like ATM Machine.. I think you should be set if you do an "sudo apt-get install kodi-bin kodi" and configure lightdm to autologin your user.

[AttacktheCow]

I can't help you, but calling a black screen you can access through ssh and network shares a softbrick feels like pushing it.

Sorry, i didn't want to overrate my problem As some might have noticed, i am not really and expert user here....

*facepalm* If you can ssh, then why don't you delete the .kodi (or similar, I dont use OE) directory.

to be honest, i don't know where it is saved within the openelec system and what it will happen, when there is no kodi left on the system.

ssh in, rm -rf /storage, reboot.

gives me a:

Code:

rm: can't remove '/storage': Read-only file system

[fritsch]

rm -rf /storage/*