Oops! Sorry!
Forgot to say that we are using Secure Boot Disabled on both computers
(Acer TravelMate B117-M & B118-M).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN:
Present on 18.04.3 and 16.04.6 (64 bit, LTS with latest updates)
-
$ dmesg | grep Couldn
[2.215723] Couldn't get size: 0x800e
[2.215759] MODSIGN: Couldn't get UEFI MokListRT
Error "Couldn't get size: 0x800e" has resurfaced despite of
the released fix. I found this error in latest Ubuntu 18.04 install.
Release fix needs to be re-evaluated.
$ dmesg
.
[0.933031] Loading compiled-in X.509 certificates
[0.934003] Loaded X.509 cert 'Build time
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications about this bug go to:
On my Disco Dingo see this also, though it doesn't seem to have any
negative effect.
kernel: 5.0.0-16-generic
secureboot: Secure boot could not be determined (mode 0)
[2.243394] Loaded X.509 cert 'Build time autogenerated kernel key: ...'
[2.267416] Couldn't get size:
This bug is marked as "Fix Released" but after years of running Manjaro
I decided to give Ubuntu a try again with Disco Dingo 19.04 and it was
simply impossible because it still exists. I could get past the initial
error, and Ubuntu thought it was installed, but trying to boot just
output the
Present on 19.04 Disco Dingo with kernel:
Linux 5.0.0-11-generic #12-Ubuntu SMP Thu Apr 11 16:41:13 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
Errors in dmesg show:
[1.116542] Loading compiled-in X.509 certificates
[1.117339] Loaded X.509 cert 'Build time autogenerated kernel key:
after resetting the bios to factory reset I was able to avoid the
following error :
Couldn't get size: 0x800e
MODSIGN: Couldn't get UEFI db list
But I still got the following error:
[5.354582] Couldn't get size: 0x800e
[5.354610] MODSIGN: Couldn't get UEFI
I am also facing this issue the logs are as follows:
[5.325847] Couldn't get size: 0x800e
[5.325850] MODSIGN: Couldn't get UEFI db list
[5.325867] Couldn't get size: 0x800e
[5.325868] MODSIGN: Couldn't get UEFI MokListRT
[5.327139] zswap: loaded using
kamiccolo, Nebojsa Grujic,
Is secure boot enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications about this bug go to:
This is really a nasty one. I installed a brand new machine, did not
have any problems. Then upgraded the graphics to nvidia 1070, and
started having this same issue. Disabled the secure boot, problem went
away, however, fstab mounted my second drive as home, as I had it
before, now problem came
Still a thing on 4.15.0-45-generic #48~16.04.1-Ubuntu :|
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications about this bug go
slightly different on a different hardware
07:39:58 kernel: MODSIGN: Couldn't get UEFI db list
07:39:58 kernel: Couldn't get size: 0x800e
System:
Host: corrado-HP-p3-cc-0515 Kernel: 4.15.0-22-generic x86_64 bits: 64
compiler: gcc v: 7.3.0 Desktop: Gnome 3.28.1
Distro: Ubuntu
Still having the problem:
06:07:39 kernel: Couldn't get size: 0x800e
06:07:39 kernel: MODSIGN: Couldn't get UEFI db list
06:07:39 kernel: Couldn't get size: 0x800e
corrado@corrado-p6-cc-0509:~$ inxi -SCx
System:Host: corrado-p6-cc-0509 Kernel: 4.15.0-22-generic x86_64
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications
v4.13 final, all good!
[1.485360] Loaded X.509 cert 'Build time autogenerated kernel key:
2977791a6bc138cb597bcddff841bb4e6c0cdbe0'
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Can you see if v4.13 final has the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To
No, it doesn't.
The kernel was updated to 4.13.0-32-generic, and this still has the bug, I
believe the 4.13.0-21 might have it also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
Does this bug go away if you boot back in to 4.13.0-21?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications about this bug go
Not in my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications about this bug go to:
I'm seeing something slightly different. MokListRT vs dbx list. Is it
the same issue?
[1.066401] Couldn't get size: 0x800e
[1.066403] MODSIGN: Couldn't get UEFI MokListRT
[1.066728] zswap: loaded using pool lzo/zbud
--
You received this bug notification because you are
None os this kernels has the bug.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't get UEFI db list
To manage notifications about this bug go to:
I'd like to perform a "Reverse" bisect to figure out what commit fixes
this bug. We need to identify the last kernel version that had the bug,
and the first kernel version that fixed the bug.
Can you test the following kernels and report back:
v4.14-rc1:
The bug is fixed in the upstream 4.15-rc8, still in the mainline.
Thanks
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743908
Title:
MODSIGN: Couldn't
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
25 matches
Mail list logo
