On Fri, Jun 07, 2019 at 03:43:39PM +0200, Paul de Weerd wrote: > I've just replaced my home gateway with a brandless machine with an > i5-7200U. While preparing, I noticed the message "ucode too large" > scrolling by on the serial console, just before the kernel starts. > > The dmesg shows cpu0 as mode 06-8e-09: > > cpu0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2395.19 MHz, 06-8e-09 > > While /etc/firmware/intel/06-8e-09 is the biggest file in that > directory (at 193kB), so this probably has something to do with that > and the MDS "fun". > > Machine works fine as far as I can tell (typing this mail over an SSH > session through it).
The limit was raised only for efiboot. https://marc.info/?l=openbsd-cvs&m=155853966111794&w=2 For non-efi it is still 128KB. The region of memory it uses starts at 1MB. I think you should be able to raise the 'too large' check to 256KB without problem but have not tested this. You'll need to run installboot after installing. Wouldn't hurt to have a miniroot on removable media to recover if needed. Index: arch/amd64/stand/boot/conf.c =================================================================== RCS file: /cvs/src/sys/arch/amd64/stand/boot/conf.c,v retrieving revision 1.46 diff -u -p -r1.46 conf.c --- arch/amd64/stand/boot/conf.c 15 May 2019 06:52:33 -0000 1.46 +++ arch/amd64/stand/boot/conf.c 7 Jun 2019 14:05:58 -0000 @@ -40,7 +40,7 @@ #include <biosdev.h> #include <dev/cons.h> -const char version[] = "3.44"; +const char version[] = "3.45"; int debug = 1; Index: arch/amd64/stand/libsa/exec_i386.c =================================================================== RCS file: /cvs/src/sys/arch/amd64/stand/libsa/exec_i386.c,v retrieving revision 1.31 diff -u -p -r1.31 exec_i386.c --- arch/amd64/stand/libsa/exec_i386.c 28 May 2019 17:38:02 -0000 1.31 +++ arch/amd64/stand/libsa/exec_i386.c 7 Jun 2019 14:04:19 -0000 @@ -226,7 +226,7 @@ ucode_load(void) return; buflen = sb.st_size; - if (buflen > 128*1024) { + if (buflen > 256*1024) { printf("ucode too large\n"); return; }
