Red Hat Bugzilla – Bug 604936
amttool powerup bios fails on iAMT5 host
Last modified: 2011-06-27 14:25:27 EDT
Description of problem: The amttool utility has an option to select BIOS Serial-Over-LAN redirection during powerup. It works targeting an older Intel AMT system but fails on a newer one. It prints "soap failure". Version-Release number of selected component (if applicable): How reproducible: Always with iAMT5 system. Steps to Reproduce: 1. Have AMT provisioned in SMB mode on an iAMT5 host 2. run "amttool hostname powerup bios" from Fedora system on the LAN 3. enter "y" to allow powerup Actual results: Tool yields soap failure and target machine remains off. Expected results: Target machine powers up and shows BIOS in SOL session accessible via amtterm. Additional info: Info from newer target where amttool fails: % amttool target ### AMT info on machine 'target' ### AMT version: 5.2.20 Hostname: target. Powerstate: S5 (soft-off) Remote Control Capabilities: IanaOemNumber 157 OemDefinedCapabilities IDER SOL BiosSetup SpecialCommandsSupported PXE-boot HD-boot cd-boot SystemCapabilitiesSupported powercycle powerdown powerup reset SystemFirmwareCapabilities f820 Info from older target that succeeds: % amttool localhost ### AMT info on machine 'target' ### AMT version: 3.2.1 Hostname: target Powerstate: S0 Remote Control Capabilities: IanaOemNumber 157 OemDefinedCapabilities IDER SOL BiosReflash BiosSetup SpecialCommandsSupported PXE-boot HD-boot SystemCapabilitiesSupported powercycle powerdown powerup reset SystemFirmwareCapabilities f023 Debug output: % amttool target powerup bios host target., powerup [y/N] ? y execute: powerup -- <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <soap:Body> <RemoteControl xmlns="http://schemas.intel.com/platform/client/RemoteControl/2004/01"> <Command>17</Command> <IanaOemNumber>343</IanaOemNumber> <OEMparameters>1</OEMparameters> <SpecialCommand>193</SpecialCommand> </RemoteControl> </soap:Body> </soap:Envelope> -- result: soap failure
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.