[malcolms]

how do i get to hangouts

[giant25]

I'm having a problem with "No signal" on the HDMI port connected to my dual-boot Chromebox after a reboot. I have a new Samsung UN65JU6500 4k TV and have read through this forum. I've tried creating an autostart.sh in /storage/.config, which looks like this:

Any idea on what could be going on? Please let me know if there's any other info I can provide that might help. I've also tried putting HDMI1 in PC and UHD color as suggested earlier in this thread. I'm on the latest Firmware on my Samsung TV. Thanks.

is this a box you just set up, or was it previously working and how doesn't due to an update?

Previously working, not working with new TV, no other changes. I have since updated to OE 6, but same behavior before that update.
Does my autostart.sh look right?
Any other way to force 1080p?
Is it possible I need a FW or BIOS update on Chromebox (ran script in February)?
Thanks.

Hey Matt, any idea on those questions? Thanks.

[Matt Devo]

Yeah, i do think is the BIOS. Anyway no biggy, the important thing is the usb improvement.

2015-12-14 update should fix

Checked in the manual just now and on the HDMI inputs my TV supports these VESA modes: 800x600,1024x768,1280x1024@60 [email protected].
Initial installation of OpenELEC - first firmware flashing - I remember I had small letters on the screen. And all the time the brief text flashes during boots. But now they are quite big. So I assume that the previous BIOS was using the 1920x1080 resolution and the current BIOS some other lower resolution. And that's why the HDMI input looses the Just Scan mode.

2015-12-14 update should fix

how do i get to hangouts

srsly? use google.

Previously working, not working with new TV, no other changes. I have since updated to OE 6, but same behavior before that update.
Does my autostart.sh look right?
Any other way to force 1080p?
Is it possible I need a FW or BIOS update on Chromebox (ran script in February)?
Thanks.

1) no, remove the parentheses and ampersand. You don't want the boot process to continue until that command returns.
2) try updating to the latest Legacy Boot payload (2015-12-14)

also, try another cable if you haven't already. If that doesn't work, I'll add an option to the script to use the headless video BIOS (for the legacy boot payload, it's already an option for the standalone firmware), which allows booting even when a connected display isn't connected. Then, the autoscript command should force the correct video mode.

[Ladeef]

Has anyone here with a Chromebox or Haswell box installed the EGL ppa build (Ubuntu server + 4.3 kernel) and experienced hang/freeze issues while browsing menus and idle?

I do and posted all info with debug logs in official thread but @fritsh asked me to find more people preferably non Chromebox users with the same problem. He won't be able to pick up this until january but would be good if more people post in the VAAPI EGL thread about this problem and help with debug logs (You know the more the better).

Thanks!

I had the same issue, I believe I changed the setting "vertical display sync" to Let the driver choose and that fixed it.

[fvlserevere]

Hello Matt

I got a weird issue trying to update SeaBIOS. When I run the script and choose option 5 I got the next message: "Invalid parameter name: platform_family. This feature is only valid for Haswell and Broadwell based ChromeOS devices". I'm on your 20150618 SeaBIOS version. My device is a Dell Chromebox (Tricky).

Do you have an idea about what's wrong with it?

Hi Matt, any news on this matter?

[Matt Devo]

Hi Matt, any news on this matter?

Didn't have a chance to test last night, was busy with the firmware release. Will try to do so tonight

[fvlserevere]

Didn't have a chance to test last night, was busy with the firmware release. Will try to do so tonight

Ok, I'll be back later. Thank you.

[malcolms]

Hello Matt, what do you believe I should do to repair.

[Matt Devo]

Hello Matt do you believe I should do to repair.

I can't suggest any action yet, since I'm still not totally clear on what box you have, what firmware you loaded/restored, and what recovery image you used. Once I know that we can move forward. But I think it will be done most easily via a chat program, like IRC, hangouts, whatsapp, etc.

[malcolms]

ok i figured out hangouts whats your name on it

[Matt Devo]

ok i figured out hangouts whats your name on it

<snip> but will probably be easiest for me to walk you thru it on Hangouts. Hit up up when you get a chance ([email protected])

[giant25]

1) no, remove the parentheses and ampersand. You don't want the boot process to continue until that command returns.
2) try updating to the latest Legacy Boot payload (2015-12-14)

also, try another cable if you haven't already. If that doesn't work, I'll add an option to the script to use the headless video BIOS (for the legacy boot payload, it's already an option for the standalone firmware), which allows booting even when a connected display isn't connected. Then, the autoscript command should force the correct video mode.

Hey Matt, thanks for the suggestions. Removing the parens and & didn't really change anything. Updating to the latest Legacy Boot payload didn't either. A different cable had already been tried. I did make progress, however. I enabled "HDMI UHD Color" on the Samsung 4k TV and the Chromebox will now boot up upon reboot. Here's the 3 scenarios I've tried on the 4k Samsung:

