11:56 p.m.
A while back I acquired a NVMe caddy but did not get to use it. I now did as I got an NVMe
disk.
The caddy is
https://www.aliexpress.com/item/1005001346524009.html
Color: 10Gbps M2PV C3
The disk is
1TB WD Blue SN580 NVMe WDS100T3B0E (PCie v4)
I expected to see 1GB/s speed.
Read [X=Y] cable from USB-X to USB-Y. Caddy on left, machine on right.
1) Directly connecting the caddy to the machine (caddy-[C=C]-socket) I see 36MB/s. So
USB-2? speed.
2) Using a caddy-[C=USB3M]-socket I get 442 MB/s. So USB-3.0 speed. This is expected.
3) The kicker: caddy-[C=USB3M] then [FUSB3=C]-socket (two cables) I get the expected
1000MB/s.
I tried a few C=C , no change. Two different machines. same.
What I want, of course, is good speed with a straight C=C cable.
TIA
--
Eyal at Home (fedora(a)eyal.emu.id.au)
1 a.m.
On 12/7/23 21:56, fedora(a)eyal.emu.id.au wrote:
A while back I acquired a NVMe caddy but did not get to use it. I now
did as I got an NVMe disk.
The caddy is
https://www.aliexpress.com/item/1005001346524009.html
Color: 10Gbps M2PV C3
The disk is
1TB WD Blue SN580 NVMe WDS100T3B0E (PCie v4)
I expected to see 1GB/s speed.
Read [X=Y] cable from USB-X to USB-Y. Caddy on left, machine on right.
1) Directly connecting the caddy to the machine (caddy-[C=C]-socket) I
see 36MB/s. So USB-2? speed.
2) Using a caddy-[C=USB3M]-socket I get 442 MB/s. So USB-3.0 speed. This
is expected.
3) The kicker: caddy-[C=USB3M] then [FUSB3=C]-socket (two cables) I get
the expected 1000MB/s.
I tried a few C=C , no change. Two different machines. same.
What I want, of course, is good speed with a straight C=C cable.
Maybe your straight C=C cables don't have the extra pins wired for the
higher speed. What do the logs show for each of those connections?
3:55 a.m.
On 8/12/23 18:00, Samuel Sieb wrote:
On 12/7/23 21:56, fedora(a)eyal.emu.id.au wrote:
> A while back I acquired a NVMe caddy but did not get to use it. I now did as I got an
NVMe disk.
>
> The caddy is
> https://www.aliexpress.com/item/1005001346524009.html
> Color: 10Gbps M2PV C3
> The disk is
> 1TB WD Blue SN580 NVMe WDS100T3B0E (PCie v4)
>
> I expected to see 1GB/s speed.
>
> Read [X=Y] cable from USB-X to USB-Y. Caddy on left, machine on right.
>
> 1) Directly connecting the caddy to the machine (caddy-[C=C]-socket) I see 36MB/s. So
USB-2? speed.
> 2) Using a caddy-[C=USB3M]-socket I get 442 MB/s. So USB-3.0 speed. This is
expected.
> 3) The kicker: caddy-[C=USB3M] then [FUSB3=C]-socket (two cables) I get the expected
1000MB/s.
>
> I tried a few C=C , no change. Two different machines. same.
>
> What I want, of course, is good speed with a straight C=C cable.
Maybe your straight C=C cables don't have the extra pins wired for the higher speed.
What do the logs show for each of those connections?
I considered this so I tried 5 different C-C cables. Same results.
Note, this mobo does not have USB-C so installed is a PCIe controller.
$ lspci -v
06:00.0 USB controller: ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller (prog-if
30 [XHCI])
It shows as USB bus 3 and 4.
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 20000M/x2
Bus 1 and 2 is on the mobo.
I expect that the mtp/thunar messages are not relevant but I left them in.
Speed is from 'hdparm -t'.
1) Using the C-C cables, speed 33.64 MB/sec
Dec 8 20:04:26 e7 kernel: usb 3-1: new high-speed USB device number 18 using xhci_hcd
Dec 8 20:04:27 e7 kernel: usb 3-1: New USB device found, idVendor=0bda, idProduct=9210,
bcdDevice=20.01
Dec 8 20:04:27 e7 kernel: usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Dec 8 20:04:27 e7 kernel: usb 3-1: Product: RTL9210B-CG
Dec 8 20:04:27 e7 kernel: usb 3-1: Manufacturer: Realtek
Dec 8 20:04:27 e7 kernel: usb 3-1: SerialNumber: 012345679039
Dec 8 20:04:27 e7 kernel: usb-storage 3-1:1.0: USB Mass Storage device detected
Dec 8 20:04:27 e7 kernel: scsi host7: usb-storage 3-1:1.0
Dec 8 20:04:27 e7 mtp-probe[3926339]: checking bus 3, device 18:
"/sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/usb3/3-1"
Dec 8 20:04:27 e7 mtp-probe[3926339]: bus: 3, device: 18 was not an MTP device
Dec 8 20:04:27 e7 mtp-probe[3926349]: checking bus 3, device 18:
"/sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/usb3/3-1"
Dec 8 20:04:27 e7 mtp-probe[3926349]: bus: 3, device: 18 was not an MTP device
Dec 8 20:04:27 e7 thunar-volman[3926344]: Couldn't connect to accessibility bus:
Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
Dec 8 20:04:27 e7 Thunar[3926344]: thunar-volman: Unsupported USB device type
"usb".
Dec 8 20:04:27 e7 thunar-volman[3926359]: Couldn't connect to accessibility bus:
Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
Dec 8 20:04:27 e7 Thunar[3926359]: thunar-volman: Unsupported USB device type
"usb-storage".
Dec 8 20:04:28 e7 kernel: scsi 7:0:0:0: Direct-Access Realtek RTL9210B-CG 1.00
PQ: 0 ANSI: 6
Dec 8 20:04:28 e7 kernel: sd 7:0:0:0: Attached scsi generic sg9 type 0
Dec 8 20:04:28 e7 kernel: sd 7:0:0:0: [sdi] 1953525168 512-byte logical blocks: (1.00
TB/932 GiB)
Dec 8 20:04:28 e7 kernel: sd 7:0:0:0: [sdi] Write Protect is off
Dec 8 20:04:28 e7 kernel: sd 7:0:0:0: [sdi] Write cache: disabled, read cache: enabled,
doesn't support DPO or FUA
Dec 8 20:04:28 e7 kernel: sd 7:0:0:0: [sdi] Attached SCSI disk
-- lshw
*-usb
description: Mass storage device
product: RTL9210B-CG
vendor: Realtek
physical id: 1
bus info: usb@3:1
logical name: scsi7
version: 20.01
serial: 012345679039
capabilities: usb-2.10 scsi emulated scsi-host
configuration: driver=usb-storage maxpower=500mA speed=480Mbit/s
*-disk
description: SCSI Disk
product: RTL9210B-CG
vendor: Realtek
physical id: 0.0.0
bus info: scsi@7:0.0.0
logical name: /dev/sdi
version: 1.00
serial: 0000000000000000
size: 931GiB (1TB)
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=512
2) Then connected to a USB3 port using a C-USB3 cable: speed 441.36 MB/sec
Dec 8 20:19:37 e7 kernel: usb 2-7: new SuperSpeed USB device number 19 using xhci_hcd
Dec 8 20:19:37 e7 kernel: usb 2-7: New USB device found, idVendor=0bda, idProduct=9210,
bcdDevice=20.01
Dec 8 20:19:37 e7 kernel: usb 2-7: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Dec 8 20:19:37 e7 kernel: usb 2-7: Product: RTL9210B-CG
Dec 8 20:19:37 e7 kernel: usb 2-7: Manufacturer: Realtek
Dec 8 20:19:37 e7 kernel: usb 2-7: SerialNumber: 012345679039
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
Dec 8 20:19:37 e7 kernel: scsi host7: uas
Dec 8 20:19:37 e7 mtp-probe[3935963]: checking bus 2, device 19:
"/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Dec 8 20:19:37 e7 kernel: scsi 7:0:0:0: Direct-Access Realtek RTL9210B-CG 1.00
PQ: 0 ANSI: 6
Dec 8 20:19:37 e7 mtp-probe[3935963]: bus: 2, device: 19 was not an MTP device
Dec 8 20:19:37 e7 mtp-probe[3935973]: checking bus 2, device 19:
"/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Dec 8 20:19:37 e7 mtp-probe[3935973]: bus: 2, device: 19 was not an MTP device
Dec 8 20:19:37 e7 thunar-volman[3935968]: Couldn't connect to accessibility bus:
Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
Dec 8 20:19:37 e7 Thunar[3935968]: thunar-volman: Unsupported USB device type
"usb".
Dec 8 20:19:37 e7 kernel: sd 7:0:0:0: Attached scsi generic sg9 type 0
Dec 8 20:19:37 e7 kernel: sd 7:0:0:0: [sdi] 1953525168 512-byte logical blocks: (1.00
TB/932 GiB)
Dec 8 20:19:37 e7 thunar-volman[3935986]: Couldn't connect to accessibility bus:
Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
Dec 8 20:19:37 e7 kernel: sd 7:0:0:0: [sdi] Write Protect is off
Dec 8 20:19:37 e7 Thunar[3935986]: thunar-volman: Unsupported USB device type
"uas".
Dec 8 20:19:37 e7 kernel: sd 7:0:0:0: [sdi] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
Dec 8 20:19:37 e7 kernel: sd 7:0:0:0: [sdi] Preferred minimum I/O size 512 bytes
Dec 8 20:19:37 e7 kernel: sd 7:0:0:0: [sdi] Optimal transfer size 33553920 bytes
Dec 8 20:19:38 e7 kernel: sd 7:0:0:0: [sdi] Attached SCSI disk
## lshw
*-usb:3
description: Mass storage device
product: RTL9210B-CG
vendor: Realtek
physical id: 7
bus info: usb@2:7
logical name: scsi7
version: 20.01
serial: 012345679039
capabilities: usb-3.20 scsi
configuration: driver=uas maxpower=896mA speed=5000Mbit/s
*-disk
description: SCSI Disk
product: RTL9210B-CG
vendor: Realtek
physical id: 0.0.0
bus info: scsi@7:0.0.0
logical name: /dev/sdi
version: 1.00
serial: 0000000000000000
size: 931GiB (1TB)
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=2048
3) Finally, again C-C using a C->USB3 then USB3->C, speed 1006.17 MB/sec
Dec 8 20:28:22 e7 kernel: usb 4-1: new SuperSpeed USB device number 18 using xhci_hcd
Dec 8 20:28:22 e7 kernel: usb 4-1: New USB device found, idVendor=0bda, idProduct=9210,
bcdDevice=20.01
Dec 8 20:28:22 e7 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Dec 8 20:28:22 e7 kernel: usb 4-1: Product: RTL9210B-CG
Dec 8 20:28:22 e7 kernel: usb 4-1: Manufacturer: Realtek
Dec 8 20:28:22 e7 kernel: usb 4-1: SerialNumber: 012345679039
Dec 8 20:28:22 e7 kernel: scsi host7: uas
Dec 8 20:28:22 e7 kernel: scsi 7:0:0:0: Direct-Access Realtek RTL9210B-CG 1.00
PQ: 0 ANSI: 6
Dec 8 20:28:22 e7 mtp-probe[3938049]: checking bus 4, device 18:
"/sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/usb4/4-1"
Dec 8 20:28:22 e7 mtp-probe[3938049]: bus: 4, device: 18 was not an MTP device
Dec 8 20:28:22 e7 mtp-probe[3938060]: checking bus 4, device 18:
"/sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/usb4/4-1"
Dec 8 20:28:22 e7 mtp-probe[3938060]: bus: 4, device: 18 was not an MTP device
Dec 8 20:28:22 e7 thunar-volman[3938054]: Couldn't connect to accessibility bus:
Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: Attached scsi generic sg9 type 0
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: [sdi] 1953525168 512-byte logical blocks: (1.00
TB/932 GiB)
Dec 8 20:28:22 e7 Thunar[3938054]: thunar-volman: Unsupported USB device type
"usb".
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: [sdi] Write Protect is off
Dec 8 20:28:22 e7 thunar-volman[3938073]: Couldn't connect to accessibility bus:
Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: [sdi] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
Dec 8 20:28:22 e7 Thunar[3938073]: thunar-volman: Unsupported USB device type
"uas".
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: [sdi] Preferred minimum I/O size 512 bytes
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: [sdi] Optimal transfer size 33553920 bytes
Dec 8 20:28:22 e7 kernel: sd 7:0:0:0: [sdi] Attached SCSI disk
## lshw
*-usb
description: Mass storage device
product: RTL9210B-CG
vendor: Realtek
physical id: 1
bus info: usb@4:1
logical name: scsi7
version: 20.01
serial: 012345679039
capabilities: usb-3.20 scsi
configuration: driver=uas maxpower=896mA speed=5000Mbit/s
*-disk
description: SCSI Disk
product: RTL9210B-CG
vendor: Realtek
physical id: 0.0.0
bus info: scsi@7:0.0.0
logical name: /dev/sdi
version: 1.00
serial: 0000000000000000
size: 931GiB (1TB)
configuration: ansiversion=6 logicalsectorsize=512 sectorsize=2048
HTH
--
Eyal at Home (fedora(a)eyal.emu.id.au)
2:30 p.m.
On 12/8/23 01:55, fedora(a)eyal.emu.id.au wrote:
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1
failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
This is the difference between the second and third ones. This didn't
happen with the mixed cables, so it was able to setup the higher speed.
You'll need to look up what the requirements are for this to work.
3:47 p.m.
On 9/12/23 07:30, Samuel Sieb wrote:
On 12/8/23 01:55, fedora(a)eyal.emu.id.au wrote:
> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
This is the difference between the second and third ones. This didn't happen with
the mixed cables, so it was able to setup the higher speed. You'll need to look up
what the requirements are for this to work.
The USB-C card implements two buses:
$ lsusb -t
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 20000M/x2
It seems that at times the NVMe disk is detected as 'high-speed' and attached to
3-1
kernel: usb 3-1: new high-speed USB device number 18 using xhci_hcd
where it ends up at the wrong speed. At other times it detected as 'SuperSpeed'
and attaches to 4-1
kernel: usb 4-1: new SuperSpeed USB device number 18 using xhci_hcd
I tried difference USB-C cables, some short, some long, some thick (100W).
Interestingly, testing on a laptop. The results are the same as above.
Connecting to a USB-3 port using the USB-C->USB-3 cable detects the drive as
SuperSpeed
Connecting to a USB-C port using a USB-C->USB-C cable detects it as high-speed only
and then runs at USB-2 rate.
Connecting to a USB-C port using a USB-C->USB-3 cable followed by a USB-3>USB-C
cable detects is as SuperSpeed.
On this laptop the USB-C port runs at 5GB/s max, but this is not the problem.
So, is it something to do with the enclosure? The cable (it does make a difference)?
Do I need a special USB-C cable for the higher speeds (5-10-20GB/s)? Even for 5GB/s?
--
Eyal at Home (fedora(a)eyal.emu.id.au)
4:36 a.m.
New subject: USB-C cabling [resolved]
On 9/12/23 08:47, fedora(a)eyal.emu.id.au wrote:
On 9/12/23 07:30, Samuel Sieb wrote:
> On 12/8/23 01:55, fedora(a)eyal.emu.id.au wrote:
>> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
>> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
>> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
>> Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
>
> This is the difference between the second and third ones. This didn't happen
with the mixed cables, so it was able to setup the higher speed. You'll need to look
up what the requirements are for this to work.
The USB-C card implements two buses:
$ lsusb -t
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 20000M/x2
It seems that at times the NVMe disk is detected as 'high-speed' and attached to
3-1
kernel: usb 3-1: new high-speed USB device number 18 using xhci_hcd
where it ends up at the wrong speed. At other times it detected as 'SuperSpeed'
and attaches to 4-1
kernel: usb 4-1: new SuperSpeed USB device number 18 using xhci_hcd
I tried difference USB-C cables, some short, some long, some thick (100W).
Interestingly, testing on a laptop. The results are the same as above.
Connecting to a USB-3 port using the USB-C->USB-3 cable detects the drive as
SuperSpeed
Connecting to a USB-C port using a USB-C->USB-C cable detects it as high-speed only
and then runs at USB-2 rate.
Connecting to a USB-C port using a USB-C->USB-3 cable followed by a USB-3>USB-C
cable detects is as SuperSpeed.
On this laptop the USB-C port runs at 5GB/s max, but this is not the problem.
So, is it something to do with the enclosure? The cable (it does make a difference)?
Do I need a special USB-C cable for the higher speeds (5-10-20GB/s)? Even for 5GB/s?
I think I figured it. The USB cables I have are all providing only minimal connectivity,
so only USB2 speed.
The USBC->USB3 (15cm) cable works well to a USB3 socket. Which made me remember that
the NVMe caddy
came with TWO short cables, one to USB3 and one to USBC.
After a long search I located the second cable (C-C) and it works well, giving me the full
1GB/s.
In short, the cable matters. I will now acquire some fast (20Gbps) cables and put the
others aside,
for charging/power. I learn something every day.
Oh, and I now checked the long (1m) USB-C M-F cable I bought with the PCIe USB-C card, and
it also
passes the full 10Gbps. Good again.
Thanks everyone.
--
Eyal at Home (fedora(a)eyal.emu.id.au)
9:22 a.m.
New subject: USB-C cabling [resolved]
Once upon a time, fedora(a)eyal.emu.id.au <fedora(a)eyal.emu.id.au> said:
I think I figured it. The USB cables I have are all providing only
minimal connectivity, so only USB2 speed.
This is how a lot of "charging" cables work - they might be able to pass
100W (or more) in power delivery mode, but only USB2 data signals.
New cables/adapters/etc. are all supposed to be marked with the data
rate and power delivery supported. For example, my recent cable
purchases have 10G/100W and 40G/240W marked. But there's no telling
with previous cables other than to plug them in with a variety of
devices and see what you get.
The data speeds are also confusing because of marketing... there's "USB
3.0" which does 5G (but was then retroactively renamed "USB 3.1 Gen 1"
and then "USB 3.2 Gen 1x1"). "USB 3.1 Gen 2" (aka "USB 3.2 Gen
2x1") is
10G, and "USB 3.2 Gen 2x2" is 20G. And then "USB4" (no space) gets
even
more modes and names. Their next renaming attempt is to stop all the
version games and go with speeds (like they should have done from the
start), so "USB 5Gbps", "USB 10Gbps", "USB 20Gbps", and so
on.
--
Chris Adams <linux(a)cmadams.net>
4:15 p.m.
On 12/8/23 01:55, fedora(a)eyal.emu.id.au wrote:
1) Using the C-C cables, speed 33.64 MB/sec
Dec 8 20:04:26 e7 kernel: usb 3-1: new high-speed USB device number 18
using xhci_hcd
This is USB 2.
Just because a cable has a USB-C connector on it doesn't indicate what
protocol it can handle.
2) Then connected to a USB3 port using a C-USB3 cable: speed 441.36
MB/sec
Dec 8 20:19:37 e7 kernel: usb 2-7: new SuperSpeed USB device number 19
using xhci_hcd
This is the max speed for USB 3.0.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1
failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U1 failed.
Dec 8 20:19:37 e7 kernel: usb 2-7: Enable of device-initiated U2 failed.
This is probably a red herring. These are lower power states for the
device.
3) Finally, again C-C using a C->USB3 then USB3->C, speed
1006.17 MB/sec
Dec 8 20:28:22 e7 kernel: usb 4-1: new SuperSpeed USB device number 18
using xhci_hcd
Now you are getting the max speed for USB 3.1.
So you have different cables and it makes sense. You will have to
carefully pick your cables if you want the speeds.
7:01 a.m.
There is a lot of spec weirdness on "usb3" cables. You have to
carefully read the description on the cable, and sometimes the
reviews.
I have seen usb3 charging cables (data is usb2).
I have seen usb3 charging (3A or 5A) + 5G, and usb3 charging + 10G.
So usb-c to usb-c any length longer than a meter or 2 would need to be
an active USB3 cable, and there are different power (3A/5A), and then
usb2 speed, 5G or 10G.
And they all say usb-c since that connector is on both ends.
On Thu, Dec 7, 2023 at 11:57 PM <fedora(a)eyal.emu.id.au> wrote:
>
> A while back I acquired a NVMe caddy but did not get to use it. I now did as I got an
NVMe disk.
>
> The caddy is
> https://www.aliexpress.com/item/1005001346524009.html
> Color: 10Gbps M2PV C3
> The disk is
> 1TB WD Blue SN580 NVMe WDS100T3B0E (PCie v4)
>
> I expected to see 1GB/s speed.
>
> Read [X=Y] cable from USB-X to USB-Y. Caddy on left, machine on right.
>
> 1) Directly connecting the caddy to the machine (caddy-[C=C]-socket) I see 36MB/s. So
USB-2? speed.
> 2) Using a caddy-[C=USB3M]-socket I get 442 MB/s. So USB-3.0 speed. This is
expected.
> 3) The kicker: caddy-[C=USB3M] then [FUSB3=C]-socket (two cables) I get the expected
1000MB/s.
>
> I tried a few C=C , no change. Two different machines. same.
>
> What I want, of course, is good speed with a straight C=C cable.
>
> TIA
>
> --
> Eyal at Home (fedora(a)eyal.emu.id.au)
> --
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
162
days inactive
163
days old
8 comments
4 participants
participants (4)
-
Chris Adams -
fedora＠eyal.emu.id.au -
Roger Heflin -
Samuel Sieb