i just updated the firmware on my chromebox for the slightly modified fan thresholds. i'm now experiencing abnormally long boot times to the point i had actually thought i managed to do something incorrectly.
i'm running openelec 5.0.8 on an asus chromebox. i used the HSZer4 script to update to coreboot-seabios-hsw_chromebox-20150604-mattdevo.rom with no selected for both headless and usb boot. after updating i shut down the box and powered it back on. i could hear the fan spin up slightly however my tv receives no signal. after leaving it sit for a few minutes the tv gets a signal and then the system powers up and boots normally. i decided to time the whole thing and from hitting reboot in openelec to finally restarting it takes 5m48s. thankfully i almost never shutdown or suspend the system so this isn't a huge issue. but i'd like to resolve it if possible.
in the course of putting this post together i've stumbled upon a larger problem and my guess is they are somehow related. my wired ethernet connection is no longer functioning. for the time being i have switched to wireless. my chromebox was originally flashed when the script didn't extract the mac address. when upgrading the firmware there was the obligatory "Failure extracting MAC address from current firmware; default will be used" line. i had successfully updated between the initial flash and today's flash so i wouldn't have expected any issue.
please let me know how i can go about getting the proper logs to help deduce the issue. if it's as simple as re-running the update script i can try that as well. i have my original firmware backed up so if it's possible to insert the mac from that somehow i wouldn't mind being able to do that at some point. i'm wondering if my tv (panasonic vt50) is incapable of displaying the bios screen which according to the wiki is 1024x768@60hz. the closest resolution kodi shows me is 1280x720p. if need be i can run out and pick up a displayport cable to further test on my monitor. unfortunately dell for some reason didn't see including an hdmi port as a necessary feature.
Okay thank you for that Devo.
So I started over. It says Chrome/OpenElec have installed properly. I can get into Chrome no problem. When I Ctrl-L I get an error:
KERNEL failed: No such file or directory.
Any direction or suggestions?
NOTE: I cannot see the numbers in the bootup menu and was wondering when you are in the script format is there a way to select your screen size? Otherwise I will just use a monitor while setting up Kodi and the like.
(2015-06-09, 19:31)furii Wrote: [ -> ]i just updated the firmware on my chromebox for the slightly modified fan thresholds. i'm now experiencing abnormally long boot times to the point i had actually thought i managed to do something incorrectly.
i'm running openelec 5.0.8 on an asus chromebox. i used the HSZer4 script to update to coreboot-seabios-hsw_chromebox-20150604-mattdevo.rom with no selected for both headless and usb boot. after updating i shut down the box and powered it back on. i could hear the fan spin up slightly however my tv receives no signal. after leaving it sit for a few minutes the tv gets a signal and then the system powers up and boots normally. i decided to time the whole thing and from hitting reboot in openelec to finally restarting it takes 5m48s. thankfully i almost never shutdown or suspend the system so this isn't a huge issue. but i'd like to resolve it if possible.
in the course of putting this post together i've stumbled upon a larger problem and my guess is they are somehow related. my wired ethernet connection is no longer functioning. for the time being i have switched to wireless. my chromebox was originally flashed when the script didn't extract the mac address. when upgrading the firmware there was the obligatory "Failure extracting MAC address from current firmware; default will be used" line. i had successfully updated between the initial flash and today's flash so i wouldn't have expected any issue.
please let me know how i can go about getting the proper logs to help deduce the issue. if it's as simple as re-running the update script i can try that as well. i have my original firmware backed up so if it's possible to insert the mac from that somehow i wouldn't mind being able to do that at some point. i'm wondering if my tv (panasonic vt50) is incapable of displaying the bios screen which according to the wiki is 1024x768@60hz. the closest resolution kodi shows me is 1280x720p. if need be i can run out and pick up a displayport cable to further test on my monitor. unfortunately dell for some reason didn't see including an hdmi port as a necessary feature.
I'm at a loss to explain the issues you're experiencing. If you have the 'wait for network to start Kodi' option selected, and your wired connection wasn't working properly, then I can see it taking up to 90s to boot, but not 5 minutes. But there's also nothing in the updated firmware which would affect your ethernet connection, regardless if you're using the default MAC address or one extracted from the original firmware. If you want to rule that out, the easiest way is to boot any Linux live USB and re-run the EZ setup script, and it should give you the option to load the MAC from the stock backup on USB when updating the firmware.
My Panny GT50 has no issues displaying the BIOS boot screen so I doubt that's your issue.
If updating your firmware with the MAC from the stock firmware doesn't fix the issue, I'd backup your existing config (via the OE add-on) and do a fresh install of OE (or a hard reset) to rule out a software/config issue.
(2015-06-09, 19:39)wallympls Wrote: [ -> ]Okay thank you for that Devo.
So I started over. It says Chrome/OpenElec have installed properly. I can get into Chrome no problem. When I Ctrl-L I get an error:
KERNEL failed: No such file or directory.
Any direction or suggestions?
I'd re-run the dual boot setup (it will only redo the 2nd part) since it sounds like a file wasn't downloaded/copied correctly. Which version of OE did you install, stable or beta?
Hi Devo.
Actually I am one step ahead of you and did re-run the dual boot setup. I am using the stable OE.
(2015-06-09, 20:02)wallympls Wrote: [ -> ]Hi Devo.
Actually I am one step ahead of you and did re-run the dual boot setup. I am using the stable OE.
what size partition did you set?
(2015-06-09, 09:00)Matt Devo Wrote: [ -> ] (2015-06-09, 08:19)Digi8 Wrote: [ -> ]Can't boot into Kodi........
I have a dual boot Chromebox running Kodi and Chrome OS. By default I'm apparently booting to ChromeOS with a 1 second delay. My CTRL+L keystroke seems to be doing nothing on boot, and ChromeOS keeps coming up. At the ChromeOS login screen I try the CTRL+ALT+F2 keystroke to go into a command prompt and nothing happens. I can log into Chrome OS fine, so the keyboard is working at that point. I've tried multiple keyboards with no luck. I used to be able to boot into either side just fine. I'm about to lose it here. Any help?
assume you've tried another keyboard?
Yes, I have tried 2 different keyboards, both of which worked before.
(2015-06-09, 20:14)Digi8 Wrote: [ -> ]Yes, I have tried 2 different keyboards, both of which worked before.
I'm going to guess you accidentally disabled developer mode, re-enable it and you should be able to boot OE again
(2015-06-09, 20:13)Matt Devo Wrote: [ -> ] (2015-06-09, 20:02)wallympls Wrote: [ -> ]Hi Devo.
Actually I am one step ahead of you and did re-run the dual boot setup. I am using the stable OE.
what size partition did you set?
I just reset my system and did the dual boot setup with OE stable (5.0.8) and a 6gb partition and had no issues. If there's an error at any point it should be reported on the screen - are you not seeing anything like that during the install?
(2015-06-09, 19:44)Matt Devo Wrote: [ -> ]I'm at a loss to explain the issues you're experiencing. If you have the 'wait for network to start Kodi' option selected, and your wired connection wasn't working properly, then I can see it taking up to 90s to boot, but not 5 minutes. But there's also nothing in the updated firmware which would affect your ethernet connection, regardless if you're using the default MAC address or one extracted from the original firmware. If you want to rule that out, the easiest way is to boot any Linux live USB and re-run the EZ setup script, and it should give you the option to load the MAC from the stock backup on USB when updating the firmware.
My Panny GT50 has no issues displaying the BIOS boot screen so I doubt that's your issue.
If updating your firmware with the MAC from the stock firmware doesn't fix the issue, I'd backup your existing config (via the OE add-on) and do a fresh install of OE (or a hard reset) to rule out a software/config issue.
must have been gremlins...
the bios screen did indeed come up properly for me but only after the 5+ minute wait time. created an ubuntu live stick and ran the ez script from that reinserting the mac address and all seems to be well. wired ethernet was also not working within ubuntu for what it's worth. really quite strange but back to normal.
cheers.
Hi
i have some Issue with the actually CoreBootFirmware. I used a Asus Chromebox with i3 have 8GB Ram and a 128Gb Plextor SSD.
Put the Machine in Developer Mode. Boot again, run the EZ Script fine
backup my Stock Firmware to USB. " Get a Error" Your current Firmware does not contain data for the device mac Address" Skip this. run to download and overwrite. now install the CoreBoot Firmware.
Succesfull. After reboot my LCD Screen is black and flashing. "No Signal" After 5 Minutes of waiting i see for a Short time the SeaBios. Keyboad wont work in the period of Time.
What's the Problem to load the SeaBios / Where is the CoreBios? with the 5 Minutes Power up? Then get a fresh Chromium Stick to load . The ChromeOS Screen boot up with the withe Screen OS verification off. left obove displays a Shell the original Chrome Panther Firmware? WTF? some as The Script has not rewritten the firmware?
The Problem. I will load Ubuntu standalone. But without reflash the Bios, Ubuntu Install USb Stick can't boot properly. Only 1Gb Ram avail in running System. with flashed Bios it reorganized all 8GB Ram in Ubuntu. But have the Hands of Issue's with long Bootperiode, No showing up Bootloader, Ethernet wont Work in Ubuntu.
What can i do? Im not a biggest Linux Crack.
Thanks at all
(2015-06-09, 21:19)Roor Wrote: [ -> ]Hi
i have some Issue with the actually CoreBootFirmware. I used a Asus Chromebox with i3 have 8GB Ram and a 128Gb Plextor SSD.
Put the Machine in Developer Mode. Boot again, run the EZ Script fine
backup my Stock Firmware to USB. " Get a Error" Your current Firmware does not contain data for the device mac Address" Skip this. run to download and overwrite. now install the CoreBoot Firmware.
Succesfull. After reboot my LCD Screen is black and flashing. "No Signal" After 5 Minutes of waiting i see for a Short time the SeaBios. Keyboad wont work in the period of Time.
What's the Problem to load the SeaBios / Where is the CoreBios? with the 5 Minutes Power up? Then get a fresh Chromium Stick to load . The ChromeOS Screen boot up with the withe Screen OS verification off. left obove displays a Shell the original Chrome Panther Firmware? WTF? some as The Script has not rewritten the firmware?
The Problem. I will load Ubuntu standalone. But without reflash the Bios, Ubuntu Install USb Stick can't boot properly. Only 1Gb Ram avail in running System. with flashed Bios it reorganized all 8GB Ram in Ubuntu. But have the Hands of Issue's with long Bootperiode, No showing up Bootloader, Ethernet wont Work in Ubuntu.
What can i do? Im not a biggest Linux Crack.
Thanks at all
I'm having a hard time following this honestly, but I'd suggest you re-flash the coreboot fimware via the EZ setup script (from Ubuntu is fine) and load the MAC address from the backed-up stock firmware file when prompted.
There's no reason for the "Your current Firmware does not contain data for the device mac Address" error when doing the initial flash from ChromeOS, since the stock firmware definitely does contain the device's unique MAC, unless perhaps you bought the box used and someone flashed it with the recovery firmware.
(2015-06-09, 20:19)Matt Devo Wrote: [ -> ] (2015-06-09, 20:14)Digi8 Wrote: [ -> ]Yes, I have tried 2 different keyboards, both of which worked before.
I'm going to guess you accidentally disabled developer mode, re-enable it and you should be able to boot OE again
How do I enable developer mode without wiping my data? Also, I haven't changed anything since the last time I was able to dual boot.
Hi
I have updated the firmware on my Asus Chromebox to 20150604 and have lost wired networking. The box takes 5 minutes + to get to the bios screen and boots with no wired network. Is there a way to downgrade or reinstall the firmware(if you think that will help)? I am running Openelec 5.95.1.
Cheers
(2015-06-10, 08:35)Digi8 Wrote: [ -> ]How do I enable developer mode without wiping my data? Also, I haven't changed anything since the last time I was able to dual boot.
you don't, but I'm only speculating that's the issue, and it's possible you or someone else hit [space] to exit developer mode without realizing it (which I've now tweaked the script to prevent). I suppose you could always log into ChromeOS, open a browser window, and hit [CTRL-T]. If you're still in developer mode, that should give you a limited terminal, if not, it won't, and you'll need to re-enable it.
(2015-06-10, 14:18)sd26 Wrote: [ -> ]Hi
I have updated the firmware on my Asus Chromebox to 20150604 and have lost wired networking. The box takes 5 minutes + to get to the bios screen and boots with no wired network. Is there a way to downgrade or reinstall the firmware(if you think that will help)? I am running Openelec 5.95.1.
Cheers
hmmm, since you're the 2nd person to report this, it would appear to not be a fluke, though I can't reproduce it myself on any of the boxes I have here. You can always boot a Linux live USB and re-run the script to re-flash the firmware and see if that helps. I'll look into the issue some more.