systemd-logind: Failed to open "/boot/efi/loader/loader.conf
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 5 of 5
  1. #1
    Join Date
    Apr 2018
    Location
    Chelsea
    Posts
    10
    Linux (Fedora) Firefox 63.0

    systemd-logind: Failed to open "/boot/efi/loader/loader.conf

    Hi,
    I've been running into some issues when I tried to reboot lately.
    My system does boot, but I have to restart it quite a few times.
    I checked the journal and I noticed a few errors, in particular with "systemd-longind".

    Code:
    Dec 02 03:03:31 router-localhost kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
    Dec 02 03:03:31 router-localhost kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:   device [8086:a114] error status/mask=00001000/00002000
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:    [12] Replay Timer Timeout  
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:   device [8086:a114] error status/mask=00001100/00002000
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:    [ 8] RELAY_NUM Rollover    
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:    [12] Replay Timer Timeout  
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:   device [8086:a114] error status/mask=00001000/00002000
    Dec 02 03:03:31 router-localhost kernel: pcieport 0000:00:1c.4:    [12] Replay Timer Timeout  
    Dec 02 03:04:06 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:08:22-1267-0' is not a problem directory
    Dec 02 03:04:07 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:01:51-1248-4' is not a problem directory
    Dec 02 03:04:07 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:08:22-1267-2' is not a problem directory
    Dec 02 03:04:08 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-19:06:47-1312-0' is not a problem directory
    Dec 02 03:04:09 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-17:59:56-1147-0' is not a problem directory
    Dec 02 03:04:10 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-06-20:45:38-1035-0' is not a problem directory
    Dec 02 03:04:10 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-16:58:31-1149-0' is not a problem directory
    Dec 02 03:04:11 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-18:02:47-1277-0' is not a problem directory
    Dec 02 03:04:11 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-07-23:37:35-1064-0' is not a problem directory
    Dec 02 03:04:12 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-18:19:34-1231-0' is not a problem directory
    Dec 02 03:04:12 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-18:42:05-1269-0' is not a problem directory
    Dec 02 03:04:13 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:08:22-1267-1' is not a problem directory
    Dec 02 03:04:14 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-19:06:19-1312-0' is not a problem directory
    Dec 02 03:04:14 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:06:07-1302-3' is not a problem directory
    Dec 02 03:04:15 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-16:53:06-1092-0' is not a problem directory
    Dec 02 03:04:16 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-16:36:20-1058-0' is not a problem directory
    Dec 02 03:04:19 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-18:42:05-1269-1' is not a problem directory
    Dec 02 03:04:19 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:06:07-1302-2' is not a problem directory
    Dec 02 03:04:19 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-07-10-16:52:38-1092-0' is not a problem directory
    Dec 02 03:04:20 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:06:07-1302-1' is not a problem directory
    Dec 02 03:04:21 router-localhost systemd-logind[940]: Failed to open "/boot/efi/loader/loader.conf": No such file or directory
    Dec 02 03:04:21 router-localhost systemd-logind[940]: Failed to read boot config from "/boot/efi/loader/loader.conf": No such file or directory
    Dec 02 03:04:21 router-localhost systemd-logind[940]: Failed to load bootspec config from "/boot/efi/loader": No such file or directory
    Dec 02 03:04:21 router-localhost systemd-logind[940]: Failed to open "/boot/efi/loader/loader.conf": No such file or directory
    Dec 02 03:04:21 router-localhost systemd-logind[940]: Failed to read boot config from "/boot/efi/loader/loader.conf": No such file or directory
    Dec 02 03:04:21 router-localhost systemd-logind[940]: Failed to load bootspec config from "/boot/efi/loader": No such file or directory
    Dec 02 03:04:22 router-localhost abrtd[1091]: '/var/spool/abrt/oops-2018-11-23-09:06:07-1302-4' is not a problem directory
    Dec 02 03:04:26 router-localhost esets_mac[1415]: error[05870000]: Cannot unblock removable media (org.freedesktop.udisks2.filesystem-mount)
    Dec 02 03:04:38 router-localhost esets_daemon[1414]: error[05860000]: Error updating Antivirus modules: An error occurred while downloading update files.
    Dec 02 03:04:51 router-localhost spice-vdagent[1600]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
    Dec 02 03:05:09 router-localhost spice-vdagent[2089]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
    Dec 02 03:05:11 router-localhost gnome-session-binary[1342]: Unrecoverable failure in required component org.gnome.Shell.desktop
    Dec 02 03:05:20 router-localhost esets_daemon[1414]: error[05860000]: Error updating Antivirus modules: An error occurred while downloading update files.
    Dec 02 03:05:37 router-localhost abrt-notification[3317]: Process 1639 (blueman-applet) of user 1000 encountered an uncaught AttributeError exception
    Dec 02 03:05:38 router-localhost abrt-notification[3335]: Process 1649 (blueman-tray) of user 1000 encountered an uncaught AttributeError exception
    Dec 02 03:06:07 router-localhost wpa_supplicant[1246]: Using interface wlp2s0 with hwaddr 7c:b0:c2:fb:3f:c9 and ssid "router.localhost"

    My laptop has UEFI and I've been using GRUB for years, but I don't get why I get the error "Failed to open "/boot/efi/loader/loader.conf": No such file or directory".
    It almost seems like gummiboot (systemd-boot) is trying to boot as bootloader and is interfering with GRUB somehow.

    Is this the reason why I'm getting that error message?
    How can I fix it?
    And what are the errors I get for the PCI-Express? (I have an NVIDIA GTX 950M)


    Thank you in advance,
    Frank.

  2. #2
    Join Date
    Feb 2009
    Location
    Florida
    Posts
    646
    Linux (Fedora) Firefox 63.0

    Re: systemd-logind: Failed to open "/boot/efi/loader/loader.conf

    Getting the same series of systemd-logind messages here with no detectable issues as a result. For now I'm treating these as a packaging error.

    I would suggest your pcie bus errors are a top candidate for generating issues. Looks like it may be a NIC card. Can you pull it and see if you affect the error log?
    Laptop: Toshiba / Intel B960 2.20Ghz x2/ 4GB/ 320GB SataII/ Intel HD/ fc29.x86_64
    Tower: GigaByte (970A) / AMD FX 8320 3.5Ghz x8/ 16GB/ 9TB Sata III/ AMD 6770HD/ fc29.x86_64
    Bookshelf: Shuttle DS61 (H61)/ i3-3225 3.3Ghz x2/ 16GB/ 320GB Sata II/ Intel HD 4000/ fc29.x86_64
    Embedded: BeagleBone Blk / ARM AM3358 1 GHz x1/ 512MB/ 2GB eMMC/ PowerVR SGX530/ fc27.armv7hl

  3. #3
    Join Date
    Apr 2018
    Location
    Chelsea
    Posts
    10
    Windows 7 Chrome 61.0.3153.0

    Re: systemd-logind: Failed to open "/boot/efi/loader/loader.conf

    I can't 'cause it's a laptop.
    I can open it and remove the wifi card, but not the ethernet adapter.
    Anyway, once it boots, it works fine and it never gives any problem, even if I leave it up and running for days (without rebooting), so I don't know whether it's Fedora or the component that it's faulty.

    For the records, I have an ASUS N552VX, with an Intel i7 6700HQ, 2.60GHz 4c/8th, an integrated Intel graphic card, an NVIDIA 950M which is disabled with the nouveau blacklisted (as I never managed to get them working properly, so I disabled it since 2016), 16GB of RAM DDR4 (8X2) and two HDDs (1TB + 1TB).

  4. #4
    Join Date
    Jan 2018
    Location
    Pisa italy
    Posts
    6
    Windows 7 Firefox 63.0

    Re: systemd-logind: Failed to open "/boot/efi/loader/loader.conf

    Hi
    I'm not sure this can help you .
    But I suggest you to make a backup of efi partition.
    You can use clonezilla and tobackup/restore any partitions efi included.
    Last edited by enricota; 6th December 2018 at 01:26 PM.

  5. #5
    Join Date
    Apr 2018
    Location
    Chelsea
    Posts
    10
    Linux (Fedora) Firefox 63.0

    Re: systemd-logind: Failed to open "/boot/efi/loader/loader.conf

    I managed to solve the issue by getting rid of bbswitch, leaving the NVIDIA Graphic Card alone and using the integrated Intel card only.
    It's an NVIDIA 950M sadly, but the days when I used to play games are long gone, so it doesn't really matter.
    It seems like bbswitch was checking the state of the NVIDIA GPU at boot and it was getting stuck at it, waiting for a response.
    I have tearing and stuttering on Xorg with Intel, but I have to use it 'cause some programmes (like Aegisub) don't work on Wayland.
    It seems like the refresh rate of the integrated GPU doesn't match the monitor one, as I get a lot of dupes.
    Last edited by FranceBB; Today at 04:25 AM.

Similar Threads

  1. F16 Boot loader failed to install
    By rexbinary in forum Installation, Upgrades and Live Media
    Replies: 5
    Last Post: 28th May 2012, 12:53 PM
  2. Boot loader problem ("grub shell" at startup)
    By convict in forum Installation, Upgrades and Live Media
    Replies: 5
    Last Post: 21st October 2009, 07:52 AM
  3. FC6 OnBoard Hardware RAID boot loader installation failed
    By FCNB in forum EOL (End Of Life) Versions
    Replies: 1
    Last Post: 31st July 2007, 01:48 PM
  4. GRUB boot loader r windows boot loader?
    By Rebels Mascot in forum Using Fedora
    Replies: 4
    Last Post: 12th May 2005, 03:50 AM
  5. boot loader failed to install
    By louie2 in forum Installation, Upgrades and Live Media
    Replies: 3
    Last Post: 19th December 2004, 05:45 AM

Posting Permissions

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