May just be bad RAM as well on a 12 year old machine. Should be cheapish to replace. Try running a memtest

RAM or Video card issue. Are you SURE the entire machine actually locks up, or just the display? Try ssh’ing into the machine when this happens to see if it’s actually staying alive, though the display stops working.

My guess is this is in GNOME? If there isn’t an eject button next to the mount name, that’s just a “favorites” link that got added, and not the actual mount. Right-click to remove it if you don’t need it anymore.

Modern HID drivers are very generalized and abstracted away from the hardware pretty much anymore in Windows and Linux. Aside from specific button customizations (pretty much all done in companion app software, not the driver anymore), you shouldn’t see any issues. The DPI switching should be done on device, but maybe ask the manufacturer before you buy to be sure. Since you don’t care about RGB control, I don’t forsee you having any issues.

You might still need this: https://github.com/linux-on-mac/mbpfan

Also, install TLP for better battery life management. Maybe have look at powertop to see what allows using power.

You’re just a coward to admit you were wrong?

Sorry to be rude, but can’t you just go read the docs to understand this?

Fedora is a fork of Red Hat, the same way Ubuntu is a fork of debian. Yes, it is now singular to being its own thing. It is also not corporate controlled.

This will give you a good inkking as to what is happening in the background. We also need to know how you have it installed via rpm pack, or flatpak?

Just figure out what you want to do. Its not like Windows where you need to run scrub scripts, or turn specific things on or off. It’s very subjective.

Examples:

• are you in a laptop? You want specific tools for battery and performance tuning.
• are you gaming?
• are you working audio or video?

Just edit your comment and throw a few things out that you’d like to do, and you’ll get a much more complete list of suggestions and tips.

No, that’s not at all true.

Red Hat owns the Fedora brand, sponsors the project financially, technically, and with some infrastructure, but does not own the project, nor pay everyone involved. Aside from a project lead here or there, it’s all community run. Literally anyone can contribute or volunteer.

A lot of people on here are new to the ecosystem 🤷

They owned up to it, and immediately dealt with the issue.

It’s open source, free, and run by volunteers who bust their asses to make these releases happen. I wouldn’t worry too much about it if it’s been working the other 99% of the time for you, and this one issue has you on the fence about it…

Check your memory. Also, if you’re seeing graphical glitches, check to see if the machine actually did boot still by pinging or sshing’ in. Could be a bad graphics card.

If you do get a clean boot, check dmesg and syslogs to find any potential errors that are happening in the background.

Then you need to ssh into both devices and confirm they can both ping each other via the tailscale interface as a starter. That will at least shownif you have a routing problem.

My first guess is that using an actual hostname isn’t going to work for you if that hostname is served by your local network DNS (meaning, not using magicdns on tailscale), which you would not be on when connected via tailscale unless you override your DNS server once connected.

Try by IP instead. Give errors if that doesn’t work.

Can you be more specific?

• What are you using to try and connect to the share?
• Can you ping the NAS over the Tailscale interface?
• If so, can you connect to port 445?
• Can any other devices also connect to the share?

That is a systems job for finding and mounting swap space on your machine. Is it failing?

When you run 'dnf update ', you want it to say it’s going to install kernel 6.9.X.

Boot to the previous kernel and run updates until you get a 6.9, or go download and install the rpms yourself.

They pushed a bad patch with 6.8.10 I think? They had to roll it back and push another real quick, but some caching issue still delivered it to a bunch of people. You should on the 6.9 line now anyway as 6.8 is EOL.

Your disks volume can’t boot, so it’s dropping you to a prompt to investigate. You need to run a disk check with ‘fsck’ at a minimum. If you’re not familiar with the CLI , just boot a LiveISO, and check your system disks from a desktop you’re familiar with.