Recent content by gabrioth

If anyone finds this thread attempting to do what I was trying to do: I never found a way to get OS-prober to notice PVE's boot-partition, but I did find a way to do what was my initial wish. I used "efibootmgr" to list all partitions and their UUIDs, as well as the paths to their bootable...

I would most like to not replace GRUB as the main bootloader for my production machine if possible. But the tip on efibootmgr was actually good, at least helps in getting correct info on where the boot binary is and on which UUID etc :)

Well... I have one cluster and a few standalone setups in my home that run proper PVE. This specific one is going to be used as a lab setup only, using some hardware I don't have in the other setups and cannot really afford to buy for them either. (especially now, with the component crisis...

I run a dual-boot setup on my main workstation for testing purposes. My main driver is a fully updated Manjaro Linux. I boot said Manjaro installation using GRUB installed to the NVMe0-drive's EFI-partition. Proxmox is installed onto NVMe1. When running "update-grub" the bootloaders of all...

Is there any application/package you can install into a container or VM to make the virtual/remote console work just like it does when interacting with the virtual console of the server itself? I know how to set up a virtual RS232/serial port on a VM/container and use xterm.js, but that terminal...

It is not related to the monitor. If I only connect that (through HDMI) everything is fine. It's when I connect a mouse and/or keyboard, through the switch, the messages start. All pointing devices are USB. No touch screen. The receiver I'm using is a Logitech Logi Bolt with a keyboard and...

I have my three proxmox machines (7.4-16 and 8.0.4) connected to a KVM-switch made by Delock. Which gives them access to my monitor and a receiver for Logitech keyboard/mouse. Whenever I switch to a machine, that machine starts spamming the below message in both syslog: "Oct 09 22:29:58 proxmox...

Replies like this one is why I always post the answers to my own questions on forums :D

Anyone else reading this and having the same problem try the following and retry installation after each step: 1. Make absolutely sure SR-IOV is OFF on all four interfaces. 2. Update your BIOS 3. Make absolutely sure SR-IOV is OFF on all four interfaces. 4. Update your NIC's firmware 5. Make...

Yes, I upgraded it to version 20 from https://www.dell.com/support/home/en-in/drivers/driversdetails?driverid=23wp1 (the cards were bought from Dell and had version 19 on them)

I tried some other linux distributions on the same machine, Ubuntu 22.04LTS and Manjaro 20.1. None of them recognize the i350 as network interfaces. Windows 10 recognizes them and they are assigned IP-adresses and can communicate fine. Pfsense also works fine. NomadBSD also works fine.

I tried the 7.2 and 7.1 ISOs, to no avail. Still only the onboard interface gets detected as a NIC. I also installed pfsense on the machine; where all interfaces worked and recieved IP addresses from the DHCP, so it's definitely a driver issue with Debian/Proxmox (or linux itself. Gonna try with...

Good tip, SInce it's a new system I'll download the 7.2 ISO and install that to see if it works. The cards check out according to that guide you linked to. Also, they are ordered directly from Dell europe (placed the order inside our production order system myself) so recieving counterfeits...

In a newly installed system "ip a" only lists one NIC aside from the virtual devices: 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000 link/ether 1c:87:2c:46:73:89 brd ff:ff:ff:ff:ff:ff That is the bridge port to my vmbr0...

Efter a reboot for maintenance, I enabled the job again yesterday, and tonight it started syncing, so probably just some temporary hiccup.