Recent content by Taylan

I'm glad, you're welcome!

You are booting with grub and not EFI. You have to add those lines into your `/etc/default/grub`. Don't forget to run `update-grub` so it appends its content to all linux entries in/boot/grub/grub.cfg. Check here for more information: https://pve.proxmox.com/wiki/Host_Bootloader

Are you booting via "proxmox-boot-tool"? What is the output of following? proxmox-boot-tool status And in the meantime, please post your content of your `/etc/kernel/cmdline`.

It still works here. It's probably another issue. Is this a cloud server? Do they have some kind of remoting software for IPMI? Maybe ask them or double check your cmdline file and don't forget to create the initram with the new information. update-initramfs -u -k all pve-efiboot-tool refresh...

Ah sorry then. I think I'm already on UEFI with proxmox-boot-tool: root@Proxmox:~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with uefi DCD8-7B59 is configured with: uefi (versions: 6.2.16-19-pve, 6.5.11-4-pve...

Thanks for the heads up!

I have a similar issue, with a twist. I didn't reboot after upgrading. While upgrading to proxmox-kernel-6.5.11-6-pve-signed I received the error "/usr/sbin/grub-probe: error: compression algorithm inherit not supported" I have following logs also: Nov 29 14:38:11 Proxmox systemd[1]...

This is sadly not fixed. With today's update "proxmox-kernel-6.5.11-6-pve-signed" the issue still persist: "/usr/sbin/grub-probe: error: compression algorithm inherit not supported" ... Copying kernel and creating boot-entry for 6.5.11-6-pve run-parts: executing...

Hello everyone, after upgrading the package `zfsutils-linux/stable 2.2.0-pve3` I get following errors with `arc_summary`: # arc_summary ------------------------------------------------------------------------ ZFS Subsystem Report Sun Nov 19 12:32:54 2023 Linux...

You're welcome, but, if you aren't sure, what every piece of that config does, you shouldn't just copy&paste it. So try to understand, would be my advise. You trusted some stranger on the internet, so trust again, when I say, sure, it'll be ok ;)

Yes and then reboot.

sorry, I didn't pay enough attention. Those lines should be added to kernel cmdline: So the workaround is this: echo " i915.fastboot=1 drm.edid_firmware=edid/1280x1024.bin" >> /etc/kernel/cmdline update-initramfs -u -k all && pve-efiboot-tool refresh My config looks like this: # cat...

I have the same cpu, it has an intel igpu, so the config above should just work as it is.

Yes, but the config is for intel igpu. Don't forget to do this afterwards: update-initramfs -u -k all

Until the bug gets fixed, the workaround described in edit2 is the way to go.