this post was submitted on 19 Jun 2024
72 points (89.1% liked)
Technology
59589 readers
2946 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, I've had more than a few chipsets or periphs that worked on Windows, and worked on Linux but were.... quirky, especially when dealing with stuff like suspend states etc.
For USB3 in particular, I've found many storage devices or adaptors like to drop out partway through an longer copy process on Linux (like they'll be fine for copying a smaller amount of data, but the controller or device would reset during longer ones). This didn't seem to occur in Windows, but I'm pretty sure the copy process was also slower so guessing it's some sort of buffer or heat quirk that 'nix didn't account for in the more generic driver
If the device says it's a generic storage device (to the system that is) but actually isn't (based on your description) then it's 100% devices fault and not a Linux fault.
That's not a distinction that users care about, or should need to care about.
Honestly I think it's generally more of a bus driver issue, because it seems more tied to the motherboard than a given device