If you follow the git instructions linked in another thread, make sure to slowly move through major version numbers. You most likely will not be able to jump straight to 25 and will need to step through major versions to figure out what changed and how to fix it.

Once you can make sure newer packages will work with the nonstandard gpu you’ll have some chance of doing htpc stuff.

Idk your background but this seems like a good time for a car metaphor:

“I just got this passenger side rear door to a 2006 Tahoe for super cheap and I want to make use of it so it doesn’t go to waste. The Chevy forums have some information on what models of the same year might mount it and what three letter codes correspond to the options on my door but nothing useful about mounting it to newer models. How can I make use of this thing?”

The Jetson boards are development kits intended for prototyping iot and edge ai devices. You could use your jetson board to prototype or even implement an edge AI device. Machine vision is a phenomenal way to use these smaller thingies like the old coral tpu.

Dev kits are often shipped with limited support and intended to provide the bare minimum to prove to an engineer that a particular chip or platform will work to some application. The rest is left up to the customer.

You don’t have an nvidia branded raspberry pi, you have the thing they send to palantirs hired geeks so they can map out the precise extent to which the panopticon can be weaponized. You could probably use it to sort and catalogue pictures of your pets and family.

Yeah, a python venv has two parts, one part is just a bunch of copies of some basic python shit that you know you’re gonna need, that’s honestly 99% of what you want when you do a venv and need to install a million stupid piles of crap by copy pasting a pip one liner into your shell.

You use this part by just invoking your python3 or pip command inside the venv folder. So ~./<venv_location>/pip install <joes_dumb_crap> or something.

The other one percent is actually invoking the venv which is a really important one percent in terms of not being a guy who plays fast and loose with his systems security and privacy when messing around with totally trustworthy python stuff. It’s only one percent because tbh no one is that guy they’re all the “do whatever just make it run” guy.

So you could have a script file called rectarg in your local path folder that invokes rectarg.py using the python3 executable inside your venv folder and passes whatever you type after “rectarg” straight to rectarg.py.

One man’s right place is another man’s evidence of clinical insanity. You could just leave them on your desktop and invoke them through the venv. You could make a folder called Folder For Python Scripts That Don’t Run Good and put all your different python things there.

You can also put the target python script inside the folder its respective venv lives in.

Really the world is your oyster because ultimately you’re gonna make another script that does something like “read $a; ~./<venv_location>/python3 <target_.py_file> $a;” and naming it what you wanna type to run your .py and put it in your local $PATH directory.

Don’t trust that one liner btw it’s definitley wrong.

I haven’t had time to look deeply into the fix posted in that GitHub link, but on first read it seems to be fixing exactly what you’re describing by tying the mixer channels used for the integrated speakers together correctly.

A lot of these newer realtek chips have an insane amount of tweakability. Even back in the day if you were able to settle for their latency you’d get access to a very powerful hardware mixer and sometimes synthesizer.

Hey when pip doesn’t work:

You’re using Debian, so if you don’t want to set up virtual environments the best bet is to install your dependencies using apt like a normal person. All the python stuff in apt will show up under the prefix python3-. So you’ll need python3-numpy, python3-tiffile etc.

Apt supports tab completion so something like “apt install python3-num” then the tab key would show a list of possible completions (and jump forward any letters that are common between completions).

If you want to use venvs there’s a bunch of posts explaining how to do that.

When you want to “install” the .py doohicky you just downloaded, put it in your path! $PATH will tell you what locations get scanned for executable files when you type something and you can add a local directory like ~/.bin to it, then put your .py file in there. If you go with venvs, put the .py file in the right place to run inside the venv, then make a one liner script that runs it from the venv with the file name set to what you wanna type to run the .py, put it in your local path directory and you’re off to the races!

I also use Debian and am coerced into using python software so reply with any questions and I’ll set you straight.

Your exact surface pro isn’t there yet.

Switch to win 10 21h2 iot ltsc using massgrave and you can wait for linux support to get right till 2032.

That’s weird.

It sounds like there’s an additional amplifier used to drive the internal speakers that isn’t getting turned up. When you fire up alsamixer on the command line do you see more controls than in the gui mixer?

Present in headphones?

here’s the Debian mailing list thread about it. It made a splash a little while back. Might be due to a combination of kernels and btrfs but nonetheless that’s exactly the situation you describe yourself trying to avoid.

Not a slag against btrfs or a lauding of zfs, just trying to point out that you might be barking up the wrong tree if you’re looking for stability and simplicity.

I use ext4 volumes in mergerfs with nightly snapraid parity snapshots for my own data that doesn’t matter. Migrated to that system from zfs looking for simplicity, stability and straightforward recovery and gained increased drive life and lowered power consumption as well. Your mileage may vary.

What is the symptom?

It kinda seems like you don’t need to be using btrfs. If the possibility of your kernel updates breaking scared you off zfs, a system that has been in very widespread use for just going off the dome twice as long as btrfs has been around, why do you think using btrfs is somehow okay?

I’m not trying to suggest you use zfs either.

E: I went and looked and zfs has been in widespread use for around twice as long as btrfs has been marked as stable. It’s worth mentioning too that since being marked as stable btrfs has suffered from a silent data corruption bug.

Been using Debian stable since Hans reiser got locked up.

It’s fine and it will continue to be fine.

What model number?

Just fix RDSEED32, what’s the big deal?

Someone already said massgrave, and they’re right, but I wanna be 100% clear: Microsoft can’t take these away. If they did then smart fridges would be complaining about how they’re not registered, massive enterprises would have to completely change how they provision systems, pc manufacturers would have to change their processes and even if it was as simple as a change to the generic disk image they ship (it’s not) they’d have to handle all the systems out there in the world.

And

Even if Microsoft went ahead anyway and removed the ability to use some method (like they did with kms38, which had nothing to do with mas and everything to do with addressing the end of the Unix epoch) there are methods they cant effectively remove like hwid.

Anyway, go to the massgrave page about 21h2 iot ltsc and read up.

Use windows 10 21h2 iot ltsc. Security updates till 2032.

It will buy you some time to see how things shake out with windows.

After taking some time to think, it’s worthwhile to remember that basically everything we think of as modern open source happened in a time of unipolar global hegemony with the express approval of that hegemony.

Open source as we know it and experience it today likely cannot exist in a time of real contestation over the levers of power in the world and you probably shouldn’t make the mistake of voting with your dollars or time in that contest. Any money or time that you find sloshing around is probably better spent elsewhere preparing yourself for the outcome of that contest rather than cheering or contributing in it.

Fair warning, if you apply enough scrutiny to any big distribution you’ll find tons of stuff like this.

Theres some awesome schizo timecube esque website that documents Debian (my chosen distro) mess in great detail. I’ll edit in the url if I can find it.

E: found it: Debian History Harassment & Abuse culture evolution

If you can’t be a truther about something you’ll lie for anything I guess

don’t.

If you wanna learn then buy a cheap used laptop and a pixel and fuck around on those until you figure out what you actually want to do. Don’t “switch”. You’ll be unhappy.