[megamanwilson]

[/quote]

Why are you running such and old version of Mint? The 3.2 kernel is definitely your issue; you should be running Mint 17 with kernel 3.14 or newer

---

[quote='wackid' pid='1852941' dateline='1417690270']

Thanks for the reply I did this version of mint becuasue in their website it said it was long term release meaning that I would not have to
update every six months and would be supported through 2017.

Look around the net and it looks like xubuntu 14.04 its long term release. So if I were to replace the linux mint installtion with xubuntu 14.04 I would just create the usb instatallion and boot chromebox from usb and install.

Just found out that 14,04 is not the updated kernel. I am just going to install mint 17 and forget about long term release.

[john.cord]

The standalone firmware uses the same VGA BIOS as my fixed SeaBIOS payload for the stock firmware, so if it is the issue, flashing the standalone firmware won't fix it. Have you tried using the suspend/resume script in the wiki? It forces the video/audio to reconnect upon resume.

I did not because i thought that this could not solve my problem. I did not get a signal even with the box booting from power off. The workaround with the powerd down hdmi switch is working too if i try to wake the box from sleep. If the TV is on, the HDMI switch is on and the box is in slepp the wakup results in a "No Signal" to the TV. If the Box is in Slepp and the TV and HDMI Switch on and i power down the HDMI Switch, then wake up the Box an then power on the HDMI Switch i get a signal and everything is normal. Same thing with Box completely shutted down.

[Matt Devo]

I did not because i thought that this could not solve my problem. I did not get a signal even with the box booting from power off. The workaround with the powerd down hdmi switch is working too if i try to wake the box from sleep. If the TV is on, the HDMI switch is on and the box is in slepp the wakup results in a "No Signal" to the TV. If the Box is in Slepp and the TV and HDMI Switch on and i power down the HDMI Switch, then wake up the Box an then power on the HDMI Switch i get a signal and everything is normal. Same thing with Box completely shutted down.

you can install 14.04 + updated kernel (think Ubuntu has 3.16.5 available) and you'll be good to go. Mint 17 still requires a kernel update I believe.

I did not because i thought that this could not solve my problem. I did not get a signal even with the box booting from power off. The workaround with the powerd down hdmi switch is working too if i try to wake the box from sleep. If the TV is on, the HDMI switch is on and the box is in slepp the wakup results in a "No Signal" to the TV. If the Box is in Slepp and the TV and HDMI Switch on and i power down the HDMI Switch, then wake up the Box an then power on the HDMI Switch i get a signal and everything is normal. Same thing with Box completely shutted down.

if you're not getting a signal on a cold boot even with the TV/switch on, then my only suggestion would be to use an inline device like a Dr. HDMI (I think that's what it's called) which will store the EDID data from the TV and present it to the ChromeBox when powered on

[john.cord]

if you're not getting a signal on a cold boot even with the TV/switch on, then my only suggestion would be to use an inline device like a Dr. HDMI (I think that's what it's called) which will store the EDID data from the TV and present it to the ChromeBox when powered on

ok so in your oppinion this is not a bug related to the chromebox? Why is it then that any othe HDMI Device is working with this tv and only the chromebox not? Your advice with the dr. hdmi is nice but i dont want to pay 80€ for a device that is fixing a bug.

I think i move the chromebox in my Livingroom and buy a hashwell nuc for the bedroom...

[Matt Devo]

ok so in your oppinion this is not a bug related to the chromebox? Why is it then that any othe HDMI Device is working with this tv and only the chromebox not? Your advice with the dr. hdmi is nice but i dont want to pay 80€ for a device that is fixing a bug.

I think i move the chromebox in my Livingroom and buy a hashwell nuc for the bedroom...

I'm not sure which exact component is to blame, but using it on another setup where it doesn't exhibit the issue is obviously the most cost effective solution

[LilSnoop40]

Question, so I received the 2 other ASUS Chromeboxes I ordered and have them all up and running. Any point to update to RC1 Kodi or just wait till final?

Second I am not sure if I did the bios update on one of my boxes, will this be a problem? All 3 boxes where standalone installs.

3rd, is there any reason to use a custom advanced settings .xml file, if so what one should I use?

Lastly does the suspended feature work running openelec, the shutdown works fine.

Thanks!

[Matt Devo]

Question, so I received the 2 other ASUS Chromeboxes I ordered and have them all up and running. Any point to update to RC1 Kodi or just wait till final?

