Normally the TV (and monitor) will be advertising a 'preferred mode' in its EDID data and the OS will probably be selecting that mode or a mode that both support. If it isn't (and some TV's don't, or don't do it properly, or even lie) then the OS doesn't know what to do with it or selects one that the TV doesn't actually support. Often that's things like the TV claiming it can do 4096x2160@60p (which is apparently "cinema 4k") but can actually only handle that for 30p.

The other thing that has screwed me in the past are garbage HDMI cables. The easiest thing to try is a different cable. Many cheap/older cables are not spec'd for 4K60p and while the TV may report that in their EDID the cable can't deliver it.

If the OS is using X11 or Wayland will change how you configure the mode. I forget off the top of my head what the exact commands are, but that should hopefully be enough to search for help for your OS. If you figure out the commands just drop it down to FHD and go up from there. Using the CLI will let you do it via SSH and not be dependant on the screen because ng available.

Probably need to adjust hdmi settings involving frame rate or handshake or something similar. I’m troubleshooting a similar type of issue with my projector and our home theater receiver. Search the model of television for specs on what specific input it accepts and go from there, I’d think.

Out of curiosity, what’s the full specs of your intel nuc? Had one of those bastards last two years before it shit the bed on me with MOBO issues

My 3070 worked fine with hdr in kde arch for over a year.

I will say though HDR isn't something you should turn on unless you have a display that does good HDR, otherwise everything looks washed out.

I agree with your first half, but regarding the second half I'd argue that docker isn't a necessity, especially early on. You can host multiple things fine without docker.

