GMKTEC K12 | Ryzen 7 H 255 | Problem with IGPU

just for testing i updated to 2.02. didnt like it much. ReBAR as a setting is gone and you cant set the fans to fixed values anymore. only dynamic fan curves are supported. annoying for a "server", but valid for desktops i guess.

i downgraded to 1.07 again and will stay there for now.
 
Hi,
It turns out that it is indeed the RAM's fault :)
In Poland, it's Sunday, 1:49 a.m., already 5 days after changing the RAM, and everything is working beautifully now. At first, I thought it was the fault of the drives and the PCIe, but it wasn't.
So it turns out that this GMKTEC K12 doesn't like such differences. I transferred the 48GB and 16GB to my gaming laptop and everything works, so it's the fault of the GMKTEC itself.

Translated with DeepL.com (free version)
 
not sure if its gmktecs fault as such. it might just be good old compatibility between components.
i have had this in the past that certain memory modules (ddr4-3600 in that case) worked fine in an intel machine, but the amd machine didnt like it at all.
but that was not related to modulesize at all, just that those particular modules introduced instability when used in an amd machine.

on minipcs manufacturers sometimes tell you to avoid certain memory brands.
my topton-machine here for example says not to use hyperx fury modules because they are not 100% compatible with the mainboard.

havent seen such a warning from gmktec, but its possible that there are modules that dont work properly.
 
beisser said:
not sure if its gmktecs fault as such. it might just be good old compatibility between components.
i have had this in the past that certain memory modules (ddr4-3600 in that case) worked fine in an intel machine, but the amd machine didnt like it at all.
but that was not related to modulesize at all, just that those particular modules introduced instability when used in an amd machine.

on minipcs manufacturers sometimes tell you to avoid certain memory brands.
my topton-machine here for example says not to use hyperx fury modules because they are not 100% compatible with the mainboard.

havent seen such a warning from gmktec, but its possible that there are modules that dont work properly.
Click to expand...
You may be right about the Kingston Furry, because I've had the same problem more than once, but the strangest thing is that this is my third GMKTEC K12 mini PC, and this configuration works in the others, only in this model it didn't.
But never mind, you know, I found somewhere after assembling laptops for people another 3x48GB 5600MHz, so I threw them in and now I have a full cluster in Proxmox
48 cores, 288 RAM, and 2x4TB WD RED m2 in each server.
Time to play Minecraft :)
 
  • Like
Reactions: beisser
both me and @Glupikocz got it working.

for me its working until i restart the vm from proxmox, then it goes haywire, but as long as i restart the vm from inside windows it works fine. i use it daily.


​

​

 
BIOS and similar items may not be redistributed unless explicitly provided by the manufacturer.
 
I've struggled getting a copy of the 1.07 BIOS from their Google Drive -- is there anything that would prevent me from getting this working with the 1.06 BIOS which is currently installed (and would someone be as kind to provide a copy of 1.07?)
 
beisser said:
he likely is struggling with the stupid google drive quota where downloads are limited.
i ran into it several times myself.

i sent @avluis86 a pm with a link (for me the download from google drive worked btw, just tested).
Click to expand...
You are correct, yes -- tried copy/pasting as many guides suggest (and GMK) but that was failing as well.
Highly appreciate the link and yep, after all that struggling it just worked this morning o_O
 
Last edited:
Just updating I got igpu passthru working also
Bios 2.03, vbios 2.02 that i extracted myself
Args from beisser’s post thanks
 
I have passed through a second nvme which got assigned to PCI 05:00.0 and after setting the romfile to AMDGopDriver_8745hs.rom (and NOT AMDGopDriver_8845hs.rom!) I got for the first time a HDMI DisplayLink output on my monitor with this setup:

agent: 1
args: -cpu 'host,+hv-emsr-bitmap,+hv-frequencies,+hv-reenlightenment,+hv-tlbflush-direct,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vendor_id=intel,hv_vpindex,-hypervisor,+invtsc,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,host-phys-bits=true'
bios: ovmf
boot: order=ide2
cores: 2
hostpci0: 0000:66:00.0,pcie=1,romfile=vbios_7xxx.bin,x-vga=1
hostpci1: 0000:66:00.1,pcie=1,romfile=AMDGopDriver_8745hs.rom
hostpci2: 0000:05:00.0,pcie=1,rombar=0
ide2: none,media=cdrom
localtime: 0
machine: q35
memory: 8192
meta: creation-qemu=11.0.0,ctime=1781373753
name: BazziteVM
net0: virtio=BC:24:11:92:EE:F4,bridge=vmbr0
numa: 0
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=524cd184-c115-463a-8085-dacbaee096b6
sockets: 1
vga: none
vmgenid: 0f7ec33c-c241-433d-b4c9-1f966dbe0096

Now I'm going to check some distributions (not using Windoof).
 
Last edited:
You must log in or register to reply here.
Top Bottom
Back