run it under strace. Though, I'm not at all surprised to see that a python tool is fragile w.r.t. where it's run.
On Sun, Feb 12, 2017 at 5:41 AM Zoran Stojsavljevic < zoran.stojsavljevic@gmail.com> wrote:
Why I am not surprised??? ;-)
BCT tool link (I downloaded it): *Download the from the Binary Configuration Tool from GitHub below*:
https://github.com/IntelFsp/BCT I did exactly what documentation for BCT tool says (reading it with okular, using my UEFI dual boot HDD on bare HW: WIN10 64 PRO and Fedora 25 x86_64):
*2.2 Linux Install*
*1. Copy the BCT tar.gz file to a local directory.*
- a. For 32-bit versions, choose bct-<current version>.i686.fc22.tar.gz*
- b. For 64-bit versions, choose bct-<current
version>.x86_64.fc22.tar.gz* *2. From the console terminal, navigate to the folder that contains the BCT tar.gz file and issue the following command:*
- a. For 32-bit versions, >tar -xvf bct-3.0.2-1-i686.fc22.tar.gz*
- b. For 64-bit versions, >tar -xvf bct-3.0.2-1-x86_64.fc22.tar.gz*
*3. The installation extracts a binary executable, bct, and three folders: help, xrc, and documentation inside a folder named bct.* *4. Run the BCT program by issuing:*
Let me see what I am using:
[user@localhost bct]$ uname -r *4.9.8-201.fc25.x86_64* [user@localhost bct]$
Fedora 22? Even Fedora 23 is already obsolete... My God! :-((
[image: Inline image 1]
Anybody else experience this problem? 😬
Thank you, Zoran
-- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
