Fujitsu Esprimo D756/E9X Intel Xeon

[Crafto]

Hi,

I have an Fujitsu Esprimo D756/E9X (not sure if 94 or 90). It came with an Intel Core i3-6100.

I am using it as a homelab server. It's sufficient so far, but as more users find themselves using the server I thought it may be time for an upgrade. Thus I did some research and found the Intel Xeon E3-1245v5. It uses the same socket and some pages/articles claim they are compatible with the Q150 chipset of the D3431. I even found a store selling the Esprimo D756 with the Intel Xeon 1275v5.
The store: https://www.workstation4u.de/Konfigurati...0404010114

I bought the CPU and went to try it out... Upon powering on the system I can hear a relais click (from the PSU) and the power light on the front briefly turns on - then it turns off again.

The BIOS Version is R1.28.

Can anyone give me some more insight or maybe even point me to a solution?
Maybe a BIOS update is enough, maybe there is a modded BIOS or it is just restricted by Intel and/or Fujitsu.
I also can't entirely rule out I have a defective Xeon chip.

Thanks

Dump from dmidecode:

Code:

Base Board Information
Manufacturer: FUJITSU
Product Name: D3431-A1
Version: S26361-D3431-A1

BIOS Information
Vendor: FUJITSU // American Megatrends Inc.
Version: V5.0.0.11 R1.28.0 for D3431-A1x                   
Release Date: 07/23/2019
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.28

[DeathBringer]

Download CSME System Tools v11 and unpack it.
Run \Flash Image Tool\WIN32\fit.exe
Drug and drop your BIOS firmware into Flash Image Tool's window.
Go to Intel® ME Kernel->Reserved
Change a value of Reserved parameter to Yes.
Press Ctrl+B to build modded firmware. Then choose Yes
The file with name outimage.bin is modded firmware.

[Crafto]

Ok, thank you. I will try that, but this requires Windows.
Is it also possible with Linux by any chance?

[DeathBringer]

Is it also possible with Linux by any chance?

Use the virtual machine with Windows.

[Crafto]

You have to excuse me, but how do I get "my" BIOS firmware?

[DeathBringer]

Just read & write by any suitable hardware programmer.

[Crafto]

I managed to read the firmware using
flashrom --programmer internal -r dump.bin
and then modified it using fit.
using
flashrom -programmer internal -w mod.bin
I got the following. I assume I will actually need to get myself a external programmer. CH341A is what I often read.



flashrom 1.4.0 on Linux 6.14.8-2-pve (x86_64)
flashrom is free software, get the source code at https://flashrom.org

No DMI table found.
Found chipset "Intel Q150".
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to flashrom@flashrom.org including a verbose (-V) log.
Thank you!
Enabling flash write... Warning: BIOS region SMM protection is enabled!
Warning: Setting BIOS Control at 0xdc from 0xaa to 0x89 failed.
New value is 0xaa.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG1: BIOS region (0x00800000-0x00ffffff) is read-write.
FREG2: Management Engine region (0x00003000-0x007fffff) is read-only.
FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
At least some flash regions are write protected. For write operations,
you should use a flash layout and include only writable regions. See
manpage for more details.
Enabling hardware sequencing because some important opcode is locked.
PROBLEMS, continuing anyway
========================================================================
You may be running flashrom on an unknown laptop. We could not
detect this for sure because your vendor has not set up the SMBIOS
tables correctly. Some internal buses have been disabled for
safety reasons. You can enforce using all buses by adding
-p internal:laptop=this_is_not_a_laptop
to the command line, but please read the following warning if you
are not sure.

Laptops, notebooks and netbooks are difficult to support and we
recommend to use the vendor flashing utility. The embedded controller
(EC) in these machines often interacts badly with flashing.
See the manpage and https://flashrom.org/Laptops for details.

If flash is shared with the EC, erase is guaranteed to brick your laptop
and write may brick your laptop.
Read and probe may irritate your EC and cause fan failure, backlight
failure and sudden poweroff.
You have been warned.
========================================================================
Found Macronix flash chip "MX25L12805D" (16384 kB, Programmer-specific) on internal.
===
This flash part has status UNTESTED for operations: WP
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to flashrom@flashrom.org if any of the above operations
work correctly for you with this flash chip. Please include the flashrom log
file for all operations you tested (see the man page for details), and mention
which mainboard or programmer you tested in the subject line.
You can also try to follow the instructions here:
https://www.flashrom.org/contrib_howtos/...ested.html
Thanks for your help!
Reading old flash chip contents... done.
check_for_unwritable_regions: cannot write/erase inside Flash Descriptor region (00000000..0x000fff).
Write Failed!Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Good, writing to the flash chip apparently didn't do anything.
This means we have to add special support for your board, programmer or flash
chip. Please report this to the mailing list at flashrom@flashrom.org or on
IRC (see https://www.flashrom.org/Contact for details), thanks!
-------------------------------------------------------------------------------
You may now reboot or simply leave the machine running.