akko/blog
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Finish framework blog post

Browse Source
This commit is contained in:
Akko
2022-03-21 22:26:17 +01:00
parent 1dca4b0d58
commit ef30028b18
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
org/posts/framework.org
View File

@@ -17,7 +17,7 @@ Assembling the DIY edition took no time at all; you could probably speedrun this
Replaceable RAM, storage and battery are table stakes - you can get that in plenty of laptops if you look for it. What's impressing about the Framework is first of all the sheer ease with which to disassemble it. It's a world of difference even compared to my old Thinkpad X230t, which is​^H​^H was an extremely servicable laptop (;_;). It's an experience.
Also very impressing is the sheer extent of things that can be replaced. You can see their store of replacement parts [[https:https://frame.work/marketplace/parts][here]] and it includes everything from the audio board to the hinge to the CPU heatsink and so on. The parts aren't even expensive either!
Also very impressing is the sheer extent of things that can be replaced. You can see their store of replacement parts [[https:https://frame.work/marketplace/parts][here]] and it includes everything from the audio board to the hinge to the CPU heatsink and so on. The parts aren't even expensive either! I'd like to give some special credit to the charger. The power brick itself is entirely modular, with detachable wall power socket and USB-C cables, making the (cheap, fragile) cables replaceable without having to replace the (more expensive, durable) power brick.
My enrapturement was short-lived, though, as after a quick assembly my new laptop would not boot up or charge. Not even the charging light would come on. After some searching we did find a [[https://guides.frame.work/Guide/Fully+Resetting+the+Mainboard+State/113][guide]] with instructions on how to fully power cycle the mainboard, and that resolved the issue. It seems the issue could potentially be caused by a dead CMOS battery. Regardless of what caused it, the fix was an obscure and somewhat dangerous fix for what I'd consider a big quality assurance failure.
@@ -113,8 +113,4 @@ Personally, I'm getting a rare chance to critically examine all the little confi
* Appendix B: lock.py
#+INCLUDE: "~/Scripts/lock.py" src python
* TODO
remark on modularity of charger
remark on finish of modules
/last modified: {{{modified}}}/