From f22305fbf585a4d16109ad44b24739228ae5b503 Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Sat, 27 Apr 2024 17:01:38 +0100 Subject: update macbook21/x60/t60 status Signed-off-by: Leah Rowe --- config/coreboot/macbook11/target.cfg | 2 +- config/coreboot/macbook11/warn.txt | 1 + config/coreboot/macbook11_16mb/target.cfg | 2 +- config/coreboot/macbook11_16mb/warn.txt | 1 + config/coreboot/macbook21/target.cfg | 2 +- config/coreboot/macbook21/warn.txt | 1 + config/coreboot/macbook21_16mb/target.cfg | 2 +- config/coreboot/macbook21_16mb/warn.txt | 1 + config/coreboot/t60_16mb_intelgpu/target.cfg | 2 +- config/coreboot/t60_16mb_intelgpu/warn.txt | 1 + config/coreboot/t60_intelgpu/target.cfg | 2 +- config/coreboot/t60_intelgpu/warn.txt | 1 + config/coreboot/x60/target.cfg | 2 +- config/coreboot/x60/warn.txt | 1 + config/coreboot/x60_16mb/target.cfg | 2 +- config/coreboot/x60_16mb/warn.txt | 1 + 16 files changed, 16 insertions(+), 8 deletions(-) create mode 100644 config/coreboot/macbook11/warn.txt create mode 100644 config/coreboot/macbook11_16mb/warn.txt create mode 100644 config/coreboot/macbook21/warn.txt create mode 100644 config/coreboot/macbook21_16mb/warn.txt create mode 100644 config/coreboot/t60_16mb_intelgpu/warn.txt create mode 100644 config/coreboot/t60_intelgpu/warn.txt create mode 100644 config/coreboot/x60/warn.txt create mode 100644 config/coreboot/x60_16mb/warn.txt diff --git a/config/coreboot/macbook11/target.cfg b/config/coreboot/macbook11/target.cfg index 404e0129..3c06a458 100644 --- a/config/coreboot/macbook11/target.cfg +++ b/config/coreboot/macbook11/target.cfg @@ -4,4 +4,4 @@ payload_grub="y" payload_grub_withseabios="y" payload_seabios="y" grub_scan_disk="ahci" -status="untested" +status="unstable" diff --git a/config/coreboot/macbook11/warn.txt b/config/coreboot/macbook11/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/macbook11/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. diff --git a/config/coreboot/macbook11_16mb/target.cfg b/config/coreboot/macbook11_16mb/target.cfg index 404e0129..3c06a458 100644 --- a/config/coreboot/macbook11_16mb/target.cfg +++ b/config/coreboot/macbook11_16mb/target.cfg @@ -4,4 +4,4 @@ payload_grub="y" payload_grub_withseabios="y" payload_seabios="y" grub_scan_disk="ahci" -status="untested" +status="unstable" diff --git a/config/coreboot/macbook11_16mb/warn.txt b/config/coreboot/macbook11_16mb/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/macbook11_16mb/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. diff --git a/config/coreboot/macbook21/target.cfg b/config/coreboot/macbook21/target.cfg index e9eab4e9..b4feb4de 100644 --- a/config/coreboot/macbook21/target.cfg +++ b/config/coreboot/macbook21/target.cfg @@ -5,4 +5,4 @@ payload_grub_withseabios="y" payload_seabios="y" payload_memtest="y" grub_scan_disk="ahci" -status="untested" +status="unstable" diff --git a/config/coreboot/macbook21/warn.txt b/config/coreboot/macbook21/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/macbook21/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. diff --git a/config/coreboot/macbook21_16mb/target.cfg b/config/coreboot/macbook21_16mb/target.cfg index e9eab4e9..b4feb4de 100644 --- a/config/coreboot/macbook21_16mb/target.cfg +++ b/config/coreboot/macbook21_16mb/target.cfg @@ -5,4 +5,4 @@ payload_grub_withseabios="y" payload_seabios="y" payload_memtest="y" grub_scan_disk="ahci" -status="untested" +status="unstable" diff --git a/config/coreboot/macbook21_16mb/warn.txt b/config/coreboot/macbook21_16mb/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/macbook21_16mb/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. 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. diff --git a/config/coreboot/t60_intelgpu/target.cfg b/config/coreboot/t60_intelgpu/target.cfg index 6a6d833a..004ba1b0 100644 --- a/config/coreboot/t60_intelgpu/target.cfg +++ b/config/coreboot/t60_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_intelgpu/warn.txt b/config/coreboot/t60_intelgpu/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/t60_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. diff --git a/config/coreboot/x60/target.cfg b/config/coreboot/x60/target.cfg index 6a6d833a..004ba1b0 100644 --- a/config/coreboot/x60/target.cfg +++ b/config/coreboot/x60/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/x60/warn.txt b/config/coreboot/x60/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/x60/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. diff --git a/config/coreboot/x60_16mb/target.cfg b/config/coreboot/x60_16mb/target.cfg index 6a6d833a..004ba1b0 100644 --- a/config/coreboot/x60_16mb/target.cfg +++ b/config/coreboot/x60_16mb/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/x60_16mb/warn.txt b/config/coreboot/x60_16mb/warn.txt new file mode 100644 index 00000000..5bffd9da --- /dev/null +++ b/config/coreboot/x60_16mb/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. -- cgit v1.2.1