Huge warning: Do not attempt to update the bios in Windows PE. I got a bsod midway and the box was temporarily bricked (but fixing it only took 45 minutes!) I read the board manuals beforehand and knew there was a recovery feature so I guessed how it worked. You can find Fujitsu downloads here by plugging in model numbers and hitting the "OS Independent" tab:
https://support.ts.fujitsu.com/IndexDownload.asp?lng=en&OpenTab=
Bricked bios recovery guide:
1. ID the board in your S920. Mine was a D3313-E1x. It's easy to tell if the box is in working condition but otherwise there's an S920 pdf that explains the different board variants. The boards have different components.
https://support.ts.fujitsu.com/indexdownload.asp?Softwareguid=ebc493fd-3eac-44a0-894f-8af8404735a4
2. Download "BIOS Update - Admin Pack for D3313-xyz" and unpack
3. In the same bios tab there's a link to a FreeDOS USB creation tool for Windows:
https://support.ts.fujitsu.com/Inde...wareGUID=4C7EAC35-E4B9-4EB2-B51D-C7AB265A9690
4. Plug in a flash drive you don't care about and provision it with the FreeDOS tool
5. Copy paste the unpacked bios files as-is onto the flash drive
6. Pop open the case on your S920. It's only two screws and it's not completely obvious how it comes apart but it shouldn't be too hard. The part that slides out is connected to the front panel.
7. Your board should have a recovery pinout labeled "RCV" like this, where X should be where the jumpers were located when I opened the box:
- -
X
X -
"RCV" SILKSCREENED UNDERNEATH
arrange the jumpers like this
--
-
X X
"RCV" SILKSCREENED UNDERNEATH
8. Plug your flash drive into the front USB and turn on the S920
9. Your flash drive should light up and the speaker should make a bunch of weird noises. There are multiple tones, do not do anything until the tones change and start repeating.
10. Rearrange recovery jumpers to stock position
11. Reset machine and enjoy your long-winded bios update! Remember to change your power-on settings and decrease APU shared memory to 32 MB.
Note: The latest bios is currently V4.6.5.4 R1.16.0 and it is probably important so do consider flashing it:
- Microcode updates added.
- Memory module frequency limited to maximum
supported speed (1600MHz).
Here's some OPNSense performance off the top of my head with this hardware. Tests all done with NIC accelerations kept enabled except for IPS.
GX-424CC @ 2.4 GHz
4GB DDR3
Dell I350-T4 (T34F4) variant flashed with latest Intel firmware
(don't even ask me how I did this I don't remember I probably flashed it in Linux. claims to support SR-IOV)
Originally came with an AMD FirePro on original riser. This riser variant has a metal support bar that runs down the middle.
Onboard ethernet is some kind of Realtek, have not tried using it yet
Power adapter: Some Lenovo thing I had that happened to fit the specs
(ADP-65YB D, 20V 3.25A 65W, Lenovo P/N 36200337)
iperf3 Loopback (?): 3.43 GB/s
WAN with/without traffic shaping: Enough to saturate 1 gbit
WAN with IPS: 400 MB/s (Suricata seems extremely buggy with this hardware anyways just don't bother)
iperf3 inter-NIC on i350-t4: 400-500 MB/s
(laptop gbit on OptX to firewall on OptY, need to retest with 2 different machines later)
Basically it's fast enough for most homes, a little slow for enthusiasts and I'm happy with my ~$55 box and $50 quad NIC.
P.S Anyone know how to undervolt this CPU on BSD? I was able to take off 100 millivolts in Linux across all pstates. The software reported at one or two watts of savings, would love to have that. I see there's a BSD tool for manipulating MSRs but that's way over my head.
P.P.S My S920 was assembled in Germany (!) and the D3313s are industrial boards made by Kontron. I'm sad I only bought a single one. The quality speaks for itself.
P.P.P.S mSata SSD on mine reports about 3 years of power-on hours despite the unit looking completely spotless. I think these came from healthcare.