Technology

37724 readers

475 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

Los@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

Dell Chromebook Pulls a Jesus (Resurrects) (lemmy.one)

submitted 1 year ago by copolymer__@lemmy.one to c/technology@beehaw.org

8 comments fedilink hide all child comments

I bought a refurbished Dell chromebook, and used it for several months, taking it apart a few times. One day, I took it apart, and pulled the motherboard out, because I was curious if I could modify it, maybe change the ram, even though it's not meant to be changed. When I put it all back together, it wouldn't boot, not by opening the lid, not by pressing the key, nothing. I figured I shocked the board (since I neither own nor use any antistatic gear), and it was bricked. After a few months of sitting around, I tried ro turn it on again, just out of curiosity, and it booted like everything was normal.

Does anyone have any idea what could have happened?

Tldr: Chromebook I thought was bricked started like normal after months of sitting ¯\_ (ツ) _/¯

you are viewing a single comment's thread
view the rest of the comments

[–] WalterLatrans@yiffit.net 2 points 1 year ago (1 children)

Did you try plugging it in initially after you disassembled it and reassembled it? I've found on chromebooks that the embedded controller doesn't seem to wake up until the charger is plugged in after unplugging the battery. Could it be that you initially didn't plug it in before trying it months ago, but months later you figured the battery would be low after all that time so you plugged it in finally starting the embedded controller?

[–] copolymer__@lemmy.one 1 points 1 year ago

No, I didn't plug it in initially, but I also didn't plug it in when it started, until I saw that the battery was low