1) UHD Color Disabled -- Will not boot upon power on/reboot
2) UHD Color Enabled & autostart.sh set to 1080p -- boots up, blank screen until my Kodi skin shows up (no OS Verif, no BIOS, no OE logo, no Kodi logo), but works fine. This is what I'm using for now.
3) UHD Color Enabled & autostart.sh removed -- boots up, but blank screen. I ssh in and run xrandr and see that current res is 4096x2160 @ 24Hz.
4) Ctrl-D at boot to ChromeOS is a blank screen all the time (but works on my older 1080p monitor's HDMI)

So I'm halfway there, was just hoping to find a way to be able to see the boot screens and ChromeOS. I'm wondering if there's a way to prevent the Chromebox from attempting to connect at 4k from the get go (I'm assuming the autostart.sh only kicks in when OE starts to boot.)

Excellent wiki, btw. I hadn't read it in a while and it is one of the most solid out there.

Any other guidance would be appreciated. Not sure where to go from here. Thanks.

[Cbeatz]

My first time posting here and was wondering if anyone could help. I have an Asus Chromebox and earlier in the year was experimenting with loading Ubuntu and Windows on it which I was successful in doing. Now I would like to turn ON the OS verification so that the device boots in Chrome OS without pausing. Currently when I press the space bar it does nothing but beep and eventually shows the bios version to the top left, then shows the boot screen, then goes blank. I think I have the original firmware backed up, I see the files on my share but not sure how to load it. I don't mind manually nuking the device back to its original state. Does any one have alternate steps to Turn OS verification back on or steps for restoring the original firmware? Thanks in advance.

[Matt Devo]

Ok, I'll be back later. Thank you.

fixed, scripted updated

Hey Matt, thanks for the suggestions. Removing the parens and & didn't really change anything. Updating to the latest Legacy Boot payload didn't either. A different cable had already been tried. I did make progress, however. I enabled "HDMI UHD Color" on the Samsung 4k TV and the Chromebox will now boot up upon reboot. Here's the 3 scenarios I've tried on the 4k Samsung:

1) UHD Color Disabled -- Will not boot upon power on/reboot
2) UHD Color Enabled & autostart.sh set to 1080p -- boots up, blank screen until my Kodi skin shows up (no OS Verif, no BIOS, no OE logo, no Kodi logo), but works fine. This is what I'm using for now.
3) UHD Color Enabled & autostart.sh removed -- boots up, but blank screen. I ssh in and run xrandr and see that current res is 4096x2160 @ 24Hz.
4) Ctrl-D at boot to ChromeOS is a blank screen all the time (but works on my older 1080p monitor's HDMI)

So I'm halfway there, was just hoping to find a way to be able to see the boot screens and ChromeOS. I'm wondering if there's a way to prevent the Chromebox from attempting to connect at 4k from the get go (I'm assuming the autostart.sh only kicks in when OE starts to boot.)

Excellent wiki, btw. I hadn't read it in a while and it is one of the most solid out there.

Any other guidance would be appreciated. Not sure where to go from here. Thanks.

there's no reason the ChromeBox shouldn't work properly at 2160p24/30 - in fact I've set up several that way for friends/customers. Unfortunately I don't have a whole lot of experience with 4K TVs, and none with the Samsungs, but it sure sounds like a glitch on their end. Have you tried googling for others having similar issues with that particular model or series set? The only thing I can think of to try and work around the issue from this end would be to blacklist the 4K modes in the video BIOS, forcing it to output 1080p60 max, but I'm not sure I can do that, nor do I have any way of testing it.

thanks for the kind words on the wiki. It's far from where I'd like, but we're dealing with a lot of highly technical firmware-related issues, and distilling that down into something functional for users with a wide range of technical knowledge is a tough job indeed. I'd love to have more input from the community, but that's been hard to come by.

My first time posting here and was wondering if anyone could help. I have an Asus Chromebox and earlier in the year was experimenting with loading Ubuntu and Windows on it which I was successful in doing. Now I would like to turn ON the OS verification so that the device boots in Chrome OS without pausing. Currently when I press the space bar it does nothing but beep and eventually shows the bios version to the top left, then shows the boot screen, then goes blank. I think I have the original firmware backed up, I see the files on my share but not sure how to load it. I don't mind manually nuking the device back to its original state. Does any one have alternate steps to Turn OS verification back on or steps for restoring the original firmware? Thanks in advance.

when you use the 'Set Boot Options' feature of the script, it sets a firmware flag to lock developer mode on, to prevent accidentally disabling it via the space bar. If you're looking to have it boot ChromeOS immediately, you can either set the boot delay to 1s, or set the boot options back to default (which removes the dev mode lock) and then re-enable verified boot mode. Either way, run the script and set the boot options as desired.

[turbobuickguy]

Matt, just want to say thanks for all the hard work you've done with the chromeboxes! Whenever I have run into an issue, its either covered in the WIKI, or already been addressed by you here in this thread. My system works great, and it is due to your willingness to help all of us out. Thanks!