Thanks. Finally after Mint didn’t recognise my network adaptor I tried Manjaro (everything worked great, but I don’t think I’m ready for Arch) so ended up on Pop_OS … everything works so I’m going to stick with this for now.
Good to hear, I’ve not had any issues so far. The only “niggle” I’ve had is when pairing my Bluetooth devices I’ve needed to turn Bluetooth on and off for each pairing bit once done they’ve reconnected fine.
Make sure you have the latest firmware for your motherboard. This sounds like unstable voltages for memory, or an overly-aggressive PBO curve. Did you try disabling the XMP profile on the RAM, disabling PBO, and upping the voltages (within safe limits) of the SOC, DDR, and VDDP? You might find some useful info here[0] or here[1] if you intend to run your memory at 3200 MHz.
Motherboard firmware is up-to-date, and I’ve already tried disabling XMP. I’ll give disabling PBO a try, thanks!
I don’t necessarily have to run at 3200MHz, if it means that the system is finally stable. But since it’s already crashing at the default 2133MHz, I suppose there’s no use in playing with the voltages?
It’s difficult to say for sure with certainty what the issue is without trial and error. I would expect that the motherboard’s manufacturer would make sure that their board can successfully pass all tests with the standard JEDEC spec for DDR4 (2133 MHz).
Since you say that you’ve tried different RAM kits, another alternative could be the cleanliness of power from the power supply. Perhaps there is intermittent voltage droop, and you need to experiment with the Load Line Calibration settings to adjust for vdroop between idle and load. Disabling frequency boosting and manually setting the CPU frequency could help check if it’s related to that. PBO curves might be undervolting too much while idle.
I’m a bit speechless right now. I’ve disabled PBO and didn’t have a single crash since then, everything’s been running fine for hours. Just to make sure that this really was the issue, I’ve enabled PBO again - but still haven’t experienced any crashes in the last hours. I have no idea how simply disabling and then enabling the feature again fixed my issue, but for now it seems like all is well.
Do you have any explanation for this weird behavior?
Anyway, thank you very much for your suggestion, looks like this actually did the trick!
Sounds like voltage droop and/or a motherboard with faulty automatic “training” settings. I don’t recall if the Ryzen 3000 had custom PBO curves, but tweaking this can fix it. Upping LLC and the SOC and CPU voltage slightly alternatively could help. Though I’ve had my most stable overclock by disabling PBO entirely and using a manual CPU multiplier.
[cosmic-randr] uses the wlr output configuration Wayland protocols.
Does this mean cosmic-randr should work on other compositors that support the wlr output configuration protocol (e.g. sway, hyprland, river, …)? It’s great to see cosmic adopting existing protocols, instead of compositor specific protocols (or worse, no external app support at all).
Also, it’s great how portable Cosmic DE seems to be, as it’s already mostly packaged on NixOS. On first look, cosmic-term seems to be a quick terminal so I might switch to it, as well as cosmic-files.
If they support the wlr output configuration protocols, then yes it’ll work fine. There are some more advanced features that we want that aren’t supported by the protocol though, so we will likely develop some cosmic protocol extensions for those features.
How many actual PC handhelds are there?
The link in the article that promises “plenty” of handheld examples talks about Steam deck, Asus, and… the switch. And that’s it. And obviously the switch is not a PC handheld, so… ?
There’s quite a few. Steam deck and Asus, as you mentioned, but there’s also AyaNeo, GPD, OneXPlayer, Aokzoe, Lenovo, etc. And many of these brands have several different models, if you’re counting individual products.
Anecdotally, I have an Aya Neo. I know a few people with a few of the others brands. There’s a decently sized Aya Neo Discord that I’m part of, and I would assume the other brands have something similar. There’s definitely use of non-Steam handhelds, or there wouldn’t be a growing market for them.
I personally love it, and yes it can with a dock similar to the Switch’s. It’s ran every game I’ve thrown at it, and I’ve an original 2021 version. There’s a few quirks, like the joysticks will sometimes just decide to not do a random direction, but recalibrating is easy. Obviously the resolution quality isn’t as stellar as if you were running a pc meant output to a monitor, but on the built in screen everything is crispy. It’s decently heavy though, so my baby wrists get tired after a while. But yeah it’s great, playing whatever wherever is pretty ace.
Not sure what you mean – they all run Linux. The images just have the video hardware configs baked in with a preconfigured user and start script. You would be amazed at how easy that is to do, all things considered. I have a few kiosk configurations I created for the two Home Assistant panels I have in my house.
And, most importantly, money bags to subsidise the hell out of it. Let’s not kid ourselves here, the damn low price is one of the main reasons why people buy the SD rather than the ~2x more expensive alternatives.
Some of my favourites are Void Linux, Artix and Opensuse Tumbleweed
Void was my first non-systemd distro, and it was super snappy as well. Some packages may not available but overall I had a really great experience with it. It also offers a version with the musl C library. Pretty cool if you ask me.
Opensuse tumbleweed is an overall a great distro, it’s one of my favourites. Also I noticed that many people have recommended it and that’s for a good reason. It’s installer isn’t that user friendly but I would prefer it over Fedora’s installer any day. ( I haven’t tried the last 3 iterations of Fedora, so it might have changed now )
Artix is well… arch with different init systems. Nothing too crazy. Its what I have been daily driving for the past year or so.
You need to first understand what kind of interaction you expect with your OS. For this, you can start by considering what you use your OS for and currently what you do for your OS. e.g. Before I jumped to Linux, I was just starting to learn PowerShell on Win, because I saw a lot of places in my system where I wanted to use it. I felt consistently dissatisfied with the lack of things I could just tell the system to do, making me go to scripting. This way, I knew I won’t have a problem with putting time into something that takes a lot of configuring. But since I was still new and wanted an easy start, I went with Manjaro KDE. It was based on Arch, but had a system of differed updates, giving me a feel of it being easier. Plus, it had a lot of customisations out of the box, some of which, I learnt from, when making my own configurations for EndeavourOS. EndeavourOS considers itself to be more terminal oriented, and it is possible to easily get a full-fledged tty system, just by selecting it in the installer. I chose KDE because I like changing the Appearance a lot, but you might want to look at other DEs depending upon your expectations.
Ubuntu has been shifting a lot to snaps, so if you want your computer to be snappy (the literal meaning), you might want to avoid it (ironically). But at the same time, if you want less configuration requirements and want to keep most of your exp outside the terminal, on top of finding it easier to install software from vendors’ websites, you can consider it. If you are fine with putting in the minimal amount of brain usage it takes to understand the installation instructions of the website - and by that I mean, read the heading telling you which distro the copy-paste text is meant for (I know ppl too lazy to do that and trying paste an apt command into Red Hat) - I suggest Fedora/Linux Mint and a slew of others.
DE = Desktop Environment apt = Package Manager (kinda like an app store on terminal) used for Ubuntu
P.S.: If you choose an Arch-based distro, make sure you keep a backup OS that is in the Debian/Fedora tree. I keep a Debian KDE, mainly for older linux games, which ask for packages that have been long removed from Arch, but it is useful in case you break something. That way you won’t have to wait for the time it takes to make a Live USB and can just restart.
Hi! Here’s you, like 2 yrs down the road. I have no opinion on the server OS since I started with ubuntu server but my projects went a similar direction.
One major thing I’d recommend is thinking about security: web facing servers with your private data on it are a very bad idea. So unless you mean a website for personal use, I’d split the “home” server and the “personal web server” or vps in two so you have the stuff you want others to use unsupervised and the stuff you use at home and from the road.
Another thought is bandwith, unless you have insane upload, I’d stay away from web facing stuff like websites, game servers and social media instances. This works on a cheap vps with gigabit bandwith up and down. Way less hassle and less security issues.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.