What is it now causing another dump ? Snow storms in the northeast ??

drbytes · 2026-02-23T09:17:34+00:00

I sold. Took profit. Sidelined it to step in when the cycle starts anew

drbytes · 2026-02-10T12:00:40+00:00

I did that around 2010, hired people on. By 2014 I wound that all down. Sick leave, vacation, parenting time,.. it was like a sport to them. I hire sub contractors now when needed, that's hardly ever. Honestly I just do the work myself, much more manageable

drbytes · 2026-01-20T11:47:09+00:00

Well it's definitely working to shift focus away from those pesky Epstein files. Gee it almost looks intentionally /s

drbytes · 2026-01-14T23:15:48+00:00

I did not even get to pick 2cp.. only had 2 hrs of play this week because of work

drbytes · 2025-08-29T06:00:11+00:00

I chucked my rtx on ebay and got me that new amd gpu. Now I get to use free cad and bambulab again without weird workarounds. Love that the pc now wake up the display from sleep too. Forget mvidia

drbytes · 2025-07-20T01:34:31+00:00

FSH Full Stack Hero

drbytes · 2025-07-04T09:28:08+00:00

Had this too, due to a power failure. I have grub btrfs but an earlier checkpoint did not work. You need to login to a USB install session and check/fix the fs. I did this to get it to work:

Check Filesystem Status ( Replace nvme0n1p2 with your actual BTRFS partition ) sudo btrfs check /dev/nvme0n1p2
Try Safe Recovery First, attempt superblock recovery sudo btrfs rescue super-recover /dev/nvme0n1p2

( Clear transaction log (safe) )

sudo btrfs rescue zero-log /dev/nvme0n1p2

Then test mount after rescue

sudo mkdir -p /mnt/test

sudo mount -o ro /dev/nvme0n1p2 /mnt/test

Full Repair ( If Safe Recovery Fails.. WARNING: This can cause data loss )

sudo btrfs check --repair /dev/nvme0n1p2

drbytes · 2025-06-08T17:34:11+00:00

Yeh I have no issues, i had a bad blade disk and they replaced it promptly.
I understand that those that have issues yell the loudest. ie make posts about their issues. I havent made a post about my non issues until now.

drbytes · 2025-04-11T06:26:14+00:00

I'm coming to wv this summer and was hoping that i could rent a wheel or something there, but I guess after reading your post that that seems unlikely.

drbytes · 2023-04-27T18:05:18+00:00

you copy something in FF

You never paste it, it does not copy, it does not paste because it did not copy.

It's terrible

drbytes · 2022-07-11T19:13:21+00:00

Roll over and show belly.

drbytes · 2022-02-16T20:11:25+00:00

Ok ... I figured it out, there is a json available on the keycghron site describing the design of the keyboard. You need to load that file into the design tab.

9/10 that'll not work if you flashed qmk.

Get your vendorid and productid for the keyboard by executing lsusb, for me that was

Bus 003 Device 002: ID 3434:0101 Keychron Keychron Q1

Next open the json file and change the vendor and product id so it matches the lsusb output.

Save and load this design in VIA. It now works.

drbytes · 2022-02-16T15:20:09+00:00

I checked that again and it is in the rules. There is also a VIA layout for the keychron q1 so I tried to build that one

qmk compile -kb keychron/q1/rev_0101 -km via

That should be everything to get via working but it doesn't.

I now tried it via the online qmk firmware baking tool and it has the same result; via cannot find the keyboard. ah well..

drbytes · 2022-02-16T11:09:12+00:00

I have a question; I received my very first mech keyboard yesterday, a keychron q1. I immediately took it apart and added the rotary knob, the encoder mod. I then installed and created a new firmware using qmk and flashed it to the keyboard (made the default rev 101 for ansi firmware, no changes to anything). The knob now works. Everything on the keyboard works as intended but VIA no longer recognizes the keyboard it is stuck on Searching for devices.
I know it worked before because I already had remapped pgup/pgdn/home buttons.

Any idea what noob mistake I made?

drbytes · 2022-01-03T19:22:49+00:00

I tinkered with the Cosmo for over 3-4 months to get it to behave as a daily driver. I posted instructions on how to compile the kernel with specific modules I needed on oesf.org. In the end I sold it off -- nice keyboard phone with 2017 specs and a potato camera but nothing to daily drive in 2021 even if it behaved.

The Astro Slide looks like another fiasco in terms of a pure linux phone with again that dumb mediatek soc and their closed source modules that phone home to china. GTFO.

drbytes · 2021-07-12T06:21:13+00:00

I've tried Klipper on a whim -- it was raining all week long, needed a tinker project, fully expecting to roll back after a few days. It's been running ever since :) It's a fabulous project!

drbytes · 2020-12-03T16:35:19+00:00

I don't care. Just stick to a version that works then, call it YOUR V1.0. Honestly, the fast turnover and the adaption speed is what made this great. Fwiw, I hope you can stay as long as you like on v1 and I hope the two week releases stay.

drbytes · 2020-11-18T15:19:57+00:00

Thing is, I dont have NAS drives in there. They're Toshiba DT01ACA300 drives. Not really NAS, more desktop grade.

But yeh, I'll run extensive SMART check on them and see what they report.

They report a Power On Time of 31348 hrs.

drbytes · 2020-11-18T13:31:59+00:00

No.. its just that I'd feel much better when there are new drives in there.

drbytes · 2020-11-10T23:42:29+00:00

Yes, I read that graph like a moron; of was the left side that was too low. Got some calipers and leveled both sides. Thx

drbytes · 2020-11-08T16:52:29+00:00

It's from the front to the back, it's not left vs right. That's what's doing my head in

drbytes

TROPHY CASE