GRUB menu does not appear after “Welcome to GRUB!” [closed]
Clash Royale CLAN TAG#URR8PPP
The GRUB welcome message appears, and disappears after a moment, then there is a blank screen. However, it still responds to Ctrl+Alt+Del, in the same way as this question.
My issue has all of the symptoms of when GRUB was installed for BIOS instead of UEFI, but my motherboard doesn't support UEFI. I have confirmed this using the output of dmidecode -t 0, which does not mention UEFI. Running the same command on a PC that does support UEFI yields UEFI is supported at the bottom of the Characteristics section.
I followed this guide for using ZFS as the root file system on Arch. I don't think ZFS is the issue though, because I don't get to the GRUB menu screen, let alone mounting filesystems.
linux grub bios
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
asked Jan 8 at 20:06
MutantoeMutantoe
1317
closed as unclear what you're asking by Rui F Ribeiro, Mr Shunz, nwildner, thrig, JigglyNaga Jan 10 at 13:05
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
The GRUB welcome message appears, and disappears after a moment, then there is a blank screen. However, it still responds to Ctrl+Alt+Del, in the same way as this question.
My issue has all of the symptoms of when GRUB was installed for BIOS instead of UEFI, but my motherboard doesn't support UEFI. I have confirmed this using the output of dmidecode -t 0, which does not mention UEFI. Running the same command on a PC that does support UEFI yields UEFI is supported at the bottom of the Characteristics section.
I followed this guide for using ZFS as the root file system on Arch. I don't think ZFS is the issue though, because I don't get to the GRUB menu screen, let alone mounting filesystems.
linux grub bios
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
asked Jan 8 at 20:06
MutantoeMutantoe
1317
closed as unclear what you're asking by Rui F Ribeiro, Mr Shunz, nwildner, thrig, JigglyNaga Jan 10 at 13:05
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
dmidecode doesn't yield UEFI identifiers if you weren't booted up with UEFI to begin with.
– Shadur
Jan 10 at 11:32
@Shadur I didn't know that, that's useful information for the future. I did check a different way by installing Ubuntu, which installed GRUB using BIOS, so I reinstalled Arch using that method.
– Mutantoe
Jan 10 at 13:14
add a comment |
The GRUB welcome message appears, and disappears after a moment, then there is a blank screen. However, it still responds to Ctrl+Alt+Del, in the same way as this question.
My issue has all of the symptoms of when GRUB was installed for BIOS instead of UEFI, but my motherboard doesn't support UEFI. I have confirmed this using the output of dmidecode -t 0, which does not mention UEFI. Running the same command on a PC that does support UEFI yields UEFI is supported at the bottom of the Characteristics section.
I followed this guide for using ZFS as the root file system on Arch. I don't think ZFS is the issue though, because I don't get to the GRUB menu screen, let alone mounting filesystems.
linux grub bios
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
asked Jan 8 at 20:06
MutantoeMutantoe
1317
The GRUB welcome message appears, and disappears after a moment, then there is a blank screen. However, it still responds to Ctrl+Alt+Del, in the same way as this question.
My issue has all of the symptoms of when GRUB was installed for BIOS instead of UEFI, but my motherboard doesn't support UEFI. I have confirmed this using the output of dmidecode -t 0, which does not mention UEFI. Running the same command on a PC that does support UEFI yields UEFI is supported at the bottom of the Characteristics section.
I followed this guide for using ZFS as the root file system on Arch. I don't think ZFS is the issue though, because I don't get to the GRUB menu screen, let alone mounting filesystems.
linux grub bios
linux grub bios
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
asked Jan 8 at 20:06
MutantoeMutantoe
1317
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
asked Jan 8 at 20:06
MutantoeMutantoe
1317
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
edited Jan 8 at 20:16
Rui F Ribeiro
39.6k1479132
39.6k1479132
asked Jan 8 at 20:06
MutantoeMutantoe
1317
asked Jan 8 at 20:06
MutantoeMutantoe
1317
asked Jan 8 at 20:06
MutantoeMutantoe
1317
1317
closed as unclear what you're asking by Rui F Ribeiro, Mr Shunz, nwildner, thrig, JigglyNaga Jan 10 at 13:05
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Rui F Ribeiro, Mr Shunz, nwildner, thrig, JigglyNaga Jan 10 at 13:05
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
dmidecode doesn't yield UEFI identifiers if you weren't booted up with UEFI to begin with.
– Shadur
Jan 10 at 11:32
@Shadur I didn't know that, that's useful information for the future. I did check a different way by installing Ubuntu, which installed GRUB using BIOS, so I reinstalled Arch using that method.
– Mutantoe
Jan 10 at 13:14
add a comment |
1
dmidecode doesn't yield UEFI identifiers if you weren't booted up with UEFI to begin with.
– Shadur
Jan 10 at 11:32
@Shadur I didn't know that, that's useful information for the future. I did check a different way by installing Ubuntu, which installed GRUB using BIOS, so I reinstalled Arch using that method.
– Mutantoe
Jan 10 at 13:14
1
1
dmidecode doesn't yield UEFI identifiers if you weren't booted up with UEFI to begin with.
– Shadur
Jan 10 at 11:32
dmidecode doesn't yield UEFI identifiers if you weren't booted up with UEFI to begin with.
– Shadur
Jan 10 at 11:32
@Shadur I didn't know that, that's useful information for the future. I did check a different way by installing Ubuntu, which installed GRUB using BIOS, so I reinstalled Arch using that method.
– Mutantoe
Jan 10 at 13:14
@Shadur I didn't know that, that's useful information for the future. I did check a different way by installing Ubuntu, which installed GRUB using BIOS, so I reinstalled Arch using that method.
– Mutantoe
Jan 10 at 13:14
add a comment |
1 Answer
1
active
oldest
votes
When I reinstalled, I did two things differently:
My root partition was supposed to be specified as
Solaris Rootinstead ofLinux FilesystemI created a separate
/bootdirectory, withext4as the filesystem
One of these fixed my issue, but I'm not sure which.
answered Jan 9 at 16:14
MutantoeMutantoe
1317
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When I reinstalled, I did two things differently:
My root partition was supposed to be specified as
Solaris Rootinstead ofLinux FilesystemI created a separate
/bootdirectory, withext4as the filesystem
One of these fixed my issue, but I'm not sure which.
answered Jan 9 at 16:14
MutantoeMutantoe
1317
add a comment |
When I reinstalled, I did two things differently:
My root partition was supposed to be specified as
Solaris Rootinstead ofLinux FilesystemI created a separate
/bootdirectory, withext4as the filesystem
One of these fixed my issue, but I'm not sure which.
answered Jan 9 at 16:14
MutantoeMutantoe
1317
add a comment |
When I reinstalled, I did two things differently:
My root partition was supposed to be specified as
Solaris Rootinstead ofLinux FilesystemI created a separate
/bootdirectory, withext4as the filesystem
One of these fixed my issue, but I'm not sure which.
answered Jan 9 at 16:14
MutantoeMutantoe
1317
When I reinstalled, I did two things differently:
My root partition was supposed to be specified as
Solaris Rootinstead ofLinux FilesystemI created a separate
/bootdirectory, withext4as the filesystem
One of these fixed my issue, but I'm not sure which.
answered Jan 9 at 16:14
MutantoeMutantoe
1317
edited Jan 10 at 0:01
answered Jan 9 at 16:14
MutantoeMutantoe
1317
answered Jan 9 at 16:14
MutantoeMutantoe
1317
answered Jan 9 at 16:14
MutantoeMutantoe
1317
1317
add a comment |
add a comment |
1
dmidecode doesn't yield UEFI identifiers if you weren't booted up with UEFI to begin with.
– Shadur
Jan 10 at 11:32
@Shadur I didn't know that, that's useful information for the future. I did check a different way by installing Ubuntu, which installed GRUB using BIOS, so I reinstalled Arch using that method.
– Mutantoe
Jan 10 at 13:14