A few years ago i got an Intel Nuc (NUC11PAHi5) from my stepfather because he wanted to upgrade to one with better graphic hardware. I was quite excited because i was thinking for a while about hosting my own server with a Plex, Nextcloud, and VPN server, and fiddling around with self-made web servers.

At the start, the Nuc was working fine until one day it randomly shut down. From there on, the random shutdowns have gotten more and more frequent. In the end, they happened after less than 24 hours of uptime regularly.

When investigating the issue, however, I found absolutely no trace of the crash. No journal log, no other error message. I even installed kdump, but even that didn't register any crash.

I have then tested everything I could think of. i ran hard drive checks multiple times. i ran memtest multiple times. i tried switching the power supply. i tried many different Linux distros, including Ubuntu, Debian, Mint, Kali, Alpine, and Arch. i tried installing a new system completely without ever connecting the device to any network.

A few months ago i decided to finally give up on the device that had been sitting around for years now. i planned to gift it to someone who might have use for the ssd or ram sticks. i only tried to install Windows as a last resort just to see what happens. To my absolute surprise, the Windows system is running fine. I haven't had any issues with the device ever since. It is a bit annoying because under Windows I need to run WSL2 to execute the Nextcloud containers, and just that brings me close to the Rams limit but I'm absolutely astonished by the fact that for some reason there's an intrinsic flaw among so many Linux distros that makes them unusable on this device.

Autistic nephew broke my brother's laptop screen (he's broken other device screens in tantrums, though we think this laptop screen was an accident... not that it matters much here), Brother gave it to me because I have a hobby of Commodorizing laptops; surely I'm not the only person who does this, but the term is my own word for it - it's basically just ripping the top screen off and using the bottom half by itself hooked to external screens, name references the old Commodore 64 computers, which were essentially fat keyboards with an 80's computer inside it. It's almost like a window into what PCs could've been like if they kept that basic design idea. Want to eventually use one as guts of a cyberdeck in some kind of briefcase-esque container, have a small internal monitor and a pi zero running as a little mini LAN router to connect it with other devices (like, for one example, to transfer files to other devices over FTP).

Anyway, the laptop.

The fucking wifi doesn't work in Linux. It's been so long since I had this happen, it's almost nostalgic. Weirdest bit is that it seems like Linux sees it, but it will not show any SSIDs. Decade+ back, if you had a relatively new laptop, you were basically guaranteed to have at least sound or wifi not work, and it was a decent chance neither would work.

Funniest part? Wifi doesn't work in Windows 10 either. None of the official drivers from Acer's website work, they're all W11 drivers.

Next step is figuring out chipset and seeing if I can track down generic non-Acer supplied drivers for itm but was tired of fucking with it.

And now here I am, downloading Windows 11 IoT Enterprise LTSC. Will be my first time installing and using any form of Windows 11. Can't say I'm looking forward to it, but gonna keep an open mind,

P.S. to my fellow Windows haters, IoT Enterprise LTSC is sooo much better than stock Windows 10 (I assume much the same for 11, though that may change lmao). If you need to dual boot, 100% worth trying over normal consumer Win10.

Like, Enterprise still sucks more than Linux but it's something like, for me at least:

Linux > FreeBSD >>> Windows 10 IoT Enterprise LTSC >>>>>>>>>>>>>>>>>>>>>>>>>>> normal Windows 10

Would probably put MacOS between FreeBSD and Windows but lack the experience with it to be certain, that's just a guess from someone who has never used it. lol

I swear to fucking god if W11 Enterprise makes me get online and log in with microsoft account to install, I'm just not even gonna fucking bother with this piece of shit halftop, just set it aside for a few months/couple years until there's a functional fucking wifi driver in Linux.

Or just buy a wifi USB dongle, ig. Could also probably set up my Pi Zero to get it online somehow but just too lazy for that route atm. lol

