On Saturday, 22 July 2017 at 08:42, Dave Pawson wrote:
On 21 July 2017 at 23:49, Dominik 'Rathann' Mierzejewski
> On Friday, 21 July 2017 at 17:53, Sérgio Basto wrote:
>> On Fri, 2017-07-21 at 16:49 +0100, Dave Pawson wrote:
>> > Leigh has (rather unhelpfully) responded with a snippet
>> > [ 0.000000] BRK [0x230390000, 0x230390fff] PGTABLE
>> > [ 0.000000] Secure boot enabled and kernel locked down
>> > [ 0.000000] RAMDISK: [mem 0x3ed5a000-0x3fffdfff]
>> > Would someone be kind enough to interpret please?
>> Should mean that you need disable secure boot on BIOS , or you will
>> need sign kernel modules (kmods) of Nvidia drive.
> For the record, there's a bug in grub2 that was fixed in F26 but not in
> earlier releases that causes 4.11.x kernels to be unable to detect
> SecureBoot status and disables kernel lockdown, hence allowing unsigned
> modules (like nvidia kmod) to be loaded. That's why the "issue" is
> after upgrade to F26.
That seems illogical, since I am running F26 Dominik?
You said it worked on F25. Which grub2 and kernel versions did you have
installed back then? Compare with current non-working F26 installation
and draw your own conclusions.
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"