[zeroq]

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.

Thanks will do that for now

[jamesasus]

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?

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

[Matt Devo]

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.

[jamesasus]

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.

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.

[Matt Devo]

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?

[jamesasus]

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?

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.

[Matt Devo]

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.

the developer mode boot screen and the full firmware / legacy boot screen run at different video modes (1024x768x16 and VESA text mode respectively), so the former not working isn't indicative that the latter likely won't.

[turbobuickguy]

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.

[mxlance]

@matt devo

wanted to say thank you!
my chromebox + kodi is brilliant, and not possible without you.

i started out using kodibuntu and it worked well until i upgraded to kodi 16 and
things got buggy. so i returned here to search for help. now i am running galliumos per your recommendation and kodi is working smoother and faster than ever.

i highly recommend galliumos to anyone who needs more than just kodi on there chromebox. galliumos also makes it possible to run the latest firefox browser which plays flash video streams better than chrome, or so it seems to me.

thank you again.

[goujam]

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.

[BoxFreak]

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.

That's right. And at least first AccuEQ didn't do equalizing at all. Audyssey does adjustments also on higher frequencies. Btw. you can't measure subwoofer's distance with tape measure, because it doesn't tell you how much (processing etc.) delay your subwoofer has got. Typically subwoofer's real distance is 1-2m less than measured with Audyssey. And yes I've had AVR's for 20 years, so I've also used that tape measure -method too.

Enough off topic for this thread...

[Help09]

Apparently I did something wrong. I dual booted chromeos and Ubuntu. Then changed my boot options to 30 sec + Ubuntu.

But now I can't seem to access chromeos or even launch the command prompt to change my boot options back to chromeos. While waiting 30 seconds to boot in the top right I see
Gbb.flags is nonzero: 0x000000488
Read-only firmware I'd: google_panther .4920.24.21
Active firmware I'd: google_panther .4920.24.21

I'm assuming I missed a step or something. Any help would be greatly appreciated!

EDIT: different keyboard worked

[PWH1]

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

[Matt Devo]

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

Paul,

are you attempting to do a standalone or dual boot install of OpenELEC? CTRL-D not working on the recovery screen means you're already in developer mode, so that doesn't sound like a problem. It appears to me that you did a standalone install before, but used the legacy boot update (rather than the full firmware) and set the boot options to default to legacy boot with a short delay. Then, after you used the ChromeOS recovery USB to restore ChromeOS, it wiped out the updated legacy boot, but left the boot flags alone, leaving you in the state you find yourself now.

what you need to do is boot ChromeOS, run the script, and set the boot options back to the default. Then install either the standalone firmware (and install OpenELEC via USB) or run the dual boot setup (which needs to be done twice) and don't change the boot flags until after you have a working setup.

[PWH1]

Matt -

Thanks for the response. I performed a dual boot install with OpenELEC. On my initial install I did change the delay to 30 seconds on my initial installation. I will follow your steps and see how I get along. I will post back my progress.

Paul