2014-10-16, 19:53
(2014-10-16, 19:51)mcord Wrote: So there was an issue or likely me not entering things correctly?
I didn't change anything, just verified it. Be sure to use a capital 'o' in the curl command
(2014-10-16, 19:51)mcord Wrote: So there was an issue or likely me not entering things correctly?
(2014-10-16, 09:06)Matt Devo Wrote: major script update:
- updated to support running under any Linux OS
- added separate firmware update script for bash-less OS, eg OpenELEC
- switched to using OpenELEC disc image for standalone media creation
- reduced unnecessary script verbosity
- updated coreboot firmware to upstream/master HEAD; includes numerous ACPI fixes
- updated SeaBIOS payload to upstream/master HEAD
- updated to support new Acer/Dell Haswell-based ChromeBox models
eventually the separate firmware update script will become a fully-automated XBMC add-on, if I ever get the time
(2014-10-16, 16:48)Matt Devo Wrote:(2014-10-16, 09:46)Sunflux Wrote: Hmm, can't do a standalone BIOS update:
looks like it didn't correctly download the 'latest version' file from dropbox, I've thrown a check in for that. Try again?
I updated ChromeOS from the Stable channel to the Beta channel Version 38.0.2125.101 beta (64-bit) a few weeks ago. Everything has been working fine.
Today I tried to do a standalone BIOS update but unfortunately the update is failing.
curl -L -O http://goo.gl/HSZer4
sudo bash HSZer4
When I run HSZer4 I see the following errors.
Problem1: Exists on both OpenELEC and ChromeOS
----------------------------------------------
dmesg | grep DMI now returns
DMI: GOOGLE Panther, BIOS Google_Panther.4920.24.25 05/12/2014 [ChromeoS]
DMI: GOOGLE Panther, BIOS 05/12/2014 [OpenELEC]
^^^^^^^
HSZer4 line 48 is looking for "DMI: Google Panther". I was able to correct this by making the grep case insensitive (changing-m1 to -im1). The HSZer4 script continues and says that this script is going to install a newer firmware version.
Problem2: ChromeOS specific running Beta Channel only
------------------------------------------------------
Next, I get the error "Failure reading current firmware; cannot proceed"
This failure is occurring since /tmp is mounted with he noexec option which prevents executables running from /tmp
I fixed this by making the following changes.
tmpdir=/usr/local/tmp
mkdir -p $tmpdir
flashromcmd="$tmpdir/flashrom"
cbfstoolcmd="$tmpdir/cbfstool"
...
cd $tmpdir (rather than cd /tmp)
Problem3: Exists on both OpenELEC and ChromeOS
---------------------------------------------
$tmdir/cbfstool bios.bin extract vpd.bin -f vpd.bin
E: File not found: vpd.bin
Failure extracting MAC address from current firmware
Not sure how to fix this one.
I did go back and install the stable version of ChromeOS. Problem 1 and Problem 3 remained. The Problem 2 changes are no longer required however the changes made are still compatible.
I am assuming that installing the Beta channel updated the firmware although I have no way to confirm this. If this version of firmware is what will be coming in a future update then can support be added for this firmware version? If not then how do I recover?
Thanks,
Geoff..
Quote:This script is only intended to update a ChromeBox already running my custom coreboot firmware, and will not work under ChromeOS/ChromiumOS.
(2014-10-17, 07:09)Sunflux Wrote: It works fine now if I do it quickly on and off, but it was a 4+ hour period of time in sleep that triggered the issue. The power button still worked, and after that I could resume/suspend by remote, but that's when I noticed that I wasn't getting any audio (despite the USB stick's LEDs indicating it was active), and videos had these lengthy pauses on playback/stop (likely due to the selected audio device being non-responsive). Then I rebooted, and everything resumed working as it should.
I'll wait to see if the issue happens again before doing anything further.
Nice to hear that you keep backups - because the previous release was working well, but I was wooed by the promise of ACPI fixes. :-)
Quote:Jimmulus Wrote:
Hi Matt,
I am a bit ashamed to say i did a factory reset with openelec running.
When i startup i get this message, discussed earlier
(SeaBIOS (version -20140706_180417-build120-m2)
Press ESC for boot menu.
Booting from Hard Disk...
early console in decompress_kernel
KASLR using RDRAND...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
The problem i have is that keyboards are no longer working (tried 2, wired and wireless), So i can't get into developer mode.
Is there any way to restore the chromebox?
Thanks in advance.
your SeaBIOS build string indicates you are running the stock version, which does not allow for any keyboard input due to broken USB support. You need to press [CTRL-D] *before* the black SeaBIOS screen displays in order to run ChromeOS / re-run the script.
Quote:(SeaBIOS (version -20140706_180417-build120-m2)
Press ESC for boot menu.
Booting from Hard Disk...
early console in decompress_kernel
KASLR using RDRAND...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
(2014-10-18, 17:46)warp123 Wrote: but i can't press ctrl-D , it's never work, do you have a other solution ?
Also i have try to do a framework reset but it's does nothing.always this screen.
Quote:(SeaBIOS (version -20140706_180417-build120-m2)
Press ESC for boot menu.
Booting from Hard Disk...
early console in decompress_kernel
KASLR using RDRAND...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
Reading current firmware
Failure extracting MAC address from current firmware.