Here is a complete list of the Proxmox servers currently running continuously in our environment. Not included in this list is the TR server, which has been taken offline for the time being due to components being removed for reuse, and the Proxmox Backup Server, which continues to be used automatically as a backup destination by all VM servers.

The configurations for these two (TR server and PBS) are detailed in this post.

Hardware:

Firmware:

Software:

Screenshots:

Documents / Drivers

Server-PVE-Monitoring Drivers at Dell
Server-PVE-Services Drivers at HP
Server-PVE-Media and Server-PVE-Streaming Drivers at HP

Der Beitrag <h5>Setup: </h5><h3><b>Proxmox Low Power Server</b></h3> erschien zuerst auf flohs blog.

I never would have thought that FlexIO v2 and the “improper” use of the 10 GbE module – which is actually intended for other HP workstation models – would change the project so much.

It all started when I saw these mini PCs on sale, equipped with just a single RAM stick. Normally, that’s a disadvantage because the CPU doesn’t run in dual-channel mode. But for me, it was ideal – two 8 GB sticks would have been significantly worse in my situation, and that happens more often than you’d think.

Next is an overview of the four “energy-saving servers” we now operate instead of two.

Der Beitrag <h5>Mini-PC Server #12: </h5><h3><b>Conclusion</b></h3> erschien zuerst auf flohs blog.

The next step is to reconfigure the RAM on all other affected devices so that the desired configuration can be implemented.

Important side note:
With the 10 GbE module installed, the SATA caddy fits “just barely” as it hooks onto the side of the case and the CPU cooler and is slid in to secure it. It is then secured to the mini-PC with two screws. Inside the caddy, the SATA port is held in place by two Torx screws, and the space is so tight that you have to remove the right one of the two (behind the 10 GbE module) to get everything slid in without causing any damage. After installation, you can reattach the screw that was removed.

Since the hardware is now running as expected, it’s time to tackle the software side. There isn’t really much to say about this. Install Proxmox VE via Rufus onto a GPT- or UEFI-bootable USB drive, and you’re good to go. After installation, re-enable UEFI Secure Boot.

Migrating the many VMs will take a few hours, since the backups are stored on rather slow hard drives connected to a very underpowered PC.

Der Beitrag <h5>Mini-PC Server #11: </h5><h3><b>Final steps</b></h3> erschien zuerst auf flohs blog.

It will also be interesting to see how the temperatures of the installed NVMe SSDs behave. After all, the installation space is very limited, and these SSDs tend to run quite hot.

To illustrate the respective changes, I conducted measurements without a SATA caddy (including a fan), with a caddy and fan, and finally with a caddy, fan, and a homemade aluminum passive cooler.

A Mega Fastro MS200 with 2 TB was always installed in M.2 slot #2; this tends to run very hot (especially the controller). A Samsung 970 Evo Plus reaches slightly lower but ultimately similar temperatures. A “Drive Temperature 2” doesn’t seem to exist, which is why it’s missing below.

Laufwerkstemperatur 1

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

Laufwerkstemperatur 3

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

Laufwerkstemperatur 4 (Probably the controller)

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

Laufwerkstemperatur 5

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

Laufwerkstemperatur 6

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

Laufwerkstemperatur 7

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

The effectiveness of the thermal pad and aluminum heat sink, in particular, cannot be denied.

Der Beitrag <h5>Mini-PC Server #10: </h5><h3><b>Temperatures of NVMe SSDs under various conditions</b></h3> erschien zuerst auf flohs blog.

Here, too, I plan to use a Honeywell thermal interface pad, again the PTM7950, again from AliExpress. I don’t intend to replace the TIM on this mini-servers in the next few years, so a thermal interface pad makes sense.

This time, I bought an 80 x 40 mm pad, cooled it slightly, and cut it down to about 30 mm wide. I did that twice, which leaves about 20 mm of pad – that would even be enough for a smaller chip.

I documented how to apply the pad the first time I installed one; the only difference is that this time I pre-cooled it. That actually helped: peeling off the first film was a lot easier. However, the adhesion to the heat spreader was even worse.

So, as a next improvement, I would pre-cool it again, then peel off the first sheet from the pad and wait until the pad has reached room temperature again. Only then would I try to peel off the second sheet. Even so, the process isn’t fun even on the second and third tries.

Photos of the pads being applied

Comparative measurements: MX-4 / PTM7950

On the unmodified mini-PC, I performed meaningful comparative tests using Arctic MX-4 and Honeywell PTM7950 to demonstrate the difference. Here, too, direct-die cooling would be optimal rather than cooling via the heat spreader, and several hot-cold cycles were performed to ensure the thermal pad functioned properly. I used Prime95 with Small FFTs and AVX as the test load.

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

