Hi Nico,
On 24.04.2018 19:38, Nico Huber wrote:
> not sure what you are looking for, but I guess this is what you need,
> because
I only was testing the image with the different extracting tools.
>> Error: Unable to detect BIOS Image type.
I guess, if you flash the vendor bios and then reread
Hi!
On 24.04.2018 21:27, Mat wrote:
> I'd like to have system updated against spectre, and other possible
> vulnerabilities as much as possible.
With the retpoline option in the Linux kernel, it should be usually safe
(see attachment).
"IBPB is considered as a good addition to retpoline for Va
Hi everybody,
yesterday I created a user group "corporate" on review.coreboot.org and
added all people who I assume are paid for working on coreboot (based on
their email address domains).
Corporate contributions tend to be high volume and there are usually
multiple people interested in getting t
Hello!
On 24.04.2018 21:27, Mat wrote:
> That's why I (believe I) need the blobs from the newest update. Is the
> reasoning correct, or I could do it more wise?
AFAIK: You only really need the microcode update from Intel.
Don't know, if gbe.bin or ifd.bin is vulnerable.
If you apply the micro
On Thu, Apr 26, 2018 at 10:05 AM diffusae via coreboot <
coreboot@coreboot.org> wrote:
>
> Don't know, if gbe.bin or ifd.bin is vulnerable.
>
they are configuration "blobs" not binary blobs, no executable code
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/list
Hi!
I'm also interested in a running version of current master.
On 25.04.2018 12:51, Nicola Corna wrote:
> If needed I can do some tests on this PC.
I also would do some testing on this machine, if that helps.
Regards,
Reiner
--
coreboot mailing list: coreboot@coreboot.org
https://mail.corebo
Hi,
I have a KCMA-D8 and am willing to provide a status update but have no idea
what is the formal way to do it.
I guess it begins with testing a specific version (4.7 or latest source ?).
Please could you point me to a procedure.
Thanks
From: coreboot on be
On Wed, Apr 25, 2018 at 1:51 PM, Nicola Corna wrote:
> April 18, 2018 3:54 PM, "Kyösti Mälkki" wrote:
>
>> Having romstage stack smashed seems irrelevant for the no-boot issue.
>> That nehalem raminit code, struct raminfo, seems to eat a lot of stack
>> and an error message for that case was adde
On Thu, April 26, 2018 5:09 pm, Pierre P wrote:
> Hi,
>
>
> I have a KCMA-D8 and am willing to provide a status update but have no
> idea what is the formal way to do it.
>
> I guess it begins with testing a specific version (4.7 or latest source
> ?). Please could you point me to a procedure.
Loo
Thank You
On Thu, Apr 26, 2018 at 5:09 PM, Matt DeVillier
wrote:
> On Thu, Apr 26, 2018 at 10:05 AM diffusae via coreboot <
> coreboot@coreboot.org> wrote:
>
>>
>> Don't know, if gbe.bin or ifd.bin is vulnerable.
>>
>
> they are configuration "blobs" not binary blobs, no executable code
>
> --
>
In the meantime I've decided to go in the following direction:
1. install intel microcode onto my ubuntu box
the result is:
x220$ $ dmesg | grep microcode
[0.00] microcode: microcode updated early to revision 0x2d,
date = 2018-02-07
[0.881361] microcode: sig=0x206a7,
People
I've just upgraded my corebot BIOS.
To have ctrl <-> fn keyboard switch, I use nvramcui as secondary payload.
The problem is that when I press esc to enter menu, then choose nvramcui,
the exit operation (with f1 key) results with immediate system hang with
large number of hexadecimal digit
I've compared configuration before and after. Here is the diff.
The case is I didn't choose any new options, thus the difference probably
appears because of new options added to coreboot in the meantime.
22,23c22,24
< # CONFIG_COLLECT_TIMESTAMPS is not set
< CONFIG_USE_BLOBS=y
---
> CONFIG_COLLEC
On Wed, Apr 4, 2018 at 3:38 PM taii...@gmx.com wrote:
> At the rate things are going soon there will be no non-development
> boards that are still in the repos due to the arbitrary increasing of
> standards.
>
I can tell you, based on the 19 years of this project's existence, that it
was not arb
Hi Florentin,
Dne 25.4.2018 v 18:42 eche...@free.fr napsal(a):
> Hello Rudolf,
> First thank your for finding these blobs and the hack to use them, and for
> testing and validating them.
> But please could you tell us what was the setup for your tests :
> - what was your hardware : cpu + mobo (c
How urgent is "urgent" given that the board remains in git, and all it
takes is for a new board status to be submitted (and any bugs fixed)?
If it is so urgent, why don't you submit a report instead of phrasing
your email in a panic-like and accusatory manner?
taii...@gmx.com:
> This is a great b
On Thu, April 26, 2018 11:13 pm, Duncan wrote:
> How urgent is "urgent" given that the board remains in git, and all it
> takes is for a new board status to be submitted (and any bugs fixed)?
>
> If it is so urgent, why don't you submit a report instead of phrasing
> your email in a panic-like and
On Thu, Apr 26, 2018 at 12:06 PM, awokd via coreboot
wrote:
> On Thu, April 26, 2018 5:09 pm, Pierre P wrote:
> > Hi,
> >
> >
> > I have a KCMA-D8 and am willing to provide a status update but have no
> > idea what is the formal way to do it.
> >
> > I guess it begins with testing a specific vers
18 matches
Mail list logo