Make sure you have a backup before starting, especially of /usr/lib/unifi/data/db
.
You will need to iterate though each major version of MongoDB, e.g. 3.6 -> 4.0 -> 4.2 -> 4.4.
Edit the APT repo
nano /etc/apt/sources.list.d/mongodb-org-3.6.list
Comment out the old one and add the new version, you will probably have to use [allow-insecure=yes]
since the certificate has expired and APT doesn’t like that.
#deb [signed-by=/usr/share/keyrings/mongodb-org-server-3.6-archive-keyring.gpg] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 multiverse
deb [allow-insecure=yes] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.0 multiverse
Remember you will need to iterate though every version, so you will need to change the 4.0
to 4.2
, then 4.4
, after each upgrade.
Update APT
apt update
apt upgrade
# You will need this for the next step too:
apt install mongodb-org-shell
Start mongod
with the Unifi database
screen mongod --dbpath /usr/lib/unifi/data/db
Then detach the screen session so it runs in the background: Ctrl+A
, then D
Upgrade the Mongo database
Open a mongo shell, (using mongo shell
) and follow the official upgrade guide.
For example, I did this for version 4.0:
db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
db.adminCommand( { setFeatureCompatibilityVersion: "4.0" } )
db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
Stop mongod
from earlier
screen -r
Then type Ctrl+C
, to stop it.
Restart from the beginning for the next version, until you get to your desired version.
Fix up the APT repo for version 4.4
This will get rid of those GPG/verification errors.
wget -qO- https://www.mongodb.org/static/pgp/server-4.4.asc \
| gpg --dearmor -o /etc/apt/trusted.gpg.d/mongodb-org-server-4.4-archive-keyring.gpg
echo "deb [arch=amd64,arm64 signed-by=/etc/apt/trusted.gpg.d/mongodb-org-server-4.4-archive-keyring.gpg] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 multiverse" \
| tee /etc/apt/sources.list.d/mongodb-org-4.4.list
rm /etc/apt/sources.list.d/mongodb-org-3.6.list
Fix permissions (optional)
If Unifi isn’t starting, and you are getting permission denied errors in the mongo logs (tail -f /var/log/unifi/mongod.log
), you may need to chown
back to the unifi user.
For example:
chown -R unifi:unifi /usr/lib/unifi/data/db
This guide should still work for newer versions of MongoDB, although there are a few exceptions:
confirm
field to the set version command, so you will need to run db.adminCommand( { setFeatureCompatibilityVersion: "7.0", confirm: true } )
instead.Smartctl
.Supported LBA Sizes
, you should hopefully see (at least) two entries, 512
and 4096
. If you only see 512
, then the SSD does not support 4Kn.Namespace 1 Formatted LBA Size:
Will also tell you the LBA that the SSD is currently formatted to, which is usually the default LBA size (unless the user has changed it).There is a great article on the Arch Wiki for formatting as Advanced Format, but mostly:
nvme-cli
installed,nvme id-ns -H /dev/nvme0n1
to double check it supports 4K LBAs (replacing nvme0n1
with the respective device)nvme format --lbaf=1 /dev/nvme0n1
(replacing ‘1
’ with the respective LBA ID)Note: This will destroy any data currently on the drive!
This was quickly thrown together, so it will not be detailed, complete, accurate, or up to date. I will try to keep it updated though.
Drive | Max LBA | Default LBA |
---|---|---|
Western Digital 1TB Black | 4096 | 512 |
Corsair MP600 CORE XT 1TB | 4096 | 512 |
Crucial T700 1TB | 4096 | 512 |
Samsung 1TB 990 Pro | 512 | 512 |
Kingston KC3000 1TB | 512 | 512 |
Crucial P5 Plus 1TB | 512 | 512 |
After a bunch of troubleshooting, I did end up making my monitor present a VRR EDID, which I dumped here, but here’s the things you should modify if you can’t:
get-edid > monitor.bin
extd_timg
to 0x01
, I believe this is required for VRRmin_Vfreq
and max_Vfreq
are correctly set to your monitor’s range (eg. 48-144 Hz)min_Hfreq
should be the same as max_Hfreq
, if it’s not set it to the same as max_Hfreq
(eg. Both 168 kHz)/usr/lib/firmware/edid/
drm.edid_firmware=DP-1:edid/monitor.bin
to your kernel command line, replacing DP-1
with your monitor’s connector name, and monitor.bin
with the EDID file name.You can specify multiple EDIDs in the kernel command line using a comma, eg. drm.edid_firmware=DP-1:edid/monitor1.bin,DP-2:edid/monitor2.bin
Firstly you need to have SR-IOV enabled and working, and also have the VF’s showing up on the host, eg. interfaces similar to ens6f0v2
showing up in ip a
.
Since as you may have noticed, proxmox doesn’t support this in the UI so you’re going to have to add these to the LXC’s config (nano /etc/pve/lxc/<ct-id>.conf
).
lxc.net.0.type: phys
lxc.net.0.link: ens6f0v32 # Replace with your VF interface
lxc.net.0.flags: up
lxc.net.0.ipv4.address: 192.168.0.111/24 # Replace with your IP
lxc.net.0.ipv4.gateway: 192.168.0.1 # Replace with your Gateway
lxc.net.0.name: eth0 # Not needed, but it makes things easier
# lxc.net.0.mtu: 9000 # Enable Jumbo Frames, doesn't work on my NIC
Depending if you’ve already got a network interface in the container, you may need to change the lxc.net.0
to lxc.net.1
or higher. Then you can start the container and your interface should show up in the container’s ip a
:
root@lancache:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
299: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 0a:5b:a7:31:6d:4c brd ff:ff:ff:ff:ff:ff
altname enp129s0f0v32
inet 192.168.0.111/24 brd 0.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2001:<removed>/64 scope global dynamic mngtmpaddr
valid_lft 49244sec preferred_lft 49244sec
inet6 fe80::85b:a7ff:fe31:6d4c/64 scope link
valid_lft forever preferred_lft forever
Sources:
]]>/bin/sh -c '(echo "* * * * * if ! pidof rclone; then rclone sync /data remote:data; fi" | crontab -) && crond -f'
That will add the rclone command to the crontab to run every minute if it’s not already running, then start the cron daemon in the foreground, so the container doesn’t exit.
For example, here’s the full docker command:
docker run \
--volume ~/.config/rclone:/config/rclone \
--volume ~/data:/data:shared \
--user $(id -u):$(id -g) \
--entrypoint '/bin/sh' \
rclone/rclone \
'-c' '(echo "* * * * * if ! pidof rclone; then rclone sync /data remote:data; fi" | crontab -) && crond -f'
Yes, you could also just start the container from cron on the host, but I didn’t like the log spam it created and wanted to keep it all in docker.
]]>Original Title: Fix Bad IPv6 Routing from an ISP Modem on Linux
Linux on my PC has always struggled to use IPv6 when connected to my Telstra Smart Modem (Windows was fine however), and it’s always bugged me but I could never figure out why, I’ve tried different distros, NICs, and for some reason I never thought that my ISP would misconfigure my modem so that it would send bad routes over DHCP until now, but here I am. This was tested on Ubuntu, but should work on any distro with NetworkManager.
ping -6 one.one.one.one
will sometimes work and sometimes not, basically randomly.You must have 2 or more routes, you can check with ip -6 r
or nmcli
:
$ ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2001:db8:feed:f00::/64 dev ens16 proto ra metric 100 pref medium
2001:db8:feed:f00::/56 via fe80::coo1:cafe dev ens16 proto ra metric 100 pref medium
fe80::/64 dev ens16 proto kernel metric 1024 pref medium
default proto ra metric 100 pref medium
nexthop via fe80::coo1:cafe dev ens16 weight 1
nexthop via fe80::dead:beef dev ens16 weight 1
In my case the first one was pingable (it’s also the one with the /56 route), the second was not, so the first one would be the most likely to be the actual default route, which it was in my case.
nmcli connection
to find the connection ID that you need to modify, if you have multiple that are using the same modem, you will need to repeat the solution for all of them. Replace <id>
in the next few commands with the connection ID, if it contains spaces then surround them with quotes eg, "Wired connection 1"
.nmcli connection modify <id> ipv6.ignore-auto-routes yes
This will make the connection ignore IPv6 routes given from DHCP.nmcli connection modify <id> ipv6.routes "::/0 <gateway>"
Replacing nmcli connection modify <id> +ipv6.routes "<subnet>"
so your local subnet doesn’t get routed though your modem, Linux does seem to work it out itself though. (subnet example: 2001:db8:feed:f00::/64
).You might need to restart your connection (systemctl restart NetworkManager
), but once ip -6 r
only shows 1 route, make sure none of the symptoms are still showing; eg. Run ipv6-test.com a few times until you’re comfortable that it’s fixed.
For reference this is the working routes for the example:
$ ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2001:db8:feed:f00::/64 dev ens16 proto static metric 100 pref medium
fe80::/64 dev ens16 proto kernel metric 1024 pref medium
default via fe80::coo1:cafe dev ens16 proto static metric 100 pref medium
The card has drivers for Windows, Linux, FreeBSD, and VMware. After testing, Debian and FreeBSD have the drivers built in, but FreeBSD seemed to not properly setup the NIC sometimes. The latest driver that works on Windows (and possibly other OSs) is version 25.6, newer versions faced a similar problem as FreeBSD.
However an important thing to note, is that my card is missing all of the Intel branding as well as shipping from China in a generic box, possibly meaning this is a Chinese clone of the X520-DA1. I didn’t know they existed at the time, but after searching up my problems with FreeBSD and TrueNAS Core, I found this thread where people are discussing the problems they’ve had.
SR-IOV is a big plus for me, essentially it allows you to allocate the NIC to multiple VMs with full hardware acceleration, without loosing access to it on the host.
The NIC doesn’t have support for RDMA, but it apparently supports “Storage Over Ethernet” giving it iSCSI and NFS acceleration, or according to Intel “The controller enables fast and reliable networked storage with native iSCSI initiator support with Microsoft, Linux, and VMware OSs as well as support for iSCSI remote boot.”
Like most SFP+ NICs, this NIC does not feature Wake-On-LAN.
ethtool
outputSettings for ens1:
Supported ports: [ FIBRE ]
Supported link modes: 10000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: 10000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Auto-negotiation: off
Port: Other
PHYAD: 0
Transceiver: internal
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
iperf3
receive from a SFN5122F[ 5] local 192.168.0.2 port 39348 connected to 192.168.0.31 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 1.14 GBytes 9.82 Gbits/sec 30 1.30 MBytes
[ 5] 1.00-2.00 sec 881 MBytes 7.39 Gbits/sec 308 332 KBytes
[ 5] 2.00-3.00 sec 844 MBytes 7.08 Gbits/sec 125 1.49 MBytes
[ 5] 3.00-4.00 sec 1.11 GBytes 9.54 Gbits/sec 111 804 KBytes
[ 5] 4.00-5.00 sec 706 MBytes 5.92 Gbits/sec 231 1.29 MBytes
[ 5] 5.00-6.00 sec 1.15 GBytes 9.90 Gbits/sec 0 1.43 MBytes
[ 5] 6.00-7.00 sec 1.15 GBytes 9.89 Gbits/sec 31 1.33 MBytes
[ 5] 7.00-8.00 sec 1006 MBytes 8.44 Gbits/sec 182 105 KBytes
[ 5] 8.00-9.00 sec 1014 MBytes 8.50 Gbits/sec 9 1.54 MBytes
[ 5] 9.00-10.00 sec 1.15 GBytes 9.88 Gbits/sec 0 1.54 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 10.1 GBytes 8.64 Gbits/sec 1027 sender
[ 5] 0.00-10.00 sec 10.1 GBytes 8.63 Gbits/sec receiver
iperf3
send to a SFN5122F[ 5] local 192.168.0.31 port 52374 connected to 192.168.0.2 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 1.13 GBytes 9.70 Gbits/sec 0 1.41 MBytes
[ 5] 1.00-2.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.72 MBytes
[ 5] 2.00-3.00 sec 1.13 GBytes 9.70 Gbits/sec 0 1.86 MBytes
[ 5] 3.00-4.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.86 MBytes
[ 5] 4.00-5.00 sec 1.13 GBytes 9.68 Gbits/sec 0 1.86 MBytes
[ 5] 5.00-6.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.86 MBytes
[ 5] 6.00-7.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.86 MBytes
[ 5] 7.00-8.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.86 MBytes
[ 5] 8.00-9.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.86 MBytes
[ 5] 9.00-10.00 sec 1.13 GBytes 9.69 Gbits/sec 0 1.86 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 11.3 GBytes 9.69 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 11.3 GBytes 9.69 Gbits/sec receiver
iperf3
bidir with a SFN5122F[ ID][Role] Interval Transfer Bitrate Retr Cwnd
[ 5][TX-C] 0.00-1.00 sec 1.10 GBytes 9.48 Gbits/sec 0 2.06 MBytes
[ 7][RX-C] 0.00-1.00 sec 1.08 GBytes 9.31 Gbits/sec
[ 5][TX-C] 1.00-2.00 sec 1.03 GBytes 8.82 Gbits/sec 0 2.54 MBytes
[ 7][RX-C] 1.00-2.00 sec 1.06 GBytes 9.11 Gbits/sec
[ 5][TX-C] 2.00-3.00 sec 936 MBytes 7.86 Gbits/sec 211 1.73 MBytes
[ 7][RX-C] 2.00-3.00 sec 1.02 GBytes 8.79 Gbits/sec
[ 5][TX-C] 3.00-4.00 sec 1.12 GBytes 9.59 Gbits/sec 0 1.94 MBytes
[ 7][RX-C] 3.00-4.00 sec 1024 MBytes 8.58 Gbits/sec
[ 5][TX-C] 4.00-5.00 sec 1.11 GBytes 9.56 Gbits/sec 0 2.07 MBytes
[ 7][RX-C] 4.00-5.00 sec 952 MBytes 7.99 Gbits/sec
[ 5][TX-C] 5.00-6.00 sec 1.12 GBytes 9.61 Gbits/sec 0 2.21 MBytes
[ 7][RX-C] 5.00-6.00 sec 971 MBytes 8.15 Gbits/sec
[ 5][TX-C] 6.00-7.00 sec 1.12 GBytes 9.62 Gbits/sec 0 2.24 MBytes
[ 7][RX-C] 6.00-7.00 sec 1021 MBytes 8.57 Gbits/sec
[ 5][TX-C] 7.00-8.00 sec 1.11 GBytes 9.57 Gbits/sec 0 2.25 MBytes
[ 7][RX-C] 7.00-8.00 sec 1.10 GBytes 9.47 Gbits/sec
[ 5][TX-C] 8.00-9.00 sec 1.10 GBytes 9.46 Gbits/sec 0 2.30 MBytes
[ 7][RX-C] 8.00-9.00 sec 977 MBytes 8.19 Gbits/sec
[ 5][TX-C] 9.00-10.00 sec 1.11 GBytes 9.51 Gbits/sec 62 2.01 MBytes
[ 7][RX-C] 9.00-10.00 sec 980 MBytes 8.22 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.00 sec 10.8 GBytes 9.31 Gbits/sec 273 sender
[ 5][TX-C] 0.00-10.00 sec 10.8 GBytes 9.30 Gbits/sec receiver
[ 7][RX-C] 0.00-10.00 sec 10.1 GBytes 8.64 Gbits/sec 168 sender
[ 7][RX-C] 0.00-10.00 sec 10.1 GBytes 8.64 Gbits/sec receiver
Interestingly the performance was greater than 10 Gbps when tested between VMs using SR-IOV. I don’t know how this is possible, but I’m assuming it’s Intel’s Virtual Machine Device Queues (VMDq) at work.
iperf3
[ 5] local 192.168.0.3 port 37114 connected to 192.168.0.2 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 1.77 GBytes 15.2 Gbits/sec 0 3.05 MBytes
[ 5] 1.00-2.00 sec 1.81 GBytes 15.5 Gbits/sec 0 3.05 MBytes
[ 5] 2.00-3.00 sec 1.80 GBytes 15.4 Gbits/sec 0 3.05 MBytes
[ 5] 3.00-4.00 sec 1.80 GBytes 15.5 Gbits/sec 0 3.05 MBytes
[ 5] 4.00-5.00 sec 1.77 GBytes 15.2 Gbits/sec 0 3.05 MBytes
[ 5] 5.00-6.00 sec 1.67 GBytes 14.3 Gbits/sec 172 2.65 MBytes
[ 5] 6.00-7.00 sec 1.62 GBytes 13.9 Gbits/sec 0 2.79 MBytes
[ 5] 7.00-8.00 sec 1.76 GBytes 15.2 Gbits/sec 163 2.62 MBytes
[ 5] 8.00-9.00 sec 1.79 GBytes 15.4 Gbits/sec 0 2.69 MBytes
[ 5] 9.00-10.00 sec 1.79 GBytes 15.4 Gbits/sec 0 2.70 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 17.6 GBytes 15.1 Gbits/sec 335 sender
[ 5] 0.00-10.00 sec 17.6 GBytes 15.1 Gbits/sec receiver
iperf3
bidir[ ID][Role] Interval Transfer Bitrate Retr Cwnd
[ 5][TX-C] 0.00-1.00 sec 1.28 GBytes 11.0 Gbits/sec 0 3.11 MBytes
[ 7][RX-C] 0.00-1.00 sec 417 MBytes 3.50 Gbits/sec
[ 5][TX-C] 1.00-2.00 sec 1.34 GBytes 11.5 Gbits/sec 0 3.11 MBytes
[ 7][RX-C] 1.00-2.00 sec 457 MBytes 3.83 Gbits/sec
[ 5][TX-C] 2.00-3.00 sec 1.15 GBytes 9.91 Gbits/sec 177 2.88 MBytes
[ 7][RX-C] 2.00-3.00 sec 459 MBytes 3.85 Gbits/sec
[ 5][TX-C] 3.00-4.00 sec 1.32 GBytes 11.3 Gbits/sec 0 2.92 MBytes
[ 7][RX-C] 3.00-4.00 sec 413 MBytes 3.46 Gbits/sec
[ 5][TX-C] 4.00-5.00 sec 1.29 GBytes 11.0 Gbits/sec 0 2.94 MBytes
[ 7][RX-C] 4.00-5.00 sec 525 MBytes 4.40 Gbits/sec
[ 5][TX-C] 5.00-6.00 sec 1.11 GBytes 9.54 Gbits/sec 0 2.99 MBytes
[ 7][RX-C] 5.00-6.00 sec 692 MBytes 5.80 Gbits/sec
[ 5][TX-C] 6.00-7.00 sec 1.24 GBytes 10.6 Gbits/sec 0 3.03 MBytes
[ 7][RX-C] 6.00-7.00 sec 577 MBytes 4.84 Gbits/sec
[ 5][TX-C] 7.00-8.00 sec 1.27 GBytes 10.9 Gbits/sec 0 3.03 MBytes
[ 7][RX-C] 7.00-8.00 sec 518 MBytes 4.34 Gbits/sec
[ 5][TX-C] 8.00-9.00 sec 1.35 GBytes 11.6 Gbits/sec 0 3.03 MBytes
[ 7][RX-C] 8.00-9.00 sec 444 MBytes 3.73 Gbits/sec
[ 5][TX-C] 9.00-10.00 sec 1.35 GBytes 11.6 Gbits/sec 0 3.03 MBytes
[ 7][RX-C] 9.00-10.00 sec 454 MBytes 3.81 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval Transfer Bitrate Retr
[ 5][TX-C] 0.00-10.00 sec 12.7 GBytes 10.9 Gbits/sec 177 sender
[ 5][TX-C] 0.00-10.00 sec 12.7 GBytes 10.9 Gbits/sec receiver
[ 7][RX-C] 0.00-10.00 sec 4.84 GBytes 4.16 Gbits/sec 157 sender
[ 7][RX-C] 0.00-10.00 sec 4.84 GBytes 4.16 Gbits/sec receiver
Feature | Aquantia AQC107 | HP NC552SFP | Intel X520-DA1 | Mellanox MCX311A-XCAT EN | Solarflare SFN5122F |
---|---|---|---|---|---|
Ports | 1 | 2 | 1 | 1 | 2 |
Port Type | Ethernet | SFP+ | SFP+ | SFP+ | SFP+ |
Port Speed | 100Mb/1GbE/2.5GbE/5GbE/10GbE | 1GbE/10GbE | 1GbE/10GbE | 1GbE/10GbE | 1GbE/10GbE |
PCIe | PCIe 3.0 x4 | PCIe 2.0 x8 | PCIe 2.0 x8 | PCIe 3.0 x4 | PCIe 2.0 x8 |
SR-IOV | Windows Only1 | Not Working2 | Windows Only1a | ||
Max VFs per Port* | 32 | 63 | 63 | 127 |
Overall it’s probably the best card with fully supported SR-IOV you can get for under US$50.
]]>The Motherboard Drivers and BIOS are available on jginyue.com.cn.
I’ve also made a custom lm-sensors config file for this motherboard.
All of this article is my own findings but Miyconst’s video is worth checking out.
If you experience AER errors in Linux, they can be avoided by disabling PCI-E ASPM, you will need to disable it globally and then go through each IIO Socket setting PCI-E ASPM to Disabled. This is common with other X99 motherboards.
The PCIe x1 slots can easily be cut open using small side cutters to fit a card bigger than x1, but using a bigger card will obstruct an M.2 SSD.
dmidecode
BIOS InformationHandle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 5.11
Release Date: 05/14/2021
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
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: 5.11
If you’re wondering what some of those options even do, looking though the manual of a similar X99 or C600 motherboard can help.
For example here’s the manual for a X10DRi-T4+.
Uninstall preserving data
Remove-AppxPackage -Package "MicrosoftCorporationII.WindowsSubsystemForAndroid_1.7.32815.0_x64__8wekyb3d8bbwe" -PreserveApplicationData
The Package argument should be the same as (Get-AppxPackage -Name "MicrosoftCorporationII.WindowsSubsystemForAndroid*").PackageFullName
Install new version
Add-AppxPackage -Path .\MicrosoftCorporationII.WindowsSubsystemForAndroid_2203.40000.1.0_neutral_~_8wekyb3d8bbwe.Msixbundle
The Path argument should be the same as the file downloaded from store.rg-adguard.net
Done!
]]>URL: https://uk.lxd.images.canonical.com/images/
Click on a distro and version then navigate to arm64/default/<build date>/
Just copy the link for rootfs.tar.xz
and paste it in the ‘Download from URL’ dialog thats in proxmox’s storage then ‘CT Templates’.
If you like you can also copy the SHA-256 Hash for rootfs.tar.xz from SHA256SUMS
and paste it in the ‘Checksum’ input, making sure to select the SHA-256 ‘Hash algorithm’.
Alternatively you can wget it to /var/lib/vz/template/cache/
or /mnt/pve/<storage>/template/cache/
URL: https://jenkins.linuxcontainers.org/view/Images/
When I first checked Canonical only seemed to have Debian, I don’t know why, the folders were there they were just empty?
Click on a distro, click on a version under arm64 & default, copy the link for rootfs.tar.xz
and paste it in the ‘Download from URL’ dialog thats in proxmox’s storage then ‘CT Templates’.
Alternatively you can wget the link to /var/lib/vz/template/cache/
or /mnt/pve/<storage>/template/cache/