(2016-09-15, 18:16)RayTrace77 Wrote: @tredman,

Can you SSH into your box while it's on and use xrandr to query the current display status ?

(2016-09-16, 15:33)RayTrace77 Wrote: *Excuse the formatting of the text, I typed it in Notepad first.

So the scenario was this:

1.) Chromebox in a dual boot state with stock firmware
2.) Chromebox was set to boot LibreELEC immediatley, no 30s wait
3.) Chromebox had been restored using Googles Recovery Utility(it said it was successful) <------that is where the problems started

Quote:4.) ESC key's did not work on any keyboard to get to boot selection menu
6.) When it tried to boot the partition where LibreELEC was installed it just went to a blank screen, no keys worked, nothing.
7.) I didn't have another 1.8" SSD to try and use.

Quote:5.) ChromeOS did not boot as it says the owner has disabled ChromeoS boot in developer mode"

Quote:1.) The Ctrl+U took a lot of searching to find, now I've searched specifially for it, I can find stuff on it, but when I was researching the issues I was having, I could hardly find anything, only 1 post in a forum that mentioned Ctrl+U.

Quote:2.) Before all of this, I could not find a single post or thread or anything about how to actually switch from a dual boot, to a single boot, I'm talking about a small guide, I'm sure that would have saved me this issue, I think the way you would do it now is, just boot of a USB Chromium/Ubuntu, go to a R/W'able location and download/run Matt's E-Z Script which will allow you to flash the coreboot firmware.

Quote:3.) In a few places it's mentioned that before you restore to factory "so be sure to reset them back to the 'ChromeOS + 30s default'", but I could not find anything that actually told me how to do it, on the same page further down it does mentioned that "The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script" which I didn't see so that was my fault, at the same time I didn't know how to boot USB so I would have had to figure that out first.

Quote:6.) At the time I could not see anywhere that said if the coreboot firmware flash also updates SeaBIOS, which I did eventually find on the original kodi.wiki Chromebox page "http://kodi.wiki/view/chromebox", the answer is yes.

Quote:7.) I'm starting to see that the information I needed is out there but scattered in different locations, the Chromebox guide on kodi.wiki is comprehensive but I think it could do with some touch ups when it mentiones something you need/can do, for instance, under "2.3 Perform a Factory Reset", it says "so be sure to reset them back to the 'ChromeOS + 30s default'", that could do with a caption or something next to it that says something like "See 3.2 Dual Boot OS Selection for how to do this"

(2016-09-16, 18:16)tjfluharty Wrote: Hey Mr. Chromebox,

I think I'm bricked. I'd be surprised if anyone can help me out of this one.

I bought the Lenovo Chromebox a couple weeks ago on sale. Yesterday I followed the directions in the OP to do a standalone setup. I removed the write-protect screw, put the Chromebox into developer mode, and kicked off the Kodi E-Z Setup script. I selected the custom coreboot firmware but neglected to do the ChromeOS backup. I didn't have a flash drive with me at the time.

It said the installation was successful and then I chose to shutdown the device. When I started it up, it no longer output video. I tried about three different monitors and a couple TVs with a handful of various HDMI and DisplayPort cables. No luck. When you press the power button the device immediately shuts off. It doesn't seem to be getting very far in the boot process.

Please advise. Thank you for the help.

(2016-09-16, 18:34)RayTrace77 Wrote: @tjfluharty

That sounds like a bad or wrong firmware flash, if when you press the power button it immediatly powers off then I think the only case a backup of the original firmware would be helpful is if you can reflash the rom chip where the firmware is stored, but that's a lot of work, since it says it was successful, I think it flashed the wrong firmware, I could be wrong.

(2016-09-17, 02:34)RayTrace77 Wrote: Hey Matt,

Ok so I never said I couldn't press Ctrl+D, anything related to booting into ChromeOS was not a option for me, whenever I pressed Ctrl+D at the developer screen it did try to boot ChromeOS but then it said the owner had disabled boot in dev mode, the article below talks about the function, the person I bought it from should have un-enrolled it or removed it from whatever organization it got it's policy's from, way too long ago to do anything about now, I tried to find a picture of the screen on Google but couldn't.
https://bugs.chromium.org/p/chromium/issues/detail?id=412587