The pad improves the average by a full 1.5°C – not bad, all things considered.

Comparative measurements of both mini-PCs with the PTM7950

It’s also interesting to note the differences between the two PCs, due to the modified cooler and the apparently lower contact pressure.

The three values in the table, from left to right, are: Minimum, Maximum, and Average. The values stated are in degrees Celsius.

The modified cooler, which doesn’t seal perfectly, runs just under 3°C hotter. I would have expected worse, so I’m perfectly fine with that.

Der Beitrag <h5>Mini-PC Server #9: </h5><h3><b>PTM7950</b></h3> erschien zuerst auf flohs blog.

Given the significantly modified third mounting point on the CPU cooler, it is unclear whether the contact pressure is sufficient to prevent thermal throttling. Since I have two identical mini-PC units, I can easily compare the modified cooler with the original one.

Using the MX-4 thermal paste initially, I tested whether thermal throttling occurred, but that was not the case. Since we still live in an attic apartment and outdoor temperatures have exceeded 30°C in recent days, the measurements were largely unusable; when the intake air is easily 5°C warmer than the day before, the results are not meaningful. The maximum values were around 84°C with Cinebench R23 running a 30-minute multicore test.

Pressure image

Unfortunately, my countersunk screw design cannot replace the original contact pressure:

It’s good to see that the pressure point isn’t centered but has shifted slightly to the right, which indicates that more pressure would be needed in the modified corner.

I’ll leave my setup as is, since the temperatures haven’t deteriorated significantly. Still, this isn’t ideal: For a 65-watt model with a more powerful cooler, this setup wouldn’t really be an option. I think I’m just barely getting away with the aluminum bracket because the CPU is so energy-efficient (35 watts).

Next, I’ll replace the thermal paste on both EliteDesk 800 G6 DM units with Honeywell PTM7950 thermal pads so I won’t have to touch the coolers for as long as possible.

Der Beitrag <h5>Mini-PC Server #8: </h5><h3><b>Cooling capacity?</b></h3> erschien zuerst auf flohs blog.

Now that the cooler has been modified to fit properly and I’ve confirmed via HWiNFO that extreme temperatures don’t occur – at least under light load, I turned my attention to the firmware:

The Marvell/Aquantia controllers have internal firmware that can be updated. Issues are still being fixed to this day, and it’s highly recommended to flash the latest firmware version, even if that entails certain risks. The update is (only?) possible under Windows, so it makes sense for me to do this now, before Proxmox and thus Debian is running on the mini-PCs.

There are good resources for the Aquantia controllers at station-drivers.com

Update Process

I was a little worried, after all, you can easily render the module unusable if something goes wrong. It’s similar to a BIOS or UEFI update during a power outage.

That’s why I updated in two steps: first to version 1.5.38 using the official Marvell firmware updater and then a small step up to 1.5.45 using the modified updater from station-drivers.com. Both are available for download there, along with a detailed forum thread:

Download v1.5.38 (Official)
Download v1.5.45 (Mod)
Forum thread

The release notes are also interesting; there have been a lot of improvements over the years, thanks to Marvell / Aquantia:

FW version 1.5.45 for Marvell AQC113 Family of Controllers
==============================================

1.5.45
?
-------
* Updates the PCIe Gen3 x4 advertisement information.
* Tunes the PCIe memory timing for 0.7 V power supply.
* Sets hysteresis to 50 mV.
* Provides SRAM ECC protection.
* Restricts the presets to used only P4-P9.


1.5.38
27 February 2024
-------
* Bypassed automatic execution of PCIe Configuration from Bootloader.
* PCIe Serdes Firmware integrated into MAC Firmware image and loaded during cold boot.
* PCIe initialization triggered from MAC Firmware.
* ROMBIN atlantic2 set to Antigua_1_5_xxx_487


1.3.37
31 October 2023
-------
* Signed PXE ROM v3.1.106 with EFI v2.1.13 FW 
* Added fix for Pre-Boot DMA protection


1.3.36
31 October 2023
-------
* Signed PXE ROM v3.1.105 with EFI v2.1.12 FW 
* Added boot time optimization and check for cable detect status - fix for Lenovo


1.3.34
3 February 2023
-------
* Reverted the change of loading the PCIe PHY FW to PCIe PHY SRAM (Change introduced in 1.3.29).
  The PHY FW will be loaded from PCIe PHY ROM as it was before


1.3.28
8 April 2022
------------
* Added Advertize 2.5 and 5G NBase-T speed capabilities
* Added AQC113 device ID 0x34C0 to inventory list


