search

Ylianst / MeshCentral

A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
https://meshcentral.com
Apache License 2.0
3.88k stars 528 forks source link

Intel AMT not detected on HP 400 Mini G9 under Ubuntu #5780

Open thermionic opened 6 months ago

thermionic commented 6 months ago

Describe the bug Intel AMT not detected on HP 400 Mini G9 under Ubuntu 22.04.3 (works perfectly under Win11)

To Reproduce Steps to reproduce the behaviour:

  1. Install agent (as root) in "fully automatic" group
  2. Does not progress to CIRA
  3. Console shows "Intel AMT not detected"

However (with light obfuscation)

root@mini9-a:/home/mini# ./meshcmd amtinfo
DHCP error, timeout
Intel SM v16.1.27, activated in Admin Control Mode (ACM).
Wired Enabled, DHCP, E0:73:E7:B2:B1:B3, 192.168.12.123
Trusted DNS suffix: meshc.mydomain.com
Connection Status: Direct, CIRA: Disconnected.

root@mini9-a:/home/mini# ./meshcmd amtversions
BIOS Version = U23 Ver. 02.12.02
Flash = 16.1.27
Netstack = 16.1.27
AMTApps = 16.1.27
AMT = 16.1.27
Sku = 16400 (ISM, Corporate)
VendorID = 8086
Build Number = 2225
Recovery Version = 16.1.27
Recovery Build Num = 2225
Legacy Mode = False
root@mini9-a:/home/mini#

There is no output from "eval SMBiosTables.amtInfo" in the console under Ubuntu, but under Win11 it shows 

{"AMT":true,"enabled":true,"storageRedirection":true,"serialOverLan":true,"kvm":false,"TXT":true,"VMX":true,"MEBX":"0.0.0.0","ManagementEngine":"16.1.27.2225"}

Expected behaviour the AMT config to be shown, and be able to progress to CIRA

Server Software (please complete the following information):

Remote Device (please complete the following information):

Additional context Looks related to #3846 and #4092

This issue is just to hopefully prevent somebody else getting frustrated like I have been for the past couple of hours with this hardware...

