As a newbie in this space, I had interactions with a few distros over the years and lately switched (hopefully) permanently.
My first experience was with Mint 10 years ago. Installing it would cause some GPU driver defect (AMD card) and would turn the whole login screen into an epileptic checkerboard pattern with no way of doing anything. It took me a few reinstalls and a ungodly amount of googling to find a solution which involved opening the terminal at boot process. You can only imagine how frustating that can be for a newcomer.
Later in time I had Ubuntu on my laptop which had a bug that wouldn’t spin up the CPU fan and it would simply overheat and shutdown. I had to take it to a technician to find out what was causing the random shutdowns.
A year ago I decided to try Debian on my desktop PC as many have praized it for it’s rock-wolid stability. It didn’t want to work on my PC. No internet connection and some weird bugs. Took me two-three days to get ti to work and I still don’t know what exactly fixed it as I have applied every possible solition I came across.
Much later, aka now, I decided to go with Bazzite on my desktop as many have claimed excelent support. I wanted to install the mimalloc because I play Factorio a lot and a few reddit posts claimed 20% UPS improvement over the stock scheduler. After downloading the source code and following the 4 very easy steps, cmake would throw some random eerors at me claiming some critical files were missing, although they were right there in the usr directory. Turns us Bazzite some some issue and Fedora 40 compiled the code in seconds without any issues.
Conclusion: Linux users, which are very tech savvy or work in that space, know what to do when things don’t work out, while the rest of us keeps googling and crying over error messages for things that seem trivial. You never seem to know if it’s you, the system or your hardware.
It’s something we’ll take for granted. With enough time and experience, you could fire off a one liner to fix a problem in less than a minute. For most people thst could take an hour, and they’d probably give up within 10 minutes
Could you point me to a good place to start learning how to troubleshoot? I added Unbuntu as a dual-boot to my gaming rig a while back, and when it works, it’s great. But as soon as I hit an error, I drop back to Windows because I know how to fix shit there.
First suggestion: commit to using Ubuntu for a set period of time. Could be a week, could be 2 hours. When you encounter issues, force yourself to stay on Ubuntu.
What you’ll find is that at first, errors will seem like gibberish, then you’ll do some snooping online, and find out how to access some log files or poke around your loaded modules. You’ll slowly learn commands and what they do.
Eventually, something will click, ie; “wait a minute, I just checked to see which kernel modules are loaded, and I’m missing one that was mentioned in my error, that must mean I need to load that module at boot.” You load that module, reboot, try your command again, and bam, everything works. You’ve learned how to troubleshoot an issue.
The best way to learn Linux is to immerse yourself in it. You can’t efficiently learn German if, every time you hear a phrase you don’t understand, you switch back to English, right?
Just come ask here when you have trouble, and we’ll try to help.
When troubleshooting, the biggest thing is searching the web honestly. But some more things to help you out: look for logs. Linux has loads of logs and sometimes can tell you how to fix the problem.
Logs may not be immediately apparent. Some programs have their own log files that you can look into. Sometimes, if you run the program from the terminal, it’ll print out logs there. Otherwise, you read look through journalctl, although this has logs for everything so might be harder to search.
Another useful tip, particularly for system tools and terminal tools, is manual pages. Just run man ls and replace ls with any command, you’ll get the documentation on how to use that tool.
The first thing I’ll say is the reason you’re more comfortable with Windows is because you’ve been using it for however long and learning to deal with the issues it has. The same needs to be done on Linux. You’ll have to learn how it works just like you forgot you did for Windows.
Second, along with logs like other users said, you have to know how to use a search engine well. Most issues will be easy to solve, but some may take some searching. The Arch wiki is a good resource even if you aren’t using Arch.
I can't say I've ever really liked a controller, so I never experimented with fancy ones. The one that was the most fine was the ps controller. the joycon was ok until drift kicked in. The xbox controller made my hands hurt after too long. I think if I'd had more xbox games back then I would have gotten more into controllers to find one for my tiny hands. I mostly prefer a keyboard.
I mean... is this a big deal? Every retro ARM handheld out there runs some version of Linux or Android. I gues Retroid was an Android-focused brand, hence the name, but if you wanted to run Batocera on a handheld there is no shortage of options.
Nah. This is running a Snapdragon 865 SOC with an older Adreno GPU. If you think Windows on ARM gaming is a struggle this isn't going to be your Linux handheld killer. There's also no reason for it to be, the Steam Deck already exists.
For its intended use case as a retro handheld (or an Android gaming handheld, I suppose), this seems like it'll be fine, but I'm also less excited about these mid-tier ARM handhelds now that we have good x64 alternatives with decent battery life and better performance that aren't much more expensive. I still think the cheap, tiny ones are cool, though.
I guess this is nominally cool because other comparables like they Ayn Odin 2, need a bunch of tinkering to run Linux, but beyond that it seems Linux is well represented on both extremes around this awkward middle ground of more expensive ARM handhelds.
the most recent Android is Linux v5 I think, so I’m kind of with you that the gain isn’t huge when compared to modern mobile devices.
Still, for older ARM sets, the max Android they used had only Linux v3, so it’s impressive that they mainlined enough of the hardware to be usable in today’s market.
It could be a big deal if the developers of GarlicOS / OnionOS support it. I have a Retroid 3+, a Miyoo Mini (lost it) , and now an Anbernic GBA SP.
The Retroid seemed amazing at first but after using a Miyoo with OnionOS, I’m not going back to Android retro gaming.
The usability of being able to pick up a hand held and play immediately cannot be understated. Android doesn’t normally shutdown. It sleeps which means it only lasts a few days (not being used!) without being plugged in unless you explicitly pick power down from the menu. If you do power down, it takes over a minute to boot. The Android retro front ends also take hours and hours to setup.
OnionOS/GarlicOS completely power down so the battery always has charge and is ready to go. Because there is no Android, boot to being back in your game (it defaults to powering up right back where you left off in a game), takes seconds. The menu scraping works so there’s virtually no setup needed.
This thing is supposed to be fairly powerful, I don't know that the straightforward, minimal approach of Garlic/Onion makes sense on it. Ideally you'd want a bit more versatility. For that I think the Anbernic SP and that class of slightly cheaper devices probably make more sense.
I mean, as I said above that's my thing with these flagship ARM handhelds. At some point it takes a lot to justify spending a couple hundred on one of these instead of a bit more for a more flexible Steam Deck. The smaller, cheaper ones are a lot more charming, and they fit in your pocket, so they can be a throwaway toy to carry with you.
But hey, we live in the handheld golden age, I'm not gonna complain about more options.
Snapdragon hasn’t had mainline kernel support and has always been a pain to set up, enough so that nobody does it. This is using a snapdragon processor. Those are also fairly powerful.
Using “server” instead of “instance” is misleading. An instance could use many servers behind the scenes. It may be more appropriate to simply call it a “domain” instead, cause that’s kinda all it is. But instance is also well-understood.
If you really wanted to unify the terminology, you would call communities and magazines “groups”, as this is what they are called in ActivityPub. It is a group of all the people following the community.
But I don’t think terminology unification is a goal in itself. Different clients and implementations can use different terminology and that’s a good thing. There’s no need to force anyone to use a certain term. There’s no need to nail down language like that - it is a fluid, evolving thing after all.
A static type sound can occur while biting where you eustachian tubes are cleared. The same thing can happen when yawning (it is why yawning is encouraged when feeling inner ear stress while taking off in an airplane).
It happens without earbuds too, but might be more noticable.
I can personally pop those voluntarily, as I’m a scuba diver, and you have to clear your ears quite frequently.
It’s a silly way to secular-wash a Christian system. If you want a secular calendar, you should have it not oriented around the birth of Christ. Very underrated decision by the dprk to have their calendar based on the founding of the country.
Interestingly, on Taiwan they have the Republic of China calendar (in addition to the Western calendar) which begins from the establishment with of the RoC (1912 on the Western calendar).
I mean, having been to NY, where there was stuff open all night, I was surprised the SF closed down at night. I just expected big cities to be like NY. Nope. Only gas stations and maybe Denny’s until 2-3am.
Depends what you want in an OS. The increasingly invasive ads and loss of control in Windows is overwhelmingly a good enough reason for me. But it is not the case for everyone.
Linux has its quirks, and it’s a different approach to an OS in general, so it can be intimidating if you only want an office machine.
kbin.life
Oldest