LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
Reload this Page [SOLVED] Parabola and GRUB
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
Page 1 of 5 1 23 Last »
  Search this Thread
Old 05-24-2021, 12:31 PM   #1
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Rep: Reputation: Disabled
Parabola and GRUB

I performed the installation (with openRC) until I reached section 5.4 in https://wiki.parabola.nu/Installation_Guide#OpenRC_2

when I run modprobe efivars, I get:

FATAL: Module efivars not found in directory /lib/modules/5.7.10-gnu-1

But when I use:

ls /lib/modules/ I get 5.10.27-gnu-1-lts (folder)


How do I solve this?
 
Old 05-24-2021, 02:04 PM   #2
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,528

Rep: Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495
Quote:
/sys/firmware/efi
When you checked the above directory did you find the efi directory to verify you are booting efi by checking /sys/firmware/efi?

Quote:
Module efivars not found in directory /lib/modules/5.7.10-gnu-1
Your software is looking for 5.7.10-gnu-1 and you show in your post you have 5.10.27-gnu-1-lts. I expect you would need to either change whatever script is looking for 5.7.10 to have it look for 5.10.27 or download the older version. What else do you have in that directory?
Last edited by yancek; 05-24-2021 at 02:05 PM.
 
Old 05-24-2021, 02:24 PM   #3
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
[QUOTE=yancek;6253594]When you checked the above directory did you find the efi directory to verify you are booting efi by checking /sys/firmware/efi?
[/QUOTE=yancek;6253594]

I found efivars, so I guess I'm alreadynin EFI


Quote:
Your software is looking for 5.7.10-gnu-1 and you show in your post you have 5.10.27-gnu-1-lts. I expect you would need to either change whatever script is looking for 5.7.10 to have it look for 5.10.27 or download the older version. What else do you have in that directory?
How do I change the script for that?

And here are the contents this directory:
kernel modules.builtin.alias.bin modules.dep.bin modules.symbols
modules.alias modules.builtin.bin modules.devname modules.symbols.bin
modules.alias.bin modules.builtin.modinfo modules.order pkgbase
modules.builtin modules.dep modules.softdep vmlinuz
 
Old 05-25-2021, 07:31 AM   #4
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,528

Rep: Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495
Which Linux distribution are you using. I meant the contents of /lib/modules not /lib/modules/5.10.27. If you already have a Linux installed and it is booting UEFI, I don't expect you would need to do the step under 5.4 on that page as that section just explains installing/configuring Grub. So what distro are you using, do you have Grub installed and if not what boot loader are you using?

If that is not the case, post back with the above info.
 
Old 05-25-2021, 07:52 AM   #5
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
/lib/modules has 5.7.10-gnu-1 and only

I thought it would be a good idea to reinstall grub to get rid of my long list of previously installed distros (clean up the UEFI boot list for neatness)

Would deleting 5.7.10-gnu-1 and reinstall grub just work?
Last edited by MUSTDOS; 05-25-2021 at 07:54 AM.
 
Old 05-25-2021, 01:04 PM   #6
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by yancek View Post
Which Linux distribution are you using. I meant the contents of /lib/modules not /lib/modules/5.10.27. If you already have a Linux installed and it is booting UEFI, I don't expect you would need to do the step under 5.4 on that page as that section just explains installing/configuring Grub. So what distro are you using, do you have Grub installed and if not what boot loader are you using?

If that is not the case, post back with the above info.
I expected to re-install grub since I thought 5.4 was still necessary, now I'm on USB live of parabola of x64

Only two OSes are installed now, windows 7 and parabola. Both are not bootable for now

I tried in 5.4 to do as chroot in /mnt: grub-install /dev/sda

and got: grub-install: error: cannot find EFI directory.

although I mounted /dev/sda1 (EFI partition with flags: boot and esp)
 
Old 05-25-2021, 01:56 PM   #7
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
I even tried in chroot while /dev/sda1 is mounted to boot with this with no errors

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck
grub-mkconfig -o /boot/grub/grub.cfg

But my computer shuts down if I try to boot into grub
 
Old 05-25-2021, 02:16 PM   #8
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,528

Rep: Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495Reputation: 2495
Quote:
/lib/modules has 5.7.10-gnu-1 and only
The above is from post 5 which conflicts with your initial post which indicates you have 5.10.27-gnu-1-lts in /lib/modules. So what do you have in /lib/modules?