1.3.27
18 March 2022
------------
* OEM specific release
* exluded SerDes FW to 3.5.0
* Added configuration to enable SRAM ECC detection and correction


1.3.26
23 feb 2022
------------
* OEM specific release
* Added CFG TLV configuration changes(need your input)


1.3.25
16 feb 2022
------------
* OEM specific release
*	Fixed the unintended Wake-On-Link-Up behavior on the Mac-OS environment.
* Fixed the issue of untimely wake-up from Wake-On-Timer.


1.3.24
08 feb 2022
------------
* Updated the SerDes FW to 3.5.0
* Limited the PCIe preset mask to p4-p9 for Gen3 and Gen4


1.3.23
15 jan 2022
------------
* Introduced additional provisionable PCIe configuration mode to workaround PCIe instability observed on some platforms
  Relevance- AQC113C


1.3.22
5 jan 2022
------------
* Removed default advertisement of GARP and Unsolicited NA in Sleep Proxy mode. The driver can use the new capability mask bit in the offload-control register to control this feature
* Do not wait for 20sec (linklatchuptimeout) to enable Wakeonlinkup if the link is down at the time of suspend/sleep
* Removed the extra link flap on Wake-on-link. And when the system wakes up, initialize the link at the highest possible speed
  Relevance: fast-boot mode


1.3.21
11 nov 2021
------------
* Updated PCIe VPD data
  Relevance: images with PCIe VPD support
* Added support for drvdiag -s in PCIROM v3.1.4 UEFI driver
  Relevance: UEFI


1.3.20
16 oct 2021
------------
 * OEM specific release with specific provisioning


1.3.19
-----------
* Skipped version


1.3.18
02 july 2021
------------
* Fixed the issue of incorrect packet statistics counters reported by fw
* Removed 1G half duplex speed advertisement from the speed capability configuration
* Fixed the invalid speed advertisement 
  Relevance: AQC115C-B1
* Fixed the wrong led behavior at 2.5G speed 
  Relevance: AQC115C


1.3.17
23 apr 2021
-----------
* Added firmware support to disable NCSI via BDP provisioning
* Fixed longer link downtime during os suspend to resume transition in fast-boot mode


1.3.16
13 apr 2021
-----------
* Fixed the TFTP pxe boot failure due to failure to acknowledge Ock/Oack 
  Relevance: FW images with PCIe option rom support


1.3.15
02 apr 2021
-----------
* Added mDNS support
 
 
1.3.14
-----------
* Skipped version


1.3.13
13 feb 2021
-----------
* PHY firmware updated to v6.01.02 for Bx
* PHY change: only enable autoneg timeout when downshift is enabled if downshift was active
* Disable Reed Solomon feature in PHY firmware
* Fixed AQC113 power consumption is higher when cable is removed vs. Attached


1.3.12
08 feb 2021
-----------
* Revert additional fix for mDNS


1.3.11
05 feb 2021
-----------
* Fixed answers in mDNS query differ between when system is in sleep and when the system is awake - additional fix
* Fixed panic case: extended Lom port not open up after secure request was sent


1.3.10
01 feb 2021
-----------
* Fixed AQC113 failed when configured with 10G/full-duplex and came back up with a hot-plug of cable


1.3.9
28 jan 2021
-----------
* Fixed additional fix - remove questions from response (mDNS)


1.3.8
26 jan 2021
-----------
* Fixed AQC113: link became inactive and still fails with hot-plug of cable
* Fixed additional fix for regression test failure
* Fixed AQC113: answers in mDNS query differ between when system is in sleep and when the system is awake
 
 
1.3.7
20 jan 2021
-----------
* Fixed AQC113 ping failed after stress test when system is in sleep
* Fixed [Lom] ping6 extLom is successful after the system panics without pinging basic Lom


1.3.6
10 jan 2021
-----------
* Fixed AQC113 PTP tx ring appears to stop working

	
1.3.5
6 jan 2021
----------
* Fixed AQC113 A0 : built-in became 10base after cable was plugged in switch
* Fixed [Lom] extended mode enabled before 30 sec window
* Fixed [Lom] extended Lom port should be closed after 300 seconds, not 500+ seconds
* Added provision registers 3660 and 3664 in config
* PHY firmware updated to v6.01.01 for Bx


1.3.4
18 dec 2020
-----------
* Fixed AQC113 extended Lom port should be closed after 300 seconds, not 500+ seconds - "shutdown" case
* Fixed AQC113 extended Lom port kept open after Lom unenrolled
* Fixed AQC113 ping6 ext Lom drops packets when system is shutdown (power on failed)


