You are not logged in.
Pages: 1
I have clean installed arch with systemd-boot. Whenever I tried to get into bios menu, it just shows black screen with underline cursor and not thing works.
i have tried getting into bios menu by following ways:
- Using F2 at time of booting
- Using reboot into firmware setup on systemd-boot menu
- Using systemctl reboot --firmware-setup
But all three ways results in the same, black screen with underline cursor.
I have this problem when I was using grub2 with dual booting windows.
This time I have clean installed, removing windows and creating new Partition table(UEFI/GPT).
I have Acer Preator Helios 300 laptop.
This is my /boot/loader/loader.conf
default arch.conf
timeout 3
editor no
bootctl status
System:
Firmware: UEFI 2.60 (INSYDE Corp. 21044.273)
Secure Boot: disabled
Setup Mode: user
Current Boot Loader:
Product: systemd-boot 244.3-1-arch
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
✓ Boot loader sets ESP partition information
ESP: /dev/disk/by-partuuid/<UUID>
File: └─/EFI/systemd/systemd-bootx64.efi
Random Seed:
Passed to OS: yes
System Token: set
Exists: yes
Available Boot Loaders on ESP:
ESP: /boot (/dev/disk/by-partuuid/<UUID>)
File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 244.3-1-arch)
File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 244.3-1-arch)
Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0004
Status: active, boot-order
Partition: /dev/disk/by-partuuid/<UUID>
File: └─/EFI/systemd/systemd-bootx64.efi
Boot Loader Entries:
$BOOT: /boot (/dev/disk/by-partuuid/<UUID>)
Default Boot Loader Entry:
title: Arch Linux (arch.conf)
id: arch.conf
source: /boot/loader/entries/arch.conf
linux: /vmlinuz-linux
initrd: /intel-ucode.img
/initramfs-linux.img
options: root=UUID=<UUID2> rw
Last edited by someGuyBlah1024 (2020-08-03 13:36:09)
Offline
According to this post F2 is the correct key to use but
There is another way to get into BIOS if your laptop boots up way too fast to even get into it spamming f2. Click Start menu, then the power icon at the bottom and then hold SHIFT and click on restart. This will take you into a blue menu from there you click Troubleshoot and then click Advanced Options, then Select UEFI Firmware Settings and hit Restart
Offline
Pretty sure those are Windows instructions. For systemd-using Linux systems, see
man systemctl | less -p firmware-setup
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pretty sure those are Windows instructions. For systemd-using Linux systems, see
man systemctl | less -p firmware-setup
man pages doesnt say much about this. It says this functionality is not supported on all system. But in cases where this functionality is not supported, I think systemctl should give error firmware is not supported. Not sure but I have seen some users getting this error.
But in my case system reboots and lands on black screen.
Other things I noted, on this black screen only Ctrl+Alt+Del works which reboots the system.
And i have setup boot password, but password prompt doesnt comes up when trying to get into BIOS menu. Password prompt comes up on mormal boot.
PS:
In case if its relevant, I have TPM on this laptop.
Last edited by someGuyBlah1024 (2020-08-03 13:28:24)
Offline
If the OS-specific instructions don't work, and the specified POST-time hotkey doesn't work, then the only options left are clearing the CMOS and seeking support from the device manufacturer.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
By the way is your system updated? Systemd 244-3 is very old.
Offline
pacman -Qs systemd
local/netctl 1.23-1
Profile based systemd network management
local/systemd 245.7-1
system and service manager
local/systemd-boot-pacman-hook 2-1
Pacman hook to upgrade systemd-boot after systemd upgrade.
local/systemd-libs 245.7-1
systemd client libraries
local/systemd-sysvcompat 245.7-1
sysvinit compat for systemd
At this point of time 245.7-1 is latest version for systemd.
Dont know why there is mismatch between this and bootctl status
Offline
If the OS-specific instructions don't work, and the specified POST-time hotkey doesn't work, then the only options left are clearing the CMOS and seeking support from the device manufacturer.
Sorry, accidently reported your post.
If I clear the CMOS, is there a chance that my system will brick?
Offline
Sorry, accidently reported your post.
Hey, that is what brought me here
If I clear the CMOS, is there a chance that my system will brick?
Always, but very remote. More likely you could find yourself in a state where things don't work until you sort out the settings; like USB legacy setup, eMMC configuration, Legacy boot vs uEFI, SATA configuration.
The thing I would worry about would be to get Secure boot enabled with no way to disable it.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Pages: 1