Date: Sun, 3 Jun 2018 10:31:15 -0400 From: Albert Gem <dsifriend@gmail.com> To: Idwer Vollering <vidwer@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Message-ID: <E54652E9-A95A-4221-8EDB-FB60B7A542F9@gmail.com> In-Reply-To: <CAPp9Ork3iC=Z_Tdqw-sFk4YqcZwFVFiaBiiDOdLu2B0esHnWfg@mail.gmail.com> References: <CAN0zgYXvsLJqBvUy25AGZZrkX9%2B4NcT_5OmEB_6wsowy2zrD-A@mail.gmail.com> <247b08cf-29ae-2410-ed52-1f211c1df565@gmail.com> <CAPp9Ork3iC=Z_Tdqw-sFk4YqcZwFVFiaBiiDOdLu2B0esHnWfg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
SeaBIOS 1.10.2 Upgrading seems to do the trick > Am 03.06.2018 um 06:25 schrieb Idwer Vollering <vidwer@gmail.com>: > > 2018-06-03 7:23 GMT+02:00 Albert <dsifriend@gmail.com>: >> Hi, >> >> >> I successfully tested the memstick.img on: >> Acer Chromebook 14 (EDGAR) [CB3-431-C5EX] >> >> The Results: >> UEFI (Coreboot) works perfectly, no issues there. >> BIOS (SeaBIOS) does *NOT* work. It puts the machine into a bootloop until >> the install medium is disconnected. It does, however, make it past the >> FreeBSD boot loader on the first try. > > That's odd, which version of SeaBIOS are you using? did you had to run > 'gpart recover <device>'? > > CFT report: I'm able to boot > FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img using > coreboot with SeaBIOS 1.11.1 just fine. > >> >> >> >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E54652E9-A95A-4221-8EDB-FB60B7A542F9>