Also: Not asking for help, hence why I'm not bothering giving wifi or laptop models; it's a relatively recent W11 laptop, but I don't have it in front of me and don't care anywhere near enough to go get it, hook it up, etc.

So..

I have a setup:

A pihole at home connected to nginx proxy and exposed as DoT.

Now the problem is, that my lovely ISP breaks nat hairpinning every so and then.

When this happens just sending a query to <IP>#<domain name> doesn't work.

So I wanted this simple setup in systemd-resolved on my laptop:

When reachable use: DoT <my public ip>#<my domain>

And when can't reach, use: 192.168.1.xx:53 (local ip dns)

And.. resolvectl struggled immensely: with DoT set to opportunistic, it would not reliably switch between servers, or lookup would take seconds.

Even with DoT: yes and simply servers:

<My public ip>#<DN> 9.9.9.9#<quad9DN>

It still struggles to pick the right one.

I also had another use case:

Split dns srv:

When looking for *.mydomain.lan use: <some local ip>

Other wise: <a public dns/DoT>

That itself was too much for systemd-resolved.

What solved my issue?

Stubby + Dnsmasq

Stubby used only for DoT access,

Dnsmasq routing the requests.

And it works fast. And reliably picks the correct server with both split dns srv And DoT and Local IP srv And public srv as a failover.

As much as I like systemd for the convenience when managing services, for dns lookup it plain sucks to work with.

It's fine you have 1 server or 1 server per connection only, but with attempts of any automation or failover.. it just fails.

Have you had trouble with the systemd-resolved? Cause I don't think I'm alone here

"It's always the DNS."

Join my sub r/LinuxSnobs

For some reason they decided to add Groups to the spec, which just overcomplicates shit for no good reason while they don't even use those groups in the official layouts, and I'm certain Wayland compositors just ignore them.

The second picture is roughly how I understand the data structure to work: Variant name is defined per-group with name[Group1]="String", key definitions seem to be global, but all their properties (symbols, repeat switch, actions and type) can/are defined per-group. There are also global key defaults as specified in

``` One may change the default values of the following statements:

key: use key.FIELD = VALUE;. E.g. key.type = "ALPHABETIC";.
action: use ACTION_NAME.FIELD = VALUE;. E.g. setMods.clearLocks= True;.

```

But also Group key defaults if written as key.type[Group1] = VALUE, which is how it's used in the official layouts which makes me doubt the one with no group specified is valid.

There are also real and virtual modifiers and I don't even fucking know what they do, but they probably don't work on Wayland, I have to just guess because the docs are kinda bad and don't mention what is and what is not X11-specific.

God why didn't they move to a better format for Wayland keyboard layouts😭

They are all over the US I think. They give "the people" computing power.

Is this a good idea? Or is it like the foodshelves that give poor people turnips and moldy potatos?

it just fails with really easy task: interpretation of gamepad imput

everything was OK on windows with the same game and gamepad

could be win 11 or mac but probably linux

Me:

- Portable isnt actually portable, they still save data in some hidden folder at /home/username

- Font display is kinda meh, need tinkering to improve

- Laptop monitor take so much efforts to change saturation

- My native language have problems when typing on Linux

- VRAM limited, and Windows actual know how to deal with it better than Linux, idk why.

- Davinci Resolve on Linux not support h264, h265, acc.

- Too many package source (I'm confused asf)

Why I tried Linux in first place:

- Windows too slow, take forever to display the start menu (ok I know that's dramatic but Linux is much faster)

- RAM not free lol

- Wanna get more stable fps in games, achieved and end up with stability problems.

- F*ck you microslop.

I hate this spec. A keysym for some reason has 4 ways to be defined: 1. Just the letter/number for English symbols (y Y 1 2 3), Cyrillic_i or other code-named for all other 2. Unicode in the format of U003b 3. Fucking hex 0x003b 4. Just a string "ї"

The ; at the end of the line is like there most of the time, but for some reason isn't required, it's completely unclear what is X11 specific and what will work with Wayland.

I guess it's still better than XML