• 1 Post
  • 66 Comments
Joined 3 years ago
cake
Cake day: July 30th, 2023

help-circle

  • I remember when I was a kid messing with Windows 95/98, I had this intuitive feeling of what was happening under the hood. Just like how you describe your theory. Honestly you’re probably on the right track. In theory on linux you can actually dive into the source code and try to figure out what’s actually happening, but that’s intimidating AF. Hard to say if the problem is between wine and the Direct Rendering Manager (DRM), X11, Wayland, KDE, or the GPU driver…

    I had a kind of similar problem with my display not outputting when it was connected. I had to use a DRM file in /sys and udev script to fix it, wrote a blog about it. If your monitors are still messed up after a reboot, it sounds like this won’t help you though.

    Also you made me lol to “wine strikes me more as an emulator”. It totes is. The “Wine Is Not an Emulator” name is a joke, the original name was “WINdows Emulator”, which they changed to avoid Microsoft’s lawyers.





  • I used a very similar method in a similar situation to albb0920. They describe it as vibe coding too.

    The exact chip that handles everything is undocumented, but similar ones in the same series have datasheets. A maintained version of the linux driver handily collated all of the available datasheets and configurations used by different motherboards. Between that and my microcontroller/hardware experience, that side of things wasn’t too bad.

    What I didn’t know anything about was writing an Illumos driver. I used the chatbot with a free claude account, compiling and running the code manually myself. I was impressed that it was able to build out the boilerplate and get something going at all. Course it took a few tried to get something that compiled and worked somewhat correctly. At some points I needed to look through the generated code and point out exactly what what wrong, but at least it would address it.

    Code running in the context of the kernel is definitely not something I would have autonomously executing by a LLM. The end result is absolutely not something I would want put into the official Illumos source.







  • I used an old phone with a broken screen as a webcam since covid untill it totally broke recently.

    However it needed some stars to align; I had a 3D printer to make a custom holder so it could sit on my monitor unobtrusively. I also luckily had a phone with a built in method to limit the battery charging so it could be plugged in 24/7. I was able to disable all power saving and permission features, so the app could run 24/7 without being killed by android.

    I used droidcam, which works with an OBS plugin nowadays. I got it to the point that I just needed to launch OBS and my webcam was on, no touching or fiddling with the phone at all.









  • I think it would be fine. Friend of mine has Immich on a N100, like you mentioned, the initial ML tasks on a big library takes over 24 hours but once it’s done it doesn’t need much. I don’t have experience running next cloud but the others you mentioned don’t need much RAM/CPU.

    ZFS doesn’t need much RAM, especially for a two disk 4TB mirror. It soaks up free RAM to use as a cache which makes people think it needs a lot. If the cache is tiny you just end up hitting the actual speed of the HDDs more often, which sounds within your expectations. I dare say you could get by with 8 GB, but 16GB would be plenty.

    I’d only point out if you’re looking for it to last 10 years, a neat package like the ugreen might bite you. A more standard diy PC will have more replaceable parts. Would be bigger and more power hungry though.