1.3.3
15 dec 2020
-----------
* Fixed AQC113 (both A0/B0) FW does not respond to mDNS query while sleeping
* Fixed AQC113 did not wake after tcp keepalive expires
* PHY firmware updated to v6.0.15


1.3.2
26 nov 2020
-----------
* Fixed AQC113 (both A0/B0) FW does not respond to mDNS query while sleeping (side-issue with uncast request)
* Fixed thermal shutdown functionality is not provisionable
* Remove support for 10m_HD and 100m_HD


1.3.1
09 nov 2020
-----------
* Added support for B1 devices


1.2.3
27 oct 2020
-----------
* Fixed AQC113 Lom0 doesn't generate interrupts for link change events


1.2.1
14 oct 2020
-----------
* Added support for B0 devices


1.1.27
16 sept 2020
------------
* Fixed MAC firmware hang while pc wakeup from suspend state
* Fixed unexpected wake when thunderbolt ethernet adapter is connected
* Fixed regression: ipv4 ping to nic proxy not functioning


1.1.24
22 july 2020
-------------
* Fixed configuration for GPIO
* Fixed calculation read bytes for smbus transaction of Lom
* Fixed interrupt line for Lom if rx packet available
* Fixed Lom interruption pin set to "asserted" after initializing


1.1.19
26 june 2020
-------------
* No changes


1.1.18
25 june 2020
-------------
* Fixed processing of mDNS resource records
Known issue:
* GPIO pin for reset function should be pulled up instead of pulled down


1.1.12
10 june 2020
-------------
Bug fixes:
* Fixed possible datapath stuck after hot-reset
* Fixed link negotiation issue caused after reset for AQC113C 7x7 devices
* Fixed chip stuck which may be caused by soft reset
* Fixed issue preventing chip reset when reset requested while loading ITI


1.1.5
6 may 2020
-----------
Bug fixes:
* Fixed issue that cause PCIe link drops
* Fixed issue when MAC calculated PHY hash before PHY is ready
Enhancements:
* FW provide packet to driver that woke up the system
New features:
* SNR data were added to driver interface


1.0.32
16 march 2020
-------------
Bug fixes:
* PHY reset stability improvements
* Fixed PHY FW stuck caused by fast reset
* Fixed ipv6 offload issue which may prevent receiving fragmented packets
* Fixed VPD corruption caused by multiple VPD read/write operations
Enhancements:
* Hot reset alarm support added
* MSM settings may be applied without link drop-off


1.0.25
14 february 2020
-------------
Bug fixes:
* FW no longer wake host after first link down/up immediately after hibernation
* Fixed SerDes initialization which cause disappearance from PCIe
* Fixed wake on link up
Changes:
* Disabled half-duplex by default for 10M, 100M, 1G speeds


1.0.22
31 january 2020
-------------
Enhancements:
* Disabled half duplex on 10M, 100M, 1G speeds by default
Changes:
* Disabled run-time power optimizations


1.0.19
24 january 2020
-------------
Enhancements:
* Added "coma" power mode
Bug fixes:
* Fixed disappearing from PCI after hibernating
* Fixed data at mDNS response for ipv4 "A" request
* Fixed missing response for mDNS PTR+TXT request
* Fixed chip licensing, which hadn't got settings from efuse high word


1.0.13
10 january 2020
-------------
Enhancements:
* Reduced minimal timeout for TCPKA from 60 to 1 sec
Bug fixes:
* Fixed link up in sleep proxy mode
* Fixed missed ipv6 probes after TCPKA timeout
* Fixed wake up caused by receiving TCPKA probe with wrong flags
* Fixed data at mDNS reply


1.0.11
30 december 2019
-------------
New features:
* Added chip licensing functionality
* Added thermal monitor interface
* Added cable diagnostics
Bug fixes:
* Fixed flow control configuration. Incoming pause frames cause traffic slow down as intended.
* Fixed forced reset of PHY FW caused by MAC FW
* Fixed incorrect data at probe packet which is generated by TCPKA offload
* Fixed invalid src ipv6 at mDNS reply
* VPD mailbox was removed from FW
* Fixed wake up counter
* Fixed resending probes by TCPKA after receiving correct ack on first probe


1.0.3
20 december 2019
-------------
Initial release

FW version 1.5.45 for Marvell AQC113 Family of Controllers
==============================================

1.5.45
?
-------
* Updates the PCIe Gen3 x4 advertisement information.
* Tunes the PCIe memory timing for 0.7 V power supply.
* Sets hysteresis to 50 mV.
* Provides SRAM ECC protection.
* Restricts the presets to used only P4-P9.


