Minisforum MS-01 BIOS
- Thread starter the-last-englishman
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I just built my MS-01 Proxmox box and have never used it before.
I noticed it didn't want to detect my second LAN connection that I was setting up as a active passive bond.
To fix I needed auto start for the interface.
Seems that Proxmox has interesting ways of handling the network stack that maybe is the issue more than the machine?
This isn't 1.26 specific but are your BIOS Fan Settings at 'Automatic'? (Mine are).
This is my observation as well; avg 1.22 temps in high 30's and now in the mid 40's with 1.26. One other thing to note is that I had TURBO disabled for 1.22, and I'm now using default settings with 1.26 (TURBO enabled).
Are you running an i9-13900 model? Would be interesting to see what happens to temp if you disable TURBO (just to rule that difference out).
I am using 'Automatic' fan settings.
Yes, I am running an i9-13900. I agree - I will be turning TURBO off after an important pending operation completes (sometime around Thursday unfortunately). Currently the said operation is running on a Proxmox VM with 8 cores allocated under ~40-50% load and the host btop is reporting 75-90C tempsAre you running an i9-13900 model? Would be interesting to see what happens to temp if you disable TURBO (just to rule that difference out).
I'm not sure how accurate those values are, but btop gave me the numbers I referenced in my previous post. On the other hand, the Proxmox GUI is showing 38-42C temps for all three NVMe drives (with rather heavy read/writes), though I don't know how reliable those values are either.EDIT: I compared btop values to lm-sensors output and it appears they come from the same source.
EDIT2: Disabling TURBO dropped my CPU temps 6-7C. I'm now ranging 40-42C.
Last edited:
After I installed BIOS 1.26, everything started well. Then I turned off (poweroff) MS-01, disconnected from the power, and it is not starting. No fan moves, no light like there is no power. I checked the power adapter and it produces 20V, so it is okay. I reset BIOS (disconnected and connected battery), but it did not help. I removed RAM, removed disk, and nothing helped. Any suggestions?
In my case it had nothing to do with a firmware upgrade, it was still running 1.17.
Just after a shutdown pressing the power button, it never came back.
Thank you so much for this. I was able to boot after moving the shell.efi from /x64 to the root of the usb drive and I was finally able to flash 1.26. Why didn't they include this with the bios package?
i'm no expert, but I've done this a few times on my 5 node MS01 cluster. I'm guessing they don't include shell.efi in the firmware update because you don't need to boot from the USB device containing the update. the system has a UEFI shell built in. if you boot to that, with the USB drive inserted, you can apply the update.
@anewsome it would not load to the UEFI shell UNLESS that shell.efi file was located on the USB drive. I believe the last time I flashed it (the 1.22) the file was included.
Can your system boot to UEFU shell without a USB drive inserted at all? It should. Here's what I have for the 1.22 version:
Code:
.
├── 0-HOW TO FLASH.txt
├── AfuEfiFlash.nsh
├── AfuEfix64.efi
├── AfuWinFlash.bat
├── AFUWINx64.exe
├── AHWSA.1.22.bin
├── amigendrv64.sys
├── EFI
│ └── BOOT
│ └── BOOTX64.efi
├── EfiFlash.nsh
├── Fpt.efi
├── FPTW64.exe
└── WinFlash.batFor the 1.26 version, that folder doesn't exist. Copy it over, or use that link I sent and put the Shell.efi into the root of the USB drive and you'll be golden.
I've tried every iteration I can find in this thread, but I keep getting "Secure Boot Violation. Invalid signature detected. Check secure boot policy in setup."
This screen comes up whether I put the Shell.efi in /EFI/BOOT/BOOT64.efi or if I simply leave Shell.efi at the root of the USB. Did anyone have to turn off secure boot to do this? I think that requires making an admin password.
This screen comes up whether I put the Shell.efi in /EFI/BOOT/BOOT64.efi or if I simply leave Shell.efi at the root of the USB. Did anyone have to turn off secure boot to do this? I think that requires making an admin password.
My apologies and thank you for pointing that out. Somehow I was blind to that on earlier pages of this thread. That fixed it and I was able to flash 1.26 successfully. In case anyone else needs more clarity, you need to Setup > Security and set an admin password. Be sure to save and exit that screen and also allow it to save and reset everything. When you cold boot again, enter the admin password, then you can go in and disable secure boot on the same screen where you set the admin password.
Last edited: