aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSebastian 'Swift Geek' Grzywna <swiftgeek@gmail.com>2019-12-15 01:57:46 +0100
committerSebastian 'Swift Geek' Grzywna <swiftgeek@gmail.com>2019-12-15 01:57:46 +0100
commitc48e71b505652a794ba7c012cc2d19bd0ad51fc8 (patch)
tree3122008d797434459d6099f881256c035e82645c /docs
parentd289e2191874d34f9e2378755ac6a0c315626e82 (diff)
downloadlibrebootfr-c48e71b505652a794ba7c012cc2d19bd0ad51fc8.tar.gz
librebootfr-c48e71b505652a794ba7c012cc2d19bd0ad51fc8.zip
Remove pure speculation sections on X200 page
Diffstat (limited to 'docs')
-rw-r--r--docs/hardware/x200.md51
1 files changed, 0 insertions, 51 deletions
diff --git a/docs/hardware/x200.md b/docs/hardware/x200.md
index 99f9ff21..b0ff096a 100644
--- a/docs/hardware/x200.md
+++ b/docs/hardware/x200.md
@@ -219,57 +219,6 @@ outputs from the X200:
- BIOS 3.15, EC 1.06
- [hwdumps/x200/](hwdumps/x200/)
-RAM, S3 and microcode updates {#ram_s3_microcode}
-=============================
-
-Not all memory modules work. Most of the default ones do, but you have
-to be careful when upgrading to 8GiB; some modules work, some don't.
-
-Someone on reddit also did their own research on RAM compatibility: [on
-this
-post](https://www.reddit.com/r/libreboot/comments/5ax17e/liberated_x200_is_really_picky_with_memory/)
-
-[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might
-be useful for RAM compatibility info (note: coreboot raminit is
-different, so this page might be BS)
-
-pehjota started collecting some steppings for different CPUs on several
-X200 laptops. You can get the CPUID by running:
-
- # dmesg | sed -n 's/.*microcode:.*sig=\([^,]*\),.*$/\1/p' | uniq
-
-What pehjota wrote: The laptops that have issues resuming from suspend,
-as well as a laptop that (as I mentioned earlier in \#libreboot) won't
-boot with any Samsung DIMMs, all have CPUID 0x10676 (stepping M0).
-
-What pehjota wrote: Laptops with CPUID 0x167A (stepping R0) resume
-properly every time and work with Samsung DIMMs. I'll need to do more
-testing on more units to better confirm these trends, but it looks like
-the M0 microcode is very buggy. That would also explain why I didn't
-have issues with Samsung DIMMs with the Lenovo BIOS (which would have
-microcode updates). I wonder if VT-x works on R0.
-
-What pehjota wrote: As I said, 10676 is M0 and 1067A is R0; those are
-the two CPUIDs and steppings for Intel Core 2 Duo P8xxx CPUs with
-factory microcode. (1067 is the family and model, and 6 or A is the
-stepping ID.)
-
-*TODO: check the CPUIDs and test S3 resume and/or KVM on any C2D
-systems (including non-P8xxx ones, which I don't have here) you have
-available. I'd be curious if you could confirm these results.*
-
-It might not be coreboot that's buggy with raminit/S3; it might just be down to
-the microcode updates.
-
-Unsorted notes {#unsorted}
---------------
-
- <sgsit> do you know if it's possible to flash thinkpads over the LPC debug connector at the front edge?
- <sgsit> that would make life much easier for systems like this
- <sgsit> all the Wistron manufactured systems have this thing called a "golden finger", normally at the front edge of the board
- <sgsit> you can plug a board in which gives diagnostic codes but i'm wondering whether it is capable of more
- <sgsit> http://www.endeer.cz/bios.tools/bios.html
-
Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\
Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net>\