I do fully understand the change since @Ylianst was "let go" from Intel and that this may be "a while" before anyone looks at it, I am however very happy to do any testing if somebody picks it up (-:

si458 commented 6 months ago

The output of amtinfo shows DHCP error, timeout are u sure the interface can get an ip address from ur dhcp correctly when the machine isn't running?

silversword411 commented 6 months ago

...and it's not wifi...

thermionic commented 6 months ago

@si458 only Ethernet was connected, WiFi was not configured. The Meshcentral agent was able to connect over the Ethernet port, and the AMT web interface was accessible via the Ethernet address (as expected until CIRA is activated).

It may be related to the desktop only having vPro Essentials, but Meshcentral worked perfectly at configuring when the computer was rebuilt with Windows 11 instead of Ubuntu 22.04.3 (again with only Ethernet connected) which is why I think it may be related to the other two issues.

I might try a few other distros when I next get the time (will be a few weeks).

@silversword411 only using Ethernet

si458 commented 6 months ago

Does the /dev/mei* exist?

Edit. Also try running eval SMBiosTables.amtInfo from the console tab of the device in meshcentral and see what the reply comes out with?

thermionic commented 6 months ago

Good question about /dev/mei*

Before running "meshcmd amtinfo" and "meshcmd amversions", I compiled and ran https://github.com/mjg59/mei-amt-check which produced output similar to meshcmd, so I presume that /dev/mei* existed, however I will recheck when I next have the opportunity.

Re "eval SMBiosTables.amtInfo"

From above, "There is no output from "eval SMBiosTables.amtInfo" in the console under Ubuntu, but under Win11 it shows"

si458 commented 6 months ago

so the is an issue with SMBIOS and linux then, so needs investigating, however Intel AMT is currently unsupported by intel, so i will try my best to help find/fix the issue, but no promises

can you also try running smbios and rawsmbios in the console tab of a device too and share the reply?

thermionic commented 6 months ago

I had some unexpected time (-:

Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-94-generic x86_64)

/dev/mei exists

xclocal@mini-g9:~$ ls -al /dev/mei*
crw------- 1 root root 234, 0 Feb 13 17:41 /dev/mei0
xclocal@mini-g9:~$

agent was installed as root (sudo su -)

Console output

smbios

> smbios
{
  processorInfo: {
  }
  memoryInfo: {
  }
}

rawsmbios

> rawsmbios
Table type #0, BIOS information
  00200038434333323032424D56008CC3202B002000000D1617000F0100000000000000000000000000000001656E5553000E006465444500DEDE65734553000E0E697449
  52000F0F6A614A50000A00707450540000006461444B00DA0D7376534500000E6E6C42450000BE6E6F4E4F00000066694649000F0F7A68434E00000C7A6854570000007275525500000000021118000102030405010615000A000000485000003839
  000301000C00BA100002000000003200030001121000005265666572656E636520436F6465202D20435055000EFE0E0CEC0D0E0C075436F64652056657273696F6E0000CDE0E000005458542041434D2076657273696F6E00000AC000E000000DD1A1B000301000C00BA100002000000000000030410011BB1085265666572656E636520436F6465202D204D45000EFE0E0CEC0D0E0E4D4542782076657273696F6E000E0B0E000004D45204669726D776172652056657273696F6E000EF00000A0E0E0000436F72706F7261746520534B55000C00000A0E00
  00DD521D000B01000C00
  000180
  4C322043616368650002CA0C00071B2100018201004800482000
  4C332043616368650003CA0C00043222000103CD0275060900FFFBEBBF038964003011AC0D41401F002000210004050606060CFC00CD00060006000C0000005533453100
  000008093000010002121046524F4E542055534220332E30000F00000B03046726F6E7420555342332E3020506F7274203200F000000B3000000000809310001000212105553420000B526561722055534220332E3020506F72742031000EA000B03000001000809320001000212105553420000B526561722055534220332E3020506F72742032000EA000B03000002000809330001000212105553420000B526561722055534220332E3020506F7
  0000000000536C6F7432202F204D32205353440000000202000027163B00000102030405060700801209FFFFFFFFFFFF4E554C4C0000004E554C4C0000004E554C4C0000004E554C4C0000004E554C4C0000004869676820456666696369656E6379000000EF0F0C0E0C4E554C4C00000000290B3C00018301000000104F6E626F6172642049474400000B0A0D0D00290B3D00018501000000FE4F6E626F617264204C616E00000B0A0D0A0082183E0024414D540101010101A5FF028000000000000000000083403F003500
  0001001000B1081B0000000000FE001C1A0000000000000000260000007650726F000000000000115C40000100
  4D31000D001436F6E74726F6C6C6572314368616E6E656C4144696D6D3000C0000000E010C0A0E0A0D0004B696E6773746F6E000000000046394638323636310
  0000000000000000000000000000
Table type #3
  080000115C41000100FEFF000000000000010001020200000000000000000000000000000000000000
  CB0360C402FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Table type #5, memory controller information
  3524944205374617475730000A0C0D000A0044697361626C6564000D0A0BED53412D43524944204F726967696E616C20
  1E
Table type #6, Memory module information
  48
Table type #8, Port connector information
  0103020809
  01030200FF
  0100020B1F
Table type #9, System slots
  01B208040101000405000000A300000000000000
Table type #10, On board devices information
  48204873696F205665
  00000E0000EF
  0A0EAB00000E0000EF00
  8301
Table type #11, OEM strings
  06
Table type #12, System configuration options
  17010003030300000004FEFF020000000000000000000000131F120000000000FFFF7F00010001000000000000000000000000000000000000001A1300010200F003FF8099093C10004000010F0C021203200048500000553233205665722E2030322E31322E30320002030E0002120023
  050125000546F2042652
Table type #13, BIOS language information
  18150001230203040303
Table type #14, Group associations
  526566657265
  0A0D0F0000ED00
  6F642073656E73650000
  01DB0000
Table type #27, Cooling device
  FFFF650000000000008001
Table type #32, System boot information
  021A8000800C030405
  00000000000000
Table type #43
  4E5443000200020007000100030001180000000000000000000000
Table type #47
  01000C00BA10000203FFFFFFFFFF0400FFFFFF11000500FF
Table type #68
  33000D003436F6E74726F6C6C6572304368616E6E656C4144696D6D3000C0000000E000C0A0E0A0D0003938373635343332313000987654321001423020000000000FFFF7F
Table type #69
  000A0008092C000100020D1D46524F4E5420415544000F000A0D46726F6E742048656164736574000F0000EA0D0E0008092D0001FF02001D53504B52000000537065616B65720000
Table type #72
  726F204D696E6920343030204739204465736B746F702050430000000000040009DE000000C53424B50460000B0F38434333323032424D56008CC3202B003642324432454123414255006B2D
Table type #76
  616368650001CA0C00071B1F00018001C000C0002000200000040307C0000000C00000004C3120436163686500
Table type #77
  000E014D454932000E024D454933000E034D454934000E04007F04FFFE0000
Table type #80
  4275696C642056657273696F6E00000B000D0E000005468756E646572626F6C7428544D292046572056657273696F6E000000D0E0B0000000F0E0000053797374656D204
Table type #82
  72656E636520436F6465202D20504348000EFE0E0CEC0D0E0C05043482D43524944205374617475730000C0C000D0A00044697361626C656400D00AB0ED5043482D43524944204F726967696E616C2056616C75650000C0C000D00000A000A0E50
Table type #83
  30000A0A000809350001FF0200FF505752000004D61696E20706F7765720000A00000E000809360001FF0200FF43505546414E000C0F0A435055206661
Table type #128
  0000B00403080000
Table type #202
  092500010302080950
Table type #221
  0101000400000000

Happy to try in other distros if desired.

randominternetuser commented 5 months ago

It looks like the current meshagent on Linux is missing the smbios module?

I tracked it through the loading process and it fails right here at this catch, printing that exception revealed it cannot find the smbios module https://github.com/Ylianst/MeshCentral/blob/0e055ef7414a60b820d42107fce8755ef29555a3/agents/meshcore.js#L765

This would explain why all the smbios commands are blank as well.

Infact after writing around this I also discovered that the amt-manage module is also missing? I find it strange how so much is missing.

randominternetuser commented 5 months ago

image image

SMBiosTables.amtInfo = { AMT: true, enabled: true, storageRedirection: true, serialOverLan: true, kvm: true, TXT: true, VMX: true, MEBX: "16.1.25", ManagementEngine: "16.1.25.2124"};

With this added to force some SMBios AMT data in it did try to connect however the agent seems to restart and mesh overwrites my core with an linux-amt one again.