[coreboot] The OpenBMC port for the KGPE-D16 and KCMA-D8 is almost done - try the beta!

2017-12-15 Thread taii...@gmx.com
At last - not one but two easily obtainable, affordable, owner controlled, no-PSP/ME, libre firmware boards that are new enough to be useful and have 99% feature parity with commercial closed source systems. (100% if we had SR-IOV/ARI support)

Re: [coreboot] Black screen during SeaBIOS boot

2017-12-15 Thread taii...@gmx.com
I would do what awokd said with the multiple vga adapters option, I would also consider using grub as a payload and/or selecting Coreboot Execute Option ROM's/VGA Option ROM's with the appropriate YABEL options/restrictions for security (more secure than SeaBIOS method) Youness he is using a

Re: [coreboot] Black screen during SeaBIOS boot

2017-12-15 Thread Youness Alaoui
Try a 'cbmem -t' to see how long coreboot itself took to boot. There might be some delay somewhere causing it to take longer to boot (current system I'm on, it takes 8 seconds, and on other systems I saw it take 15 seconds, because it waits for the ME to respond until it times out) so it might not

[coreboot] Depthcharge License

2017-12-15 Thread tturne
Preparing to mirror the coreboot.org requires us to vet the various licenses, etc. There doesn't appear to be a LICENSE or COPYING file in the Depthcharge tree. My understanding is that Depthcharge is licensed GPLv2 (or later). How would I confirm this with an online source? Cheers,

Re: [coreboot] Disabling Intel ME 11 via undocumented mode

2017-12-15 Thread Zoran Stojsavljevic
> pretty sure the I is for Intel ;-) Sure. AMD has AME, as I recall. VIA has VME, Cyrix had CME, etc. ;-) It is ME, simple and plain. I(ntel)ME is a pleonasm (please, look on the Webster Dictionary what the pleonasm is?!). Zoran On Fri, Dec 15, 2017 at 6:18 PM, Matt DeVillier

Re: [coreboot] Black screen during SeaBIOS boot

2017-12-15 Thread awokd via coreboot
On Fri, December 15, 2017 11:10 am, Daniel K wrote: > Starting up with coreboot and SeaBIOS, the screen is completely black for > around 30 seconds before my on-disc bootloader (grub2) is loaded and > displayed. > > I'm assuming SeaBIOS counts down with some timer before launching the > on-disc

Re: [coreboot] Disabling Intel ME 11 via undocumented mode

2017-12-15 Thread Matt DeVillier
On Fri, Dec 15, 2017 at 10:23 AM, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > IME (I is typo) = ME . > pretty sure the I is for Intel ;-) (or, at least that's how I've seen it referenced elsewhere) > > Zoran > -- coreboot mailing list: coreboot@coreboot.org

Re: [coreboot] Disabling Intel ME 11 via undocumented mode

2017-12-15 Thread Zoran Stojsavljevic
IME (I is typo) = ME . Zoran On Fri, Dec 15, 2017 at 5:14 PM, Gregg Levine wrote: > Hello! > (I'm working from the office today on a library computer...) > My regular laptop might be wearing one of those dratted things. But > before we start confusing people further,

Re: [coreboot] Disabling Intel ME 11 via undocumented mode

2017-12-15 Thread Gregg Levine
Hello! (I'm working from the office today on a library computer...) My regular laptop might be wearing one of those dratted things. But before we start confusing people further, perhaps one of the group needs to reiterate exactly what that contraption is, and why it was necessary. Oh and what the

Re: [coreboot] Disabling Intel ME 11 via undocumented mode

2017-12-15 Thread Philipp Stanner
Thanks. They didn't seriously include a Java Runtime Environment into the IME?? I can't believe what's going on with this company. Am Freitag, den 08.12.2017, 16:16 +0100 schrieb Thomas Heijligen: > For those who are interested in the Intel ME, the slides and white  > papers > from the Black Hat

Re: [coreboot] Lenovo G505s AMD Hardware Virtualization

2017-12-15 Thread awokd via coreboot
On Fri, December 15, 2017 10:00 am, Ivan Ivanov wrote: > awokd, could you please answer some questions: > > 1) From where you got that 0x06001119 microcode patch? > Is it a trusted source of a microcode? (hope its directly from AMD) > > > 2) Is there any way to determine that 0x06001119 is really

Re: [coreboot] Lenovo G505s AMD Hardware Virtualization

2017-12-15 Thread Ivan Ivanov
awokd, could you please answer some questions: 1) From where you got that 0x06001119 microcode patch? Is it a trusted source of a microcode? (hope its directly from AMD) 2) Is there any way to determine that 0x06001119 is really the latest microcode? Or there could be more recent versions