If you'd like to get the LEDs working with armbian, you can run these commands (or similar ones for different indications: echo "r8169-0-100:00:link" > /sys/class/leds/green:lan/trigger echo "stmmac-0:01:link" > /sys/class/leds/green:wan/trigger echo "heartbeat" > /sys/class/leds/red:power/trigger Note that "red:power" is actually the "green:sys" LED. I don't see a way to control the red power led (which is fine, the green:sys is what want to control anyway). Here's all the choices available for "triggers": none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on panic usbport mmc1 rfkill-any rfkill-none r8169-0-100:00:link r8169-0-100:00:10Mbps r8169-0-100:00:100Mbps r8169-0-100:00:1Gbps stmmac-0:01:link stmmac-0:01:10Mbps stmmac-0:01:100Mbps stmmac-0:01:1Gbps netdev "activity" is also a good one for red:power if you prefer that to "heartbeat"

I changed the devicedesc, but game still shows same error. And the launcher shows it is another name. (Nvdia Geforce 6800).Ps: must go bed for now XD.

Not sure its related, but on the MusePi Pro I was getting odd happenings with the PCIe. Adding this to the command line resolved it my case: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

@Curvy Android I don't see meaningful differences in the kernels init msgs for top and bottom PCIe slots - besides that "Buffer I/O error" that leads to the non-working NVME. Besides that, the "faulty power saving mode" line looks familar. I have trouble with my Samsung NVME with that power saving blurb as well. Can you retry with NVME in the top slot and an additional pcie_aspm=off added to your booting SD card in the /boot/extlinux/extlinux.conf file behind append kernel params?

I can see it has already set: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum Mali-G610 MC4