

Lol…yuuup


Lol…yuuup


deleted by creator


Well, like I said, there are plenty of guides out there detailing how to make your own image, like this one
As far as your HW acceleration, I’d check to make sure which driver is actually loaded, and if it’s properly showing it loaded.


They have images to flash to it. Just flash whatever they have, or build your own. Plenty of docs and guides out there, but that version of Ubuntu is way too old to make it very useful: https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-devkit


Push button just like anything else. Same issues exist on Fedora that exist elsewhere, which is really an Nvidia problem, and has nothing to do with the distro.
There are a couple distros that install Nvidia drivers as part of their package selection, but they also have the same issues, because, Nvidia.


Every Linux distro will work with your hardware, aside from edge case components in certain situations. There is no difference in distros for hardware compatibility, unless you’re thinking of running a very old versions of something. Anything will work.
There is also no major difference between distros for gaming performance. The only difference in “gaming” distros is that they have certain software preselected and installed. You can just do this yourself anyway.
I currently suggest Fedora for beginners because it’s dead simple. The big difference between any distro is going to be the default Desktop Environment, and you can choose whatever you want after you install anyway.
If you like Windows’ UI, give KDE a shot. If you want something more like MacOS, go for Gnome. Either work great.
If you want to try multiple, download some LiveUSB images, start em up and poke around a bit. If you change your mind after install, you can just install a different DE and switch over without needing to reinstall the entire OS.


This isn’t a distro thing, it’s generally the Desktop Environment, though with the Surface devices, there is a custom kernel lots of people use that has some extra drivers for the rest of the hardware, so look for that. You can use it with any distro.
As far as the DE, Gnome has better general touch support over others right now, so it’s probably going to give you the experience you’re expecting. Every art app I’ve tried with a pen has great pressure support.
You don’t need to “Install” them like in Windows. Everything in Linux is just a call to launch something, and for Python is just python someprogram.py.
If you’re regularly going to be calling this program, you can put it anywhere makes sense for you, but generally somewhere in your PATH, and then you can make an alias for your preferred terminal to launch it easily.
If that’s super confusing, give this a try (cross platform): https://github.com/InkAurora/PythonAliasManager


You didn’t mention what Desktop Environment you’re using.


I think you’re unfamiliar with the general ideas around exactly what a display is in an OS, so don’t be offended if I break it down:
In Windows, there is only THE compositor, meaning no separate distinction from one process or another, it’s all the same display process as far the OS goes.
In MacOS, there is the compositor (the screen display manager) that loads first, and everything after that is a subprocess that handles different things: login security, window management, launcher, search…etc.
In Linux everything is generally separate. Your first login screen is its own process, which then calls another process to load your DE or whatever, and then everything is handed off after that.
If all you want is a “Kiosk Mode”, you just skip everything else. No display manager, login manager, DE…etc. You just boot the kernel, and have a compositor load. That compositor will then be responsible for displaying what you launch from there. So you Daisy chain things like that, and skip all the stuff you don’t need.


You can, but you need to basically completely turn that laptop into a router. A cheap WiFi bridge would be more flexible.


Wayland isn’t going to be your issue if you’re saying you’re building something from scratch. It’s pretty lightweight on its own, because it’s just a framework of libraries and APIs.
The compositor and environment you build around that is what will be taking the majority of resources to run whatever rinterface you’re going to have.
Sway is fairly minimal, but if you just run a bare compositor layer and figure out a launcher from there, it would be lighter. But you’re talking about Megabytes of difference, so it’s not going to be much different.
Edit: also, I was assuming you’re asking about memory, but could be wrong.


This is spam


Give this a shot: https://github.com/dimtpap/coppwr


I’m not aware of anything that ties display and audio output together in the way you’re expecting, but you could make a Pipewire config to tie some things together and probably make it work. If your TV is using DP or HDMI for audio output, then this is already handled for you in some small part because it helps to define which display will be in use.


“It’s really great, and I hate it” is kind of an insane take, but if you’re looking for things to tune, tweak, or squeeze extra performance out of, try compiling your own optimized kernel and drivers. Maybe get into building a more portable profile for yourself so your changes can move with you elsewhere.
This will immediately get struck down in court even if it passes, though everyone should make their voices heard in saying this is complete nonsense.
Yet another case of antiquated politicians not understanding technology whatsoever.