summaryrefslogtreecommitdiff
path: root/config/coreboot/t60_16mb_intelgpu
diff options
context:
space:
mode:
Diffstat (limited to 'config/coreboot/t60_16mb_intelgpu')
-rw-r--r--config/coreboot/t60_16mb_intelgpu/target.cfg2
-rw-r--r--config/coreboot/t60_16mb_intelgpu/warn.txt1
2 files changed, 2 insertions, 1 deletions
diff --git a/config/coreboot/t60_16mb_intelgpu/target.cfg b/config/coreboot/t60_16mb_intelgpu/target.cfg
index 6a6d833a..004ba1b0 100644
--- a/config/coreboot/t60_16mb_intelgpu/target.cfg
+++ b/config/coreboot/t60_16mb_intelgpu/target.cfg
@@ -5,4 +5,4 @@ payload_grub_withseabios="y"
payload_seabios="y"
grub_scan_disk="ahci"
grub_background="background1024x768.png"
-status="untested"
+status="unstable"
diff --git a/config/coreboot/t60_16mb_intelgpu/warn.txt b/config/coreboot/t60_16mb_intelgpu/warn.txt
new file mode 100644
index 00000000..5bffd9da
--- /dev/null
+++ b/config/coreboot/t60_16mb_intelgpu/warn.txt
@@ -0,0 +1 @@
+Presumably fully stable, but see lbmk issue 179: https://codeberg.org/libreboot/lbmk/issues/179 - T60 on just battery power had the error in GRUB: alloc magic is broken at 0x7b1aedf0: 0 ----- the rev for Libreboot 2024050x is set to the LB 202306235 rev (February 2023) for now. I still think the users with that issue, and there weren't that many, just had bad RAM. GRUB shows that error on bad RAM, and I've seen it in that case on other machines too. So this machine is most likely fully stable, but I'm marking it unstable until we know fully what we're dealing with.