installation worked like a charm, but grub doesnt shows up at boot..
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
installation worked like a charm, but grub doesnt shows up at boot..
hello
here on two different laptops i have a problem :
there are already both on windows, but the simple attempt to install linux is a bit complicated.
the LMDE systems boot up well from liveusb. The installation works like a charm. But after a reboot, systematically the computer boot up into windows, with not showing the grub menu. Because it doesnt boot up directly on grub.efi
well, if I F9 the bios at startup, the bios itself can find within the HDD the both windows and grub efi files and boot up well on linux ; but my wish is to get the grub firstly (whom contains windows's entry) from bios. I can't change the efi variables from the bios, as it's a insydebios one.
how could i fix it?
i tried
a/ by distinguish both /boot/efi mount point and partition at the partition step of installation wizard, with no effect
b/ to install grub, in the step after, on the /dev/sda2 (instead of default /dev/sda), where sda2 is vfat efi partition (with windows), and sda8 the / root system partition,
with no effect..
i have well as the same as others computer with the same win8 and linux systems, the same /boot/efi/EFI variables, as Boot/debian/Microsoft.
im totally lost, im wondering why the computer always boot up directly on mswindows instead of grub..
i already tried those attempts, with no more success :
without forgetting the mount -t efivarfs efivarfs /sys/firmware/efi/efivars
what am i doing wrong?
the last time i observed a such issue, it was on a similar lenovo laptop, i did this (to separate /boot/efi by creating a completely new efi partition, then asking the installer to install grub on /dev/sda10 instead of /dev/sda) :
Quote:
=================================
had that problem too :
win8 installed by default, EFI mode, with GPT. Dont want to wipe all out.
Had several new partitions for nux/bsd. So I booted on my beloved LMDE5 liveusb.
I did about ten installs without understanding, why would that not work?
each time when installation started very well, it finishes on a grub-installation
failure, everytime.
Even by trying changing different settings.
Even using the grub-repair utility -whom, like gparted, is only on lmde5live, not lmde5 default install!-
so I finally went up to boot back on my beloved LMDE5 liveusb, and took a precaution regarding it :
1. before starting again and again the installation process, I just launched gparted
2. created a new EFI fat32-somthing type of partition (could be seen in fdisk /dev/sda)
in addition of the EFI-partitions made by default windows installation.
3. Means after getting at the end of the disk my several partitions (50GB /, home, +efi)
4. I attempted to install back LMDE5 with standard installer ; saying "no, dont use /dev/sda1
nor /dev/sda2 windows partitions to put your grub files/efi system, but only on /dev/sda8 new fat32 efi partition!"
[I already have exactly flex20405 laptop, whom grub is well on the "windows efi standard partition", like
all my others win8-10/lmde5/obsd laptops, working well since the beginning]
5. so after I did a such experience, told LMDE5 installer to use not only /, /home and swap partitions to use,
but also a efi-specific partition added only for it -about 500MB-, it worked immediately.
Dont know why the G50 laptop have this thing, but now, hope it would help some linuxians hearts
Conclusion : on my own, I have triboot of win/LMDE5/obsd, like on my previous laptop.
Yes, it really worth a post after those years (means hours/days of working on that problem/solution). Definitely
==================================
but here, it doesnt works at all... for two lenovo and HP laptops.
Do you have the Linux OS set to first boot priority in the BIOS? If you can use the F9 key for a one time boot option to boot Linux you need to make the change permanent. What is the boot order from: sudo efibootmgr -v?
This is what works on my hp: f10 to access bios/firmware 'system configuration'>'boot options'>'os boot manager' use f5 f6 key to move items up and down to change order, f10 to save and exit.
Generally, the one time boot option for an HP is the F9 key and access to the BIOS is with the F10 key and you may find the options you are looking for under System Configuration or under Boot Options. I don't know about Lenovo but as pointed out above, it is a simple task to change the boot priority in the BIOS with HP.
Do you have the Linux OS set to first boot priority in the BIOS? If you can use the F9 key for a one time boot option to boot Linux you need to make the change permanent. What is the boot order from: sudo efibootmgr -v?
well, on the HP G7/efi :
F9 could well boot into linux. BUT. Yes, there is a but :
using liveusb/mount/grub-install/update-grub/efibootmgr-o + boot-repair, did NOT repair it.
everytime, it boots back on windows's efi
im wondering about using the g50-70 trick, whom consists to create a vfat-formated efi partition and to install on /grub/sda8 at that time (it's the situation of the quoted part of my first post)
for the lenovo flex20405, for a huge time i had to F11 immediately at bootup to avoid going into windows's efi.
thus, since i did a simple :
plus both mixed together (the grub-install --recheck /dev/sda permitted to flex20405 to boot directly on grub instead of win8 by default, i had during a f... year to F11 at each reboot)
for the hp g7 2257sf, i still have, after all those commands, plus the efibootmgr -o [debianfirst,then common order], still the computers boots up on windows'efi.
i can use the F9 key to boot under linux, yes, at bios's boot up.
Quote:
Originally Posted by colorpurple21859
This is what works on my hp: f10 to access bios/firmware 'system configuration'>'boot options'>'os boot manager' use f5 f6 key to move items up and down to change order, f10 to save and exit.
unfortunately i have nothing to manage direct EFI entries into that insyde end-user bios/efi.
Quote:
Originally Posted by yancek
Generally, the one time boot option for an HP is the F9 key and access to the BIOS is with the F10 key and you may find the options you are looking for under System Configuration or under Boot Options. I don't know about Lenovo but as pointed out above, it is a simple task to change the boot priority in the BIOS with HP.
the thing is, im not looking to "find a way to boot on linux by F9/EFI", almost all efi computers have it
im looking for a solution, where after a common linux's wizard installation including grub installation, after update-grub/grub-install with recheck option, after boot-repair tool attempt, after efibootmgr -o orders change, to get another way to avoid windows's boot first, than to replace directly msftwindows's efi file by grub's efi one.
only the -n option from F9-key booted linux/grub makes the computer booting directly on grub/linux. Not -o . Or anything else.
but i dont want to be restricted to such manipulation, just want if somebody without my password wants to reboot, the choice of win/nux should be made by grub, not windows directly if no keystroke is entered...
yepp, everytime i poweroff the computer completely (no reboot) to test if the latest manipulation could avoid windows efi boots directly.
until here, none worked on that hp g7.
im not looking to "find a way to boot on linux by F9/EF
And that is exactly what we were trying to explain to you. The F9 key is almost always a ONE TIME change. It is not a permanent change. It only makes the change for that boot and if you want to make it permanent, you need to not use the F9 one time boot option but another key which should show. On my HP it is the F10 key to actually access the BIOS to make a permanent change.
most efibootmgr changes do not work on HP computers but you can very easily make the change once you learn how to actually access the BIOS. Where you make the change will vary as an earlier post above says it is under System Configuration while on mine it is under Boot Options. You find OS Boot Manager and you can make the change there by using the F6 key to move a highlighted entry up or the F5 key to move an entry down. This information is printed on that page in your BIOS firmware. I don't have a Lenovo so I have no idea how that would work.
I see reference in your posts to boot repair. Is there any particular reason why you did not use the Create BootInfo Summary Option suggested on the boot repair page? That would give members here a link to view details on your system.
When you use the one time F9 boot option to boot LMDE, can you view your EFI partition? Can you see the proper files and directories there? Do you have a directory for LMDE? I don't know what it would be called, debian??
At this point I would suggest you run boot repair and post the link you get it when it finishes so there is some detailed information specific to your computer.
Maybe this will work: back up the EFI/BOOT/Bootx64.efi file on the efi partition and replace it by copying Slackware grubx64.efi on the efi partition to EFI/BOOT/Bootx64.efi on the efi partition
Maybe this will work: back up the EFI/BOOT/Bootx64.efi file on the efi partition and replace it by copying Slackware grubx64.efi on the efi partition to EFI/BOOT/Bootx64.efi on the efi partition
this is what i want to avoid : not touching to efi files and fix the solution by grub-tools (i didnt had to touch .efi files on lenovo nor asus efi laptop)
Quote:
Originally Posted by yancek
And that is exactly what we were trying to explain to you. The F9 key is almost always a ONE TIME change. It is not a permanent change. It only makes the change for that boot and if you want to make it permanent, you need to not use the F9 one time boot option but another key which should show. On my HP it is the F10 key to actually access the BIOS to make a permanent change.
i agree
Quote:
Originally Posted by yancek
most efibootmgr changes do not work on HP computers but you can very easily make the change once you learn how to actually access the BIOS. Where you make the change will vary as an earlier post above says it is under System Configuration while on mine it is under Boot Options. You find OS Boot Manager and you can make the change there by using the F6 key to move a highlighted entry up or the F5 key to move an entry down. This information is printed on that page in your BIOS firmware. I don't have a Lenovo so I have no idea how that would work.
i agree
Quote:
Originally Posted by yancek
I see reference in your posts to boot repair. Is there any particular reason why you did not use the Create BootInfo Summary Option suggested on the boot repair page? That would give members here a link to view details on your system.
i tried, no effect, i have the txt log report in attachment
Quote:
Originally Posted by yancek
When you use the one time F9 boot option to boot LMDE, can you view your EFI partition? Can you see the proper files and directories there? Do you have a directory for LMDE? I don't know what it would be called, debian??
yes, i see "debian" just under windows, or grub.efi if i browse ; this is only available on the F9, not in the bios.
Quote:
Originally Posted by yancek
At this point I would suggest you run boot repair and post the link you get it when it finishes so there is some detailed information specific to your computer.
The Boot Info log you posted is interesting as I don't believe I have seen this before. Your efibootmgr output shows the current boot as 0002 which below shows debian as 0002 so that would be your LMDE. Curiously, 0002 does not show in the boot order so I see the problem. Obviously, you can't put it first if it does not show an entry. I don't know why that would happen. You could try the suggestion in the post above but if that fails, I expect it is hardware related. Is this the HP or the Lenovo?
This solution only works as long as you boot into lmde. After booting into Windows will have to use f9 key to boot back into lmde.
Create a /etc/rc.local file with this in it:
Code:
#!/bin/bash
#a place to run local commands at boot
efibootmgr -n 0002
exit 0
The Boot Info log you posted is interesting as I don't believe I have seen this before. Your efibootmgr output shows the current boot as 0002 which below shows debian as 0002 so that would be your LMDE. Curiously, 0002 does not show in the boot order so I see the problem. Obviously, you can't put it first if it does not show an entry. I don't know why that would happen. You could try the suggestion in the post above but if that fails, I expect it is hardware related. Is this the HP or the Lenovo?
Distribution: ChromeOS,SlackWare,Android and Lubuntu
Posts: 68
Rep:
As for the BIOS entry key on HP machines it is esc and the one time boot selector key is f9 however, the temporary boot option isn't a permanent solution.
I'd recommend that the OP consider investigate installing the grub II boot loader and let OS-Robber discover the windows 8 installation. Furthermore Windows 8 has long been EOLed
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.