(2014-06-19, 01:05)tetsuya Wrote:

(2014-06-19, 00:08)Veronica Wrote: Does anyone know how to access OpenElec via VNC? i already have vnc viewer extension installed in chrome in my windows 8 pc and was working fine when i had ubuntu installed.
All relevant posts are about raspberry pi agrr

TIA

[WIP] jDownloader Addon with X-Server and VNC Support (i386 & x86_64)

There are two ways to this addon remotely:

- Using Xming based X-Server
- VNC Connection optionally VNC Connection to XBMC too

(2014-06-19, 16:54)live4ever Wrote: I'd like to upgrade to coreboot with this script but I can't seem to get the CN60 Chromebox to boot from USB (ChromiumOS) anymore.

Currently I'm running the SeaBIOS from here:
http://johnlewis.ie/asus-chromebox-owners-rejoice/

and booting a dedicated OpenELEC from the SSD.

Pressing ESC at boot I get the choice of SSD or USB (options 1&2) but it always boots from the hard drive (even if I remove the SSD).
It booted fine before from USB when I installed OpenELEC.

Thanks for all your work Matt.

(2014-06-19, 22:00)Veronica Wrote: Is anyone else experiencing unresponsivness (kind of a screen hang/freeze) if you leave openelec ON without use for several minutes? the screen just hang and i cant make it work with the remote control, mouse or yatse so i dont think it gets in suspend mode. Also about "suspend mode" when i click on it, the box shutdown so suspend mode doesnt seem to work. Is it a bug in latest openelec or is there a configuration i'm missing?. For now what i care more is that "hang" state because i'm unable to access the hdd attached to the box or ssh the box or access it via VNC.

Quote:Ahhh btw what can i do if i press ctrl+alt+F2, it goes into a black screen and nothing can make it go back to openelec, not even ctrl+alt+F7, ONLY a reboot (again not nice).

(2014-06-19, 23:17)Matt Devo Wrote:

(2014-06-19, 22:00)Veronica Wrote: Is anyone else experiencing unresponsivness (kind of a screen hang/freeze) if you leave openelec ON without use for several minutes? the screen just hang and i cant make it work with the remote control, mouse or yatse so i dont think it gets in suspend mode. Also about "suspend mode" when i click on it, the box shutdown so suspend mode doesnt seem to work. Is it a bug in latest openelec or is there a configuration i'm missing?. For now what i care more is that "hang" state because i'm unable to access the hdd attached to the box or ssh the box or access it via VNC.

OE rebooting when coming out of suspend with the stock firmware is a known issue. Works fine with Coreboot firmware.

Quote:Ahhh btw what can i do if i press ctrl+alt+F2, it goes into a black screen and nothing can make it go back to openelec, not even ctrl+alt+F7, ONLY a reboot (again not nice).

I'm confused as to what you are trying to do. CTRL-ALT-F2 will bring up a terminal with a shell prompt in ChromeOS; in OpenELEC it will likely switch to an uninitialized terminal. CTRL-ALT-F1 should get you back in any case (in both ChromeOS and OE).

