thanks, i'll try it later and let you know
for the moment i've put on meshcentral
Getting vPro remote KVM working on Minisforum MS-01
- Thread starter merlina2
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
for the moment i've put on meshcentral
How did you add it to meshcentral?
I cannot deploy a agent because there is none made for the OS i use
no, i've deployed meshcentral on my Syno and add the MS-01 as "AMT Client", so like your MeshCmd with WebUI
Right. What OS are you using?no, i've deployed meshcentral on my Syno and add the MS-01 as "AMT Client", so like your MeshCmd with WebUI
Gents - daft question I know, but.... what key press enters BIOS on bootup? Have tried the usual suspects Del, Ins, F2, F12, etc
I dont know if Ive pressed the right key too late, or am just pressing wrong keys.
Does not help that the splash screen is just "minisforum" with no indication and only lasts for a split second!
I dont know if Ive pressed the right key too late, or am just pressing wrong keys.
Does not help that the splash screen is just "minisforum" with no indication and only lasts for a split second!
Mesh Commander works fine for me except i also find that networking mounting an iso through AMT is janky AF and doesn't work right half the time, or is painfully slow.
Whoever said vPro is finicky couldn't be more right. I finally got both MeshCommander and ip:16993 access working on the MS-01. MeshCommander KVM also works, but what a pain it is to get it all working correctly. This is my first time working with vPro and I can say without reservation, I much prefer a dedicated IPMI. In the end, I did have to use a dedicated IP for vPro - shared wouldn't work in my setup. I also could not get it to work without a DNS entry, so now I have a DNS entry. Not exactly thrilled that my MS-01 cluster will now consume yet another 5 IP addresses, but I do like having an IP KVM, so I'll accept it.
I was also able to get the Serial-over-LAN terminal working, which is actually faster for some things, compared to full KVM. The SOL is on ttyS4.
The times that did work for you, do you remember what you did? i just mount the iso.. i say reboot to the machine and finito.... it popup up and let me connect again after much time where the iso is unmounted is its a no go for any remote installation.
This is cool.
So in the i226-LM port connected RJ-45 to USB serial port in this case? Is there anything additional need to enable TTY?
You need to enable a getty on the port (/dev/ttyS4). Assuming Debian 12 here (also applies to Proxmox 8 and I assume most other systemd based distros), use systemd:
Bash:
# systemctl enable serial-getty@ttyS4.service
# systemctl start serial-getty@ttyS4.service
# systemctl status serial-getty@ttyS4.serviceHi
All just thought I would share my findings on this in case it helps others.
I actually found the old version for Mesh Commander AMT firmware which i flashed to the AMT, now I can remote KVM from the device itself, without the need for a Mesh Commander server, which is perfect for my needs.
Its not on their website anymore but can be be found in web archive
The tool only connects to port 16992 so can only be used to flash from the local host (as SSL is enforced on remote connections)
I my case I run pve so I had to pass through the following devices to a windows guest in order to flash it:-
Once flashed with the Mesh Commander firmware the pcie devices can be removed from passthrough.
Here is the result from accessing https://vproip:16993
All just thought I would share my findings on this in case it helps others.
I actually found the old version for Mesh Commander AMT firmware which i flashed to the AMT, now I can remote KVM from the device itself, without the need for a Mesh Commander server, which is perfect for my needs.
Its not on their website anymore but can be be found in web archive
The tool only connects to port 16992 so can only be used to flash from the local host (as SSL is enforced on remote connections)
I my case I run pve so I had to pass through the following devices to a windows guest in order to flash it:-
Once flashed with the Mesh Commander firmware the pcie devices can be removed from passthrough.
Here is the result from accessing https://vproip:16993
Just a quick follow on, once the devices have been passed through I found that I needed to reboot the proxmox host to have them available again to it. I think this is because loads passthrough drivers for the devices and then doesn't reset the driver when removing from passthrough.
I am sure someone with more knowledge could explain it better!
I am sure someone with more knowledge could explain it better!
Hi , Thank you for your information.
For the connection problem it was resolved by setting an IPV4 address in the bios
For the connection problem it was resolved by setting an IPV4 address in the bios