In order to utilize GTR Pro full potential for AI applications, I’m required to install Ubuntu 24.04 along with AMD ROCm (which is not supported on windows 11). After installing Ubuntu, I noticed a recurring problem with the built in ethernet adapters. Whenever the computer encounters load on the GPU, the ethernet card would crash and the only way to get it to work again is to unplug my machine from power. It seems that other users of GTR Pro are also experiencing this issue: https://community.intel.com/t5/Ethernet-Products/Intel-Ethernet-Controller-E610-Firmware-Recovery-Mode-Under-Load/td-p/1719424 Linux Kernel is 24.04c oem as required by ROCm Things I’ve tried: Installing the ubuntu LAN driver version 6.0.6 provided in the beelink driver package - fails under ubuntu 24.04 Installing the latest LAN driver from Intel website - The ethernet card still crashes Installing an older version (6.1.4) - The ethernet card still crashes. Please advise as this makes the machine unusable as a server under Linux. It happens on gaming distributions such as Bazzite, as well.

I am on manjaro linux, and it seems like you can just use the intel default package for nvm updates for the 610 NIC ( https://www.intel.com/content/www/us/en/download/845408/non-volatile-memory-nvm-update-package-for-intel-ethernet-e610-series-linux.html ) to flash it to 1.30. Just make sure you can see the nic with lspci before you start (if not, coldstart).

f70w I attempted the above, no luck unfortunately. Beelink is working on a solution

Sorry for the trouble. Currently, the Lan issue of the GTR9 395 persists, and its root cause lies in the Ethernet driver. As of now, there is no new driver available to resolve the problem of the Intel E610. The current workarounds are as follows: Perform a physical power-off and re-plug the power cable. We suggest you to to use a Wi-Fi connection instead. A complete resolution to this issue will only be possible once a new driver is released

Beelink CS-George I was just about to place an order for this device… after reading these posts and the implicated lack of urgency in your response (not even and indicated time-line) to this major issue. I’ll hold off and quite likely look at the Framework product.

Oh, and the fact that your driver web page is inaccessible…

Welly Hi there, it is accessible, here is the link https://dr.bee-link.cn/?dir=uploads%2FGTR%2FGTR9-395

Welly Sorry for the inconvenience. We already urge Intel to develop a good driver. We will update it once it is released.

Beelink CS-George I will keep an eye out for this news.

Thanks for the update but what’s the confidence level that the new driver will resolve this issue? Are you able to reproduce it? What is the root cause? Could you share more details? Thank you very much.

LEPT Thank you for your understanding and patience. decryp7 Thank you for your response. The issue stems from missing drivers, which have caused the Ethernet functionality to become inoperable. New drivers are currently under development.

GTR 9 Pro Ethernet Malfunction under load

jotapesse

tbocek Thanks! Could you please also try to use the Furmark 2 benchmark and push the GPU 100% for several minutes and confirm if you are able to trigger it and get the same results? Let us know please.

ivangotoy

jotapesse
Cannot trigger this by running furmark with many different options, unigine superposition also does not trigger it on my end but at least gzdoom with vulkan renderer + special doom2 mods works like a charm 🤣

decryp7

jotapesse

I don’t quite understand what you are trying to do. I already pointed out it is not reproducible using furmark and also share my scenario with ollama which you can use to reproduce it. 😄

ivangotoy

ivangotoy
p.s. when changing game renderer from vulkan to “opengl es” game is playable without triggering nic fw crash for 5 min. as a test

jotapesse

decryp7 I’m trying to understand everything, establish an easy Linux common reproducible process for all and understand in what conditions the issues can be triggered or not. Different people reported different experiences. Not everyone uses LLMs as you have. Specifically regarding Furmark 2 I’m trying to establish if it doesn’t trigger it for everyone or just for me or the case you reported and why - because it clearly stresses the GPU 100% - so it’s odd to not trigger it. Or maybe it can trigger it on certain conditions (what and why?).

Reported triggers:

LLM: Open WebUI Chat (gpt-oss:20b);
LLM: llama.cpp (several models);
3D Game: Doom Runner (gzdoom/doom2.wad - Vulkan);
WebApp: Opening many animated GIFs on Discord;

jotapesse

decryp7 Hi! I really can’t reproduce this on Linux. I tested it on LM Studio 0.3.28 with openai/gpt-oss-120B (vulkan) on NixOS Linux (kernel 6.17.1) with multiple chat messages with Reasoning Effort: High. No issues at all. All good!

decryp7

Hi All,
Can you try to enable ECO mode in Bios and try again?
Thank you very much.

tbocek

I’m just wondering if Beelink is looking into this issue. Any information is appreciated about the progress. I read somewhere that Beelink needs to wait for new firmware from Intel. So, are you still waiting? Did Intel acknowledge the bug, can you push Intel to deliver faster?

decryp7

tbocek

Hi,

Can you try to enable Eco mode and try to reproduce the phenomenon again? It looks like after I enabled Eco mode, the problem disappears. It can be a workaround at least until the driver is released.

tbocek

decryp7 ohhhh, let me try… Eco mode was the first thing I disabled.

ivangotoy

decryp7
Hi, for me eco mode enable gave me just 4-5 more minutes game time before NIC fw crashed. I can’t rely on that as a temporary mitigation.

tbocek

decryp7 Nice, for my llama.cpp case, I have not seen the NIC crash, and I running for some time now. So, for me the ECO mode has a positive effect. I’ll try to run it for longer and report back.

Edit: I did some more testing, LLM, transcoding, and no NIC issues so far…
Edit2: Nope, it crashed, it just took longer.

decryp7

tbocek thank you very much. It looks like this cannot workaround the problem temporarily.

jotapesse

I’d like to report that I’m experiencing the same two issues others have mentioned:
amdgpu flip_done timed out / commit wait errors

Here are some of the recurring log entries I see in dmesg:

amdgpu 0000:c4:00.0: [drm] ERROR [CRTC:86:crtc-0] flip_done timed out
amdgpu 0000:c4:00.0: [drm] ERROR flip_done timed out
amdgpu 0000:c4:00.0: [drm] ERROR [CRTC:86:crtc-0] commit wait timed out
amdgpu 0000:c4:00.0: [drm] ERROR flip_done timed out
amdgpu 0000:c4:00.0: [drm] ERROR [PLANE:83:plane-7] commit wait timed out

The flip_done timed out issue can occur under very different circumstances (sometimes while idle, sometimes under heavy load). It happens across different desktop environments (so it doesn’t seem to be tied to GNOME/KDE/etc.).

Running the following command helps to recover the GPU without rebooting or losing the current session:
sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover

kx Hi! I’m also on Linux and l also get those occasional system freezes, even on idle for long, apparently related to the amdgpu kernel module driver pageflip handling. I have opened a dedicated topic for that discussion here.

decryp7

So far eco mode is ok for me. Not sure if the new driver help as well.
https://rocm.docs.amd.com/projects/install-on-linux/en/latest/install/quick-start.html

tbocek

decryp7 I am using with Vulkan for LLM. For ROCm, I am currently using TheRock nightlies (https://github.com/ROCm/TheRock), which crash consistently during token generation. This did not happen before with older nightlies, so this is a ROCm issue and not related to the NIC problem.

LEPT

From the notes for the latest version of the drivers (but it seems that this problem has persisted since the first versions of the drivers):
"It may be possible that invalid PCIe configuration can cause that EEUpdate will not show the
adapter in OS."

decryp7

tbocek Thank you. Good to know.

DesruX

gtaranti I have also performed the NIC firmware update to 1.3 and updated BIOS to 1.08 - I still have crashes. Seems system not stable under load - disabling NICs in windows helps but there are still issues with stability.
Also I cannot get the system to sleep - need to do shutdown every time.
There are two fans in the system, but I can only get RPM on one of them - might be unrelated.

gtaranti

@DesruX Sorry, I’ve returned it to Beelink for a refund. I’ve spent long hours to debug it..

Gabriel

Is there any update regarding this issue? 👀
Still happening? 🤞

« Previous Page Next Page »