1.5.38
27 February 2024
-------
* Bypassed automatic execution of PCIe Configuration from Bootloader.
* PCIe Serdes Firmware integrated into MAC Firmware image and loaded during cold boot.
* PCIe initialization triggered from MAC Firmware.
* ROMBIN atlantic2 set to Antigua_1_5_xxx_487


1.3.37
31 October 2023
-------
* Signed PXE ROM v3.1.106 with EFI v2.1.13 FW 
* Added fix for Pre-Boot DMA protection


1.3.36
31 October 2023
-------
* Signed PXE ROM v3.1.105 with EFI v2.1.12 FW 
* Added boot time optimization and check for cable detect status - fix for Lenovo


1.3.34
3 February 2023
-------
* Reverted the change of loading the PCIe PHY FW to PCIe PHY SRAM (Change introduced in 1.3.29).
  The PHY FW will be loaded from PCIe PHY ROM as it was before


1.3.28
8 April 2022
------------
* Added Advertize 2.5 and 5G NBase-T speed capabilities
* Added AQC113 device ID 0x34C0 to inventory list


1.3.27
18 March 2022
------------
* OEM specific release
* exluded SerDes FW to 3.5.0
* Added configuration to enable SRAM ECC detection and correction


1.3.26
23 feb 2022
------------
* OEM specific release
* Added CFG TLV configuration changes(need your input)


1.3.25
16 feb 2022
------------
* OEM specific release
*	Fixed the unintended Wake-On-Link-Up behavior on the Mac-OS environment.
* Fixed the issue of untimely wake-up from Wake-On-Timer.


1.3.24
08 feb 2022
------------
* Updated the SerDes FW to 3.5.0
* Limited the PCIe preset mask to p4-p9 for Gen3 and Gen4


1.3.23
15 jan 2022
------------
* Introduced additional provisionable PCIe configuration mode to workaround PCIe instability observed on some platforms
  Relevance- AQC113C


1.3.22
5 jan 2022
------------
* Removed default advertisement of GARP and Unsolicited NA in Sleep Proxy mode. The driver can use the new capability mask bit in the offload-control register to control this feature
* Do not wait for 20sec (linklatchuptimeout) to enable Wakeonlinkup if the link is down at the time of suspend/sleep
* Removed the extra link flap on Wake-on-link. And when the system wakes up, initialize the link at the highest possible speed
  Relevance: fast-boot mode


1.3.21
11 nov 2021
------------
* Updated PCIe VPD data
  Relevance: images with PCIe VPD support
* Added support for drvdiag -s in PCIROM v3.1.4 UEFI driver
  Relevance: UEFI


1.3.20
16 oct 2021
------------
 * OEM specific release with specific provisioning


1.3.19
-----------
* Skipped version


1.3.18
02 july 2021
------------
* Fixed the issue of incorrect packet statistics counters reported by fw
* Removed 1G half duplex speed advertisement from the speed capability configuration
* Fixed the invalid speed advertisement 
  Relevance: AQC115C-B1
* Fixed the wrong led behavior at 2.5G speed 
  Relevance: AQC115C


1.3.17
23 apr 2021
-----------
* Added firmware support to disable NCSI via BDP provisioning
* Fixed longer link downtime during os suspend to resume transition in fast-boot mode


1.3.16
13 apr 2021
-----------
* Fixed the TFTP pxe boot failure due to failure to acknowledge Ock/Oack 
  Relevance: FW images with PCIe option rom support


1.3.15
02 apr 2021
-----------
* Added mDNS support
 
 
1.3.14
-----------
* Skipped version


1.3.13
13 feb 2021
-----------
* PHY firmware updated to v6.01.02 for Bx
* PHY change: only enable autoneg timeout when downshift is enabled if downshift was active
* Disable Reed Solomon feature in PHY firmware
* Fixed AQC113 power consumption is higher when cable is removed vs. Attached


1.3.12
08 feb 2021
-----------
* Revert additional fix for mDNS


1.3.11
05 feb 2021
-----------
* Fixed answers in mDNS query differ between when system is in sleep and when the system is awake - additional fix
* Fixed panic case: extended Lom port not open up after secure request was sent


1.3.10
01 feb 2021
-----------
* Fixed AQC113 failed when configured with 10G/full-duplex and came back up with a hot-plug of cable


1.3.9
28 jan 2021
-----------
* Fixed additional fix - remove questions from response (mDNS)


1.3.8
26 jan 2021
-----------
* Fixed AQC113: link became inactive and still fails with hot-plug of cable
* Fixed additional fix for regression test failure
* Fixed AQC113: answers in mDNS query differ between when system is in sleep and when the system is awake
 
 
1.3.7
20 jan 2021
-----------
* Fixed AQC113 ping failed after stress test when system is in sleep
* Fixed [Lom] ping6 extLom is successful after the system panics without pinging basic Lom


