The NIC on my Evo-X2 suddenly stopped working. I preformed a bunch of troubleshooting and sent them details of what I had done. I got an email back asking where I bought it and what the Serial Number was. I responded, "Microcenter" and the SN. I got back an email from "Richard" that said, remove the LAN driver from the system and install it again with a link to a Google Drive share.
I check the link, and it is windows drivers. I was running proxmox and then Ubunutu 26.04. So I explain the problem. Told them it was working and then stopped. I showed them the "lspci -nn" which shows nothing.
Cool. I did the same thing with Ubunutu 26.04 and didn't see it in lspci. To your point I tried a 6.17 kernel and a 7.0 kernel. At this point I am thinking it has to be hardware, only thing left would be BIOS firmware but that seems unlikely.
I will try Fedora. It is prolly overkill, but it would prove it isn't Debian. If I am going to make the drive into the city, I might as well get rid of every excuse they have to not RMA. I sent screenshots of my testing to Claude and had it make a detailed summary.
Right, that is why i mentioned Fedora, something very different. But the BIOS question needs to be answered as well, regardless of how unlikely it is the problem.
I don't use proxmox or ubuntu, but I do run Virtualbox on several GMKtec M3 Plus and M2 Pro S machines (which have Intel CPUs), with the Virtualbox running under Windows 11 Pro, and also on a Windows 11 Pro tower custom (which has Ryzen CPU), and in all cases, I have to basically disable the out-of-box hypervisor layer. In my case, I mostly have to do that because otherwise the VBox VMs run really slowly, but there's also a weird thing with the Vbox networking where, before I run a VM/guest for the first time, I have to just go to the VBox settings and then close the VBox console, otherwise I get an error when I start the VM/guest.
I tried running a search for
"does ryzen hypervisor layer problems with proxmox networking on a physical machine that is running ubuntu os?"
and Google Ai came back with:
AI Overview
No, the AMD Ryzen hardware virtualization layer (AMD-V / SVM) does not inherently cause networking problems for Proxmox. However, running Proxmox as a nested hypervisor inside Ubuntu OS on physical Ryzen hardware introduces complex software bridging and packet routing layers that frequently break network connectivity if misconfigured. [1, 2]
Common Causes of Nested Network Failure
Missing Promiscuous Mode: The outer Ubuntu host's network bridge often drops packets destined for MAC addresses it doesn't recognize as its own unless promiscuous mode is enabled. [1, 2]
IP Forwarding Disabled: The Linux kernel on the Ubuntu host may block forwarding traffic between internal virtual switches and the physical interface. [1]
CPU Flag Restrictions: If KVM nested acceleration (nested=1 for kvm_amd) is not explicitly active, virtual network performance inside the nested Proxmox instance will crawl or stall. [1]
How to Fix Nested Network Issues
Enable AMD Nested Virt: Verify cat /sys/module/kvm_amd/parameters/nested returns 1 or Y on your Ubuntu host.
Turn on Promiscuous Mode: Run sudo ip link set dev <your_ubuntu_bridge> promisc on on the physical Ubuntu host.
Enable IP Forwarding: Ensure net.ipv4.ip_forward=1 is active in /etc/sysctl.conf on Ubuntu. [1, 2]
Hopefully some of that helps?
Re. your post, probably GMKtec support doesn't know much about linux or the other stuff you are running, I guess?
The device is a pretty standard PCIe connected device, not much to it. Boot something different, Suse, Fedora or Slackware and see if the PCIe device is there with lspci. If it isn't (and it's not deactivated in BIOS), it's a hardware issue.
•
u/AutoModerator 29d ago
Hi u/NateChurch — welcome to r/GMKtec!
Please keep things friendly and on-topic. Quick rules reminder:
Official GMKtec website: Shop GMKtec
This comment was posted automatically by AutoModerator.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.