Option to enter bios skipped on start-up after install

I just installed Ubuntu 24.04.3 LTS via USB ISO, next to Windows 10.
However on re-boot Windows 10 was only option seen in BIOS.
So I re-installed BIOS to see if this resolved issue, but instead the PC just boots straight into Ubuntu - no option at start-up to get into BIOS and enable Dual-Boot option. (No Alienware logo, nor prompt to hit F2 or F12 keys.)
I write this because I do need dual boot & ability to access BIOS.
I can no longer access Windows 10.


I have tried reinstall of Ubuntu, reinstall of BIOS, and flashing BIOS, all to no avail. Have also tried blinding tapping, F2, F12 (previous options) also Escape, and combined Function+F1 keys. Any advice appreciated +++ thanks.


Ubuntu 24.04.3 LTS
Dell Alienware Area 51 R2 (2016)
Processor Intel® Core™ i7-6950X Processor
(10 cores, 25MB Cache, TurboBoost Max 3.0,
Overclocked up to 3.8 GHz)
Operating Systems N0.2 - Windows 10 Pro
Memory 64GB (4X16GB) DDR4 2133MHz SDRAM Memory
1ry Hard Drive 512GB SSD 6Gb/s Main + 4TB 5400RPM SATA 6Gb/s Storage
Storage 3x 8TB
Video Dual NVIDIA® GeForce® GTX 1080 with 8GB GDDR5X
each (NVIDIA SLI® Enabled)
MoBo Alienware 0FRTKJ .BMH0LG2.CN6970267R0706. A00
Bios Alienware A14, 02-Jul-2018

Welcome to Ubuntu Discourse :slight_smile:

I assume you are currently booting Ubuntu?

If yes, please open a terminal and run this command:

sudo fdisk -l

Copy the output and paste it back here into a new reply, then highlight the text and click on the </> icon in the composer to wrap with code tags.

Let’s first try and see where things are holding before the next steps.

(a) After you have successfully booted into Ubuntu, open a terminal and enter:-

sudo systemctl reboot --firmware-setup

(b) If you edit grub to ensure that the grub boot menu appears, then you will have a choice of operating systems.
Together with an option to boot into UEFI Firmware Settings

sudo nano /etc/default/grub

Example below

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false

Update grub to reflect the new options

sudo update-grub

Thanx Rubi… as requested…

Disk /dev/loop0: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 73.91 MiB, 77504512 bytes, 151376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 245.13 MiB, 257036288 bytes, 502024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 73.92 MiB, 77512704 bytes, 151392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 247.09 MiB, 259092480 bytes, 506040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 11.13 MiB, 11673600 bytes, 22800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 516.01 MiB, 541073408 bytes, 1056784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 516.2 MiB, 541278208 bytes, 1057184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: LITEON CV3-CE512
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DD042886-A368-40B9-BC3C-AF55D798BD7A

Device         Start        End   Sectors   Size Type
/dev/sda1       2048     411647    409600   200M EFI System
/dev/sda2     411648     444415     32768    16M Microsoft reserved
/dev/sda3     444416  726444031 725999616 346.2G Microsoft basic data
/dev/sda4  972879872  973801471    921600   450M Windows recovery environment
/dev/sda5  973801472 1000214527  26413056  12.6G Windows recovery environment
/dev/sda6  726444032  972879871 246435840 117.5G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000DM004-2CX1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 949E401F-C287-4F44-9160-90B7BDF201E3

Device     Start         End     Sectors  Size Type
/dev/sdb1     34       32767       32734   16M Microsoft reserved
/dev/sdb2  32768 15628050431 15628017664  7.3T Microsoft basic data

Partition 1 does not start on physical sector boundary.


Disk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000DM004-2CX1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: DB136C29-0A13-43F4-ADD0-1D10D69E46AD

Device     Start         End     Sectors  Size Type
/dev/sdc1     34       32767       32734   16M Microsoft reserved
/dev/sdc2  32768 15628050431 15628017664  7.3T Microsoft basic data

Partition 1 does not start on physical sector boundary.


Disk /dev/sdd: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000AS0002-1NA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B61417C4-18A9-458F-B6DD-A8EBE616D6CF

Device      Start         End     Sectors  Size Type
/dev/sdd1      34      262177      262144  128M Microsoft reserved
/dev/sdd2  264192 15628052479 15627788288  7.3T Microsoft basic data

Partition 1 does not start on physical sector boundary.


Disk /dev/loop8: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 10.83 MiB, 11354112 bytes, 22176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 49.29 MiB, 51687424 bytes, 100952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 50.77 MiB, 53235712 bytes, 103976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 576 KiB, 589824 bytes, 1152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 209.98 MiB, 220176384 bytes, 430032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sde: 7.52 GiB, 8074035200 bytes, 15769600 sectors
Disk model: Flash Disk      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x086b2af6

