wreckedcarzz

joined 1 year ago
[–] wreckedcarzz 3 points 1 day ago

"don't care"

still comes back to argue

hmmmmmmm

[–] wreckedcarzz 5 points 1 day ago (1 children)

"obviously fake ai sludge"

[–] wreckedcarzz 1 points 1 day ago (1 children)

I know it's a sub-brand, but as I don't own any products by them...

It's like "do you use windows at work? lol you are an Xbox lover" like ???

[–] wreckedcarzz 1 points 2 days ago (3 children)

One-time, where I risk losing 8TB of data that, at the time, I did not have a complete backup of: abso-fucking-lutely. That they handled my situation with speed and without any further bullshit is why I remain a customer.

I have a list of companies that I will not do business with, because of their fuckups, because of shady business tactics, etc. For example, I haven't bought anything from Nvidia in... 18 years? iRobot, in 7. Haven't given Hilton any funds willingly in almost 3. Intel, 19 years...

I don't purchase any SanDisk products so 🤷‍♂️

[–] wreckedcarzz 1 points 2 days ago

If the nas dies but the drives are fine, I just grab a new (synology) nas and stick the drives in. The OS will see that it's in a new model, and start the process of migration (anything that needs changing, enabling, or disabling vs the prior unit, hardware and software capabilities, etc). It's super easy; I've done it myself when I upgraded units a few years ago. If the drives die I have local and remote backups.

I believe it is possible to extract data with a standard Linux system, though it's been several years since I looked into it. I don't run raid on my usual machines (well, I have a wd black pcie card with 2x nvme drives running in raid0 on a hw raid chip onboard, but the system is oblivious and thus so am I), so I'd have to do research again if such a situation occurred. I'm not planning on moving away from syno so currently the hypothetical would end up just buying a new unit and being done with it.

[–] wreckedcarzz 1 points 2 days ago

Boeing over here turning bugs into features

[–] wreckedcarzz 3 points 2 days ago

Still need to wait for the safety information cutscene though

[–] wreckedcarzz 2 points 2 days ago

Loose time sure got a purdy mouth

[–] wreckedcarzz 5 points 2 days ago

Weird, I don't remember making this comment

(I use the new Volvo VNL sleeper with the stock engine, so 85 is about all it can do, but you ever got up on 2 wheels - technically 5 but - at a near-perfect 45 degree tilt, while doing 80, because you are determined to prove that "30 mph advisory speed" sign wrong? 85 the whole way, ducking and weaving and using the shoulders and the median...)

[–] wreckedcarzz 9 points 2 days ago (1 children)

parking brake

This a fwd model? Get me some McDonald's trays, I'm gonna show atc a cool trick

[–] wreckedcarzz 4 points 2 days ago

Guys, I think I know what happened to that plane in SK...

[–] wreckedcarzz 1 points 2 days ago (2 children)

Not to advertise but that's one of the reasons I haven't moved from synology. They have some special sauce version of raid that allows different drives and sizes without any fuss. I'm mostly attached to the UI but it's nice to know for when one drive dies, I don't have to match it or anything.

11
submitted 7 months ago* (last edited 7 months ago) by wreckedcarzz to c/[email protected]
 

(my first post on lemmy so I hope I'm doing this right)

Distro: Spiral Linux (Debian, KDE spin), by recommendation

System: Lenovo ThinkPad X13 Gen 2 (Intel) (distro recommended as I am looking for Debian(-based), + btrfs, snapshots, and fde, included via the gui installer)

I'm having issues getting ModemManager to unlock my X55 modem. This morning I wiped my drive to install Spiral (KDE), coming from Kubuntu 24.04. While the modem worked after running the proper fcc unlock script in Kubuntu, it is entirely missing in my Spiral install. While I assumed that it would not be that simple, I copied /etc/ModemManager from my Kubuntu live environment to Spiral, ran

sudo ln -sft /etc/ModemManager/fcc-unlock.d /usr/share/ModemManager/fcc-unlock.available.d/105b:e0ab

and restarted, but alas that's not enough, so I'm stuck. I have added the network profile + apn to ModemManager (the UI) but of course without the modem unlocked, I can't connect. I'm new to cellular modems in Linux (this was a windows machine until ~6 weeks ago) but I'm otherwise comfortable with the terminal and commands. The modem was working as expected last night in Kubuntu.

I haven't got the system setup yet (trying this first before going further) so if I botch this, an install is no problem. I'm assuming it's either (or both?) a service, or a missing package that sets up what's needed, but I'm at a loss as to how to proceed.

I discussed this here https://lemmy.world/comment/10540509 this morning, though I think I got all the important details typed up above. But maybe it could be useful somehow.

Any suggestions are welcomed :)

view more: next ›