Recent content by caramb

Hello, After upgrading the microcode, I did not make any change to the BIOS settings. As far as I remember, it is running the BIOS defaults. As you can see in my previous post, I have C-states enabled. It is common pratice to try disabling some C-state in case of stability problems ; especially...

Hi there, Small contribution to this thread. Running Proxmox on a Odroid H3 (Intel N5105). 4 x Intel(R) Celeron(R) N5105 @ 2.00GHz (1 Socket) Linux 6.2.6-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.6-1 (2023-03-14T17:08Z) GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on pcie_aspm.policy=performance...

Hi, I reply to myself to provide additional details. Today, I just figured out that the proxmox node did not properly recover from the "fencing while updating" situation. Trying to perform a regular (apt) upgrade of the node issues an error : Starting system upgrade: apt-get dist-upgrade E...

Hi there, I just would like to suggest to reconsider the severity of this issue as it may lead to some kind of disaster in some setups. As already stated by others, for some reason, the update considers not necessary to restart open-vswitch after upgrading it : Setting up openvswitch-switch...

Thank you Tom. If the fix was not released yet, some magic happened here as the warning is gone. Running a manual deep-scrub perharps changed something in the API response you base the UI on ? Anyway, that is not important ; just surprising to me. (and forgot to mention my homelab uses the...

Hummm... just figured out the oudated warning disppareared on my Promox nodes. It was there this morning ; it is not anymore. I performed a package update this morning ; some packages were updated but I did not notice anything relevant to the problem. I'm currently running version ...

Hello, I do confirm bug is still in pve-manager 7.0-14+1 At least we know it is a UI bug ; thus purely comestic and not harmful.

Good job Rad_00 ! Frankly, you went the hard way (compared to temporarily using some crapy usb network adapter during the install process) Happy my work helped... even if, to be honest, it is not completely clear to me how you managed to bootstrap the missing driver issue directly from the...

Hi Rad_00, Whenever you want to stick with kernel 5.4, I'm currently "maintaining" a dirty backport of kernel 5.9 driver for RTL8125/8125B. Please, check here : https://forum.odroid.com/viewtopic.php?f=168&t=40598 I'm providing ready-to-load modules for proxmox from 5.4.65-1-pve through...

Hi there, I'm running a Proxmox homelab cluster on 2 Odroid-H2+ SBC + 1 HP Microserver Gen8. The current kernel module (r8169) from the source tree does not support HW revision B of chipset 8125. Realtek kernel module (r8125) for this chip is broken and perform awfully when 2 8125B talk to each...