On Thu, 2021-08-26 at 11:05 +0300, Timo Lindfors wrote:
> On Thu, 26 Aug 2021, Lukasz Hawrylko wrote:
> > You can check if txt-stat dumps TBOOT log correctly. Nothing else comes
> > into my mind.
>
> Looks normal to me. I've attached a compressed version to this mail.
Looks good, thank you for
On Thu, 26 Aug 2021, Lukasz Hawrylko wrote:
You can check if txt-stat dumps TBOOT log correctly. Nothing else comes
into my mind.
Looks normal to me. I've attached a compressed version to this mail.
-Timo
txt-stat.output.gz
Description: application/gzip
On Wed, 2021-08-25 at 09:28 +0300, Timo Lindfors wrote:
> On Tue, 24 Aug 2021, Lukasz Hawrylko wrote:
> > Patch with fix is already prepared, I am waiting for GRUB team to merge
> > new multiboot2 module tag to publish it.
> >
> > In meantime, if you have a system when you are able to reproduce
On Tue, 24 Aug 2021, Lukasz Hawrylko wrote:
Patch with fix is already prepared, I am waiting for GRUB team to merge
new multiboot2 module tag to publish it.
In meantime, if you have a system when you are able to reproduce this
issue, may I ask you to test the fix?
Sure. I applied these to
Hi Timo
On Tue, 2021-08-24 at 12:19 +0300, Timo Lindfors wrote:
> [replying to an old email thread]
>
> On Tue, 7 Apr 2020, Lukasz Hawrylko wrote:
> > Unfortunately, this bug is not reported anywhere. In real life scenarios
> > I don't see any benefits of loading multiple SINITs. In most cases
[replying to an old email thread]
On Tue, 7 Apr 2020, Lukasz Hawrylko wrote:
Unfortunately, this bug is not reported anywhere. In real life scenarios
I don't see any benefits of loading multiple SINITs. In most cases you
have one SINIT that is dedicated to the platform.
I am not sure if that
On Tue, 14 Apr 2020, Lukasz Hawrylko wrote:
I don't know if that tool exists. Anyway, I will look at that multiple
SINITs bug in TBOOT, when it will be fixed, that kind of tool will not
be required.
True, that would mostly not be needed if tboot worked automatically. I can
think of two use
On Tue, 14 Apr 2020, Lukasz Hawrylko wrote:
As KBL SINIT works with both SKL and KBL platforms, the old one,
compatible only with SKL, is not longer supported and may not work with
newer versions of SKL bioses. Recommendation is to use the KBL SINIT for
both KBL and SKL systems.
To avoid
On Wed, 2020-04-08 at 18:34 +0300, Timo Lindfors wrote:
> On Wed, 8 Apr 2020, Lukasz Hawrylko wrote:
> > TBOOT has an algorithm that checks if SINIT matches platform. I can't
> > tell you right now what is wrong here, I need some logs. Please run it
> > once again, than after reboot, can you
On Wed, 8 Apr 2020, Lukasz Hawrylko wrote:
If you can connect serial port and dump serial logs too that will be
awesome. Dell's docking station has RS232 connector and TBOOT's logs are
printed there (tested on my laptop).
A boot log captured from the monitor using a camera is now available at
On Wed, 8 Apr 2020, Lukasz Hawrylko wrote:
TBOOT has an algorithm that checks if SINIT matches platform. I can't
tell you right now what is wrong here, I need some logs. Please run it
once again, than after reboot, can you launch Linux without TBOOT and
run 'txt-stat' tool that is in TBOOT's
On Wed, 2020-04-08 at 17:12 +0300, Timo Lindfors wrote:
> On Tue, 7 Apr 2020, Lukasz Hawrylko wrote:
> > Unfortunately, this bug is not reported anywhere. In real life scenarios
> > I don't see any benefits of loading multiple SINITs. In most cases you
> > have one SINIT that is dedicated to the
On Tue, 7 Apr 2020, Lukasz Hawrylko wrote:
Unfortunately, this bug is not reported anywhere. In real life scenarios
I don't see any benefits of loading multiple SINITs. In most cases you
have one SINIT that is dedicated to the platform.
The main benefit is that you can automate installation
On Thu, 2020-04-02 at 17:25 +0300, Timo Lindfors wrote:
> Hi,
>
> On Thu, 2 Apr 2020, Lukasz Hawrylko wrote:
> > There is a bug in TBOOT that may results in overlapping loaded SINITs by
> > TBOOT's logs. That problem occurs when you load multiple SINITs in GRUB
> > and in most cases the last one
Hi,
On Thu, 2 Apr 2020, Lukasz Hawrylko wrote:
There is a bug in TBOOT that may results in overlapping loaded SINITs by
TBOOT's logs. That problem occurs when you load multiple SINITs in GRUB
and in most cases the last one will be corrupted. That's why, when TBOOT
executes GETSEC[SENTER] CPU
On Tue, 2020-03-31 at 23:27 +0300, Timo Lindfors wrote:
> Hi,
>
> if I have the following ACM modules in /boot
>
> 018c4c0bc64cad7c939061e111937849f61af395c9981a03ac4a10083058aa5d
> 4th_gen_i5_i7_SINIT_75.BIN
> 0848adfea4c9479b1cd096aeda1d4a3afe309dd45ca43a1e8d8b3cf972c9c14f
>
16 matches
Mail list logo
