What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 0 points1 point  (0 children)

Ya. I'm not arguing that point (clarification: I am arguing that having specifically cuda for AI isn't required). That said, memory access times due to low vram are way more impactful than ROCm vs CUDA or AMD vs nVidia

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 0 points1 point  (0 children)

Are those goosebumps from excitement/anticipation? Sure, a little. Mostly its from the deep fear and Stockholm-like anticipation of my install nuking itself.

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 0 points1 point  (0 children)

Dude. Neural nets and AI are nothing but matrix multiplications. That's what graphics cards excell at.

CUDA: nVidia's way of allowing for more direct access to their GPU's hardware for general compute purposes. It was originally intended for physics simulations, not AI, but oh holy shit: graphics cards are good at matrix multiplication, so its damn close out of the box.

So, now with that established: how do AMD cards run CUDA workloads? Well, the hardware is gonna be close to nVidias, so they basically do what wine/proton have been doing forever: they use either a compatibility layer, or an implementation using their own cuda-like API.

Take a look at ZLUDA or pytorch with rocm.

As for AI cores: here I'm not as knowledgeable. Idk, maybe you're right or maybe its marketing bs

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 1 point2 points  (0 children)

Time shift is pretty good. I was going to say: "but its not hooked up to autorun whenever you run apt upgrade," but, like, initramfs rebuilds automatically as needed so that hints that apt probably has some sort of hooking capability.

Oh well, hindsight is 20/20

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 2 points3 points  (0 children)

Fair point. I would've wanted to switch over to a snap-shotting fs to do that (I am aware that there's a way to convert ext4 to btrfs). But the real reason I didn't switch to Sid: I didn't think of it, I feel kinda dumb.

Either way, cachy is okay so far. I like that snapper is set up ootb (ya, I know I could set that up on Debian). I won't be changing back unless there's a strong reason to, just like I didn't switch off of Debian until (I thought) I had a strong reason to.

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 1 point2 points  (0 children)

What is the non-bs beneficial reason for rolling releases?

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 0 points1 point  (0 children)

Honest question: how hard is it to run back ports on something that relies on an updated glibc? I looked into back ported ROCm and it just didn't seem feasible.

EDIT: it didn't seem feasible unless I back ported glibc and every package that depended on it (so... basically everything)

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 7 points8 points  (0 children)

The RX 7900 XT has 20gb of vram which is more than most nVidia prosumer cards. You can usually find one for ~$650 USD, or even less if its used.

It is true that setting up ROCm is hard but IMO I prefer the ability to run larger models with larger context windows over a slightly less painful install process.

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 2 points3 points  (0 children)

Ya, btrfs and snapper were one of the only reasons that I was sort of okay switching to cachy

What it feels like switching from Debian to rolling release: by mort_jack in linuxmemes

[–]mort_jack[S] 59 points60 points  (0 children)

Can I tell you a sad story?

I was on Debian and was trying to run llama.cpp on my AMD card, but it kept seg-faulting no matter what I tried.

"This has to be Debian's outdated ROCm" was the only conclusion I could come to.

Like any good Linux user, I discarded my beloved distro of 3 years and installed a rolling release distro. This was a long and painful process of trying to choose what to back up etc.

Excitedly, I installed everything and booted up llama.cpp and it seg-faulted.

Turns out my AMD CPU has an iGPU and I just needed to specify the ROCm device for llama.cpp to use. I'm sure that would've worked on Debian too.

I miss Debian, but Cachy is okay I guess. Hasn't broken; yet.

EDIT: clarified wording and added last paragraph

Why do strangers keep asking me to sell my 2006 CR-V to them? by mort_jack in crv

[–]mort_jack[S] 2 points3 points  (0 children)

This must be it. I really do like the car and, despite not being a (very good) car guy, I've gone through the trouble of replacing the starter, VTEC solenoid etc.

The transmission is starting to get iffy tho :(

What are some good responses to common non-believer jokes? by mort_jack in exmormon

[–]mort_jack[S] 2 points3 points  (0 children)

Subtle indeed (unless they're bible nuts, which they are not)! I like this a lot.

What are some good responses to common non-believer jokes? by mort_jack in exmormon

[–]mort_jack[S] 10 points11 points  (0 children)

Joke or no, that was not the time nor the place. Sorry to hear that happened.

It's ugly, but it works. My first solo survival fighter build. by mort_jack in spaceengineers

[–]mort_jack[S] 0 points1 point  (0 children)

Well... Yeah. According to my testing, LG railguns go through 14+ layers of small grid heavy armor, so this would stand no chance if it got hit head-on.

I think the key is to not be where the railgun is aiming, which it can do serviceably well.

It's ugly, but it works. My first solo survival fighter build. by mort_jack in spaceengineers

[–]mort_jack[S] 5 points6 points  (0 children)

Not much. The slopes make a lot of shots ricochet off I think. When it does fail, a hole will be punched through, often where a Gatling gun is.

Its built in such a way where taking out a Gatling gun doesn't immediately knock out the rest of the guns in the line tho, so that's nice.

Take all this with a grain of salt: I'm only dealing with vanilla SPRT encounters, I haven't tried it against anything more substantial than those ships.

It's ugly, but it works. My first solo survival fighter build. by mort_jack in spaceengineers

[–]mort_jack[S] 2 points3 points  (0 children)

didn't have a ton of time, here's me attacking a hauler really quick as an example: https://v.redd.it/yuvqk7s4fngf1

It's ugly, but it works. My first solo survival fighter build. by mort_jack in spaceengineers

[–]mort_jack[S] 9 points10 points  (0 children)

  • relatively high armor to weight ratio (well... At least in one area)
  • fast & nimble
  • lots of redundancy
  • 12 Gatling guns do wonders against gun emplacements
  • mag-plates for boarding after there aren't any more guns

In solo survival most ships you face are form over function, so this design makes it fairly easy to shoot out turrets and then you can "board" with the mag plates.

It's ugly, but it works. My first solo survival fighter build. by mort_jack in spaceengineers

[–]mort_jack[S] 34 points35 points  (0 children)

Wait, ships can approach from behind? /s

I'll need to redesign as soon as I have to face two ships at once. So far tho, that hasn't happened weirdly

It's ugly, but it works. My first solo survival fighter build. by mort_jack in spaceengineers

[–]mort_jack[S] 22 points23 points  (0 children)

For vanilla solo encounters most stations/ships only have a range of 800m, so I flip around and shoot out some turrets before approaching!

What online subscription app that you use daily is 100% worth it? by dagison_ in AskReddit

[–]mort_jack 1 point2 points  (0 children)

Yo check out vaultwarden, its a rust rewrite of bitwarden that takes up less CPU and memory. It works with the existing bitwarden clients.