Vikont
I tried asking support if they could confirm I’d get the new revision as a replacement. They dodged the question going back to it only affects a few people and we need to wait for the corrected driver.
There’ve been a number of, we’ll call not quite fixes; like the nvm 1.41 update, it seems to make the problem better, it’s been a while since I’ve seen a crash caused by lmstudio for instance, but the dawntrail benchmark does sometimes cause the same crash.
I also don’t doubt that many people will be using the device entirely over wifi and so will have seen one crash, the ethernet has disappeared and as long as they leave it plugged in they don’t see another crash so don’t report an issue. Likewise many people won’t be throwing heavy workloads at it and so might not trigger the issue.
But, it’s not a cheap machine and certainly I think it’s reasonable to expect it to work properly and reliably.
And I’m not convinced the issue has been diagnosed properly, as I’m still seeing oddities with the Internet ethernet driver completely uninstalled.
1) cold-boot the machine and observe the two ethernet controllers with the usual windows yellow triangle because there driver is not installed.
2) reboot the machine; observe they stay there, as one would expect, they should stay put until the driver is installed.
3) check under view devices by connection; the ethernet controllers show up connected to the pci express root port between the one that’s got the nvm controller and the one that’s got the audio stuff.
4) run the dawntrail benchmark twice; don’t use loop as loop throttles performance, then reboot the machine.
5) observe no missing driver network controllers in device manager. Also observe the whole pci express root port they were connected to has also disappeared.
If one shows hidden devices, the missing pci express root port shows up, greyed out and code 45; not connected to the system. This missing device has a pci vendor of 0×1022, which isn’t Intel.
Now, what this means, I’m not sure; other pcie root ports with nothing showing connected are listed so presumably that root port is failing or being disabled by the firmware for some reason, Whether the Intel chip is doing something strange that’s causing it I don’t know. I don’t know enough about pciexpress to say, but I do know many pciexpress drivers don’t handle their devices disappearing very well.
Oh, and cold-boot the machine and the missing-driver ethernet controllers are back, as is the pci express root port, right where it was between the audio stuff and the nvme stuff.
Which does raise one question; if Intel fix the driver to stop the crashing, will instead we be looking at an issue where heavy load causes the ethernet to drop off the pcie bus? Have beelink enquired of AMD if they can diagnose why this root port disappears or do they know already?
Just my thoughts on the matter. Also upset that have been waiting for these drivers since October and in that time a whole new revision of the board has been designed and built to resolve this, but support won’t clearly commit that replacements will be the new one. And I know I’d be even more upset to send off the machine, wait a few weeks, and get back another v1 board that likely still has this issue even if it won’t be seen by all users.
