Initial dual boot sreen?

[dquinn618]

I cannot get my wifi to work except when right near the router. But I'm trying to set up the dual booting in the eventuality the driver or whatever IS wrong with the wifi, might be released. So I dual booted Win 10 and Mint Mate 18.2. But to do that, to boot Mint, right now have to be ready, after first turning on the power, to press the Esc. key to get to the boot device option menu, then after selecting F9 to get to the next menu where I can select to boot up using either the Ubuntu manager or the windows manager. My question is, can I streamline that startup process so the computer goes right to the boot manager menu when I turn on the power ? Instead of at first turning on the power on and making sure I'm poised to rapidly press the Esc. key at startup, and then selecting the boot devise, then going to the manager menu?

[Laurent85]

What is the brand and model of your computer ? Following commands output in a terminal would help further:

Code: Select all

inxi -Fxz
[ -d /sys/firmware/efi ] && sudo efibootmgr -v

[dquinn618]

HP Pavilion Laptop, not everything you asked for here though. Will have to get other terminal commands done later later from that computer.

.Postby dquinn618 » Tue Nov 07, 2017 8:36 am
inxi -Fxz
System: Host: mint Kernel: 3.13.0-37-generic x86_64 (64 bit, gcc: 4.8.2) Desktop: Gnome Distro: Linux Mint 17.1 Rebecca
Machine: System: HP (portable) product: HP Notebook version: Type1ProductConfigId
Mobo: HP model: 8207 version: 77.61 Bios: Insyde version: F.26 date: 06/01/2017
CPU: Dual core Intel Core i3-6100U CPU (-HT-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9211.88
Clock Speeds: 1: 2300.00 MHz 2: 2300.00 MHz 3: 400.00 MHz 4: 2300.00 MHz
Graphics: Card: Intel Device 1916 bus-ID: 00:02.0
X.Org: 1.15.1 drivers: fbdev,intel (unloaded: vesa) Resolution: 1600x900@77.0hz
GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) GLX Version: 2.1 Mesa 10.1.3 Direct Rendering: Yes
Audio: Card: Intel Device 9d70 driver: snd_hda_intel bus-ID: 00:1f.3 Sound: ALSA ver: k3.13.0-37-generic
Network: Card-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be port: 3000 bus-ID: 02:00.0
IF: wlan0 state: down mac: <filter>
Card-2: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller
driver: r8169 ver: 2.3LK-NAPI port: 4000 bus-ID: 01:00.0
IF: eth0 state: down mac: <filter>
Drives: HDD Total Size: 1008.2GB (0.6% used) 1: id: /dev/sda model: TOSHIBA_MQ01ABD1 size: 1000.2GB temp: 31C
2: USB id: /dev/sdb model: Cruzer size: 8.0GB temp: 0C
Partition: ID: / size: 3.9G used: 37M (1%) fs: overlayfs
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: System Temperatures: cpu: 37.0C mobo: 35.0C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 166 Uptime: 8 min Memory: 565.8/7873.5MB Runlevel: 2 Gcc sys: 4.8.2 Client: Shell inxi: 1.8.4

[dquinn618]

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,3001,0000,0003,2001,2002,2004
Boot0000* ubuntu HD(1,GPT,ab4b72f7-ef64-4735-9736-b698260e1451,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0001* Windows Boot Manager HD(1,GPT,ab4b72f7-ef64-4735-9736-b698260e1451,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0002* Windows Boot Manager HD(1,GPT,ab4b72f7-ef64-4735-9736-b698260e1451,0x800,0x82000)/File(EFI\ubuntu\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...I................
Boot0003* Notebook Hard Drive - TOSHIBA MQ01ABD100 BBS(HD,Notebook Hard Drive - TOSHIBA MQ01ABD100,0x500)................-.N.......N.A.N.....................................{.......A.........................
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot3001* Internal Hard Disk or Solid State Disk RC

[Laurent85]

Change the efi boot order to grub boot loader first. Computer might not take change into account if the efi firmware is buggy:

Code: Select all

sudo -s
efibootmgr --bootorder 0,1
exit

[fabien85]

If laurent's command is not enough, go into the firmware interface (/BIOS) and change the boot order, putting the entry "ubuntu" at the top.

If that's still not enough, then the firmware is definitively buggy. This does seem to happen frequently for HP computer, see this forum thread for a workaround : viewtopic.php?t=243338