Device     Boot Start      End  Sectors  Size Id Type
/dev/sde1  *       64 15769599 15769536  7.5G  c W95 FAT32 (LBA)

Thx also Tea-4-1
I tried… “sudo systemctl reboot --firmware-setup”
But just got a persistent black screen
(It never powered powered up my monitor from sleep I note, unlike my mouse & key/b.)
Monitor stayed black and never entered BIOS nor OS.

After rebooting, I tried “sudo nano /etc/default/grub”…
And received…
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”
GRUB_CMDLINE_LINUX=“”

Not being a coder, I’m not sure what to do next. Thx again +++

Persistent black screen and unable to access UEFI is not a good sign.
UEFI firmware is the vendor’s responsibility.
Not much point in editing grub yet.

Power off
Unplug the power cord
Physically remove all disks
Power on
The PC will only have the option to access UEFI firmware

Any luck?

In your initial post, you indicate that you don’t see th machine logo on boot and are not able to access the BIOS but in a subsequent post, you show that you are booted into Ubuntu and have posted the output of sudo fdisk -l. Can you boot Ubuntu?

If you can boot Ubuntu, the first step is to follow the suggestion above regarding the /etc/default/grub file. The command you were given would open that file with root administrator permissions in a text editor. The content you posted shows you have the menu set to ‘hidden’, the timeout set to ‘0’ so you will not see a menu because of those settings. If you were to change those as suggested and add the line ‘GRUB_DISABLE_OS_PROBER=false’ to that file and run sudo update-grub, you might see the windows entry.

If you are able to boot Ubuntu, you might try checking the /boot/efi/EFI directory to see if you have both ubuntu and Microsoft directories there to verify both are UEFI installs.

Microsoft required vendors to use FAST Boot setting in UEFI. That is different than the fast startup setting in Windows…

Fast Boot assumes no system changes and immediately boots last configuration. Typically not enough time to press any key to get into UEFI or change boot choice. Best to have it off when changing system. Ok to have back on once not changing system, if you know how to bypass it.

Most system default boot after full power down or cold boot as suggested above, to give just enough time to press a key.

Reinstall of UEFI/BIOS normally resets to defaults which would be Fast Boot on.
Check your manual on fast boot settings.

1 Like

Thanks again guys for your ideas +++
Tried on another monitor - no help.
Tried disconnecting all drives - no help.
Tried resetting CMOS - no help.
In fact now, have lost ability boot for Ubuntu to appear if I wait for 2 minutes.
… all because this fantastic 3D-rendering PC won’t take Win11 & I tried to install duel boot. Grrrrrr.
I’ve had it with Microsoft - forget duel boot.
If you guys can just get me up and running on Ubuntu?
Problem now is I’ve currently now got zero access to BIOS or either OS on the drives. (USB Ubuntu stick now no longer appears on boot, probably because my resetting stopped USB being first in boot sequence???)

Is this Dell info useful?

Thx again T41 - (had not spotted that specific Dell page in my scouring :wink:
Their suggested…

  • keyboard shortcut start-up - no response
  • renaming Bios file as BIOS_IMG.rcv file - also drew no bios screens.
    I can an hear occasional soft click or two on some boot-ups but the monitor remains firmly on ‘stand-by’ while mouse/keyboard both power up. (I have checked - the monitor is still working.)

Difficulty in accessing the UEFI settings (BIOS) for a PC is not specifically an Ubuntu issue.
Regrettably, all the suggestions, so far, have drawn a blank.
Therefore, I think that you should contact the vendor (Dell) or, at least, investigate the Dell forums.

Second thoughts:-

Have a look at this post
Can you boot into an efi shell or even boot the kernel directly?

Does your system have Intel RAID or RST on (even if one drive)? You may need AHCI mode for drives.

Any older post:
https://www.dell.com/community/en/conversations/linux-general/area-51m-help-installing-linux-as-dual-boot/647f81b7f4ccf8a8de06d4a6

Final note to all…
Thanks to all seasoned Ubuntuites for your your suggestions.
I finally got into the Bios. This time round I double-checked Secure-Boot and Fast Start (both in Windows and in Bios) were all disabled… but on trying again to dual boot my machine again bricked.
I have given up, and swapped my machine to run pure Ubuntu & it’s running like silk.
thanks again to all for your patient assistance. +++

1 Like

Just to satisfy my curiosity, which method was successful?

T41… I ended up bailing and sent to PC guy on the other side of town who said he specialised in Alienware fixes. I assumed he’d would re-flash bios chip from another PC. But he said afterwards, that it was full of dust. A full clean, and MoBo solution dip, and it booted with a simple Win10 recovery file. (I had already tried this myself of course - but still got the blank screen.)
Anyhows… thx again for assisting and giving me every opportunity to sort it out myself. +++

This topic was automatically closed after 30 days. New replies are no longer allowed.