- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm new here and hope this is the right place to ask :-) I searched through old posts but couldn't find a solution to the following:
I setup AMT on a HP dc7700 and can use the web gui, the Intel AMT commander and "amttool" in Linux to connect to this host. But any try of using SOL just shows a black screen.
I tried Linux with the right "console=ttyS..." parameters without success, and even with the Intel AMT Terminal I can see nothing. I send the "Remoted reboot to bios" command from the terminal and the host rebooted into the bios, but the terminal window stayed black all the time. I switched between UFT8 and Ansi, no change. The terminal windows says "Serial-over-Lan - connected" all the time. Dis- and reconnecting doesn't help.
Any ideas why the screen stays black?
cu,
Frank
P.S.: I'm using the Intel AMT Developer Tool Kit v0.48x and AMT firmware 2.2.1.1034 (although I don't know if this is an Intel or a HP release number...)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi. Intel AMT Commander does not really know if serial-over-LAN connection is dropped, so, after you reboot to BIOS, try going in the terminal menu and disconnect and connect again. After that, press a few keys to see if the BIOS responds.
When the Intel AMT computer is in the OS, you will not see anything on the terminal unless you have a serial agent running. Run Intel AMT Outpost on the AMT computer and enable the serial agent. Make sure you ahve the serial-over-LAN drivers installed. You should see the Outpost management prompt on the terminal.
UTF-8 terminal emulation should never be used, I don't know anything that supports that mode.
I hope this helps, please let us know what your results are.
Thanks,
Ylian (Intel AMT Blog)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thanks for caring! I tried to remote boot to Bios and dis- and reconnected, but I still don't get any screen output and the remote PC/Bios does not respond to any keys that I type int the AMT Terminal :-(
I also tried "reboot remoted" and pressed F10 and Esc-0 to make the remote PC enter the bios, but it seems that no key press reaches the remote PC...
I double checked that SOL is enabled in the AMT bios on the remote PC.
Could that be an issue of the dc7700? Anything known about this HP models?
cu,
Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a side note, the original BIOS on my dc7700 would send VT100 color codes and mouse movement before each character on the screen making everything really slow. The update fixed that. If you are using the most current version of the BIOS, I will update mine to match and see what I can do.
Thanks,
Ylian (Intel AMT Blog)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do have the latest BIOS and AMT Firmware from the HP homepage. This is version 3.03, and it contains AMT firmware 2.2.1.1034. I couldn't go back to a 2.0 firmware because I don't find such an old bios on the HP page...
Strange that your dc7700 works while mine doesn't... I guess there should be no difference between the ultraslim and the miditower dc7700 regarding vpro.
I will be happy to try the older DTK version if you can tell me where to get it!
Thanks for caring!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So, here are some older versions:
Intel AMT DTK v0.21I would just try the oldest one and see if it makes a difference. Older versions are self-extract so you don't need to remove the current version. Please let us know what you find!
Intel AMT DTK v0.33
Intel AMT DTK v0.41
Ylian (Intel AMT Blog)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've also asked HP for help and they opened the case, but their support remains silent since two weeks :-(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ylian (Intel AMT Blog)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like they had a series of mainboards that had a problem with AMTA for some reason...
Thanks again for all your support!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Glad to know that the issue is solved. Thanks for letting us know this.
Thanks,
Sree
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page