FedoraForum.org - Fedora Support Forums and Community
Page 2 of 2 FirstFirst 1 2
Results 16 to 22 of 22
  1. #16
    Join Date
    Sep 2009
    Posts
    2,120

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    Please add your information to the bug that antikythera linked in post #2. It's a kernel bug... Remember, it's the squeeky wheel that get greased! I just downloaded and installed kernel 4.12.11-200.fc25.x86_64 from koji, and the bug is still present.

    dd_wizard

  2. #17
    Join Date
    Sep 2017
    Location
    West Virginia
    Posts
    1

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    Quote Originally Posted by dd_wizard
    Please add your information to the bug that antikythera linked in post #2. It's a kernel bug... Remember, it's the squeeky wheel that get greased!
    Well, I'm seeing two problems reported here actually. Some people get these errors but their system still boots fine. Others, like myself, are getting these errors on boot and hard lockups. (In fact something appears to have nuked all the files in /boot/efi on my system -- 'rpm -Va' complains about them being missing...)

    Are we sure that the hard-lockup issue is the same as the MODSIGN error issue?

  3. #18
    Join Date
    Oct 2016
    Location
    Texas
    Posts
    3

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    Is it possible that it is a bad or missing configuration in udev-rules in the initramfs?

    [root ~]# dmesg | grep MODSIGN
    [ 1.482919] MODSIGN: Couldn't get UEFI db list

    [root ~]# dmesg | grep initram
    [ 0.640562] Unpacking initramfs...

    [root ~]# systemd-analyze
    Startup finished in 1.989s (kernel) + 5.789s (initrd) + 16.185s (userspace) = 23.963s

    [root ~]# dracut -f -v
    dracut: Executing: /usr/bin/dracut -f -v
    dracut: *** Including module: bash ***
    dracut: *** Including module: systemd ***
    dracut: *** Including module: systemd-initrd ***
    dracut: *** Including module: nss-softokn ***
    dracut: *** Including module: i18n ***
    dracut: *** Including module: network ***
    dracut: *** Including module: ifcfg ***
    dracut: *** Including module: drm ***
    dracut: *** Including module: plymouth ***
    dracut: *** Including module: kernel-modules ***
    dracut: *** Including module: kernel-network-modules ***
    dracut: *** Including module: resume ***
    dracut: *** Including module: rootfs-block ***
    dracut: *** Including module: terminfo ***
    dracut: *** Including module: udev-rules ***
    dracut: Skipping udev rule: 40-redhat.rules
    dracut: Skipping udev rule: 50-firmware.rules
    dracut: Skipping udev rule: 50-udev.rules
    dracut: Skipping udev rule: 91-permissions.rules
    dracut: Skipping udev rule: 80-drivers-modprobe.rules
    dracut: *** Including module: biosdevname ***
    dracut: *** Including module: dracut-systemd ***
    dracut: *** Including module: usrmount ***
    dracut: *** Including module: base ***
    dracut: *** Including module: fs-lib ***
    dracut: *** Including module: shutdown ***
    dracut: *** Including modules done ***
    dracut: *** Installing kernel module dependencies ***
    dracut: *** Installing kernel module dependencies done ***
    dracut: *** Resolving executable dependencies ***
    dracut: *** Resolving executable dependencies done***
    dracut: *** Hardlinking files ***
    dracut: *** Hardlinking files done ***
    dracut: *** Stripping files ***
    dracut: *** Stripping files done ***
    dracut: *** Generating early-microcode cpio image ***
    dracut: *** Constructing AuthenticAMD.bin ****
    dracut: *** Store current command line parameters ***
    dracut: *** Creating image file '/boot/initramfs-4.12.13-300.fc26.x86_64.img' ***
    dracut: *** Creating initramfs image file '/boot/initramfs-4.12.13-300.fc26.x86_64.img' done ***

    --------------------------------

    I would also like to point this out:

    [ 1.483577] Loaded UEFI:MokListRT cert 'Fedora Secure Boot CA: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' linked to secondary sys keyring

    It is happening roughly almost right after it spits out the MODSIGN error. I replaced the key with 'x' in case it was sensitive information.
    Last edited by mj5030; 18th September 2017 at 03:32 PM.

  4. #19
    Join Date
    Apr 2015
    Location
    Location
    Posts
    46

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    Hi,
    I have the same issue with Fefora 27 beta, here's my post

  5. #20
    Join Date
    Dec 2007
    Posts
    246

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    "Same here" F26 from liveCD or install to disk. Stock graphics. UEFI enabled in BIOS.

    Thinking about maybe disabling secure boot and then using the CD to repair boot.

    NOTE: Disabling secure boot does not require changing UEFI boot to BIOS boot (a.k.a. "legacy" or "compatibility") mode.
    This page recommends against BIOS (legacy, compatibility) boot because it can introduce other problems.

    Code:
    2013 SAMGSUNG 305v5A-A04US laptop
    
     AMD A8-3510MX APU with Radeon(tm) HD Graphics
     OpenGL ES 3.0 Mesa 17.2.2
     OpenGL ES GLSL ES 3.00
     4.13.5-200.fc26.x86_64 x86_64
    Last edited by hellork; 22nd October 2017 at 09:16 PM.
    Data, Information Processing, Secure Hosting, and Internet Technology (D.I.P.S.H.I.T.)

  6. #21
    Join Date
    Apr 2015
    Location
    Location
    Posts
    46

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    Quote Originally Posted by hellork
    NOTE: Disabling secure boot does not require changing UEFI boot to BIOS boot (a.k.a. "legacy" or "compatibility") mode.
    True, just for the sake of information I'd like to add that I've seen a EFI implementation on a Acer laptop that requires you to boot the computer in Windows for accessing that option (through the Advanced Recovery options in Wndows 10).

    Interesting link you posted (and plenty more articles on that website). It made wonder if creating the bootable USB stick through Gnome Disks makes it UEFI bootable only or not...
    Cheers

  7. #22
    Join Date
    Dec 2007
    Posts
    246

    Re: MODSIGN: Couldn't get UEFI db list after 4.12 upgrade

    Turns out secure boot was not enabled in the 2013 SAMGSUNG 305v5A-A04US laptop. I found a setting called "legacy USB" and turned that off. It does nothing. No effect. There could be a legacy boot compatibility mode active somewhere that requires booting to the recovery partition or Windows to change. Too bad. Those are long gone along with the last 3 hard drive upgrades. Gonna look for a BIOS update.

    #sudo dmidecode
    BIOS Information
    Vendor: American Megatrends Inc.
    Version: 02QN.MI99.20110908.SKK
    Release Date: 09/08/2011

    I have made USB sticks that were UEFI bootable only. The Fedora Live CD is both-enabled, I think.
    Last edited by hellork; 22nd October 2017 at 09:16 PM.
    Data, Information Processing, Secure Hosting, and Internet Technology (D.I.P.S.H.I.T.)

Page 2 of 2 FirstFirst 1 2

Similar Threads

  1. GRUB failure after Apper F22 kernel upgrade, dual boot Win8 UEFI
    By itpwrusr in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 7th March 2016, 09:55 PM
  2. Install non-UEFI onto existing UEFI?
    By BuckleSwasher in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 13th October 2015, 10:13 AM
  3. How to make grub on F17 (uefi w/ grub 1) boot windows 7 (uefi)?
    By premudriy in forum Installation, Upgrades and Live Media
    Replies: 4
    Last Post: 21st August 2012, 06:58 PM
  4. Replies: 1
    Last Post: 3rd July 2012, 06:59 PM
  5. Why patch modsign disappeared ?
    By Jeremy38 in forum Security and Privacy
    Replies: 0
    Last Post: 11th September 2009, 09:26 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •