diff options
| -rw-r--r-- | docs/hcl/r400.html | 24 | ||||
| -rw-r--r-- | docs/hcl/t400.html | 24 | ||||
| -rw-r--r-- | docs/hcl/t500.html | 24 | ||||
| -rw-r--r-- | docs/hcl/x200.html | 22 |
4 files changed, 76 insertions, 18 deletions
diff --git a/docs/hcl/r400.html b/docs/hcl/r400.html index 1c8cca70..d1d103ce 100644 --- a/docs/hcl/r400.html +++ b/docs/hcl/r400.html @@ -45,6 +45,30 @@ <div class="section"> + <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> + + <div class="subsection"> + <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> + <p> + The R400, when run without CPU microcode updates in coreboot, currently kernel panics + if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled + for the guest, the guest panics (but the host is fine). Working around this in QEMU + might be possible; if not, software virtualization should work fine (it's just slower). + </p> + <p> + On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules + are not loaded, when using QEMU. + </p> + <p> + The following errata datasheet from Intel might help with investigation: + <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> + </p> + </div> + + </div> + + <div class="section"> + <p> The R400 is almost identical to the X200, code-wise. See <a href="x200.html">x200.html</a>. </p> diff --git a/docs/hcl/t400.html b/docs/hcl/t400.html index dffc875d..977e5c5a 100644 --- a/docs/hcl/t400.html +++ b/docs/hcl/t400.html @@ -45,6 +45,30 @@ <div class="section"> + <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> + + <div class="subsection"> + <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> + <p> + The T400, when run without CPU microcode updates in coreboot, currently kernel panics + if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled + for the guest, the guest panics (but the host is fine). Working around this in QEMU + might be possible; if not, software virtualization should work fine (it's just slower). + </p> + <p> + On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules + are not loaded, when using QEMU. + </p> + <p> + The following errata datasheet from Intel might help with investigation: + <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> + </p> + </div> + + </div> + + <div class="section"> + <p> The T400 is almost identical to the X200, code-wise. See <a href="x200.html">x200.html</a>. </p> diff --git a/docs/hcl/t500.html b/docs/hcl/t500.html index c7abf971..11f14ba3 100644 --- a/docs/hcl/t500.html +++ b/docs/hcl/t500.html @@ -45,6 +45,30 @@ <div class="section"> + <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> + + <div class="subsection"> + <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> + <p> + The T500, when run without CPU microcode updates in coreboot, currently kernel panics + if running QEMU with vt-x enabled on 2 cores for the guest. With a single core enabled + for the guest, the guest panics (but the host is fine). Working around this in QEMU + might be possible; if not, software virtualization should work fine (it's just slower). + </p> + <p> + On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules + are not loaded, when using QEMU. + </p> + <p> + The following errata datasheet from Intel might help with investigation: + <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> + </p> + </div> + + </div> + + <div class="section"> + <p> The T500 is almost identical to the X200, code-wise. See <a href="x200.html">x200.html</a>. </p> diff --git a/docs/hcl/x200.html b/docs/hcl/x200.html index b79c5d16..da0a3c3d 100644 --- a/docs/hcl/x200.html +++ b/docs/hcl/x200.html @@ -51,24 +51,6 @@ <h2 id="compatibility_noblobs">Compatibility (without blobs)</h2> - <p> - Usual limitations apply for native graphics initialization - (no VBT and/or INT10H and only GRUB works so no BIOS, so no DOS/Windows support - - who cares? There is no system but GNU, and Linux is one of it's kernels). - </p> - - <p> - When connecting the AC adapter while system is powered off, system will then power on. - This probably happens in coreboot aswell (with or without blobs). - It's a minor annoyance, but it should be fixed (if it's not already fixed by now). - </p> - - <p> - This method of disabling the ME leaves the flash descriptor and gbe in place (non-functional data, fully documented) - and disables the ME using soft straps. This means that the gigabit ethernet will still work (putting the system in - non-descriptor mode would wipe it out). - </p> - <div class="subsection"> <h3 id="hwvirt">Hardware virtualization (vt-x)</h3> <p> @@ -78,6 +60,10 @@ might be possible; if not, software virtualization should work fine (it's just slower). </p> <p> + On GM45 hardware (with libreboot), make sure that the <i>kvm</i> and <i>kvm_intel</i> kernel modules + are not loaded, when using QEMU. + </p> + <p> The following errata datasheet from Intel might help with investigation: <a href="http://download.intel.com/design/mobile/specupdt/320121.pdf">http://download.intel.com/design/mobile/specupdt/320121.pdf</a> </p> |