(2014-06-20, 03:03)Veronica Wrote: Hi @matt thanks for the response but you got it wrong, i didn't say it rebooted itself.
The problem is: Say i stop using openelec ok i change to tv mode to watch some tv, then after a while i want to get back to OpenElec and i find the screen hung (frozen, static whatever the thing is it doesn't react) and nothing can make it "wake"or react, only a FORCED (MANUAL) REBOOT. So it's not realiable i cannot access to my attached hdd from my windows 8 pc or SSH the box neather VNC it, NADA.. UNTIL i reboot the box.

NOTE THAT I DO USE THE LATEST VERSION OF COREBOOT.

I also stated that suspend mode is not working right, it seems it shutdown the box INSTEAD... well the upper light of the power button in the box TURNS OFF so that's why i think it shuts down the box but i'm not sure if that's how it is supposed to behave?

(2014-06-19, 22:00)Veronica Wrote: Is anyone else experiencing unresponsivness (kind of a screen hang/freeze) if you leave openelec ON without use for several minutes? the screen just hang and i cant make it work with the remote control, mouse or yatse so i dont think it gets in suspend mode. Also about "suspend mode" when i click on it, the box shutdown so suspend mode doesnt seem to work. Is it a bug in latest openelec or is there a configuration i'm missing?. For now what i care more is that "hang" state because i'm unable to access the hdd attached to the box or ssh the box or access it via VNC.

The only thing i can do is force reboot the chromebox, not nice as i like to safe remove my hdd first.

Ahhh btw what can i do if i press ctrl+alt+F2, it goes into a black screen and nothing can make it go back to openelec, not even ctrl+alt+F7, ONLY a reboot (again not nice).

Thanks

(2014-06-20, 04:48)tetsuya Wrote:

(2014-06-19, 22:00)Veronica Wrote: Is anyone else experiencing unresponsivness (kind of a screen hang/freeze) if you leave openelec ON without use for several minutes? the screen just hang and i cant make it work with the remote control, mouse or yatse so i dont think it gets in suspend mode. Also about "suspend mode" when i click on it, the box shutdown so suspend mode doesnt seem to work. Is it a bug in latest openelec or is there a configuration i'm missing?. For now what i care more is that "hang" state because i'm unable to access the hdd attached to the box or ssh the box or access it via VNC.

The only thing i can do is force reboot the chromebox, not nice as i like to safe remove my hdd first.

Ahhh btw what can i do if i press ctrl+alt+F2, it goes into a black screen and nothing can make it go back to openelec, not even ctrl+alt+F7, ONLY a reboot (again not nice).

Thanks

You can ssh in or type in the TTY that you can't see

Code:

xrandr --auto

it should fix that. I had to do that on my old Ivy Bridge (Xubuntu) once or twice when I forgot to turn the tv and computer off over the weekend when I wasn't home. I just used JuiceSSH on my tablet and fixed it that way.

(2014-06-20, 04:21)Matt Devo Wrote:

(2014-06-20, 03:03)Veronica Wrote: Hi @matt thanks for the response but you got it wrong, i didn't say it rebooted itself.
The problem is: Say i stop using openelec ok i change to tv mode to watch some tv, then after a while i want to get back to OpenElec and i find the screen hung (frozen, static whatever the thing is it doesn't react) and nothing can make it "wake"or react, only a FORCED (MANUAL) REBOOT. So it's not realiable i cannot access to my attached hdd from my windows 8 pc or SSH the box neather VNC it, NADA.. UNTIL i reboot the box.

NOTE THAT I DO USE THE LATEST VERSION OF COREBOOT.

I also stated that suspend mode is not working right, it seems it shutdown the box INSTEAD... well the upper light of the power button in the box TURNS OFF so that's why i think it shuts down the box but i'm not sure if that's how it is supposed to behave?

I've never seen anything like that here, I've left the box running all day, switched inputs (it's connected to my desktop monitor ATM), no issues. After this happens, you should check the logs (accessible via SMB in the \logs dir) to see if it managed to capture anything.

Suspend is supposed to turn off the power button light. When you resume (via the power button, or via WOL by YATSE) it comes back on.

Sounds to me like an add-on or some other process is getting hung up.

(2014-06-20, 14:39)smitbret Wrote: Having trouble with the OpenELEC install and now I can't get past the recovery screen on the Chromebox. Someone on a different forum said that Matt Devo was the guy with the knowledge.

I followed this guide for installing OpenELEC:

http://geekfreely.blogspot.com/2014/...chromebox.html

I got all the way through installation on the HDD. I was all kinds of pumped up and excited, but when I restarted the Chromebox, it just went to the recovery screen and said there was no OS installed.

Tried some different combos of CTRL-L, CTRL-D, etc. with no luck. The Chromebox just kept coming back to the Recovery Screen.. I ended up doing a recovery (via Google's Recovery Tool) and trying the install again from Step 1.5 Set Firmware Boot Flags and never even got to the point where I could install the OS.

Now, when I restart the Chromebox I get a couple of BIOS announcements that quickly scroll through and ask me to press ESC to select the boot device, but it never actually responds when I do. Just goes to a full black screen with the <press ESC to select the boot drive> announcemen with the following:

Booting from Hard Disk
Early console in decompress_kernel
KASLR using RDRAND

Decompressing Linux....Parsing ELF...Performing Relocations..done
Booting the kernel

And then it just sits there with that message. If I stick the USB drive in with the Recovery Image then it posts a bunch more stuff on that page that I don't understand, just looks like more CMD Line info. I have yet to find a CTRL or CTRL-ALT or CTRL-SHFT combo that makes the Chromebox do anything.

If turn it on with a paper clip in the reset hole then I get the normal Chrome OS could not be found screen and asks me to do a recovery. In the upper LH corner is a new three lines on a background that identifies the current firmware. Hitting CTRL-I give me a bit more info of CMD line stuff that I can't decipher. I can run a recovery at this point, or it always looks like it works and the recovery completes but always boots up to this same thing.

I have even done the image download to a different USB drive for the Recovery (bypassing the Recovery Tool) but I get the exact same result every time.

I know the keyboard is being identified and works because I can scroll through the language choices on the OS recovery screen.

How in the world do I get back in to where I can reset the BIOS or just get a working recovery?

(2014-06-20, 14:39)smitbret Wrote: Having trouble with the OpenELEC install and now I can't get past the recovery screen on the Chromebox. Someone on a different forum said that Matt Devo was the guy with the knowledge.

I followed this guide for installing OpenELEC:

http://geekfreely.blogspot.com/2014/...chromebox.html

Quote:Now, when I restart the Chromebox I get a couple of BIOS announcements that quickly scroll through and ask me to press ESC to select the boot device, but it never actually responds when I do. Just goes to a full black screen with the <press ESC to select the boot drive> announcemen with the following:

Booting from Hard Disk
Early console in decompress_kernel
KASLR using RDRAND

Decompressing Linux....Parsing ELF...Performing Relocations..done
Booting the kernel

And then it just sits there with that message. If I stick the USB drive in with the Recovery Image then it posts a bunch more stuff on that page that I don't understand, just looks like more CMD Line info. I have yet to find a CTRL or CTRL-ALT or CTRL-SHFT combo that makes the Chromebox do anything.

Quote:If turn it on with a paper clip in the reset hole then I get the normal Chrome OS could not be found screen and asks me to do a recovery. In the upper LH corner is a new three lines on a background that identifies the current firmware. Hitting CTRL-I give me a bit more info of CMD line stuff that I can't decipher. I can run a recovery at this point, or it always looks like it works and the recovery completes but always boots up to this same thing.

I have even done the image download to a different USB drive for the Recovery (bypassing the Recovery Tool) but I get the exact same result every time.

I know the keyboard is being identified and works because I can scroll through the language choices on the OS recovery screen.

How in the world do I get back in to where I can reset the BIOS or just get a working recovery?

(2014-06-20, 18:05)noggin Wrote: *** EDIT : Not to worry. Decided I didn't really need ChromeOS - so went for the Stanalone Option and installed OpenElec standalone. So far so good. This little box should really rock. ***
*** EDIT 2 : Though sadly not quite perfect yet. I'd read there were problems with VAAPI. I have some 35Mbs Blu-ray H264 interlaced stuff that needs VAAPI to playback without skipping/dropping - and it hangs. In software mode it can't keep up with both H264 decoding and de-interlacing at this bitrate. I'm in Standalone mode. Is this likely to be helped by switching to a dual channel RAM set-up? ***