[jjslegacy]

Used this one from today:
LibreELEC-Generic.x86_64-8.0-Milhouse-20160419210537-#0419-gfee76be.tar
from:
http://milhouse.libreelec.tv/builds/master/Generic/

Guessing this is the issue:
Theater:~ # /tmp/flashrom -r bios.bin
flashrom v0.9.4 chromium.googlesource.com/chromiumos/third_party/flashrom : 51822fd : Apr 12 2016 22:22:28 UTC on Linux 4.4.7 (x86_64), built with libpci 3.3.1, GCC 5.3.1 20160406 (Red Hat 5.3.1-6), little endian
Cannot stat /run/lockCould not acquire lock.

I fixed it temporarily by creating the directory /run/lock that worked and allowed it to finish

[rvf263]

Thanks christoofar, appreciate it. I'll try a wired one and see if it works.

Thanks for the link Matt, I really appreciate it.

I'm hoping to get this up and running tomorrow morning after work!

[Matt Devo]

Used this one from today:
LibreELEC-Generic.x86_64-8.0-Milhouse-20160419210537-#0419-gfee76be.tar
from:
http://milhouse.libreelec.tv/builds/master/Generic/

Guessing this is the issue:
Theater:~ # /tmp/flashrom -r bios.bin
flashrom v0.9.4 chromium.googlesource.com/chromiumos/third_party/flashrom : 51822fd : Apr 12 2016 22:22:28 UTC on Linux 4.4.7 (x86_64), built with libpci 3.3.1, GCC 5.3.1 20160406 (Red Hat 5.3.1-6), little endian
Cannot stat /run/lockCould not acquire lock.

I fixed it temporarily by creating the directory /run/lock that worked and allowed it to finish

ok, I'll check that out and see what's up. I did update to a newer build of flashrom so maybe that's the issue

[Matt Devo]

Used this one from today:
LibreELEC-Generic.x86_64-8.0-Milhouse-20160419210537-#0419-gfee76be.tar
from:
http://milhouse.libreelec.tv/builds/master/Generic/

Guessing this is the issue:
Theater:~ # /tmp/flashrom -r bios.bin
flashrom v0.9.4 chromium.googlesource.com/chromiumos/third_party/flashrom : 51822fd : Apr 12 2016 22:22:28 UTC on Linux 4.4.7 (x86_64), built with libpci 3.3.1, GCC 5.3.1 20160406 (Red Hat 5.3.1-6), little endian
Cannot stat /run/lockCould not acquire lock.

I fixed it temporarily by creating the directory /run/lock that worked and allowed it to finish

ok, I'll check that out and see what's up. I did update to a newer build of flashrom so maybe that's the issue

flashrom recompiled and updated, should be good to go now.

[jjslegacy]

Thanks Matt!

[DJChrome]

Hello,

I'm trying to set up a Samsung stumpy with this script on standalone, but it keeps telling me that my write protect is turned on. I have a wire jumper on the correct spot, according to the google+ group thread on the subject (2nd jumper from top, right above the chip), have unplugged and replugged in the coin cell battery, and have checked the status with the crossystem command (it shows 0, meaning disabled.)

I am in developer mode. Am I missing something?

[Matt Devo]

Hello,

I'm trying to set up a Samsung stumpy with this script on standalone, but it keeps telling me that my write protect is turned on. I have a wire jumper on the correct spot, according to the google+ group thread on the subject (2nd jumper from top, right above the chip), have unplugged and replugged in the coin cell battery, and have checked the status with the crossystem command (it shows 0, meaning disabled.)

I am in developer mode. Am I missing something?

there's a few write-protect related variables reported by crossystem. what is crossystem reporting for both wpsw_cur and wpsw_boot? Are both 0?

[DJChrome]

wpsw_boot: 0 (Position at boot) and wpsw_cur: (error) (Current position)

It's running Google_Stumpy.2.102.0 if that makes any difference.

[mjuti]

