USB problems, especially USB-C

Samri · 发表于 2023-07-09 22:03:55

Like so many other SER5 and GTR users on this forum, I'm having endless problems with the front side USB-C and USB 3.0 ports.

1) First, the front USB-C port is not functioning as USB-C at all!

2) It certainly cannot drive a monitor. Read through the forum and you'll see this is an issue with 5500u/5560u, 5800h, 7735hs, GTR, etc. It seems the USB-C port is unable to provide the necessary bandwidth to drive a monitor.

3) Not only that, it can't even drive any USB 3.x device.

4) Speed on the port is definitely not USB 3.1 as it should be. It's not even 3.0, or even 2.0.
Read the forum - people are getting 40mb/s only speed. I'm getting the same. Some suggested solutions tell you to adjust the settings in Windows, but this speed issue is NOT a Windows issue. It seems to be a motherboard/BIOS issue, see below*

After several weeks of trying, here's what I found out...

5) The moment you connect ANYTHING to the USB-C port, it immediately "kills" the other USB-3.0 ports on the front. Even if I connect a hub with nothing attached to it, the USB-C (which itself is running at usb 2.0 or even 1.0 speed) will bring down the speed of the other ports (USB-A type) on the front. They're supposed to be 3.0 but they they also become 2.0/1.0 whenever anything is connected to the USB-C port, even a hub with nothing attached to it.

If I disconnect the external drive or external hub from USB-C, the front ports go back to being USB-3.0, but sometimes they "share" the bandwidth. So if only one is connected, I get 3.0 bandwidth. If two are connected, sometimes the speed is halved like it's being divided between the 2 ports.

This happens expecially if you connect an external hard disk, and less likely to happen with an NVME enclosure for example. Maybe the port is struggling to give power to the mechanical HDD, so it reduces the power available to the second port. Maybe...

But like I said, put anything in the USB-C port, and ALL the front USB's start having problems.

*6) Please do not suggest solutions to adjust Windows setting. They don't work, and the problem has nothing to do with Windows. Try booting a cloning/partitioning USB like Clonezilla or DiskGenius, and put an extra NVME drive in a USB-3.x enclosure. Now try cloning from internal NVME to the Enclosure NVME. You should get at least 3.1 Gen 1 speed but you don't. You only get 2GB/minute (i.e. 40MB/s) at best. So to backup a fresh installation with only 60GB on the internal SSD, it'll take 3-4 hours!

Now disconnect anything on the USB-C port, and connect the NVME enclosure to one of the USB 3.0 ports and try the backup. You'll get 16-25 GB/minute speed and the backup is done in about 10-15 minutes.

Here on the Beelink forum you see the same issue from SER5 and GTR users, including 5800h, 5560u (me), 5500u (also me), 7735hs, etc. Even a famous YouTube reviewer in Australia had the same problem. And also from YouTube, it seems not only Beelink, but also other brands using the AZW platform.

Can someone at Beelink suggest any changes to the BIOS to make the USB-C port act like a USB-C port? Or is there a new BIOS from AZW? Please help.

awrc · 发表于 2023-09-01 05:54:59

While the external SSD that I tried first produced a lot of errors when connected to the USB 4 connector, a few weeks later I picked up a Crucial X8 4TB external SSD (the other drive had been the 500GB drive that came inside the SER 6 Pro in a USB 3.2 enclosure) and it’s been trouble-free, although the drive controller acts more like a conventional drive - no ability to Mount the file system with ‘discard’ specified.

However, ‘dmesg’ is still littered with BIOS bug warnings…

[. 0.288113] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP8.RTL8], AE_NOT_FOUND (20230331/dswload2-162)
[ 0.288123] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230331/psobject-220)
[ 0.288129] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
[ 0.301538] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SBRG.EC0._REG.AMW0], AE_NOT_FOUND (20230331/psargs-330)
[ 0.301538] ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0._REG due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[ 0.301538] ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 0.301538] ACPI: \_SB_.PCI0.SBRG.EC0_: Boot DSDT EC used to handle transactions
[ 0.555707] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555737] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555759] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555781] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555804] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555827] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555849] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555871] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555893] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555916] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.555938] amd_gpio AMDI0030:00: Invalid config param 0014
[ 0.654791] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SBRG.EC0.OKEC], AE_NOT_FOUND (20230331/psargs-330)
[ 0.654808] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20230331/psparse-529)

While it may be unconnected to this problem, I’d personally be happier if the kernel wasn’t finding all these BIOS errors and was thus able to configure the hardware properly.

Samri · 发表于 2023-07-18 03:59:42

@support-03
Any updates on this?

tia

Support-03 · 发表于 2023-07-11 09:00:35

Hi there,

May I have a picture of SN on the bottom of the PC ?

Samri · 发表于 2023-07-11 18:28:56

@Support-03

Please see attached. thanks in advance.

awrc · 发表于 2023-07-12 01:53:44

I’m encountering similar issues with the USB-C port on my 7735HS.

System is running Debian, with an NVMe SSD in a 3.2 Gen 2 enclosure on the USB-C port.  At boot time the enclosure is correctly identified and the drive (initially identified as /dev/sda) mounts.  Then messages like this start appearing in ‘dmesg’…

[ 94.709714] usb 8-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd

