[SOLVED] Issues installing Proxmox on GMKtec AMD G10

[Gson]

New here, so apologies for the noob questions in advance.

I’ve been trying to get Proxmox running on a GMKtec AMD nucbox G10 mini PC.

Ethernet didn’t worked when booting straight to proxmox, so I installed Debian 12 with non-free firmware, got network access, and then installed the Ethernet driver for GMKtec (Realtek r8125 DKMS). Then I installed Proxmox VE on top of Debian.

I’ve got internet connection, but I’m unable to ping, ssh, or access the server, however I am able to ping my laptop (on the same networking) as well as 8.8.8.8 etc..

I thought installing the ethernet port driver was the final puzzle piece, but I guess not. Really appreciate any help on next steps/debugging this.

Happy to send any logs/outputs.

 

[Gson]

Solved it! I worked through a number of networking and system-level issues getting Proxmox VE running on my GMKtec NucBox G10.

To get the Ethernet driver working I installed the Realtek r8125-dkms driver manually from the awesometic GitHub repo. That got the RTL8125 NIC recognized and functional, showing up as eno1. However, I was still unable to SSH or reach the Proxmox UI from my laptop.

I checked ethtool eno1, which showed the Ethernet was up, but only linking at 100 Mbps — likely a limitation of the cable or intermediate device.

That’s when I went back to A/B testing the router. The server was plugged into a GL.iNet router, not directly into the main router. I had originally configured the travel router to allow local device discovery and pass-through, and it worked for other devices like the Philips Hue Bridge. But for some reason, Proxmox traffic wasn’t routing properly through it.

This morning, I swapped out the Ethernet cable and plugged the server directly into my main router. After that, SSH immediately worked, and I was able to access the Proxmox UI from my browser using https://192.168.1.xxx:8006. I'm still a bit unsure why it worked this time and not yesterday when I had exactly the same setup, nonetheless, hopefully it's helpful to someone.

On the system side, I also had to fix a broken pve-cluster service which was preventing the Proxmox web interface from loading properly. The root cause was that pmxcfs couldn’t resolve the hostname pve to a valid IP address.

The system didn’t consider that sufficient for binding a non-loopback address. I added this line:

192.168.1.XXX pve

After that, pve-cluster and pveproxy came up properly, and the web interface was fully operational.

 

[plamen_f]

Solved it! I worked through a number of networking and system-level issues getting Proxmox VE running on my GMKtec NucBox G10.

To get the Ethernet driver working I installed the Realtek r8125-dkms driver manually from the awesometic GitHub repo. That got the RTL8125 NIC recognized and functional, showing up as eno1. However, I was still unable to SSH or reach the Proxmox UI from my laptop.

I checked ethtool eno1, which showed the Ethernet was up, but only linking at 100 Mbps — likely a limitation of the cable or intermediate device.

That’s when I went back to A/B testing the router. The server was plugged into a GL.iNet router, not directly into the main router. I had originally configured the travel router to allow local device discovery and pass-through, and it worked for other devices like the Philips Hue Bridge. But for some reason, Proxmox traffic wasn’t routing properly through it.

This morning, I swapped out the Ethernet cable and plugged the server directly into my main router. After that, SSH immediately worked, and I was able to access the Proxmox UI from my browser using https://192.168.1.xxx:8006. I'm still a bit unsure why it worked this time and not yesterday when I had exactly the same setup, nonetheless, hopefully it's helpful to someone.

On the system side, I also had to fix a broken pve-cluster service which was preventing the Proxmox web interface from loading properly. The root cause was that pmxcfs couldn’t resolve the hostname pve to a valid IP address.

The system didn’t consider that sufficient for binding a non-loopback address. I added this line:

192.168.1.XXX pve

After that, pve-cluster and pveproxy came up properly, and the web interface was fully operational.

Do you have any other issues with G10 under Proxmox.
Currently I am running it for 10 days and this evening it restarted for the 4-th time in this 10 days period.
But after restart it stays in bios screen and no matter you are set up - only a full restart (with removing power cable) can extract it form bios screen and start it normal.