Recent content by diversity

this message is really just overhead and not really needed for the thread in the first place; But I felt the need to defend a desktop environment over a server OS like Proxmox. You see, some of us think that root on ZFS should be the default. on any system, any device. period. :) Now that I...

thank you thank you :) I accept graceful the scouts honers badge :) Nah all jokes aside. Thank you for the response. And yes you were correct. It were the non free nvidia drivers that went haywire after the kernel update. I am still not sure though do I really need them? especially given now...

The title sais it all. I am once again in a pickle because like a good trooper I hit update when I am told there are available. Especially when it is security related. But what I would like to learn is how to prevent then the nvidia drivers going bad and I can no longer use them. No longer...

did I miss the part on how to add this script to initramfs? I think this is a cool way to go. Can you please give me a pointer?

I am running Kernel Version Linux 6.8.12-2-pve (2024-09-05T10:03Z) I am going to remove CUDA. I am not using that on the host.

I guess I need to remove the old kernel then :( as I think the repos are configured correctly They are yes? Anyway haha I am such a newb :( How to remove the old kernel? :) I am not sure I dare to do that as I am known to break systems all too well :(

interesting point. I am running PVE 8.2.7. So I am not sure why I got these updates :( I am unsloving this thread and changing the title to reflect the following question. How do I make sure I am using the latest kernel?

after the cups incident I would like to remove as much unneeded stuff as possible. Just now I saw the following (security) updates available Do I need those or are they save to delete? I am running non free drivers though in case that matters.

marked the thread as solved again. it turns out that my laptop running proxmox 8.2.2 did have secure boot enabled yet somehow the boot process states "booting in insecure mode" Also going forward I will try forcing each new installation of proxmox to use grub rather than systemd-boot

Sorry guys to unsolve and necro this thread but I am confused again. My secure boot is disabled and am using UEFI. Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi EDAE-F8E1 is configured with: grub (versions: 6.8.4-3-pve...

I recently installed PVE 8.2 from the new iso available. And as per usual I used a zfs mirror to install on. However this time around the boot loader seems to be grub rather than systemd boot. Last I was aware of is that when using zfs the installer defaults to systemd boot and not grub...

something like this is what you want to see on the host when you run dmesg | grep amdgpu [ 5.084765] amdgpu 0000:06:00.0: enabling device (0006 -> 0007) [ 5.087448] amdgpu 0000:06:00.0: amdgpu: Fetched VBIOS from VFCT [ 5.087458] amdgpu: ATOM BIOS: 113-CEZANNE-017 ATOM BIOS: ***** And...

none of it during your reinstall and getting the amdgpu driver to load correctly on the host. once you have that up and running then it becomes time to think about passing it through

in your case it is best to start over. as disabling IOMMU is not required in order to not blacklist or load vfio drivers. So better use a clean slate and document well what you are doing or use a tutorial from proxmox it self like https://pve.proxmox.com/wiki/PCI(e)_Passthrough

yes