Docker is nice and all (or so I've been told), but I'd put that a lot further down on the list of things to learn. Understanding the basic services individually is more important than containerization.

My recommendations is check out the Linux upskil challenge yo get your Linux skills to a OK point then start learning docker.

You can run a lot on a pi and starting with pihole is good. Check out !selfhosted@lemmy.world for what others are running.
With docker you can run other things on the same pi like a todo list using DoneTick, or retro games in the browser with RomM, need a PDF messed with? Fix it up with BentoPDF.

After a while you will need a portal like homepage so you can keep track of what is running.

Running a few services from a raspberry is as good a starting point as any.
Reading official documentation is always a good idea, instead of getting second hand knowledge from youtube:
https://www.raspberrypi.com/documentation/computers/os.html
https://docs.pi-hole.net/main/
https://github.com/pi-hole/web/
https://docs.berryaudio.org/getting-started/introduction.html

Regarding storing pictures from your phone, read up on the 3-2-1 backup. Personally I go for NAS + USB Backup + Remote backup at my parents house.
https://www.backblaze.com/blog/the-3-2-1-backup-strategy/

Immich is immensely popular for photo gallery server use nowadays but it might be too heavy for a raspberry pi, might be better off testing something like https://github.com/bpatrik/pigallery2

It's been a long while since I set up a server other than jellyfin and that was super simple.

Long ago i set up LAMP(linux, apache, mysql and php) for my web testing environment. You could probably do the same. Put your files on the server and use services like mpv for video, mpd for audio files. Or just set up jellyfin or kodi.

For picture and file sharing you could look into nextcloud.

As far as hardware i did have my razPi B+ running kodi and it wasn't bad. Great place to start.

Other more experienced users might have some better suggestions.

Welcome to the endless rabbit hole that is self hosting!

I think the best advice I could give is keep it simple, just add one piece at a time, and take notes.

Personally I would stay away from youtube. Get used to reading installation instructions from the source and documentation, it is a valuable skill. Then come here and ask questions if you run into problems. Pihole is a great place to start, it looks pretty begginer friendly (I have not run it personally, but I just read through some docs)

I also started with pi way back when, and honestly it adds one more thing you have to learn about while you're trying to learn about hosting. It's not too bad, especially if you dont mind the command line, but you could get your hands on an old laptop or desktop for cheaper. In fact everything I use runs on a $30 desktop from 2015 (I did upgrade it a bit lol) and my rpi4 is sitting in the corner collecting dust. A more familiar interface will make troubleshooting less frustrating. I find the desktop runs a lot better than the pi too.

There's so much to learn and you will probably feel overwhelmed at times, it will pass though, just stick with it.

1. Yes. Nvidia drivers are usable enough, but they regularly cause power management related issues for me. I gave up on sleep because of Nvidia drivers. One update breaks it and then the next update fixes it, only for the next update after that to break it again. Never had any issues before the current Nvidia GPU.
2. Their drivers are simply better integrated into the OS and better developed for Linux. That's all really. AMD drivers have more effort put into them.
3. Bad. Not good. Expect tons of compatibility issues and straight up impossibilities and jumping through hoops.

I have an Nvidia GPU and I’ve been able to get HDR working on Linux (Bazzite gnome) with some tweaking for specific games. I haven’t really tried watching movies with it yet.

1. I run an Nvidia GPU daily, with little to no issues. I can stream via OBS, I can play nearly all of my games (with very, very few exceptions), and I can still use features like raytracing. Note that I don't do anything with CUDA, so I can speak to that if that's something you plan to utilize.
2. AMD has a more open driver implementation, making it way easier for Linux devs to integrate and improve things for the end user. There's currently an open source community project called NVK that is likely to supersede the closed-source Nvidia drivers, but that's still a few years away from being fully at parity (though it's making big strides relatively quickly).
3. I don't have HDR, so I do not know. My vague memory indicates support stems from Window Manager support (i.e. the engine that draws windows and determines their behavior), so look into which window managers implement HDR.

If you've got a relatively recent gpu, NVIDIA is fine on Linux these days. It's changed a lot in the last two years specifically.

HDR works fine outside of games, but is limited on the number of Wayland compositors that support it. KDE plasma and Gnome are the only two I know of. Most of the others don't.

HDR can work with games, but it involves a bit more playing around under the hood with gamescope. But that's an issue with steam/wine, that impacts NVIDIA and AMD.

I've been running an NVIDIA setup with two HDR monitors on KDE for a couple of years now, and it's perfectly fine these days. It wasn't when I started :)

If "service manager" doesn't ring a bell, think of it as a "manager of background tasks/applications". Some applications which only run in the background as background processes are called "services" (sometimes also called "daemons" or simply "servers"), and systemd offers ways to create/start/stop/restart/manage/introspect those, as well as configure how and when they start, what permissions they have when starting, and things like that. It basically replaced very old tools like "inetd".

The other main part of systemd is that it's an init system, which means that it's meant to be started as the very first process (PID 1) by the kernel during startup, and it then launches all the other processes/services which need to run before you even get to log in. Compared to the old sysv-init system which systemd basically replaced, systemd is faster and much more featureful and modern.

systemd also has a lot of other more optional components (it's a big bundle of system tools, altogether). Whether these are used is up to the administrator or the distribution which might preconfigure them (or not).

As usual in the open source world, there are alternatives for everything. You don't technically need to use systemd, or you could just use some of systemd's components and not others, but its main components are the default for most distributions nowadays. Some more niche distros pride themselves in not using systemd at all. But systemd is great overall (there's a reason why most distros use it).

I don't have suggestions, though I could look for some later. Maybe someone with personal experience with them can chime in.

Basically, search for "free online beginner coding classes". Avoid anything paid for now. There are a lot of scams, but you really don't need to pay for classes to learn.

Failing that, search YouTube for tutorials, though it helps if you know what you want to do. Start with something simple. For example analyzing a data set, make a simple game, something like that.

I'd like to try out the free online courses as l get to understand vs code better by going through the course. Could you suggest any ?

Git is just the version control part and there are better clients for git than vscode. What else will you be using it for? E.g., Python code? Web dev?

If you're completely new to dev you may benefit from some free online courses that are about what you're looking to do. Most dev classes already use vscode and git, so you will get that part anyway.

You can use qemu or virtualbox or hyperv (if your windows version supports it). Qemu without any front-end is pretty hard to use for newbies, I would go with virtualbox.

It can. Depending on the Windows 10 version you can use Windows Subsystem for Linux to test out stuff or go full VM with Microsoft Hyper-V

Qemu is a terrible idea it would most likely be slow and hard to use. Try Windows Subsystem for Linux (WSL) for a while, and see how you like it.

All I know is tailscale might work:

• https://docs.bazzite.gg/General/VPN/?h=vpn#tailscale
• https://blog.dmcc.io/journal/tailscale-adguard-dns/

I don't know the specifics for that OS but if you search "set DNS servers for 'os here'"

I don't know how. If you've got an explanation for that I'd like to learn.

Any reason you are installing it as opposed to setting the resolve.conf to use the Adguard public servers?