1. 18

  2. 1

    I’m interested in this but haven’t used it. Anybody have any experience actually using coreboot?

    1. 3

      If you’re running a BSD, then it seems like you might want to stay away.

      1. 3

        https://mail.coreboot.org/pipermail/coreboot/2018-December/088044.html indicates that NetBSD doesn’t have that issue.

        The problem is less in the “project’s origins” as alluded by Bryan, but in the testing that people do: the ThinkPad support is community provided, and apparently most people working on coreboot-on-Thinkpads use Linux.

        If somebody wants to get to the root of that issue, they can expect a supportive developer community, but coreboot is very much focused on developers, not consumers.

      2. 3

        I’m running coreboot on all my PC’s:

        • PCengines APU2 with OpenBSD
        • ThinkPad X200 with OpenBSD
        • ASUS KGPE-D16 with dualboot Gentoo / HardenedBSD
        • ASUS KGPE-D16 with HardenedBSD

        I also ran in the past ASUS F2A85-M with dualboot Gentoo / FreeBSD and ASROCK E350M1 with dualboot FreeBSD / 9front.

        My wife has ThinkPad X230 with Ubuntu.

        Generally, coreboot has its quirks but once you work it around, it works. If you have some questions, feel free to ask.

        1. 2

          Yes, reflashed my ThinkPad x60s some years ago now, had success on dfly, free, open, NetBSD. reflashed it with a new build couple of weeks ago, no issues under NetBSD. Helped someone with an x220 to reflash it a couple of years back and there was not issues on OpenBSD at the time. No idea if there have been any regressions. Currently waiting for a SOIC-8 clip so I can reflash my x230. I use the SeaBIOS payload on the x60s and x220 image I put together, the x230 will likely be the same but I may try tianocore as well. Don’t care for grub.

          1. 1

            I “used” it to boot FreeBSD (with non-upstreamed tegra210 patches) on the Nintendo Switch :D (ultimately not that interesting since the only connection to the outside world was a janky UART.. nothing showed up on XHCI when plugging in stuff via a USB-C-to-A adapter)

            A bit disappointed that there’s no framebuffer support for tegra210 in coreboot. (I thought Google would care to get display as early as possible on the Pixel C, but looks like they trust Linux to always start booting very quickly.)

            Coreboot also supports the Rockchip RK3399 — because chromebooks — so I’d like to see coreboot on the ROCKPro64, but unlike the Chromebooks, this board has DDR4 memory instead of DDR3, so there’s no memory training code (I wonder if it’s possible to attach the blob?)

            Also, I wonder if it’s possible to get an RK3399 Chromebook and just replace the depthcharge payload with TianoCore EDK2… (or at least U-Boot, that should work for sure)