flashrom recompiled and updated, should be good to go now.

Hi Matt,

I have been using your scripts on my Chromebox ( Panther ) since the 1st day I received it from Amazon. I am running Archlinux, nothing else ( standalone ) and on your April 3 coreboot firmware. Now I have this problem:

" Failure reading current firmware; cannot proceed "

Running the script directly gives:

"root@arch /tmp # /tmp/flashrom -r bios.bin
flashrom v0.9.4 chromium.googlesource.com/chromiumos/third_party/flashrom : 51822fd : Apr 12 2016 22:22:28 UTC on Linux 4.5.1-1-ARCH (x86_64), built with libpci 3.3.1, GCC 5.2.1 20151010, little endian
Error accessing high tables, 0x100000 bytes at 0x7f708000
/dev/mem mmap failed: Resource temporarily unavailable
Failed getting access to coreboot high tables.
Error accessing ICH RCRB, 0x4000 bytes at 0xfed1c000
/dev/mem mmap failed: Operation not permitted

As you can see I am root and can confirm /dev/mem does exist ( size 0 )

Thanks for your support

[Matt Devo]

wpsw_boot: 0 (Position at boot) and wpsw_cur: (error) (Current position)

It's running Google_Stumpy.2.102.0 if that makes any difference.

I just pushed an update that should work around stumpy reporting wpsw_curr = error

Hi Matt,

I have been using your scripts on my Chromebox ( Panther ) since the 1st day I received it from Amazon. I am running Archlinux, nothing else ( standalone ) and on your April 3 coreboot firmware. Now I have this problem:

" Failure reading current firmware; cannot proceed "

Running the script directly gives:

"root@arch /tmp # /tmp/flashrom -r bios.bin
flashrom v0.9.4 chromium.googlesource.com/chromiumos/third_party/flashrom : 51822fd : Apr 12 2016 22:22:28 UTC on Linux 4.5.1-1-ARCH (x86_64), built with libpci 3.3.1, GCC 5.2.1 20151010, little endian
Error accessing high tables, 0x100000 bytes at 0x7f708000
/dev/mem mmap failed: Resource temporarily unavailable
Failed getting access to coreboot high tables.
Error accessing ICH RCRB, 0x4000 bytes at 0xfed1c000
/dev/mem mmap failed: Operation not permitted

As you can see I am root and can confirm /dev/mem does exist ( size 0 )

Thanks for your support

I'm guessing either a kernel config or change in 4.5 is breaking something, hard to say as I'm not familiar with the inner workings of flashrom. I'd suggest just booting a Ubuntu (or GalliumOS) live USB and running the script from there as a workaround until I have a chance to look into it.

[mjuti]

Thanks for your prompt response Matt, good guess I believe, I 'll do what you suggested and report back

[DJChrome]

wpsw_boot: 0 (Position at boot) and wpsw_cur: (error) (Current position)

It's running Google_Stumpy.2.102.0 if that makes any difference.

I just pushed an update that should work around stumpy reporting wpsw_curr = error

It functioned perfectly, I've got standalone boot up and going now.

Thank you Matt!

[Boulder]

I'm trying to install the standalone coreboot firmware to an HP Chromebox to install Win10 on it, but I'm having two issues:

1) When trying to backup the original firmware, I get the option "0+1" for my SD card and I cannot get the backup option working because the script expects an integer

2) I get a checksum failed error when the coreboot firmware is downloaded

[Matt Devo]

I'm trying to install the standalone coreboot firmware to an HP Chromebox to install Win10 on it, but I'm having two issues:

1) When trying to backup the original firmware, I get the option "0+1" for my SD card and I cannot get the backup option working because the script expects an integer

2) I get a checksum failed error when the coreboot firmware is downloaded

1) not sure how that happened, but fixed

2) must have been a bad download, so the error checking did its job

[Boulder]

Thanks, I'll test the process again tomorrow. I did try repeating the update procedure multiple times, but maybe the backup error caused something to go wrong.