Linuxsucks

345 readers

1 users here now

Rules:

FOSS advocates and Linux evangelists aren't welcome. -We ask that you block us.
Moderation is heavy handed. Try to stay on topic (that is LINUXSUCKS!).
No Complaining Mute the sub if users, content, or rules bother you *it's ok to report rule violations

founded 8 months ago

MODERATORS

madthumbs@lemmy.world

Uschteinheim@lemmy.world

Shrug blame (lemmy.world)

submitted 8 months ago by madthumbs@lemmy.world to c/linuxsucks@lemmy.world

9 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] theunknownmuncher@lemmy.world 2 points 8 months ago* (last edited 8 months ago) (2 children)

They're all proprietary?

EDIT: I think I am wrong about WiFi being proprietary

[–] lemming741@lemmy.world 6 points 8 months ago (1 children)

The drivers are (often) proprietary.

[–] theunknownmuncher@lemmy.world 2 points 8 months ago (1 children)

True! The Bluetooth protocol is itself proprietary

[–] madthumbs@lemmy.world 1 points 6 months ago* (last edited 6 months ago)

The Bluetooth problem I had, was for the most part resolved by a script I made to reboot the USB bus it was on. (same effect as unplugging it and reinserting without wearing out the port or jostling the PC).

-If I as a non developer could essentially fix it by looking up CLI commands..

[–] madthumbs@lemmy.world 1 points 8 months ago (1 children)

They're all problematic in Linux

[–] theunknownmuncher@lemmy.world 2 points 8 months ago

🤷 WiFi and Bluetooth are not problematic across the board, but yeah there is definitely hardware with bad or no Linux drivers. I just only purchase hardware with mainline kernel support, and never have a problem.

I can't really speak on NVIDIA. Their Linux support used to be terrible, which was their own doing, but may not be anymore? I'll never know because I've switched to AMD for more than just that one reason, and it's unlikely that I'll go back to NVIDIA.