You are not logged in.

#1 2022-04-08 19:57:22

Rayshabh
Member
From: Proxima Centauri b
Registered: 2022-04-07
Posts: 38

[SOLVED] "bootctl status" command returns "n/a"

When I'm running "bootctl status" command in my terminal, the output it returns -

"❯ bootctl status
systemd-boot not installed in ESP.
No default/fallback boot loader installed in ESP.
System:
     Firmware: n/a (n/a)
  Secure Boot: enabled (user)
TPM2 Support: yes
Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─n/a

Random Seed:
Passed to OS: no
System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/4ccbdebe-7a76-014b-87a9-d9cf9076146>

Boot Loaders Listed in EFI Variables:
        Title: GRUB
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/4ccbdebe-7a76-014b-87a9-d9cf90761466
         File: └─/EFI/GRUB/grubx64.efi

        Title: Shim
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/4ccbdebe-7a76-014b-87a9-d9cf90761466
         File: └─/EFI/GRUB/bootx64.efi

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/4ccbdebe-7a76-014b-87a9-d9cf9076146>

0 entries, no entry could be determined as default. "

Well, I just wanted to know why the firmware and Current bootloader details are N/A ?

Please note: I am using GRUB Bootloader.

Last edited by Rayshabh (2022-04-18 05:57:42)

Offline

#2 2022-04-09 09:08:01

NoSavvy
Member
From: Dorchester, Dorset, UK
Registered: 2013-01-23
Posts: 97

Re: [SOLVED] "bootctl status" command returns "n/a"

Perhaps it because you are NOT using bootctl. As stated when running "bootctl status".
You are using the grub boot loader, as stated.

Last edited by NoSavvy (2022-04-09 09:33:51)

Offline

#3 2022-04-09 09:16:15

GeorgeJP
Member
From: Czech Republic
Registered: 2020-01-28
Posts: 187

Re: [SOLVED] "bootctl status" command returns "n/a"

Rayshabh wrote:

Please note: I am using GRUB Bootloader.

... then you can't report status of systemd-boot bootloader as you don't have it.

Offline

#4 2022-04-09 10:40:39

Rayshabh
Member
From: Proxima Centauri b
Registered: 2022-04-07
Posts: 38

Re: [SOLVED] "bootctl status" command returns "n/a"

So you mean to get bootctl status I need to use systemd-boot as bootloader and not GRUB, right?

Last edited by Rayshabh (2022-04-09 10:53:42)

Offline

#5 2022-04-09 12:27:32

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,833

Re: [SOLVED] "bootctl status" command returns "n/a"

Yes.  but this feels like a XY question. What do you think bootctl status would do for you?

Offline

#6 2022-04-09 13:14:09

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED] "bootctl status" command returns "n/a"

I was going to post a similar thing to the first couple of replies but apparantly some information should be shown even if systemd-boot isn't being used...

bootctl man page wrote:

These commands are available on any EFI system, regardless of the boot loader used.

status

Shows brief information about the system firmware, the boot loader that was used to boot the system, the boot loaders currently available in the ESP, the boot loaders listed in the firmware's list of boot loaders and the current default boot loader entry. If no command is specified, this is the implied default.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#7 2022-04-09 13:26:41

Rayshabh
Member
From: Proxima Centauri b
Registered: 2022-04-07
Posts: 38

Re: [SOLVED] "bootctl status" command returns "n/a"

V1del wrote:

Yes.  but this feels like a XY question. What do you think bootctl status would do for you?

I feel if the system terminal is accepting "bootctl status" commands then it should atleast show the basic firmware details and current bootloader details irrespective of the bootloaders being used by the system.

Offline

#8 2022-04-09 13:29:36

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,833

Re: [SOLVED] "bootctl status" command returns "n/a"

Firmware can only show something if your EFI has certain EFI variables filled, which isn't guaranteed the "current boot loader" info will only show information if certain EFI variables are filled, which systemd-boot will fill, others may not

Last edited by V1del (2022-04-09 13:43:32)

Offline

#9 2022-04-09 13:37:32

Rayshabh
Member
From: Proxima Centauri b
Registered: 2022-04-07
Posts: 38

Re: [SOLVED] "bootctl status" command returns "n/a"

Slithery wrote:

I was going to post a similar thing to the first couple of replies but apparantly some information should be shown even if systemd-boot isn't being used...


That's what I want to know.

According to https://man7.org/linux/man-pages/man1/bootctl.1.html, it is clearly stated under "GENERIC EFI FIRMWARE/BOOT LOADER COMMANDS" that the "bootctl status" command should return basic information about the system firmware, the boot loader being used to boot the system, the boot loaders currently available in the ESP, the boot loaders listed in the firmware's list of boot loaders and the current default boot loader entry, regardless of the boot loader used.

So if this is true, then why my firmware's details not being shown by bootctl status?

Offline

#10 2022-04-09 13:46:22

Rayshabh
Member
From: Proxima Centauri b
Registered: 2022-04-07
Posts: 38

Re: [SOLVED] "bootctl status" command returns "n/a"

V1del wrote:

Firmware can only show something if your EFI has certain EFI variables filled, which isn't guaranteed the "current boot loader" info will only show information if certain EFI variables are filled, which systemd-boot will fill, others may not



Okay.

Offline

Board footer

Powered by FluxBB