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

OMGrant

Korea_ydh Except you’re wrong about it occuring regardless of the operating system or driver version. Plenty of us have downgraded the driver and firmware on Windows 11 and are running completely stable.

Korea_ydh

OMGrant

As I said in the article, it seems to be a margin issue, and even Beelink CS is providing strange temporary guides to many people regarding the issue. Of course, regardless of the drive or OS.

Beelink CS-Ian Chan

OMGrant
Hi , there
Thanks for your sharing and feedback ,Appreciate it !

Beelink CS-Ian Chan

knekker
Hi , there
For my analysis .
Some people with the latest system and drivers still have such issue while some do not .
And some people with older intel drivers don`t have the issue while some people do .
So the portion who have issue with latest system and drivers , when they roll back to older drivers , the issue fixed.
The portion who have issue with older drivers , But when they updated the driver , the issue fixed.

And that left with a very few portion who still occurs the issue no matter with updated driver or not,
But we can use temporary solutions to make it work which indicates the hardware has no issue .
That`s why i call it as a driver or system update issue .

Beelink CS-Ian Chan

knekker
Hi , there
Thanks you for your feedback .
If you only use problematic PC to make the test article ,there`s always a problem .
But if you can check my last message explaining why i call it as driver or update issue.
You might have the whole picture.

knekker

Beelink CS-Ian Chan Thanks for the answer. May I ask why you edited your earlier posts, removing all info where you previously explained that with rev 2.2, bee-link has changed the NIC from Intel to a different brand, with the following reason that the new NIC plays more nice with the rest of the hardware on the motherboard?

knekker

Beelink CS-Ian Chan

Olii
Hi , there
Please buy from our official website for the model, I am sure there`s no problem .

Olii

Beelink CS-Ian Chan - Not possible in this market. You clearly can identify mobo revisions via serial number … but you’re refusing to provide means to do so.

So does anyone here know how to identify 2.2 or later stock?

Beelink CS-Ian Chan

Korea_ydh Hi , there
For my analysis .
Some people with the latest system and drivers still have such issue while some do not .
And some people with older intel drivers don`t have the issue while some people do .
So the portion who have issue with latest system and drivers , when they roll back to older drivers , the issue fixed.
The portion who have issue with older drivers , But when they updated the driver , the issue fixed.

Beelink CS-Ian Chan

Olii
Hi , there
SN code picture can`t tell what version of motherboard is .

Beelink CS-Ian Chan

knekker
Hi , there
I think i did not mention about rev 2.2 and Wasn`t quite sure about what changed or what unchanged ,
An unconfirmed answer or information should not be open to public from my pecpective.
I am sorry for my carelessness .

miguilim

Still no fix for me…

Beelink CS-Ian Chan

miguilim
Hi , there
Please try some solutions here :
1.
①Disable the NIC: BIOS > Advanced > Demo Board > “Device 3 Fun 2”: Disabled
②.Boot to OS
③.Run something that brings the temp. up to _75℃ for a while (e.g: furmark with appropriate fan profile)
④.Boot to BIOS and re-enable the NIC
⑤.Please do not remove the power supply.

2.
Please update to intel 1.30 or 1.40 firmware.
https://www.intel.com/content/www/us/en/download/845347/non-volatile-memory-nvm-update-package-for-intel-ethernet-e610-series.html

3.
①Boot into OS
②.Run FurMark or any benchmark until the NIC drops into recovery mode
③.Once the APU reaches >=75℃, wait for five minutes or more to ensure the PCB won’t cool down immediately once the load is gone
④.Turn off the PC
⑤.Unplug from the wall for two to five seconds, this is required to get the NIC to exit the recovery mode
⑥.Plug it back in and turn on the PC

MrGiantAxe

So, just a small update from me.
As of last weekend I upgraded my device to Ubuntu 26.04 (its still in development, but its pretty seamless from 25.10 and I wanted to anyway for updated linux firmware.)

The biggest change also lies in that part, the linux-firmware Ubuntu 26.04 ships with at the moment is 20260110, rather than 20250917 that 25.10 ships with (linux firmware is basically what it says, it controls drivers/firmware for all your hardware connected devices. That + the kernel is what eventually makes everything talk and run.)

With this configuration

Linux firmware 20260110
Linux kernel 6.18.7
NVM 1.41

I have been able to run the 10G nic stable for the entirety of last week running both LLMs and doing gaming with sunshine/moonlight for remote game streaming. (the gaming made my device run between 80 to 90 degrees at times, especially whilst compiling vulkan shaders.) So maybe…just maybe…..there might be hope after all. (At least for the linux side of things, for Windows thats a whole different story.)

Rong

MrGiantAxe The biggest change also lies in that part, the linux-firmware Ubuntu 26.04 ships with at the moment is 20260110, rather than 20250917 that 25.10 ships with

ixgbe never calls request_firmware() if you look into its code, so it has nothing to do with linux-firmware.

Gab

That sounds great. Does it also work if you completely disconnect the system from power and then plug it back in?

miguilim

I’m currently using:

Fedora 43:

Linux firmware 20260110
Linux 6.18.8-cachyos1.lto.fc43.x86_64
NVM 1.41

Before, I used to get the NIC failure as soon as I start a game, now it takes like 30 seconds after the game is open… So it changed something, but not fixed…

Beelink CS-Ian Chan

miguilim
Have you tried 1.30 or 1.40 firmware.?

Beelink CS-Ian Chan

knekker with the following reason that the new NIC plays more nice with the rest of the hardware on the motherboard?
Hi , there
Not because of it`s new NIC , but the most of the PCs were sold without problem .

RubensRainelli

I’m still facing issues on GTR9 Pro with latest firmware published on FB… 😅

Will there be a definite solution?
Actually I have all ports busy for peripherals I need, and even using some hubs… I can’t use an USB ETH… And the hubs with it that works well with the ports I’d need are all over 100 €…

@Beelink CS-George

Beelink CS-Ian Chan

RubensRainelli
Hi , there
Please update to intel 1.30 or 1.40 firmware.
Will it work?

Olii

Beelink CS-Ian Chan

It would be absolutely extraordinary for a company of this size not to keep track of part numbers used per production date / serial number range. Like extraordinary in the sense that I’ve never heard of that before. I don’t believe you.

« Previous Page Next Page »