Any attempt to access the drive after one of these messages has appeared results in a stream of error messages along the lines of:

[  200.130043] usb 8-1: reset SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[  213.517368] scsi host0: uas_pre_reset: timed out
[  213.517499] xhci_hcd 0000:75:00.3: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  213.517637] usb 8-1: cmd cmplt err -108
[  213.517645] usb 8-1: cmd cmplt err -108
[  213.517650] usb 8-1: cmd cmplt err -108
[  213.517657] xhci_hcd 0000:75:00.3: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  213.517663] usb 8-1: cmd cmplt err -108
[  213.517672] sd 0:0:0:0: [sda] tag#16 uas_zap_pending 0 uas-tag 1 inflight: CMD
[  213.517677] sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 10 00 19 00 00 04 00 00
[  213.517683] sd 0:0:0:0: [sda] tag#17 uas_zap_pending 0 uas-tag 2 inflight: CMD
[  213.517685] sd 0:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 10 00 1d 00 00 04 00 00
[  213.517688] sd 0:0:0:0: [sda] tag#18 uas_zap_pending 0 uas-tag 3 inflight: CMD
[  213.517690] sd 0:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 10 00 21 00 00 04 00 00
[  213.517692] sd 0:0:0:0: [sda] tag#19 uas_zap_pending 0 uas-tag 4 inflight: CMD
[  213.517694] sd 0:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 10 00 25 00 00 04 00 00
[  213.517735] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[  213.517738] sd 0:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 10 00 19 00 00 04 00 00
[  213.517740] I/O error, dev sda, sector 268441856 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2
[  213.517763] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[  213.517765] sd 0:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 10 00 1d 00 00 04 00 00
[  213.517767] I/O error, dev sda, sector 268442880 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2
[  213.517778] sd 0:0:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[  213.517780] sd 0:0:0:0: [sda] tag#18 CDB: Write(10) 2a 00 10 00 21 00 00 04 00 00
[  213.517782] I/O error, dev sda, sector 268443904 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 2
[  213.517790] sd 0:0:0:0: [sda] tag#19 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=5s
[  213.517793] sd 0:0:0:0: [sda] tag#19 CDB: Write(10) 2a 00 10 00 25 00 00 04 00 00
[  213.517794] I/O error, dev sda, sector 268444928 op 0x1:(WRITE) flags 0x800 phys_seg 128 prio class 2
[  213.517808] device offline error, dev sda, sector 2160 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2
[  213.517815] Buffer I/O error on dev sda1, logical block 14, lost async page write
[  213.518144] device offline error, dev sda, sector 486803824 op 0x1:(WRITE) flags 0x800 phys_seg 4 prio class 2
[  213.518163] Aborting journal on device sda1-8.
[  213.518179] device offline error, dev sda, sector 486803456 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
[  213.518188] device offline error, dev sda, sector 486803456 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
[  213.518194] Buffer I/O error on dev sda1, logical block 60850176, lost sync page write
[  213.518205] JBD2: I/O error when updating journal superblock for sda1-8.
[  213.518325] device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2
[  213.586288] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  213.825386] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

…then something to the effect that a *new* SuperSpeed etc etc drive has been found - as drive /dev/sdb and with a USB device number one higher than before, and the reset messages start again until anything tries to access the drive, at which point it produces a stream of errors and comes back again as ‘dev/sda’ and the next device number up.  If I don’t remount it it just gradually increases the device number.

Not sure if it’s related, but the ‘dmesg’ logs during early boot contain numerous errors of the form:

0.274925] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP8.RTL8], AE_NOT_FOUND (20220331/dswload2-162)
[ 0.274931] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220

The SSD and the enclosure has been functioning completely flawlessly for several months connected to my Mac.

prox_man · 发表于 2023-08-29 22:54:39

Edited by prox_man at 2023-08-29 23:07

I have same problem with debian + my ssd enclosure and looking around for month. Well, turned out it's my ser 6 pro 7735hs from begin...

@Support-03 , pls help us...may be ser 6 pro need bios update . 3 usb 3.2 type A and 1 usb 4 type C of it indeed have problem with power

Magister · 发表于 2023-08-29 23:40:43

For sure the speed can be shared between ports because the 2 front ports may be on the same hub. using

lsusb -t

in linux will show you this. Unplug everything, do the command, plug 1 thing, redo the command, plug another, redo, etc and you will see your usb tree, plug also things on the rear ports to see.

I have the old SER5 with a 5600H, I tested a USB-C hub, having an old USB2.0 key in front ports etc, and I still have 15GB/minute on my external SSD. No error in dmesg.

The problem everyone is seeing may be not enough power, but, I hope not, bad design

Tantrumus · 发表于 2023-11-08 02:12:03

I purchased the SER6 6900HX on Amazon and have no ability to use Type C. What is the fix for this?

I just want to use it for a type-C USB hub, not display.

Neither the front or back Type C works. I hear the USB device found sound, then the USB device remove sound.

Tried just a thumb drive in a type-C USB adapter and also did not work in either port.

Tantrumus · 发表于 2023-11-08 19:56:54

i think there is something wrong they are not sharing because not only USB is far slower than it should be but my NVME also caps out at like 40MBs when uncompressing a large zip file. I tested same thing on another system with same zip and an nvme (with a slower cpu too) and got 500MBs speed....