AMD APU uses whatever system RAM is as VRAM, so…yeah. NPU as well.
AMD APU uses whatever system RAM is as VRAM, so…yeah. NPU as well.
Here’s a quick idea of what you’d want in a PC build https://newegg.io/2d410e4
You can have a slightly bigger package in PC form and doing 4x the work for half the price. That’s the gist.
I just looked, and the MM maxes out at 24G anyway. Not sure where you got the thought of 196GB at. NVM you said m2 ultra
Look, you have two choices. Just pick one. Whichever is more cost effective and works for you is the winner. Talking it down to the Nth degree here isn’t going to help you with the actual barriers to entry you’ve put in place.
I’ve not run such things on Apple hardware, so can’t speak to the functionality, but you’d definitely be able to do it cheaper with PC hardware.
The problem with this kind of setup is going to be heat. There are definitely cheaper minipcs, but I wouldn’t think they have the space for this much memory AND a GPU, so you’d be looking for an AMD APU/NPU combo maybe. You could easily build something about the size of a game console that does this for maybe $1.5k.
https://discourse.joplinapp.org/t/joplin-server-documentation/24026
4 minimum. Joplin doesn’t need a server though. Just configure the storage backends to be whatever you want.
Sure seems like you’re either sourcing these images wrong, or they’re missing something. The docs themselves even reference this command as it’s a good way to test the container is linked to the host hardware properly.
Maybe try starting a shell and finding if that executable exists in the image.
‘docker exec -it jellyfin nvidia-smi’
You need to be running the Nvidia container toolkit and specify the container be launched with that runtime if you want direct hardware access to enc/dec hardware.
Yup
No offense, but this literally talked about nothing at all. The last half is just some ideas that don’t follow a cogent line from one thing to the next.
You should try writing a script about a topic, and sticking to it . Especially if you don’t feel comfortable about speaking off-the-cuff facts about what you’re delivering. It connotes a lack of understanding and knowledge about a subject.
Ask yourself when speaking about something: if a listener took something away from this speech, what would it be? Then write for that prompt.
Probably easier to just unblock Google, send some messages, then look at your filter logs to see where they are going.
Guarantee you’ll run into issues when you hop towers or networks though.
You should read up on Wireguard connections and configs to understand what you’re actually doing. I wouldn’t blindly follow guides without checking out what each step does.
You need ‘PostUp’ and ‘PostDown’ rules for your connection to handle routes when the connection comes up or down. That’s where your discrepancy is.
Unsure how networkmanager handles that in the GUI if you’re using that, but it would be under something like ‘Routes/Routing’.
First things first: you may be misunderstanding how phones run Linux. A stock Debian install certainly will not work for a number of reasons, but mainly drivers. Storage is second. Phones are flashed with specific images created to work with the storage in each specific phone.
Second: you’d need to make sure the bootloader on your phone is unlocked and able to be used for such a thing. Quick search shows that Ubuntu Touch did work on it at some point, but was deprecated long ago.
Third: if you just want practice, you can probably find packages to install on the phone that will run an HTTP server. That might be a simpler path.
I’m not saying don’t try, but you’d be starting from scratch, and if you aren’t familiar with these things already, I’m not sure this is a forum to get enough help on the VERY involved process of bootstrapping just a basic running kernel on your phone model. It probably can be done, but you’d be doing it from scratch it seems.
Handbrake or VLC. I’d honestly just learn the CLI to make this work better for your benefit though. Much simpler to do remotely if you want changes.
https://docs.datalust.co/docs/collecting-docker-container-logs
You have a formatting issue. Solve for that instead of just switching to something else hoping it will get better.
I’m not sure what you mean. You either need to post a lot more details and information about your setup, or you need to read and understand the Tailscale docs.
For all traffic. Tailscale ACLs deny by default. If you’ve never changed them, you need to do that.
You need to adjust your ACLs to allow traffic over Tailscale.
As fast as it gets to the CPU. That should be pretty obvious.