1.3.6
10 jan 2021
-----------
* Fixed AQC113 PTP tx ring appears to stop working

	
1.3.5
6 jan 2021
----------
* Fixed AQC113 A0 : built-in became 10base after cable was plugged in switch
* Fixed [Lom] extended mode enabled before 30 sec window
* Fixed [Lom] extended Lom port should be closed after 300 seconds, not 500+ seconds
* Added provision registers 3660 and 3664 in config
* PHY firmware updated to v6.01.01 for Bx


1.3.4
18 dec 2020
-----------
* Fixed AQC113 extended Lom port should be closed after 300 seconds, not 500+ seconds - "shutdown" case
* Fixed AQC113 extended Lom port kept open after Lom unenrolled
* Fixed AQC113 ping6 ext Lom drops packets when system is shutdown (power on failed)


1.3.3
15 dec 2020
-----------
* Fixed AQC113 (both A0/B0) FW does not respond to mDNS query while sleeping
* Fixed AQC113 did not wake after tcp keepalive expires
* PHY firmware updated to v6.0.15


1.3.2
26 nov 2020
-----------
* Fixed AQC113 (both A0/B0) FW does not respond to mDNS query while sleeping (side-issue with uncast request)
* Fixed thermal shutdown functionality is not provisionable
* Remove support for 10m_HD and 100m_HD


1.3.1
09 nov 2020
-----------
* Added support for B1 devices


1.2.3
27 oct 2020
-----------
* Fixed AQC113 Lom0 doesn't generate interrupts for link change events


1.2.1
14 oct 2020
-----------
* Added support for B0 devices


1.1.27
16 sept 2020
------------
* Fixed MAC firmware hang while pc wakeup from suspend state
* Fixed unexpected wake when thunderbolt ethernet adapter is connected
* Fixed regression: ipv4 ping to nic proxy not functioning


1.1.24
22 july 2020
-------------
* Fixed configuration for GPIO
* Fixed calculation read bytes for smbus transaction of Lom
* Fixed interrupt line for Lom if rx packet available
* Fixed Lom interruption pin set to "asserted" after initializing


1.1.19
26 june 2020
-------------
* No changes


1.1.18
25 june 2020
-------------
* Fixed processing of mDNS resource records
Known issue:
* GPIO pin for reset function should be pulled up instead of pulled down


1.1.12
10 june 2020
-------------
Bug fixes:
* Fixed possible datapath stuck after hot-reset
* Fixed link negotiation issue caused after reset for AQC113C 7x7 devices
* Fixed chip stuck which may be caused by soft reset
* Fixed issue preventing chip reset when reset requested while loading ITI


1.1.5
6 may 2020
-----------
Bug fixes:
* Fixed issue that cause PCIe link drops
* Fixed issue when MAC calculated PHY hash before PHY is ready
Enhancements:
* FW provide packet to driver that woke up the system
New features:
* SNR data were added to driver interface


1.0.32
16 march 2020
-------------
Bug fixes:
* PHY reset stability improvements
* Fixed PHY FW stuck caused by fast reset
* Fixed ipv6 offload issue which may prevent receiving fragmented packets
* Fixed VPD corruption caused by multiple VPD read/write operations
Enhancements:
* Hot reset alarm support added
* MSM settings may be applied without link drop-off


1.0.25
14 february 2020
-------------
Bug fixes:
* FW no longer wake host after first link down/up immediately after hibernation
* Fixed SerDes initialization which cause disappearance from PCIe
* Fixed wake on link up
Changes:
* Disabled half-duplex by default for 10M, 100M, 1G speeds


1.0.22
31 january 2020
-------------
Enhancements:
* Disabled half duplex on 10M, 100M, 1G speeds by default
Changes:
* Disabled run-time power optimizations


1.0.19
24 january 2020
-------------
Enhancements:
* Added "coma" power mode
Bug fixes:
* Fixed disappearing from PCI after hibernating
* Fixed data at mDNS response for ipv4 "A" request
* Fixed missing response for mDNS PTR+TXT request
* Fixed chip licensing, which hadn't got settings from efuse high word


1.0.13
10 january 2020
-------------
Enhancements:
* Reduced minimal timeout for TCPKA from 60 to 1 sec
Bug fixes:
* Fixed link up in sleep proxy mode
* Fixed missed ipv6 probes after TCPKA timeout
* Fixed wake up caused by receiving TCPKA probe with wrong flags
* Fixed data at mDNS reply


