Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "mst"
When my company moved to the big city we all got new equipment. I selected a ThinkPad and two 24" Dell monitors. Most got themselves a MacBook pro and a 27" Samsung monitor.
Once the new great arrived I started my journey to free the poor ThinkPad from the spy-software that is windows and install Arch.
Everything went smooth until I connected both monitors via MST to the single mini Displayport. Screens flickered, flashed or started dark. Even the display inside the ThinkPad. After half a day of trying to get MST to work with the Nvidia/Intel hybrid graphic inside my ThinkPad I installed Windows on the second ssd and got some actual work done.
The next day I finally managed a static xconf that had all three displays in just the right configuration and I started to work on Linux.
The story would end here if Arch wasn't Arch and I had not installed updates when I did.
After about 6 month of happy working on Linux Paradise I updated Arch since it was overdue (two weeks without). Shit hit the fan. Cinnamon's display manager didn't like my xconf and crashed during startup. Sadly from previous experience I knew that this was the only dm that would work somewhat stable with my hardware comp. I tried to debug, created multiple issues on the various GitHub repos and invested another week into it before dropping Linux again.
I never doubted my knowledge of Linux more than during the times I tried to get MST working with Nvidia/Intel graphics on my ThinkPad.
Recently I switched to a 27" one monitor setup and I'm back on Arch without any trouble because MST isn't in the mix this time.
I guess the story had a happy end after all3
Ah Christmas again...
That time of the year to fix your parents computer problems or in my case I am still trying to eliminate windows XP...2
So sick of my coworker explaining to me how I should do a task. Dude, I've already planned out how I'm going to handle the situation. If you really want to help, wait until I create my pull request, review it, and then make your suggestions there. Unless I ask for your advice on how to do something, I don't need you to tell me how you would do things, especially since i have, what, 5 years working in the framework when you have 2 months?
Manjaro has some quirks that annoy me(no MST timezone, spotty support for my WD NVME), so I decided that since I'm not interested in any pre-configured graphical desktop of any kind, I should just dive into Arch, since it increasingly felt like that's what I was doing anyway but with Manjaro to dull the blow. So I did, and I am over the moon for doing so. Lots of gnashed teeth, but DDG indexes an answer to every question I've had, and it always makes sense when I find it. I've enjoyed having to dive into systemd in a much more low-level way than ever before-- to actually LEARN what it's doing, how, and why.
But one by one, I have been faced with some issue that I need to resolve, and one by one, I've knocked them off. The result now is the best work and gaming desktop I have ever used.
Arch is not for geniuses or wizards. Just patient people who are willing to read. The payoff is staggering, and many times over worth the effort.4