2015-06-09, 19:31
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 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.
