EQ12 purchased 4/15 - no USB3 on second bus

GalanFaladway

Hello,

Creating  another thread with USB woes in hopes that Beelink notices that we know that their EQ12 specifications either misrepresent the unit capabilities, or that they finally take action, and publicly acknowledge and address the USB issues with the EQ12, instead of trying to hide the problems by sending people to private emails with technical support.


I purchased an EQ12 on Amazon yesterday, and I need the functionality of the high-speed USB3 ports.  However, when plugging my Google Coral TPU (USB) into the rear USB-C port, it is downgraded to USB2 at 480Mbps, which reduces inference speed per Coral documentation.  I swapped it between all 4 ports, and the only port which appears to actually be USB 3 is the front left port, at least on my EQ12 unit.

Indeed, even when all USB devices are unplugged and the unit is rebooted, the second bus (which also connects to the internal Bluetooth transceivers) is listed as USB 2.  The below is output with NO devices connected; the root bridge for Bus01.Port01 is USB 2, and that is the one connected to the various USB ports on the device.  It seems to fluctuate as to which ports it is connected to.

1. $ sudo lsusb -tv
   
2. /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
   
3.     ID 1d6b:0003 Linux Foundation 3.0 root hub
   
4. /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   
5.     ID 1d6b:0002 Linux Foundation 2.0 root hub
   
6.     |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   
7.         ID 8087:0026 Intel Corp. AX201 Bluetooth
   
8.     |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
   
9.         ID 8087:0026 Intel Corp. AX201 Bluetooth

Copy the Code

What is up, Beelink?

GalanFaladway

As a hail mary, and even though I need Bluetooth, I opened the case up and removed the m.2 wifi/bluetooth adapter, hoping that would restore USB 3.0 to the Bus 1 root bridge; unfortunately, this was not the case:

1. /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
   
2.     ID 1d6b:0003 Linux Foundation 3.0 root hub
   
3. /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   
4.     ID 1d6b:0002 Linux Foundation 2.0 root hub
   

Copy the Code

Beelink, your second USB bus on the EQ12 is 2.0, even with no devices attached to the bus.  Please explain the difference between this reality and your product specifications.


I'm reverting to my old working-but-underpowered Frigate machine which this was intended to replace, and pulling this out until I either get an answer or return it within the next 29 days.  Your customers need ALL of the specifications that they pay for.

tuiguang16

Hello there,

Thanks for your letter and sorry for the late reply.

Could you please send us a photo of SN on the bottom of your machine, we need to know your machine is EQ12 N100 or EQ12 PRO N305.

And may I ask you that when you connected your Google Coral TPU (USB), at the same time,did you plug in any other devices?

GalanFaladway

I had another post replying above, but it was moderated and has not yet appeared.  In short, I tried with every combination of USB device, including removing the wifi/bluetooth adapter and booting with nothing attached, and the USB root bridge still appears as a USB2 device:

1. * No devices attached on boot, with wifi/bluetooth m.2 card removed
   
2. 
   
3. /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
   
4.     ID 1d6b:0003 Linux Foundation 3.0 root hub
   
5. /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   
6.     ID 1d6b:0002 Linux Foundation 2.0 root hub

Copy the Code

Disregard this post however (though I want my time back), as after attempting to work around the lack-of-USB3 issue by installing another coral TPU I have into the PCIe m.2 slot, and testing 2 SATA disks as my main drive, I ran into the unshielded SATA cable issue described here:
https://forum.bee-link.com/forum.php?mod=viewthread&tid=87720

I tried with two new SATA drives: a Lexar, and the Crucial recommended in that post.  In both cases, the drives were only even being detected about 50% of the time, and when they were, they were limited to 3Gbps (half of the SATA bus bandwidth) and corrupting data.  The lack of SATA cable shielding next to the wifi m.2 card even corrupted the UEFI boot partition and would not boot after OS installation.

I am returning the EQ12 tomorrow as defective.

Support-03

Hi there,

What is the operating system in your PC ?