To flash the controller with the correct firmware, you must have access to a Windows machine.
⚠️ Do NOT use version241224-0000-00!With this version, starting the VM in Proxmox will hang indefinitely. The VM start command never completes, and you're forced to hard reset the Proxmox host. This is also the version reporting 32 SATA Devices instead of 6.
| #!/bin/bash | |
| set +exo pipefail | |
| # Call with: | |
| # wget -qO - https://gist.githubusercontent.com/mietzen/b05f050c774450247a4d1512ffaa1243/raw/proxmox-debian-ct-template-setup.sh | \ | |
| # | bash /dev/stdin $YOUR_USER_NAME | |
| ## Install deps | |
| apt-get update |
| #!/bin/bash | |
| set +exo pipefail | |
| ## Install Cloud-Init | |
| apt-get update | |
| apt-get install cloud-init openssh-server -y | |
| ## Set grub timeout to 1 sec | |
| sed -i 's/^GRUB_TIMEOUT=.*/GRUB_TIMEOUT=1/' /etc/default/grub |
| #!/bin/python3 | |
| import sys | |
| import subprocess | |
| import os | |
| import json | |
| import time | |
| def read_in_chunks(file_path, chunk_size): | |
| """Reads a file in chunks of the specified size.""" |
Today, I was painfully reminded to RTFM before upgrading. With the upgrade from Proxmox 8.1 to 8.2, there were some breaking changes:
Kernel: Change in Network Interface Names
Upgrading kernels always carries the risk of network interface names changing, which can lead to invalid network configurations after a reboot. In this case, you must either update the network configuration to reflect the name changes, or pin the network interface to its name beforehand.
See the reference documentation on how to pin the interface names based on MAC Addresses.
I like to use a custom debian container image, that has some tools installed and a non root user setup. I then dump and export the rootfs as container template.
To keep this template updated, I wrote this script.
This script works for all distribitions, you just have to update the variables:
#!/bin/bash
I always had the problem that synology doesn't let us auto update 3rd party packages such as the ones from SynoCommunity, so I wrote a shell script to auto update SynoCommunity Packages:
#! /bin/bash -e
PATH="/bin:/usr/syno/bin:${PATH}"
SYSTEM_PKGS=$(synopkg checkupdateall)
ONLY do this if you understand what this script does and when you are sure that this method is applicable to your card!!!
I'm not responsible for your doings! You are flashing the firmware of your ethernet card, in the worst case you endup with a soft- or even hardbricked card! Also this might void your warrenty.
Having said this, if you are uncertain if this will work for your card be sure to dump the ROM with a RPI, RPI Pico or 3.3v moded SPI-Flash Programmer:
I had trouble getting my i7-8700 65W to work in my m720q with a 65W PSU. It was working fine in Windows, but was throttling down first to 20 Watt, then to 15, 10, and finally to 7 Watt, which resulted in a maximum clock speed of 800 MHz.
The main problem seems to be a mix of crappy firmware settings from Lenovo/Intel (Reddit Post) and the weak power supply.
To fix this problem, we have to install some tools, and for them to work, you have to make sure that secure boot is OFF; otherwise, the kernel doesn't allow you to set the CPU power limits. The easiest way is to install in legacy mode; therefore, you need to disable secure boot and enable CSM in the BIOS, select legacy boot preferred.
| #!/usr/bin/env bash | |
| help () { | |
| echo "usage: ./bump-version version_number [major/minor/bug]" | |
| } | |
| # Check input remove prepending 'v' | |
| if grep -q -c -E '^v?[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$' <<< ${1}; then | |
| version=$(sed 's/^.\{1\}//g' <<< ${1}) | |
| else |