this post was submitted on 23 Aug 2023
786 points (95.7% liked)
Technology
59349 readers
5184 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
I think the first thing was Windows' fault (and also the fault of my dual boot setup, which i imagine most casual users won't be going for) - apparently "Fast Startup" means doing some hardware shenanigans that prevents Ubuntu from hooking into the motherboard's network adapter.
After disabling that, I had to install a specific version of the nvidia graphics driver (535) from a PPA to get all 4 of my monitors working. Before that, I couldn't configure display settings at all because my screens would flash for too long and prevent me from clicking the "Keep Settings" button. And before that, only one monitor worked and the other three were black screens that I could move the mouse to, but couldn't move applications to.
And finally I had to figure out how to set a "default" audio device because apparently this isn't a configurable thing (that I could find). I noticed I would have to manually set my audio device after every reboot - after enough reboots I found that there is a command to list audio devices by ID and to set the active output device by ID, so I added it to the list of startup commands. Honestly this one is the most perplexing because I would think setting a default audio device from a list of multiple would be some pretty basic functionality. I'm guessing that I probably just missed it, or gnome hides it.
After that is mostly gaming setup stuff. I would consider it to be common knowledge that most games aren't intended to be run on Linux, so I don't mind some difficulty there.
Slightly unrelated, I have learned that apt purging openssl is a huge no-no and am now reinstalling Ubuntu again entirely :)
I can't speak for the Nvidia issue. (Only that it is widely know that Nvidia actively works against Open source and only just has begun changing their stance, so Nvidia support is still poor on Linux. Their proprietary drivers aren't great either. I stick to AMD since using Linux, they work great out of the box)
But the audio issue baffles me. Under Kubuntu with KDE I just klick on the Loudspeaker in the systray and choose the device. It even remembers it over unplugging and replugging devices.
Rgarding openssl: Thats the price you pay for freedom, you can change the system how you want, even into non working states ^^ BTW: You can repair such mistakes with a LiveCD even major ones like this.
I had a dual boot where windows would from time to time rewrite the boot and the system would just load into it.
Because it was an older motherboard it still had IDE and SATA; after some research, I found someone saying it was a BIOS "feature" where the default master HDD was alway on the IDE channel. The solution: get rid of the IDE disk (and windows along with it).
The rest of what you describe remembers my own misadventures when I started. But back then at 2006 and with Debian.
I've read articles where people were saying that even running the NVidia Quadro boards was very much anti-climatic, with the biggest hurdle being installing the proprietary drivers.
And when it comes to games, WINE is going very far to make many things works where they were never intended to. And many titles are already being shipped with penguin in mind
Have fun!
PopOS Nvidia version for Nvidia machines - much better experience.