Search results

As you were asking: Still everything up and running since the last post.

As per this thread alone, you may come to realize, that it seems to only affect specific cards and revisions. So it would be impossible for proxmox to have ALL the different revisions of the i217/i219-V/-LM cards available. It was mentioned, that such problems seem to occur not only in this...

Using Kernel 6.8.12-11 and this script: https://community-scripts.github.io/ProxmoxVE/scripts?id=post-pve-install. So far, on the I219-LM (Rev 10) it seems to be stable.

Wow, ok, thanks. Way more sophisticated then... Ok, I am now back to .8-11 Kernel and have applied the community script as a first measure. If that ends up the same way as the test with the .14 Kernel, then I will resort to your script. And if that doesn't help either, I will quit Proxmox and...

Being curious: What does your script do different from this community script https://community-scripts.github.io/ProxmoxVE/scripts?id=nic-offloading-fix ?

And BOOM... NIC hang. So it lasted 5 days before Kernel 6.14 decided to join the club and hang up on the NIC.

Thanks for your work, but i just manually installed the kernel and did a reboot. No fancy parameters or anything else. If it turns out in a couple of days, that 6.14 did not improve the stability, I will sure use your script then, so thanks in advance ;-)

So far, since Thursday no hang/freeze with the 6.14.5-1 kernel on the I219-LM Rev 10... lets hope it stays this way.

Running the 6.14.5-1 currently, will keep you posted how this goes ....

I have just installed a new system, rocking a Lenovo Thinkcentre 920q with I219-LM (Rev 10) which has the same problem. I am under the impression that only the LM-Version seems to be affected, not the V? I am really puzzled, that a Thinkcentre 700 (which is 2 years older) has a more modern and...

Unfortunately I am unable to conduct tests with the team then. Two of my systems are in my house, which are working fine with the NICs I219-V (rev 31) and I219-V (rev 21). The affected one is on a remote site, so I am unable to run any tests there, as I would lock myself out if anything goes...

I'd guess that a lot of home labs are running on Intel NUC or some Lenovo/Fujitsu/Dell SFF PC, which are all rocking internal NICs. So no option there to change the NIC, as these systems do not offer a PCI slot to add a different NIC. Hence it would be great if the Team at Proxmox would look...

I am under the impression, that this problem seems to occur only on Intel 217/219 with revisions <21…?

For what it's worth (and may help in the debug process): I have 3 Systems in my Home Lab with Intel 217/219 NICs. Only the 217-LM (Rev04) is affected by freezes. The other systems with 219-V (Rev 21) and 219-V (Rev 31) are working fine with all kernels up to 6.8.12-10-pve (did not test -11 so...

Well, would be great if somebody from the Proxmox Team would take the time to look into this... ?

Hi, as these parameters don't survive a reboot, can somebody maybe provide an interfaces file that sets these parameters? I am not that much of a Linux guy to do this on my own, and the results from AI are different, every time I let them create such a file.... not very reassuring that these...

Es ging ja bei mir seit ewigen Zeiten direkt in der Shell / Konsole, kein Problem. Es geht nur jetzt auf einmal nicht mehr. Letzte Änderung habe ich vor Wochen gemacht, daher kann ich es nicht an einem bestimmten Event oder Update seitens Proxmox festmachen.

Wenn ich irgend einen String von einer anderen Webseite kopiere, kann ich den nicht mehr in die Konsole (Shell) von Proxmox oder einer VM oder eines LXC reinkopieren. Muss alles händisch abschreiben. Hoffe das ist verständlich? Weiss nicht, wie ich es sonst erklären soll?

Hi, ich konnte bislang problemlos im Browser per copy & paste auf die diversen Konsolen zugreifen. Seit neuestem geht das mit keinem Browser mehr, hat sich da was geändert? Es passiert einfach nichts, weder per Maus noch per CTRL-V. Bin aktuell auf 8.2.7. alle Patches installiert, Reboot des...

Ok then, thanks for clarification. Maybe it is time to either replace the FB or try Wireguard instead.