oe-chipsec.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Vorname Nachname <ldevlzero@gmail.com>
To: chipsec@lists.01.org
Subject: chipsec-1.5.0 in EFI Shell
Date: Thu, 28 May 2020 16:36:34 +0200	[thread overview]
Message-ID: <CAPwg83g_w6cEjXrE+RfDm8QofBWMjoAG=e11Q9DJLH8mWRGD7w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

Hello,

I tried to run chipsec-1.5.0 in EFI Shell without operating system but
unfortunately it doesn't run in the EFI Shell. I ran these commands:

Shell> fs0:
FS0:\> python -^# chipsec_main.py -m debugenabled

This results in a traceback with the last file chipsec/defines.py called
function get_version().

OSError: [Errno 22] Invalud argument: 'FS0:FS0:chipsec'

After that I compiled python 2.7.2 and python 2.7.10 from edk2 package
version edk2-stable201903. This is the last package version with pyhton
inside. With this version of pyhton I received another error message with
the last line:

ImportError: No module named expat; use SimpleXMLTreeBuilder instead.

What is the best way to start the latest version of chipsec in the EFI
Shell? What version of EFI Shell and pyhton is required?

best wishes
Philipp

[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 917 bytes --]

             reply	other threads:[~2020-05-28 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 14:36 Vorname Nachname [this message]
2020-05-28 21:54 ` chipsec-1.5.0 in EFI Shell Blibbet
2020-05-28 22:24   ` Holtsclaw, Brent
     [not found] <CAPwg83iAx0xpQ3kUJ1ELfaEbkaof6yuOc4uhVMhtXjQkEVrNoA@mail.gmail.com>
2020-05-29 15:16 ` Vorname Nachname
2020-06-05  9:14   ` Vorname Nachname
2020-06-05 18:33     ` Holtsclaw, Brent
2020-06-08 14:00       ` Vorname Nachname
2020-12-29 17:59     ` Holtsclaw, Brent
2021-01-04 15:53       ` Abu Cishubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPwg83g_w6cEjXrE+RfDm8QofBWMjoAG=e11Q9DJLH8mWRGD7w@mail.gmail.com' \
    --to=ldevlzero@gmail.com \
    --cc=chipsec@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).