[coreboot] Re: Extended IvyBridge CPU configuration
I personally don't think that libgfxinit instead of vgabios or vice versa will make any difference in this case. I'd recommend to test native raminit vs mrc.bin instead. Correct me if I'm wrong but isn't the mrc.bin Haswell specific [1]? From what I recall I never saw an option in "make menuconfig" to choose native raminit or mrc.bin on IvyBridge. If there is such an option (now) I'll definitely try it! If you mean microcode updates, then there's an option in coreboot's config (and you also need to enable use of binary-only repository in the General section). In terms of microcode updates I'm concerned about "compability", i.e. does Debian use an older / newer version than coreboot and vice versa, is there some specific initialization done by Debian / coreboot which the other one does not perform etc. [1] https://doc.coreboot.org/northbridge/intel/haswell/mrc.bin.html On 1/19/20 12:22 AM, Evgeny Zinoviev via coreboot wrote: From what I recall, the last coreboot master I tried resulted in crashes without your patch. If it's so, then the HT patch is not to blame... But we'll see after your tests. I intend to run following tests with the latest coreboot master (I'll note the commit hash and use the same commit for all of my tests) and SeaBIOS as payload (blobs will be extracted from the Lenovo OEM BIOS v2.81): 1. fully blob'ed (vgabios, ifd, me, gbe) 2. libgfxinit instead of vgabios 3. fully blob'ed with the me shrinked 4. libgfxinit instead of vgabios with the me shrinked I personally don't think that libgfxinit instead of vgabios or vice versa will make any difference in this case. I'd recommend to test native raminit vs mrc.bin instead. I'm unsure on how to provide the µCode patches, i.e. integrate them in coreboot or have them patched by Linux. If you mean microcode updates, then there's an option in coreboot's config (and you also need to enable use of binary-only repository in the General section). ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Extended IvyBridge CPU configuration
From what I recall, the last coreboot master I tried resulted in crashes without your patch. If it's so, then the HT patch is not to blame... But we'll see after your tests. I intend to run following tests with the latest coreboot master (I'll note the commit hash and use the same commit for all of my tests) and SeaBIOS as payload (blobs will be extracted from the Lenovo OEM BIOS v2.81): 1. fully blob'ed (vgabios, ifd, me, gbe) 2. libgfxinit instead of vgabios 3. fully blob'ed with the me shrinked 4. libgfxinit instead of vgabios with the me shrinked I personally don't think that libgfxinit instead of vgabios or vice versa will make any difference in this case. I'd recommend to test native raminit vs mrc.bin instead. I'm unsure on how to provide the µCode patches, i.e. integrate them in coreboot or have them patched by Linux. If you mean microcode updates, then there's an option in coreboot's config (and you also need to enable use of binary-only repository in the General section). ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Extended IvyBridge CPU configuration
Hi Evgeny, I didn't try the latest coreboot master in a while as I wanted to rule out hardware damage as a possible cause and reflashed the Lenovo OEM BIOS. From what I recall, the last coreboot master I tried resulted in crashes without your patch. I intend to run following tests with the latest coreboot master (I'll note the commit hash and use the same commit for all of my tests) and SeaBIOS as payload (blobs will be extracted from the Lenovo OEM BIOS v2.81): 1. fully blob'ed (vgabios, ifd, me, gbe) 2. libgfxinit instead of vgabios 3. fully blob'ed with the me shrinked 4. libgfxinit instead of vgabios with the me shrinked If all tests pass, I'll try the same tests with your patch. If a test without your patch applied fails I'd argue that something else is to blame. I'm unsure on how to provide the µCode patches, i.e. integrate them in coreboot or have them patched by Linux. Since watching videos on Firefox and compiling the coreboot toolchain seem to reliably crash the laptop I'll use those to try and provoke a crash. I'm open to suggestions for other "crash provoking workloads". I'm also considering reinstalling the OS (Debian Buster 10.2 with Gnome3) to rule out some weird configuration as a possibility. On 1/17/20 12:37 AM, Evgeny Zinoviev via coreboot wrote: Hi, Lars. Update: I flashed the original Lenovo BIOS v2.81 (with keyboard EC mod) and the issues seem to be gone. Do you have any freezes/crashes while running latest coreboot (from master) without the HT patch? ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
