[coreboot] Re: Chainloading Windows from a Linux Payload

2019-06-12 Thread Matt B
Hi, > I think SeaBIOS already has an option to build a multiboot image. In > either case you could also (in theory) pack either into a bzImage and > feed that to kexec. > Clearly this is one place I should look next. I was mainly looking at grub as I understood it to be the most capable among

[coreboot] nvidia/ck804/fadt.c

2019-06-12 Thread ehaouas
Hi, We have "#ifdef LONG_FADT" at line #36 however, that LONG_FADT is not used at all "git grep -r LONG_FADT" gives only 2 places: src/southbridge/nvidia/ck804/fadt.c:#ifdef LONG_FADT src/southbridge/nvidia/ck804/fadt.c:#ifdef LONG_FADT Do you have any idea about LONG_FADT ? can we

[coreboot] coreboot - toshiba laptop

2019-06-12 Thread miel...@t-online.de
Toshiba Tecra S4 Model No. PTS40E-01K00JGR SERIAL No. 27056280H Dear ladies and gentlemen, I could compile coreboot. A test with qemu, as described in coreboot - lesson 1 was successful. But this configuration with mainboard = emulation is for demon- stration only, isn't it ? I did not find

[coreboot] Re: Early kernel Panic linux 4.19 on ASUS KGPE-D16

2019-06-12 Thread Angel Pons
Hello, Have you tried bisecting coreboot/linux versions? It would help know where the problem is, and fix it accordingly. Microcode updates should not be a problem, so please leave them enabled for now. Best regards, Angel Pons ___ coreboot mailing

[coreboot] Re: Chainloading Windows from a Linux Payload

2019-06-12 Thread Mike Banon
At least Windows 10 supports the Legacy BIOS, and most likely 12 will too. As long as they are making a 32-bit version of Windows they're still caring about the "legacy" PCs and we shouldn't be worried. Also, it's hard to imagine a coreboot'er who would be running 12 natively - not inside some

[coreboot] Re: Early kernel Panic linux 4.19 on ASUS KGPE-D16

2019-06-12 Thread Mike Banon
While you're waiting for a more helpful reply, you could try some ancient coreboot like 4.1 to see if it boots with this new kernel - and, if yes - move towards the new builds to see where they stop booting. Maybe there's a problematic commit you'd need to find On Tue, Jun 11, 2019 at 6:28 PM