1.0.11
30 december 2019
-------------
New features:
* Added chip licensing functionality
* Added thermal monitor interface
* Added cable diagnostics
Bug fixes:
* Fixed flow control configuration. Incoming pause frames cause traffic slow down as intended.
* Fixed forced reset of PHY FW caused by MAC FW
* Fixed incorrect data at probe packet which is generated by TCPKA offload
* Fixed invalid src ipv6 at mDNS reply
* VPD mailbox was removed from FW
* Fixed wake up counter
* Fixed resending probes by TCPKA after receiving correct ack on first probe


1.0.3
20 december 2019
-------------
Initial release

Perform the first update

The requirements should be:

• Secure Boot must be disabled in UEFI
• Everything in Windows Defender must be turned off (including the “Driver Block List”)
• Other antivirus software must also be disabled

To update to version 1.5.38, simply download the archive linked above, extract it and run the “startprg.bat” file it contains as an administrator. Once the process is complete, the command prompt windows that opened will close automatically, and you should restart your PC.

Using “kickstart2.exe” you can check before or after the update to see which firmware is currently running on the controller:

Script modifications

To update to version 1.5.45, you need to make changes to the script provided by station-drivers.com, as the IDs listed there are incorrect:

For the modified updater to work with this HP FlexIO v2 module, the four ID blocks must be adjusted to match those of the module. Actually, only two of them need to be changed. To do this, in the “Check if device matches required IDs” section of the “flashUpdateScript.ps1” script file, enter the following:

    # Configuration 1 and 2
    If (($ids[1] -eq "0x1D6A") -and ($ids[3] -eq "0x1043") -and ($ids[4] -eq "0x8890")) {
        If (($ids[2] -eq "0x04C0") -or ($ids[2] -eq "0x14C0")) {
            $deviceSupported = $true
        }
    }

    # Configuration 1 and 2
    If (($ids[1] -eq "0x1D6A") -and ($ids[3] -eq "0x1043") -and ($ids[4] -eq "0x8890")) {
        If (($ids[2] -eq "0x04C0") -or ($ids[2] -eq "0x14C0")) {
            $deviceSupported = $true
        }
    }

by replacing it with:

    # Configuration 1 and 2
    If (($ids[1] -eq "0x1D6A") -and ($ids[3] -eq "0x103C") -and ($ids[4] -eq "0x88FB")) {
        If (($ids[2] -eq "0x04C0") -or ($ids[2] -eq "0x14C0")) {
            $deviceSupported = $true
        }
    }

    # Configuration 1 and 2
    If (($ids[1] -eq "0x1D6A") -and ($ids[3] -eq "0x103C") -and ($ids[4] -eq "0x88FB")) {
        If (($ids[2] -eq "0x04C0") -or ($ids[2] -eq "0x14C0")) {
            $deviceSupported = $true
        }
    }

It’s best to cross-check the IDs with the hardware IDs in Device Manager; they must match. Then save the script, close it, and run the “startprg.bat” file, which is also included.

Perform the update to version 1.5.45

The first thing I noticed was a message saying that the installed driver (from Windows Update) was too old. Once I updated it by installing the newer v3.1.11 version from the Marvell website, the update went through without any problems:

After restarting the PC, everything is working as it should. That was a nerve-wracking process – all that tinkering beforehand would have been for nothing if the update had gone wrong. Now the controller is ready for the future on Debian / Proxmox VE.

Der Beitrag <h5>Mini-PC Server #7: </h5><h3><b>Firmware Update for the Marvell / Aquantia AQC113 Controller</b></h3> erschien zuerst auf flohs blog.

First and foremost, I had to make sure that the module actually worked, both electrically and in terms of software. I’ve read in several places online that there are indeed models (e.g. the ProDesk series) where the module physically fits but doesn’t work on the UEFI side because the necessary drivers don’t seem to be integrated there. To address this, I temporarily replaced the CPU cooler with an old Intel cooler, with some thermal paste in between. This allows the module to fit:

When offline, the network adapter is recognized as such, and Windows automatically installs the appropriate driver once an Internet connection is established. However, the module should also be recognized and function properly with the driver directly from Marvell; moreover, the driver version from Marvell is always more recent (Marvell Public Drivers -> Windows -> AQC113):

Download the drivers from Marvell

Device Manager

Once everything has been installed correctly, you can check in Device Manager to see if everything has been configured or recognized as expected:

You can also learn a lot about the module using HWiNFO:

The module is connected internally via the FlexIO v2’s proprietary slot using two PCI Express 3.0 lanes, which should easily support the full 10 Gbps (one PCIe 3.0 lane theoretically provides 8 GT/s, so two lanes provide 16 GT/s. This theoretically corresponds to 1.969 GB/s, whereas 10 GbE can transfer a maximum of approximately 1.25 GB/s).

