शून्यताI have two Pi 4s. I'm going to hold onto them for another 6 months, then sell them and buy my first house. (s s) #RaspberryPi
| iFixit | https://www.ifixit.com/User/647050/in_sympathy |
| GitHub | https://github.com/in-sympathy |
@in_sympathy
- 136 Followers
- 121 Following
- 1.3K Posts
Reparing #RaspberryPi, #OrangePi, #Pine64, #NvidiaJetson and other #SBC as a hobby of #electronicsrepair.
Really enjoy #soldering and #BGA #microsoldering.
Love #tinkering with #electronics, especially with #Arduino.
Also interested in #Linux and #macOS.
Play #Guitar since I was 8.
Judeau (EatTheRich)Okay... I'm no mathematician & barely understand the difference between letters & numbers but after looking over a few charts that cover the last year, it depressingly looks like:
RAM prices are up 400%
SSD prices are up 125%
HDD prices are up 25%
Micro / SD card prices are up 150%
Processor prices are expected to start their climb.
What's next? I would like to be ahead of the game. I already sold one kidney last year for a graphics card. I really don't want to sell my other.
CHARGE.RErra: Exordium dieselpunk adventure pixel art game from Ukraine. This world is uniquely hand-drawn. Take the role of a scientist who was able to cheat death and fight the rebellious army of mechatrons
https://store.steampowered.com/app/1224030/
#ScreenshotSaturday #retrogaming #pixelart #ドット絵 #gaming #games #steamdeck
Been to the cinema just now watching #ProjectHailMary.
Cool, but here’s what I thought: if only there was some kind of a #service that offers movies with real deep scientific context… Movies, that would not only let you experience emotions, but also teach you something new on a serious level.
Would you subscribe if it had movies with both a decent story and, say, deep cuts on #engineering ,#electronics , #chemistry, #biology and so on?
Who knows - maybe someday #AI will be offering lthat.
| Sure | |
| Nah, I watch to rest | |
| Other (comment) |
Poll ends at .
Literally no one: –
Me: how about having some unnecessary #BGA #soldering practice in the shape of upgrading #RAM on a #Radxa 4B Plus from 2GB to 4GB? 🤣
Well that did not go as planned.
I used Samsung K4F6E3S4HMMGCJ 2GB RAM chips from #RaspberryPi 4B. With those Radxa would power on, but won't boot and won't go into recovery mode. Only Maskrom works but I wasn't able even to flash a firmware.
Originally it has two HYNIX H9HCNNN8KUMLHR-NME chips - I wonder what makes those different... 🤔
This cute little fella popped up on the bench today for bios flash.
Customer had this very PC already fixed in another shop, then decided to update bios himself and unit stopped posting.
Love how easy this GMKTec K12 is to disassemble really. Though bios chip choice and placement are rather questionable - was unable to reach it with my clip and had to desolder.
Anyways it was a nice and easy morning routine, so why not ✅
Jonathan CorbetAs the number of LLM-generated patches in my inbox increases, I am starting to experience the sort of maintainer stress that has long been predicted. But there's another aspect of this that has recently crossed my mind.
Just over a week ago, a new personality showed up with a whole pile of machine-generated patches claiming to fill in our memory-management documentation. A few reviewers had some sharp questions, the response to which has been ... silence. This person doesn't seem to have cared enough about that work to make an effort to get past the initial resistance.
Once upon a time, somebody who had produced many pages of MM documentation would be invested enough in that work to make at least a minimal attempt to defend it.
Kernel developers often worry that a patch submitter will not stick around to maintain the code they are trying to push upstream. Part of the gauntlet of getting kernel patches accepted can be seen as a sort of "are you serious?" test.
When somebody submits a big pile of machine-generated code, though, will they be *able* to maintain it? And will they be sufficiently invested in this code, which they didn't write and probably don't understand, to stick around and fix the inevitable problems that will arise? I rather fear not, and that does not bode well for the long-term maintainability of our software.
Just over a week ago, a new personality showed up with a whole pile of machine-generated patches claiming to fill in our memory-management documentation. A few reviewers had some sharp questions, the response to which has been ... silence. This person doesn't seem to have cared enough about that work to make an effort to get past the initial resistance.
Once upon a time, somebody who had produced many pages of MM documentation would be invested enough in that work to make at least a minimal attempt to defend it.
Kernel developers often worry that a patch submitter will not stick around to maintain the code they are trying to push upstream. Part of the gauntlet of getting kernel patches accepted can be seen as a sort of "are you serious?" test.
When somebody submits a big pile of machine-generated code, though, will they be *able* to maintain it? And will they be sufficiently invested in this code, which they didn't write and probably don't understand, to stick around and fix the inevitable problems that will arise? I rather fear not, and that does not bode well for the long-term maintainability of our software.
And all of us are paying for that one way or another.
As modern day officials tend to say - if true - it is indeed deeply concerning.
It Begins: An AI Tried to Escape The Lab
Learning new stuff - programming ITE EC chip over the keyboard connector with #SVOD4 without needing to desolder the chip.
One thing I can tell you is you better use a microscope to make sure you’re picking the right ribbon cable and that you align it well while plugging.
Quite a fiddly thing to deal with but eventually I made it work.
#repair #electronicsrepair #electronics #ifixit #laptoprepair #ite #ec
