(2016-04-01, 16:06)Matt Devo Wrote:

(2016-04-01, 08:58)zeroq Wrote: Matt Devo,
Are you going to build kodi 16 with EGL any time soon? I'm using OpenELEC 6.95.1 at the moment but i think picture is better and more clear on OpenELEC-Generic.x86_64-6.0.398-Intel_EGL if this is true i'm happy to use OpenELEC-Generic.x86_64-6.0.398-Intel_EGL until OpenELEC 17 is more stable. What do you think?

There will not be an EGL version of Kodi 16. If you prefer the 15.2 EGL version, stick with that until v17 is released.

Quote:For a standalone setup, you will need to perform the following steps:
Open the ChromeBox and remove the write-protect screw
Put the ChromeBox in developer mode
Download/run the EZ setup script
Select the Standalone / coreboot Install option, which will backup your stock firmware/BIOS and flash a custom one
Create install media for desired OS. Script includes option to create install media for OpenELEC and Kodibuntu
Power off ChromeBox

(2016-04-01, 17:30)jamesasus Wrote: I'm having a slight issue here with my Asus CN60. I successfully accessed developer mode and ran the steps for a standalone set-up

The coreboot install was successful based on the message received. I am now faced with a blank screen because I missed the step "Create OpenELEC Install Media." Instead, I rebooted and now I am faced with a blank screen. Any ideas on what I may be able to do here? Can I add these files from a laptop?

(2016-04-01, 17:39)Matt Devo Wrote:

(2016-04-01, 17:30)jamesasus Wrote: I'm having a slight issue here with my Asus CN60. I successfully accessed developer mode and ran the steps for a standalone set-up

The coreboot install was successful based on the message received. I am now faced with a blank screen because I missed the step "Create OpenELEC Install Media." Instead, I rebooted and now I am faced with a blank screen. Any ideas on what I may be able to do here? Can I add these files from a laptop?

you can create the OpenELEC install media from any machine, links/instructions are on the wiki page; the functionality to create the install media from the script is just there for convenience. Just download the disk image for whatever version you want from the wiki, and use Rufus or Win32DiskImager to write to USB. Then power on the Chromebox with the USB inserted, press ESC when prompted, and select the USB to boot.

(2016-04-01, 19:16)jamesasus Wrote: That was straightforward, I now have the USB configured. Thank you. Now, I'm running blind because the monitor is still not powering on after the Chromebox is powered-on. I think this monitor has issues with lower resolutions, but I have no choice. When booting, do I immediately press ESC? By any chance, does anyone have any screenshots by any chance? To be honest, I operated blind to get into Developer Mode. Once in developer mode everything appeared on the monitor when downloading the firmware etc.

(2016-04-01, 20:14)Matt Devo Wrote:

(2016-04-01, 19:16)jamesasus Wrote: That was straightforward, I now have the USB configured. Thank you. Now, I'm running blind because the monitor is still not powering on after the Chromebox is powered-on. I think this monitor has issues with lower resolutions, but I have no choice. When booting, do I immediately press ESC? By any chance, does anyone have any screenshots by any chance? To be honest, I operated blind to get into Developer Mode. Once in developer mode everything appeared on the monitor when downloading the firmware etc.

While you can press 'ESC 2 enter' in sequence to try and boot blindly, it would be easier to just hook up to another monitor or TV I'd think. I assume you're using some kind of output adapter if it's an older monitor?

(2016-04-01, 21:10)jamesasus Wrote: Yes, i'm using a VGA-HDMI adapter. When I was fighting to get into Developer mode, hooking up to my new Samsung TV yielded the same results (blank screen) at the time. I'll try again later when I'm home again.

(2016-03-31, 14:32)BoxFreak Wrote: No Audyssey - no more Onkyo. AccuEQ is just a bad joke.

(2016-04-05, 13:33)turbobuickguy Wrote:

(2016-03-31, 14:32)BoxFreak Wrote: No Audyssey - no more Onkyo. AccuEQ is just a bad joke.

Not sure if you've ever done calibration manually. It's very simple, and the only things you need are a tape measure, and a decent SPL meter (not expensive). Purchase these once, and you can calibrate any system better than the auto calibrations.

(2016-04-05, 16:01)goujam Wrote:

(2016-04-05, 13:33)turbobuickguy Wrote:

(2016-03-31, 14:32)BoxFreak Wrote: No Audyssey - no more Onkyo. AccuEQ is just a bad joke.

Not sure if you've ever done calibration manually. It's very simple, and the only things you need are a tape measure, and a decent SPL meter (not expensive). Purchase these once, and you can calibrate any system better than the auto calibrations.

Ho do you measure at different frequencies and adjust the spl accordingly. Such as with Audyssey on my denon x4000 will measure bass frequencies and adjust for any spikes.

(2016-04-10, 22:57)PWH1 Wrote: Hello Folks,

New to the community and Kodi. I have a Dell Chromebox (Haswell) running OpenElec (dual boot). I successfully installed Kodi a few days ago and used Community Portal SpinzTv. However, I decided I wanted to get away from use of the CP and decided to perform a fresh install of OpenElec. When attempting to boot into developer mode my Chromebox will not acknowledge the CTRL D (paperclip process). I can boot off my USB recovery image and get to developer mode after boot. I can then head to chronos and perform the steps needed to install OpenElec. However, on reboot (first pass) the box reboots then nothing.... The screen goes black.

As of now, I cannot get to developer mode using the prescribed steps. The box simply ignores the command and sits on the Chrome OS missing screen.

I will keep reading to see if I can find a similar situation. Happy to provide more info if needed.

Thanks for any support.

Paul