Quote:
I thought it would be a good idea to reinstall grub to get rid of my long list of previously installed distros (clean up the UEFI boot list for neatness)
If you have menuentries in Grub for Linux installs which you have overwritten, all you would need to do is run grub-mkconfig command. If you want to remove old EFI entries, use efibootmgr. Lots of sites with detailed tutorials.

Windows 7 is generally installed in Legacy mode meaning there would be no EFI partition. You indicate you do have an EFI partition so if you have installed Parabola in EFI mode, it will never boot windows 7 in Legacy mode. Might be best to run the following command to see what type of drive you have:

Code:
fdisk -l
You need to run the command as root privileges using sudo if your system uses that.
 
Old 05-25-2021, 03:06 PM   #9
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
[QUOTE=yancek;6253878]The above is from post 5 which conflicts with your initial post which indicates you have 5.10.27-gnu-1-lts in /lib/modules. So what do you have in /lib/modules?

Ooops, copied the wrong line, 5.10.27-gnu-1-lts is the only directory present
If you have menuentries in Grub for Linux installs which you have overwritten, all you would need to do is run grub-mkconfig command. If you want to remove old EFI entries, use efibootmgr. Lots of sites with detailed tutorials.

Windows 7 is generally installed in Legacy mode meaning there would be no EFI partition. You indicate you do have an EFI partition so if you have installed Parabola in EFI mode, it will never boot windows 7 in Legacy mode. Might be best to run the following command to see what type of drive you have:

Code:
fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA MQ01ABD0
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: 283274F2-F174-4A5F-A4CC-779C1B55941C

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 1312767 262144 128M Microsoft reserved
/dev/sda3 1312768 603604991 602292224 287.2G Microsoft basic data
/dev/sda4 603604992 925685759 322080768 153.6G Linux filesystem
/dev/sda5 925685760 968294399 42608640 20.3G Linux filesystem
/dev/sda6 968294400 976773119 8478720 4G Linux swap


Disk /dev/loop0: 856.84 MiB, 898461696 bytes, 1754808 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/sdb: 7.21 GiB, 7742685184 bytes, 15122432 sectors
Disk model: Nano Pro
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: 0x52ca9606

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3793663 3793664 1.8G 0 Empty
/dev/sdb2 180 131251 131072 64M ef EFI (FAT-12/16/32)


Disk /dev/sdc: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Disk model: Card Reader
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: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdc1 32768 124735487 124702720 59.5G 7 HPFS/NTFS/exFAT


sdc is for an sd card I have
Last edited by MUSTDOS; 05-25-2021 at 03:07 PM. Reason: typo
 
Old 05-25-2021, 04:27 PM   #10
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by yancek View Post
When you checked the above directory did you find the efi directory to verify you are booting efi by checking /sys/firmware/efi?



Your software is looking for 5.7.10-gnu-1 and you show in your post you have 5.10.27-gnu-1-lts. I expect you would need to either change whatever script is looking for 5.7.10 to have it look for 5.10.27 or download the older version. What else do you have in that directory?
[root@parabolaiso /]# ls /lib/modules
5.10.27-gnu-1-lts
[root@parabolaiso /]# modprobe efivars
modprobe: FATAL: Module efivars not found in directory /lib/modules/5.7.10-gnu-1
[root@parabolaiso /]#

That's my output
 
Old 05-25-2021, 07:57 PM   #11
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,355

Rep: Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591
from live installer
make sure your booted in uefi mode by checking the existence of /sys/firmware/efi
mount the root partition to /mnt
mount /dev/sda1 to /mnt/boot/efi
delete the /mnt/boot/efi/EFI/parabola/grubx64.efi

Code:
arch-chroot /mnt
grub-install --target=i386-efi
exit
reboot
 
Old 05-25-2021, 09:22 PM   #12
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
from live installer
make sure your booted in uefi mode by checking the existence of /sys/firmware/efi
mount the root partition to /mnt
mount /dev/sda1 to /mnt/boot/efi
delete the /mnt/boot/efi/EFI/parabola/grubx64.efi

Code:
arch-chroot /mnt
grub-install --target=i386-efi
exit
reboot
Not even this helped...
 
Old 05-26-2021, 05:25 AM   #13
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,355

Rep: Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591
post the output of
Code:
efibootmgr -v
 
Old 05-26-2021, 05:44 AM   #14
MUSTDOS
Member
 
