<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EFI Shell in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952165#M2310</link>
    <description>I'm not in a spot where I can look at the EFI shell to verify the following, but here is what Intel claims for EFI I/O redirection syntax:&lt;BR /&gt;&lt;BR /&gt;cmd &amp;gt; unicode.log&lt;BR /&gt;cmd &amp;gt;a ascii.log&lt;BR /&gt;cmd 1&amp;gt; unitcode.log&lt;BR /&gt;cmd 1&amp;gt;a ascii.log&lt;BR /&gt;cmd 2&amp;gt; unicode_stder.log&lt;BR /&gt;cmd 2&amp;gt;a ascii_stderr.log&lt;BR /&gt;cmd &amp;gt;&amp;gt; unicode_append.log&lt;BR /&gt;cmd &amp;gt;&amp;gt;a ascii_append.log&lt;BR /&gt;cmd 1&amp;gt;&amp;gt; unicode_append.log&lt;BR /&gt;cmd 1&amp;gt;&amp;gt;a ascii_append.log&lt;BR /&gt;&lt;BR /&gt;Try a few commands other than errdump, on the off chance that errdump isn't playing by the rules.  (It looks like it might not be, based on the error message.)&lt;BR /&gt;&lt;BR /&gt;Most folks tend to capture the error log using a serial-line capture; a capture from the terminal emulator.  Or from the error log, if that's available and loading up messages from the EFI level.  (But if you're looking at the error log, you also might not be booting.)&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 27 Feb 2007 11:53:16 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-02-27T11:53:16Z</dc:date>
    <item>
      <title>EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952162#M2307</link>
      <description>Red Hat Enterprise Linux 3&lt;BR /&gt;&lt;BR /&gt;In simple prompt I can send the output of a command to a text file (Example: ls -l &amp;gt; output.txt)&lt;BR /&gt;&lt;BR /&gt;How can I do the same in EFI Shell?</description>
      <pubDate>Tue, 27 Feb 2007 11:03:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952162#M2307</guid>
      <dc:creator>Tonatiuh</dc:creator>
      <dc:date>2007-02-27T11:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952163#M2308</link>
      <description>I have tried with following errors.&lt;BR /&gt;&lt;BR /&gt;Shell&amp;gt; errdump mca &amp;gt; errdump_mca.log&lt;BR /&gt;Could not open output file errdump_mca.log&lt;BR /&gt;Exit status code: Invalid Parameter</description>
      <pubDate>Tue, 27 Feb 2007 11:13:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952163#M2308</guid>
      <dc:creator>Tonatiuh</dc:creator>
      <dc:date>2007-02-27T11:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952164#M2309</link>
      <description>You must change to a disk.&lt;BR /&gt;&lt;BR /&gt;You are still in the firmware&lt;BR /&gt;Shell&amp;gt;&lt;BR /&gt;&lt;BR /&gt;try&lt;BR /&gt;&lt;BR /&gt;Shell&amp;gt; fs0:&lt;BR /&gt;&lt;BR /&gt;(or another existing disk)&lt;BR /&gt;&lt;BR /&gt;fs0&amp;gt; your_command &amp;gt; output file</description>
      <pubDate>Tue, 27 Feb 2007 11:50:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952164#M2309</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2007-02-27T11:50:12Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952165#M2310</link>
      <description>I'm not in a spot where I can look at the EFI shell to verify the following, but here is what Intel claims for EFI I/O redirection syntax:&lt;BR /&gt;&lt;BR /&gt;cmd &amp;gt; unicode.log&lt;BR /&gt;cmd &amp;gt;a ascii.log&lt;BR /&gt;cmd 1&amp;gt; unitcode.log&lt;BR /&gt;cmd 1&amp;gt;a ascii.log&lt;BR /&gt;cmd 2&amp;gt; unicode_stder.log&lt;BR /&gt;cmd 2&amp;gt;a ascii_stderr.log&lt;BR /&gt;cmd &amp;gt;&amp;gt; unicode_append.log&lt;BR /&gt;cmd &amp;gt;&amp;gt;a ascii_append.log&lt;BR /&gt;cmd 1&amp;gt;&amp;gt; unicode_append.log&lt;BR /&gt;cmd 1&amp;gt;&amp;gt;a ascii_append.log&lt;BR /&gt;&lt;BR /&gt;Try a few commands other than errdump, on the off chance that errdump isn't playing by the rules.  (It looks like it might not be, based on the error message.)&lt;BR /&gt;&lt;BR /&gt;Most folks tend to capture the error log using a serial-line capture; a capture from the terminal emulator.  Or from the error log, if that's available and loading up messages from the EFI level.  (But if you're looking at the error log, you also might not be booting.)&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Feb 2007 11:53:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/3952165#M2310</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-02-27T11:53:16Z</dc:date>
    </item>
  </channel>
</rss>

