BIOS redirection through SoL failed

BIOS redirection through SoL failed

Dear Everyone!I've looked over whole threads(mainly thread titles) in this forum to find out my problem.CPU : Intel Core2 Quad CPU Q9400chipset: Q35AMT ver: DTK command toolSoL/IDE-R enabled at MEbxSMB modeI can control others like 'Process Monitor', 'Device Manager' and 'File Explorer' at Terminal Tool.Reboot via Remote Command and WebUI tool except BIOS redirection.For TCP port Redirection, I added remote port 5900 in the list.When I run "Remote Command/Remote Reboot or /Remote Reboot to BIOS Setup" on Terminal tool menu, Terminal shows simply as follow;---AMIBIOS(C)2010 American Megatrends, Inc. BIOS Date: 11/18/10 16:07:38 Ver: 08.00.16 BIOS Release: 64-0100-000002 Build: 018 CPU : Intel Core2 Quad CPU Q9400 @ 2.66GHz ---Not BIOS configuration menu at all! BIOS menu is displayed on remote monitor!Could you point where I should make sure?Thanks.

6 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi mipsan,
Thanks for your post. Can you tellus what brand of system you have? Also, if you could tell us if your BIOS is a graphical interface, that would help.Playing around with the terminal settings alsomight help resolve the issue. If you can give usthe aboveinformation we may be able to give you more specific help.


Thanks Judy,
System comes from Kontron( and it has not a graphical UI but old text-based AMI BIOS setup utility. (80 x 25 text screen)And Terminal tool has default configuration.- Terminal Emulation: both of them I tested.- Special Key Translation: intel/alternate/VT100+ tested-When I tested another terminal tool in System Defense Utility,I met an exception error: in result, SoL connect failed.For your help, I copy and paste error log,--------2011-05-13 AM 10:39:32System.Exception: IMRSDK.dll error : ManageabilityStack.AmtRedirectorWrapper.StartSerialRedirect() : ManageabilityStack.SerialLowDriver.Start() : ManageabilityStack.SerialHighDriver.Start() : ManageabilityControls.TerminalForm.StartSerial() : ManageabilityControls.TerminalForm.SystemStateChangedHandlerEx(AmtSystem computer) : ManageabilityControls.TerminalForm..ctor(AmtSystem computer, String title, Boolean simplified) : ManageabilityControls.TerminalForm.ShowRemotingForm(AmtSystem system, IWin32Window owner, Boolean simplified) : AMT_Info_Browser.MainForm.startTerminalButton_Click(Object sender, EventArgs e) : System.Windows.Forms.Control.OnClick(EventArgs e) : System.Windows.Forms.Button.OnClick(EventArgs e) : System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) : System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) : System.Windows.Forms.Control.WndProc(Message& m) : System.Windows.Forms.ButtonBase.WndProc(Message& m) : System.Windows.Forms.Button.WndProc(Message& m) : System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) : System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) : System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

By googling, I made a conclusion that I confound SoL of AMT with that of IPMI.SoL of IPMI can redirect BIOS and boot process to local monitor display.What I wanted to get in AMT is KVM features which is supported from AMT ver 6.0.However, my system has 3.2 and Q35 does not support that function.IF I misunderstood, please give me comments.Thanks a lot everybody!

Best Reply

according to,you're out of luck :(

That's right.Thanks kotique,

Leave a Comment

Please sign in to add a comment. Not a member? Join today