Registered: Mar 2020
Distribution: antix
Posts: 100

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
post the output of
Code:
efibootmgr -v
As root

127 root@parabolaiso ~ # efibootmgr -v
BootCurrent: 0008
Timeout: 0 seconds
BootOrder: 0011,0010,0008,000B,000F,0004,0006,000E,0003,0007,0009,000C,000D,000A
Boot0000 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0002 Recovery FvFile(ab4579c4-3bc5-4489-a88e-0f21e6cebf85)
Boot0003* SATA HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0004* SATA CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0005* CD-ROM: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,be9d0102e211f3489efa0b983c96839b)
Boot0006* USB CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0007* USB FDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0008* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0009* NETWORK: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000A* ubuntu HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot000B* Windows Boot Manager HD(1,MBR,0x52ca9606,0xb4,0x20000)/File(\EFI\Microsoft\Boot\bootmgfw.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.}...a................
Boot000C* debian HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\debian\shimx64.efi)
Boot000D* Slackware HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\Slackware\elilo.efi)
Boot000E* antiX19 HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\antiX19\grubx64.efi)
Boot000F* gentoo HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\gentoo\grubx64.efi)
Boot0010* parabola HD(1,GPT,eb33e0f5-2fcb-4784-ab69-4232c683c7f8,0x800,0x100000)/File(\EFI\parabola\grubia32.efi)
Boot0011* grub HD(1,GPT,eb33e0f5-2fcb-4784-ab69-4232c683c7f8,0x800,0x100000)/File(\EFI\grub\grubx64.efi)



As chroot in /mnt

[root@parabolaiso /]# efibootmgr -v
BootCurrent: 0008
Timeout: 0 seconds
BootOrder: 0011,0010,0008,000B,000F,0004,0006,000E,0003,0007,0009,000C,000D,000A
Boot0000 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0002 Recovery FvFile(ab4579c4-3bc5-4489-a88e-0f21e6cebf85)
Boot0003* SATA HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0004* SATA CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0005* CD-ROM: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,be9d0102e211f3489efa0b983c96839b)
Boot0006* USB CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0007* USB FDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0008* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0009* NETWORK: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000A* ubuntu HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot000B* Windows Boot Manager HD(1,MBR,0x52ca9606,0xb4,0x20000)/File(\EFI\Microsoft\Boot\bootmgfw.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.}...a................
Boot000C* debian HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\debian\shimx64.efi)
Boot000D* Slackware HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\Slackware\elilo.efi)
Boot000E* antiX19 HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\antiX19\grubx64.efi)
Boot000F* gentoo HD(1,GPT,044fd531-a488-48b4-91a6-148534bfcc62,0x800,0x100000)/File(\EFI\gentoo\grubx64.efi)
Boot0010* parabola HD(1,GPT,eb33e0f5-2fcb-4784-ab69-4232c683c7f8,0x800,0x100000)/File(\EFI\parabola\grubia32.efi)
Boot0011* grub HD(1,GPT,eb33e0f5-2fcb-4784-ab69-4232c683c7f8,0x800,0x100000)/File(\EFI\grub\grubx64.efi)
[root@parabolaiso /]#
 
Old 05-26-2021, 05:54 AM   #15
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,355

Rep: Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591
do the same as in post 11, but change back to --target=x86_64-efi

from live installer
make sure your booted in uefi mode by checking the existence of /sys/firmware/efi
mount the root partition to /mnt
mount /dev/sda1 to /mnt/boot/efi

Code:
arch-chroot /mnt
grub-install --target=x86_64-efi
exit
reboot
 
  


Reply
Page 1 of 5 1 23 Last »

Tags
grub, instal, installation



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Need Help Configuring Grub (Libreboot) to Load LUKS Encrypted Parabola Logical Volume Group nekrosynthesis Linux - Newbie 35 11-12-2019 01:04 AM
Parabola GNU / Linux - Problem with ATI driver (Radeon HD 4250) when starting x Roondmoond Linux - Newbie 12 10-08-2014 03:31 PM
Infinite Grub Loop: GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB GRUB... beeblequix MEPIS 2 11-02-2013 10:56 PM
Parabola GBU/Linux 2012 laptop dualboot ilovepenquins Linux - Laptop and Netbook 4 07-18-2013 06:31 AM
"isolinux.bin missing or corrupt" for Arch, Parabola and Fedora zwitterion-241920 Linux - General 5 12-30-2011 04:57 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 08:52 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration