avidamoeba

joined 2 years ago
[–] avidamoeba@lemmy.ca 12 points 9 months ago* (last edited 9 months ago) (5 children)

I am trying to transfer data via USB at high speed without data corruption, silent resets and occasional device disconnects. Those are things that happen because the USB controllers on my motherboard made by AMD with some help from ASMedia do not function correctly at the speed they advertise. So given the problem the right solution is to get a firmware or hardware fix for these USB controllers, however that's unlikely to happen. So I'm trying to find a workaround. I already have one (PCIe add-in card) but now I'm also testing running the bad controllers at half-speed which seems successful so far but I was wondering if there's a way to do it in software. I'm currently bottlenecking the links by using 5Gb hubs between the controllers and the devices.

[–] avidamoeba@lemmy.ca 2 points 9 months ago (2 children)

Yup. A USB host controller. Specifically AMD Bixby.

[–] avidamoeba@lemmy.ca 10 points 9 months ago* (last edited 9 months ago) (2 children)

Great question. In short, garbagy AMD USB controllers. I recently switched to a newer AMD board and have been hit with the same issues faced by these poor sods. I've been conducting testing over the last week, different combinations of ports, cables, loads, add-in PCIe USB controllers. The add-in cards seem to behave well, which is one way the folks from that thread solved their problems. The other being changing to Intel-based systems. Yesterday however I was watching an intro about USB redrivers by TI and they were discussing various signalling issues that could occur and how redrivers help. That led me to form the hypothesis that what I'm experiencing might be signalling related. E.g. that the combination of controllers/ports/cables simply can't handle 10Gbps. That might be noise from some of those devices or surrounding ones that causes signal loss when operating at 10Gbps, speeds this setup can actually achieve. In order to test that I tried placing the DAS boxes behind a 5Gb hub plugged in a port that has previously shown a failure. So far it's stable. This is why I was wondering whether there's some magic in the kernel that could allow configuring 10Gb ports to operate at 5Gb.

[–] avidamoeba@lemmy.ca 2 points 9 months ago* (last edited 9 months ago) (1 children)

The extension cable is a great idea. I'm currently trying 5Gb hubs on the path. Seems to work.

E: I think the USB-A connector for 5Gb and 10Gb is the same. The 10Gb cable must simply carry double the rate without losing data due to noise. Similar to Cat 5 vs Cat 6 ethernet cables. If so an extension should keep the controller-advertised speed downstream. Seems like hubs are the only option.

[–] avidamoeba@lemmy.ca 2 points 9 months ago (7 children)

Three-way mirror?

[–] avidamoeba@lemmy.ca 4 points 9 months ago* (last edited 9 months ago) (1 children)

Then Qualcomm would become a national security asset. 😂 In fact that alone sounds like a great reason for acquisition. It's not every day that you get a obvious way to become too big/important to fail.

[–] avidamoeba@lemmy.ca 4 points 9 months ago (3 children)

Qualcomm is also American.

Whether Intel sells or not is decided by its major shareholders, pending regulatory approval, not Intel's execs or employees. Those shareholders would likely receive shares of Qualcomm which would now include Intel's expected future profits, or cash that they can use to buy Qualcomm shares to capture those profits.

[–] avidamoeba@lemmy.ca 1 points 9 months ago* (last edited 9 months ago) (1 children)

Try to use the standard virtual desktop functionality. It's not going to behave the exact same way but you might find a workable adaptation.

You can pass through USB to VMs.

You can use Premiere in a VM. Depending on what you want to do and how fast your CPU is, you might be able to use it without any special config. If you need to pass through a GPU, you can buy the config isn't trivial. Definitely doable though.

Generally you'd want to use KVM (with virt-manager) for virtualization but it doesn't support any 3D acceleration in Windows yet. The result is that the Windows UI in a VM is not "smooth." It's usable but not smooth. If you need acceleration you'd have to do GPU passthrough. There's some ongoing work to get basic acceleration without passthrough but it isn't done yet. Both VirtualBox and VMware have basic 3D acceleration for Windows VMs. They have other pros and cons but if you find that one of them works better than KVM for your use case, go ahead and use that. We use both VirtualBox and VMware for different purposes at work. I know of people who use all sorts of engineering CAD software in VMware.

[–] avidamoeba@lemmy.ca 43 points 9 months ago* (last edited 9 months ago) (20 children)

Buy recertified enterprise grade disks from https://serverpartdeals.com. Prices were around $160/16TB the last time I checked. Mix brands and models to reduce simultaneous failure. Use more than 1-disk redundancy. If you can't buy from SPD, either find an alternative or buy external drives and shuck them. Use ZFS to know if your data is correct. I've been dealing with funny AMD USB controllers recently and the amount of silent data corruption I'd have gotten if not for ZFS is ridiculous.

[–] avidamoeba@lemmy.ca 3 points 9 months ago (1 children)

I don't think anyone makes SMR drives in the current lineups anymore.

[–] avidamoeba@lemmy.ca 10 points 9 months ago

Switching wholesale from a brand or model to another could be counterproductive. There are myriad of reasons why drives can fail that aren't related to the brand and the model. What if you unknowingly switch to a less reliable model because of such a reason? You'd end up worse off. For example according to Backblaze's data, Seagate is generally worse than WD.

A better way to do this is to mix brands and models so that there's less probability to fail at the same time. I have both WD and Seagate in a single storage pool, even if the Seagate model is objectively less reliable according to Backblaze.

view more: ‹ prev next ›