Quote:Not sure about the lucky part of the USB being enabled, are you saying that there's a number of Chrome devices out there where Ctrl+U is not enabled in the stock firmware ?, even if it's switched to dev mode ? or maybe it's a dev mode specific flag ?, because if the stock Legacy Boot does not have funtioning USB ports and stock firmware dev mode has no function to tell it to boot USB then it's kind of useless, even in my case, the coreboot firmware hands off to the Legacy Boot, so even though Ctrl+U flag was on, what initiated the boot off the USB stick if the Legacy Boot had non functioning USB ports ?, did coreboot skip the handover to Legacy Boot or something ?, just trying to understand what happened there because what you said has confused me quite a bit.

Quote:For quote 6 about not seeing anywhere that said coreboot firmware flash updates SeaBIOS, a small disclaimer or notice under the heading of "Install / Update: coreboot Firmware (standalone)" on the 1st page of this thread I think would make a world of difference, something like "NOTE: Flashing/updating the coreboot firmware updates SeaBIOS at the same time"

Quote:Regarding the bad firmware flash, is there a verification of any kind performed after it's flashed the coreboot firmware to ensure the data was written correctly ?, if not, then yeah a bad flash could be possible, he said that the device powers off immediately, I would have though a failure of the VBIOS which hangs the boot process would just hang, not cause it to actually power itself off.

Quote:PS: The stuff you've done is insane(the good kind), I don't want you to think I'm trying to knock you or have a go or anything.

(2016-09-17, 08:36)bbsc Wrote: I like the present situation much more, of course. But if the temperature rises for some reason for a short time above 67 Celsius and then falls back, the FAN will remain at MEDIUM speed.
55 degrees seems to be too low for Chromebox in active state.

Thank you.

(2016-09-17, 10:44)Matt Devo Wrote: ...there's a fairly high likelihood of the temp quickly coming back up to 67, which would end up causing a constant oscillation between low and medium speeds.

(2016-09-17, 11:58)bbsc Wrote:

(2016-09-17, 10:44)Matt Devo Wrote: ...there's a fairly high likelihood of the temp quickly coming back up to 67, which would end up causing a constant oscillation between low and medium speeds.

Ok, thanks for the answer.
I suspected that this reason forced you to set those thresholds,
Definitely it's not my case because MEDIUM fan speed keeps CPU temperature near 60-62 in active state.
So, taking into consideration your conclusions and huge experience, I have to disassemble the box and have a look what's there with cooling system and thermal grease.

One question more, if you don't mind.

I've lost my original MAC for some reason and now the box runs with "standard" MAC. I'd like to get it back.
Is it enough to find "standard" MAC in the binary coreboot....rom file, replace with my original MAC and flash the binary? (I mean the file in the /tmp directory after script run)

(2016-09-17, 14:26)vispinet Wrote: Will this script work on a Samsung Chromebox i5 2450M?

(2016-09-17, 17:11)Karnis Wrote: Hi Matt:
Recently upgraded to a 4K HDTV. I run the Chromebox GUI @ 1080p 60Hz but it defaults to 120Hz during playback because that is the highest refresh rate Kodi detects and all my media is common to that refresh rate. I've tried to use 120Hz but I get stuttering. So I'd like to "cap" 1080p @ 60Hz. As I remember I can SSH into the Chromebox and look at/edit the mode line & remove 120Hz...but I don't remember the exact syntax to do it. Would you mind gently nudging me in that direction? Much appreciated!

(2016-09-17, 20:34)RayTrace77 Wrote: Hey Matt,

So there random turn on issue is still present, I tried to take a closer look at the dmesg logs and I think it is the BD remote but can't tell for sure, even then it powers on at literally random times so it's not consistent, would you be able to tell me caused the last power on/resume in the logs below ?, if it is the BD remote then I don't really know why the remote is randomly sending a button press or signal.

https://dropfile.to/hGXYhzb

PS: Thanks for your site link, a lot of info on their, should probably add that link to your signature