In summary, it appears that everything is functioning properly at the electrical and software levels. It is therefore truly “only” a mechanical issue that prevents the revised, newer module from fitting into the Mini PCs. A completely baffling decision on HP’s part.

Mechanical adjustments

On closer inspection, it should be possible to adapt the mounting point. Ideally, this would be a CNC-machined part that incorporates the factory-installed spring pressure beneath the screw to ensure the cooler continues to apply the necessary contact pressure to the CPU. However, I wanted to resolve the issue practically and quickly, so I built an adapter out of an aluminum angle profile, right on the actual component.

First, the cooler needs to be made mountable at all; to do this, I first took stock of what was possible:

The third bolt connection has to go; unfortunately, there’s no way around it. There isn’t much room, but at least there’s some.

Cooler modification

First, I removed the thermal pads to prevent metal shavings from getting inside them. Next, I unscrewed the tinplate cover of the cooler (PH0) to see what the inside looked like. Then I modified the “corner” to fit:

Now, at least, the cooler and the network module can be placed in the right spot:

Build a mount

I used a leftover piece of an aluminum angle profile and modified it accordingly. I had a suitable screw with the “UNC 6#-32” inch thread – which is (unfortunately) common in the IT sector – in my parts stash. This is the same thread used, for example, on the side mounting holes of 3.5-inch hard drives:

To determine the position of the second hole for mounting the cooler, I temporarily screwed the component into the mini PC. On the underside, where the bracket touches the circuit board, I used PVC electrical tape to provide insulation and protection:

The Torx screw facing the cooler is an M3 stainless steel countersunk screw, designed to apply at least some pressure to the processor via the countersunk head. I felt that securing it using the slotted hole in the bracket and a pan-head screw was too “unreliable” – if it slips, nothing will hold it in place. I also filed down the UNC screw at the original mounting point, since the ill-fitting module directly above the screw is unfortunately also full of components from below:

Now I was able to put everything back together and run some initial tests. I used Arctic MX-4 as the thermal interface material to check whether the modification actually works or if the cooler fits so poorly that I need to build a second, more stable version. I applied a layer of white PVC electrical tape to the filed-down screw head, just as I did on the underside of the bracket; a standard sheet of printer paper fits just barely between the SMD components and the PVC. It works, but it’s still very tight:

Now we need to determine whether the cooling capacity is still sufficient so that we can then update the network controller’s firmware first.

Der Beitrag <h5>Mini-PC Server #6: </h5><h3><b>Can’t be done? No way!</b></h3> erschien zuerst auf flohs blog.

This post from ServeTheHome essentially presents the ideal networking solution for a Proxmox mini-PC host: A suitable HP FlexIO v2 module for 10 Gigabit Ethernet, featuring the highly power-efficient AQC113 controller from Marvell / Aquantia (HP part number 56Q71AA), which also supports the intermediate speeds of 2.5 and 5 GbE!

After initial excitement about the existence of this module, disillusionment set in: it’s expensive. Roughly on par with Synology – around €120–150 for a module. On top of that, after reading the comments under this STH post, it became clear that there is a first and second revision of this module, and the second revision – which is now almost exclusively available – NO LONGER fits into the Mini PCs!

What’s really annoying, though, is that the part number (56Q71AA) hasn’t changed at HP; both revisions have the same number. So it’s impossible to specifically buy the first revision, which would simply fit but apparently had certain issues and was therefore revised, without seeing actual photos of the item.

Too bad.

A 10 GbE port and the built-in 1 GbE Ethernet port would be really great. Especially since our connection to the media files also runs through a 10 GbE switch, which is connected to the DiskStation DS1819+, which has also recently been upgraded to 10 GbE. So this module would be technically perfect for our use case; the hard drives and SSDs in the NAS or mini-PC could operate at full capacity for the first time ever.

So what is the problem with the newer version – what exactly doesn’t fit?
The module covers a mounting point on the CPU cooler in such a way that it can no longer be properly secured or even installed at all. Electrically, it should still work, as the connector and mounting screws are in the same position. So it should be a purely mechanical issue.

Well done, HP. But why?

After taking a closer look, I decided to try and get the whole thing working anyway. 10 GbE is just too good to pass up.

At Jacob Elektronik, I found the module as a B-grade item for just under €100 and took the risk of receiving the “wrong” module. That’s exactly what happened – Revision 2 arrived, and it doesn’t fit. Next, I looked for ways to make the whole thing work together anyway.

Der Beitrag <h5>Mini-PC Server #5: </h5><h3><b>The (almost) impossible 10 GbE NIC</b></h3> erschien zuerst auf flohs blog.