Recent content by CRCinAU

I use Home Assistant and log power consumption via a Zigbee based power switch. Lets me measure the actual consumption being drawn from the socket and not calculated via other methods.

Do you have details on what this is? As I posted, I saw it on an N100 CPU embedded board - which in my case has no proxmox or ubuntu on it - so would like to investigate. EDIT: Ah - just updating to kernel 6.14.2 did the trick.

I tried to report a bug to the `linux-edac` mailing list, but I'm not sure the post made it through. I've got an UP7000 embedded board, and kernel 6.13.x doesn't show this behaviour, but 6.14.1 does. This is using Fedora 41 as the distro - so this certainly isn't a proxmox issue. EDIT: Link to...

Some good news, updating to kernel 6.14 dropped the power usage in my rack by ~15 watts. Two proxmox systems, a 3700x and 5700g CPU. You can see when I rebooted both of them into the 6.14 kernel.

If you read the information on how to use DNSBL's, they *ALL* state not to use public DNS servers to query their services. That's why you have a problem. For further: https://pmg.proxmox.com/wiki/index.php/DNS_server_on_Proxmox_Mail_Gateway

@t.lamprecht Is this expected to work on PMG also? If I attempt to register via pmgconfig, I get the following: # pmgconfig acme account register BuyPass mail@domain.com -directory https://api.buypass.com/acme/directory Attempting to fetch Terms of Service from...

Awesome - that would be great. I found that IPv6 only hosts can't get certs from BuyPass - I've opened a ticket with them to see if they can fix that part.... but other than that, it all seems to work ok :)

Nice! I wasn't aware of this.... I managed to set it up using: pvenode acme account register BuyPass mail@example.invalid -directory https://api.buypass.com/acme/directory Then it appears in the Web UI. I didn't manage to come across this in the documentation... Is it documented?

ping @t.lamprecht / @Stoiko Ivanov - just for visibility....

The BuyPass Go SSL scheme uses the ACME protocol - like LetsEncrypt. They offer free certs with a 180 cert lifetime. Link: https://www.buypass.com/products/tls-ssl-certificates/go-ssl The directory URL is: https://api.buypass.com/acme/directory This should pretty much be a drop-in addition...

Likely not the fixed versions. Follow the instructions from the Intel github link above and see what microcode version you end up with then...

You can also get the microcode directly from: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/

Oh god - I'm a moron hahahaha 9E == 158 - not 9F..... Don't worry about me..... Yeah - that is your CPU hahahah - and no, it will be `0xfa` - which is newer than `0xf4`

Ah - more like upgrade to 8 ;) After a bit of hunting, fixed kernel versions are: * 6.4.9 * 6.1.44 * 5.15.125 * 5.10.189 * 4.19.290, and * 4.14.321 Anything older than these or in a different release branch won't get the kernel patches...

This should translate to 06_9FH - which isn't listed on the Intel site at all. The "Stepping" would be D (in hex = 13 decimal) Thinking further, you might have to wait for a kernel update that adds the path for `/sys/devices/system/cpu/vulnerabilities/gather_data_sampling` to be able to tell...