changes between the RC and final are likely to be minimal. I'd do a clean install of RC-1 and just set it to auto-update.

Second I am not sure if I did the bios update on one of my boxes, will this be a problem? All 3 boxes where standalone installs.

run the standalone updater script (in the OP) from a ssh prompt, it will check and update if needed.

3rd, is there any reason to use a custom advanced settings .xml file, if so what one should I use?

no

Lastly does the suspended feature work running openelec, the shutdown works fine.

Thanks!

As per the wiki, suspend/resume works fine on a standalone install.

[LilSnoop40]

Sorry to sound like I don't know, but what is this script and were do I perform it at to check the bios?

Second I am not sure if I did the bios update on one of my boxes, will this be a problem? All 3 boxes where standalone installs.

run the standalone updater script (in the OP) from a ssh prompt, it will check and update if needed.

[/quote]
As per the wiki, suspend/resume works fine on a standalone install.
[/quote]

Wonder why the box turns on while in standby?

Lastly since I removed chrome how to I do a clean install, do I use the openelec usb I made from the initial install

[Matt Devo]

Sorry to sound like I don't know, but what is this script and were do I perform it at to check the bios?

go to the first post in this thread, then to the section 'Updating the coreboot Firmware.' You need to use Putty (or a similar tool) to connect to the ChromeBox/OpenELEC via ssh, then run the two commands listed in that section.

Wonder why the box turns on while in standby?

Lastly since I removed chrome how to I do a clean install, do I use the openelec usb I made from the initial install

you need to provide more details here - how are you putting it in standby? what devices are connected? a log file would tell a lot, so connect via Putty and run the following (immediately after suspending and it resuming):

Code:

dmesg | pastebinit

and post the URL provided.

you do a clean install same as you would on any other PC - boot the install media and reinstall. If your existing install media is an older version, then just download OE and create an updated install media as per their instructions.

[LilSnoop40]

Ok, thanks Matt

[kgcaughron]

Matt, Have you thought about creating a definitive install guide for both OS's and getting Kodi to post them on the WIKI like the format for installing MySQL on different OS's? I've taken the time to actually copy the whole forum thread into word 2007 and could zip it and send to you if you would like to have some reference on hand and not have to be online for the longest time doing it. I'm planning on printing it out or using the dual monitor setup that I have and running two word documents at the same time and doing a lot of cut and paste from one to the other. I'm planning on getting two chromeboxes next summer and would like to have a guide on the easiest to install and setup guide on hand to be able to get the living room and game-day room TV's setup. I'm also going to be setting up the 6 port cable card in the server to supply TV signals to all of my XBMC / Kodi setups. I have a dedicated server for the video storage and for the TV Card. I'm not wanting to bog down that server with uTorrrent downloads and other post processing programs, so I put it onto and older Dell 4200 computer and I'm running all of the Torrents and post processing on it, then transferring the files to the server. I'm also looking into a program called DropIt. It's supposed to automaticly put the files into the correct directories that you define for shows, which it wasn't actually designed for BTW. Also if anyone is wondering about a torrent frontend program like TED, there is a real great one out now, it's Called 'Auto Torrent', and it looks better and runs faster than TED. I use it and use ShowRss.it to get the feeds. A lot of the shows that I watch I get the torrents about 2 days after showing on the TV. Thanks KC

[Matt Devo]

KC,

I maintain the ChromeBox wiki as well, and don't want to have to update both any time there is a change, so I keep everything script related in the first post of this thread, and everything else in the wiki. Both are updated continuously.

If you're planning on getting 2 ChromeBoxes next summer, I'd hold off copying/printing anything, since 1) things are likely to change, and 2) the ChromeBox might not be the best option for you in ~6 months.

-Matt

[bigdaddyo811]

Is there a way to remote desktop onto a HP chromebox + openelec ?

[Matt Devo]

Is there a way to remote desktop onto a HP chromebox + openelec ?

I don't believe so, but what would you need it for? The filesystem is accessible via SMB and SSH, and there's the XBMC/Kodi web interface and various remote apps (e.g., YATSE) for control

[wrxtasy]

I believe what your looking for would be this but its only for the ChromeOS side of a dual boot setup:

VNC® Viewer for Google Chrome™

https://chrome.google.com/webstore/detai...hbla?hl=en

However if a flavour of Linux OS (Non Openelec) were installed, then anything is possible.....