Recent content by celemine1gig

How about a "apt update && apt install proxmox-kernel-6.14"? Sorry, but if you have no clue what you are doing, concerning Linux, then buying the latest hardware and playing with that is most likely the worst idea. Kind of funny and sad at the same time. P.S.: As the software is free of charge...

As you resurrected this old thread, here is one thing, that is missing in all this discussion: The method of updating the Microcode at runtime on OS-level CANNOT work for all scenarios. In other words: The only real way to update Microcode in a way, so that it can work like intended, is through...

You have "vmbr0", the first "Linux Bridge", that is actually configured. Nothing else is done. So what do you expect? If you do not set it up in any way, how should it automagically work? So, depending on what you would like to do, it might make sense to add additional devices to the already...

If what mr44er posted should not apply (I would check that first), then have a look at the power supply. Keep in mind, that every disk is drawing short-circuit current the moment the motor needs to start turning, after having fully stopped. This can create considerable peaks in current...

If we ignore your language fu**-up for a moment, this might be helpful: https://forum.proxmox.com/threads/possible-to-change-proxmox-default-port-now.111102/

Kleiner Tip: Wenn du bei solchen Problemen Hilfe willst, dann hilft es nur bedingt, wenn du nur die Symptome beschreibst, aber keinem verrätst auf welcher Hardware du dieses Verhalten beobachtest. ;-)

https://www.thomas-krenn.com/de/wiki/AMD_EPYC_Server_mit_Ubuntu_-_SATA_Hot-Swap_aktivieren Das dürfte eventuell helfen.

Nachdem das hier im deutschsprachigen Bereich steht, hier die Antwort diesmal auf Deutsch: Jede CPU hat eine vom Hersteller vorgegebene "Zielleistung" (TDP =Thermal Design Power), für die interne Power-Logik. Diese Angabe entscheidet darüber wie lange gewisse Taktstufen gehalten werden können...

This was not "thermal"-throttling, but due to the power-limit setting. Thermals were absolutely fine. However, the overall threshold for the power-consumption over a certain amount of time was exceeded. That is why the system throttled the CPU clock. It tried to still stay inside the defined...

NFS, SMB,...?

The easiest probably would be to reformat the whole eMMC as one big single pSLC space. So, no separate areas with different configs, but everything in pSLC. As you might have seen in the linked documents, the eMMC can already tell you, what the resulting "Max Enhanced Area Size" would be. If we...

Und, wie sieht es eine Woche später aus? Läuft's (noch)?

Man kann das Ganze auch per Skript, manuell einstellen. Also nur für deinen Netzwerk-Controller ASPM deaktivieren. Zur Laufzeit und ganz ohne BIOS. Beispielhaft hier: https://wireless.docs.kernel.org/en/latest/en/users/documentation/aspm.html Startend mit dem Abschnitt "How to find the Link...

Ja, "pcie_aspm=off" sollte ASPM deaktivieren, egal was die BIOS-Settings sagen. Gilt dann systemweit. Kleines aber: Je nach Linux-Kernel Version kann da schonmal was seltsam laufen. Linux hat ja eine recht hohe Anzahl an Workarounds und BIOS-unabhängigen Optimierungen. Also Versuch macht kluch.

"Native ASPM" ist ein Flag in der BIOS ACPI FADT/FACP Table (siehe hier https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/05_ACPI_Software_Programming_Model/ACPI_Software_Programming_Model.html und auch http://smackerelofopinion.blogspot.com/2011/03/making-sense-of-pcie-aspm.html ). Das sagt grob...