Mailing List Archive

On 12/5/23 12:05, thelma@sys-concept.com wrote:
> It has been some time since I installed Gentoo.
> After partitioning, and installing the system after reboot I get kernel
> selection from grub and hitting enter,
> I don't see any text scrolling on the screen, and I don't see the login
> screen.

> I think I install grub in a wrong way.
> When I mount "boot" content of /boot:
> ls /boot/
> EFI

Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint
should be in /boot as is in your /etc/fstab.

> When I unmount "boot" content of /boot:
> ls /boot/
> System.map-6.1.57-gentoo config-6.1.57-gentoo grub vmlinuz-6.1.57-gentoo
>

Re: New installation - not booting [ In reply to ]

peter.bo at web

Dec 5, 2023, 9:29 AM

Post #3 of 17 (352 views)

Am Dienstag, 5. Dezember 2023, 18:05:56 CET schrieb thelma@sys-concept.com:
> It has been some time since I installed Gentoo.
> After partitioning, and installing the system after reboot I get kernel
> selection from grub and hitting enter, I don't see any text scrolling on
> the screen, and I don't see the login screen.
>
> Is the text scroll disabled for booting or is my configuration incorrect?
>
> Here are some details:
> Partition:
> /dev/nvme0n1p1 2048 2099199 2097152 1G EFI System
> /dev/nvme0n1p2 2099200 10487807 8388608 4G Linux swap
> /dev/nvme0n1p3 10487808 1953523711 1943035904 926.5G Linux filesystem
>
> cat /etc/fstab
> /dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
> /dev/nvme0n1p2 none swap sw 0 0
> /dev/nvme0n1p3 / ext4 noatime 0 1
>
> /etc/default/grub:
> ...
> # Append parameters to the linux kernel command line for non-recovery
> entries #GRUB_CMDLINE_LINUX_DEFAULT=""
>
> To install grub, I run:
> grub-install --target=x86_64-efi --efi-directory=/efi
>
> I think I install grub in a wrong way.
> When I mount "boot" content of /boot:
> ls /boot/
> EFI
>
> When I unmount "boot" content of /boot:
> ls /boot/
> System.map-6.1.57-gentoo config-6.1.57-gentoo grub vmlinuz-6.1.57-gentoo

Please read the first post of:

https://forums.gentoo.org/viewtopic-t-1165115.html

Kind regards,
Peter

Re: New installation - not booting [ In reply to ]

Dec 5, 2023, 10:11 AM

Post #4 of 17 (352 views)

On 12/5/23 10:16, Cara Salter wrote:
> On 12/5/23 12:05, thelma@sys-concept.com wrote:
>> It has been some time since I installed Gentoo.
>> After partitioning, and installing the system after reboot I get kernel selection from grub and hitting enter,
>> I don't see any text scrolling on the screen, and I don't see the login screen.
>
>> I think I install grub in a wrong way.
>> When I mount "boot" content of /boot:
>> ls /boot/
>> EFI
>
> Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint should be in /boot as is in your /etc/fstab.
>
>> When I unmount "boot" content of /boot:
>> ls /boot/
>> System.map-6.1.57-gentoo config-6.1.57-gentoo grub vmlinuz-6.1.57-gentoo

The /efi directory was empty
I moved /boot to /boot_backup crated /boot directory again
mount /dev/nvme0n1p1 /boot
run:
grub-install --target=x86_64-efi --efi-directory=/boot

installed kernel by running "make install" by default it install to boot ( I think).
Change fstab from /eft to /boot:
#/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
/dev/nvme0n1p1 /boot vfat noauto,noatime 1 2
but now when system boot it can not find any kernel, it just display "grub" command on the screen

Re: New installation - not booting [ In reply to ]

Dec 5, 2023, 10:13 AM

Post #5 of 17 (352 views)

On 12/5/23 11:11, thelma@sys-concept.com wrote:
> On 12/5/23 10:16, Cara Salter wrote:
>> On 12/5/23 12:05, thelma@sys-concept.com wrote:
>>> It has been some time since I installed Gentoo.
>>> After partitioning, and installing the system after reboot I get kernel selection from grub and hitting enter,
>>> I don't see any text scrolling on the screen, and I don't see the login screen.
>>
>>> I think I install grub in a wrong way.
>>> When I mount "boot" content of /boot:
>>> ls /boot/
>>> EFI
>>
>> Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint should be in /boot as is in your /etc/fstab.
>>
>>> When I unmount "boot" content of /boot:
>>> ls /boot/
>>> System.map-6.1.57-gentoo config-6.1.57-gentoo grub vmlinuz-6.1.57-gentoo
>
> The /efi directory was empty
> I moved /boot to /boot_backup crated /boot directory again
> mount /dev/nvme0n1p1 /boot
> run:
> grub-install --target=x86_64-efi --efi-directory=/boot
>
> installed kernel by running "make install" by default it install to boot ( I think).
> Change fstab from /eft to /boot:
> #/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
> /dev/nvme0n1p1 /boot vfat noauto,noatime 1 2
> but now when system boot it can not find any kernel, it just display "grub" command on the screen

When I boot strap the system I tried to run:

grub-install --target=x86_64-efi --efi-directory=/efi
Installing for x86_64-efi platform.
grub-install: error: /efi doesn't look like an EFI partition.

Re: New installation - not booting [ In reply to ]

Dec 5, 2023, 11:35 AM

Post #6 of 17 (349 views)

On Tuesday, 5 December 2023 18:11:14 GMT thelma@sys-concept.com wrote:
> On 12/5/23 10:16, Cara Salter wrote:
> > On 12/5/23 12:05, thelma@sys-concept.com wrote:
> >> It has been some time since I installed Gentoo.
> >> After partitioning, and installing the system after reboot I get kernel
> >> selection from grub and hitting enter, I don't see any text scrolling on
> >> the screen, and I don't see the login screen.
> >>
> >> I think I install grub in a wrong way.
> >> When I mount "boot" content of /boot:
> >> ls /boot/
> >> EFI
> >
> > Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint
> > should be in /boot as is in your /etc/fstab.>
> >> When I unmount "boot" content of /boot:
> >> ls /boot/
> >> System.map-6.1.57-gentoo config-6.1.57-gentoo grub
> >> vmlinuz-6.1.57-gentoo
>
> The /efi directory was empty
> I moved /boot to /boot_backup crated /boot directory again
> mount /dev/nvme0n1p1 /boot
> run:
> grub-install --target=x86_64-efi --efi-directory=/boot
>
> installed kernel by running "make install" by default it install to boot ( I
> think). Change fstab from /eft to /boot:
> #/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
> /dev/nvme0n1p1 /boot vfat noauto,noatime 1 2
> but now when system boot it can not find any kernel, it just display "grub"
> command on the screen

Please read the necessary documentation:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader

Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You must
create this partition with the appropriate EFI System type (in gdisk use
EF00).

The /efi directory must be at the top of the /boot partition filesystem,
accessible via /boot/efi.

Re: New installation - not booting [ In reply to ]

Dec 5, 2023, 12:07 PM

Post #7 of 17 (349 views)

On 12/5/23 12:35, Michael wrote:
> On Tuesday, 5 December 2023 18:11:14 GMT thelma@sys-concept.com wrote:
>> On 12/5/23 10:16, Cara Salter wrote:
>>> On 12/5/23 12:05, thelma@sys-concept.com wrote:
>>>> It has been some time since I installed Gentoo.
>>>> After partitioning, and installing the system after reboot I get kernel
>>>> selection from grub and hitting enter, I don't see any text scrolling on
>>>> the screen, and I don't see the login screen.
>>>>
>>>> I think I install grub in a wrong way.
>>>> When I mount "boot" content of /boot:
>>>> ls /boot/
>>>> EFI
>>>
>>> Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint
>>> should be in /boot as is in your /etc/fstab.>
>>>> When I unmount "boot" content of /boot:
>>>> ls /boot/
>>>> System.map-6.1.57-gentoo config-6.1.57-gentoo grub
>>>> vmlinuz-6.1.57-gentoo
>>
>> The /efi directory was empty
>> I moved /boot to /boot_backup crated /boot directory again
>> mount /dev/nvme0n1p1 /boot
>> run:
>> grub-install --target=x86_64-efi --efi-directory=/boot
>>
>> installed kernel by running "make install" by default it install to boot ( I
>> think). Change fstab from /eft to /boot:
>> #/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
>> /dev/nvme0n1p1 /boot vfat noauto,noatime 1 2
>> but now when system boot it can not find any kernel, it just display "grub"
>> command on the screen
>
> Please read the necessary documentation:
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
>
> Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You must
> create this partition with the appropriate EFI System type (in gdisk use
> EF00).
>
> The /efi directory must be at the top of the /boot partition filesystem,
> accessible via /boot/efi.

I'm kind of confused at this point.
Where the kernel files should be copied? /boot or /efi directory
- System.map-6.1.57-gentoo
- config-6.1.57-gentoo
- vmlinuz-6.1.57-gentoo

In fstab I have:
/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2

If /efi is a boot partition I assume the kernel files should be there as well; but somehow it doesn't work.

The link you provided instruct user to run:
grub-mkconfig -o /boot/grub/grub.cfg

When "/dev/nvme0n1p1 is mounted on /efi"
shouldn't it be:
grub-mkconfig -o /efi/grub/grub.cfg

Re: New installation - not booting [ In reply to ]

peter.bo at web

Dec 5, 2023, 12:53 PM

Post #8 of 17 (348 views)

Am Dienstag, 5. Dezember 2023, 20:35:11 CET schrieb Michael:
> On Tuesday, 5 December 2023 18:11:14 GMT thelma@sys-concept.com wrote:
> > On 12/5/23 10:16, Cara Salter wrote:
> > > On 12/5/23 12:05, thelma@sys-concept.com wrote:
> > >> It has been some time since I installed Gentoo.
> > >> After partitioning, and installing the system after reboot I get kernel
> > >> selection from grub and hitting enter, I don't see any text scrolling
> > >> on
> > >> the screen, and I don't see the login screen.
> > >>
> > >> I think I install grub in a wrong way.
> > >> When I mount "boot" content of /boot:
> > >> ls /boot/
> > >> EFI
> > >
> > > Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint
> > > should be in /boot as is in your /etc/fstab.>
> > >
> > >> When I unmount "boot" content of /boot:
> > >> ls /boot/
> > >> System.map-6.1.57-gentoo config-6.1.57-gentoo grub
> > >> vmlinuz-6.1.57-gentoo
> >
> > The /efi directory was empty
> > I moved /boot to /boot_backup crated /boot directory again
> > mount /dev/nvme0n1p1 /boot
> > run:
> > grub-install --target=x86_64-efi --efi-directory=/boot
> >
> > installed kernel by running "make install" by default it install to boot (
> > I think). Change fstab from /eft to /boot:
> > #/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
> > /dev/nvme0n1p1 /boot vfat noauto,noatime 1 2
> > but now when system boot it can not find any kernel, it just display
> > "grub"
> > command on the screen
>
> Please read the necessary documentation:
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
>
> Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You must
> create this partition with the appropriate EFI System type (in gdisk use
> EF00).
>
> The /efi directory must be at the top of the /boot partition filesystem,
> accessible via /boot/efi.

That is wrong.

The mountpoint for the ESP should be NOW /efi (therefore you see in our AMD64
handbook a "mkdir /efi").

/boot is the standard directory for the kernel ... and it is NOW an ordinary
directory of the root directory (so yes, the content of it resides in the root
partition). Dont mount anything to /boot. Yes, a "make install" (or genkernel)
installs the kernel into /boot.

If /etc/fstab should be: /dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
(IF this is your ESP)
After mounting this ESP to /efi (and no mount on /boot + kernel IN boot) you
should run: grub-install --target=x86_64-efi --efi-directory=/efi
AND a grub-mkconfig ! (so this routine will find your kernel in /boot and add
it to the grub's config file; Yes your grub will be also in /boot/grub.

Re: New installation - not booting [ In reply to ]

peter.bo at web

Dec 5, 2023, 1:00 PM

Post #9 of 17 (348 views)

Am Dienstag, 5. Dezember 2023, 21:07:00 CET schrieb thelma@sys-concept.com:
> On 12/5/23 12:35, Michael wrote:
> > On Tuesday, 5 December 2023 18:11:14 GMT thelma@sys-concept.com wrote:
> >> On 12/5/23 10:16, Cara Salter wrote:
> >>> On 12/5/23 12:05, thelma@sys-concept.com wrote:
> >>>> It has been some time since I installed Gentoo.
> >>>> After partitioning, and installing the system after reboot I get kernel
> >>>> selection from grub and hitting enter, I don't see any text scrolling
> >>>> on
> >>>> the screen, and I don't see the login screen.
> >>>>
> >>>> I think I install grub in a wrong way.
> >>>> When I mount "boot" content of /boot:
> >>>> ls /boot/
> >>>> EFI
> >>>
> >>> Is your EFI directory /efi or /boot? If it's /efi, then your mountpoint
> >>> should be in /boot as is in your /etc/fstab.>
> >>>
> >>>> When I unmount "boot" content of /boot:
> >>>> ls /boot/
> >>>> System.map-6.1.57-gentoo config-6.1.57-gentoo grub
> >>>> vmlinuz-6.1.57-gentoo
> >>
> >> The /efi directory was empty
> >> I moved /boot to /boot_backup crated /boot directory again
> >> mount /dev/nvme0n1p1 /boot
> >> run:
> >> grub-install --target=x86_64-efi --efi-directory=/boot
> >>
> >> installed kernel by running "make install" by default it install to boot
> >> ( I think). Change fstab from /eft to /boot:
> >> #/dev/nvme0n1p1 /efi vfat noauto,noatime 1 2
> >> /dev/nvme0n1p1 /boot vfat noauto,noatime 1 2
> >> but now when system boot it can not find any kernel, it just display
> >> "grub"
> >> command on the screen
> >
> > Please read the necessary documentation:
> >
> > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
> >
> > Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You
> > must create this partition with the appropriate EFI System type (in gdisk
> > use EF00).
> >
> > The /efi directory must be at the top of the /boot partition filesystem,
> > accessible via /boot/efi.
>
> I'm kind of confused at this point.
> Where the kernel files should be copied? /boot or /efi directory
> - System.map-6.1.57-gentoo
> - config-6.1.57-gentoo
> - vmlinuz-6.1.57-gentoo
>
> In fstab I have:
> /dev/nvme0n1p1 /efi vfat noauto,noatime
1 2
>
> If /efi is a boot partition I assume the kernel files should be there as
> well; but somehow it doesn't work.
>
> The link you provided instruct user to run:
> grub-mkconfig -o /boot/grub/grub.cfg
>
> When "/dev/nvme0n1p1 is mounted on /efi"
> shouldn't it be:
> grub-mkconfig -o /efi/grub/grub.cfg

No ... anything is alright here:

With grub-install --target=x86_64-efi --efi-directory=/efi you will installe the
first part of grub (grubx64.efi) INTO the ESP:
\efi\gentoo\grubx64.efi
<==>
/efi/efi/gentoo/grubx64.efi when you have mounted your ESP to /efi.
(see more with "efibootmgr)

With grub-mkconfig -o /boot/grub/grub.cfg you configure grub - residing IN /
boot/grub = THIS is the second part of grub !!

Maybe read:
https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/
Boot_kernel_via_UEFI#Prerequisites_for_an_UEFI_boot

(only this chapter; not the next chapter, because it is a guide for installing
a stub kernel)

Re: New installation - not booting [ In reply to ]

peter at prh

Dec 5, 2023, 3:53 PM

Post #10 of 17 (345 views)

On Tuesday, 5 December 2023 19:35:11 GMT Michael wrote:

> Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You must
> create this partition with the appropriate EFI System type (in gdisk use
> EF00).
>
> The /efi directory must be at the top of the /boot partition filesystem,
> accessible via /boot/efi.

I've been operating that way for some years, but I have reason to believe that
things have changed. I'll start a new thread tomorrow.

--
Regards,
Peter.

Re: New installation - not booting [ In reply to ]

Dec 6, 2023, 3:31 AM

Post #11 of 17 (344 views)

On Tuesday, 5 December 2023 23:53:23 GMT Peter Humphreey wrote:
> On Tuesday, 5 December 2023 19:35:11 GMT Michael wrote:
> > Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You
> > must create this partition with the appropriate EFI System type (in gdisk
> > use EF00).
> >
> > The /efi directory must be at the top of the /boot partition filesystem,
> > accessible via /boot/efi.
>
> I've been operating that way for some years, but I have reason to believe
> that things have changed. I'll start a new thread tomorrow.

Both Peters are right and my previous answer was wrong for Thelma's usecase,
the /boot directory must be on a linux fs which understands symlinks *if
vmlinuz is used* - this is because the ESP partition's FAT fs cannot use
symlinks.

The /efi directory *must* be on a FAT fs and contain the grubx64.efi, or any
other bootloader *.efi image.

If kernels are copied manually and vmlinuz symlinks are not used then a FAT
partition with mountpoint on /boot and containing the /boot/efi directory will
work as intended.

Re: New installation - not booting [ In reply to ]

Dec 6, 2023, 6:27 AM

Post #12 of 17 (343 views)

On 12/6/23 04:31, Michael wrote:
> On Tuesday, 5 December 2023 23:53:23 GMT Peter Humphreey wrote:
>> On Tuesday, 5 December 2023 19:35:11 GMT Michael wrote:
>>> Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You
>>> must create this partition with the appropriate EFI System type (in gdisk
>>> use EF00).
>>>
>>> The /efi directory must be at the top of the /boot partition filesystem,
>>> accessible via /boot/efi.
>>
>> I've been operating that way for some years, but I have reason to believe
>> that things have changed. I'll start a new thread tomorrow.
>
> Both Peters are right and my previous answer was wrong for Thelma's usecase,
> the /boot directory must be on a linux fs which understands symlinks *if
> vmlinuz is used* - this is because the ESP partition's FAT fs cannot use
> symlinks.
>
> The /efi directory *must* be on a FAT fs and contain the grubx64.efi, or any
> other bootloader *.efi image.
>
> If kernels are copied manually and vmlinuz symlinks are not used then a FAT
> partition with mountpoint on /boot and containing the /boot/efi directory will
> work as intended.

Thanks for Peters explanation now it is clear to me how it works.
But I have a question, in Gentoo manual hand book
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks
the instruction is to create 1 GiB partition for /efi

Why so large, do others file system need it so much?
In my case /efi take only 1%
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 1022M 280K 1022M 1% /efi

Re: New installation - not booting [ In reply to ]

peter at prh

Dec 6, 2023, 6:56 AM

Post #13 of 17 (343 views)

On Wednesday, 6 December 2023 14:27:21 GMT thelma@sys-concept.com wrote:
> On 12/6/23 04:31, Michael wrote:
> > On Tuesday, 5 December 2023 23:53:23 GMT Peter Humphreey wrote:
> >> On Tuesday, 5 December 2023 19:35:11 GMT Michael wrote:
> >>> Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You
> >>> must create this partition with the appropriate EFI System type (in
> >>> gdisk
> >>> use EF00).
> >>>
> >>> The /efi directory must be at the top of the /boot partition filesystem,
> >>> accessible via /boot/efi.
> >>
> >> I've been operating that way for some years, but I have reason to believe
> >> that things have changed. I'll start a new thread tomorrow.
> >
> > Both Peters are right and my previous answer was wrong for Thelma's
> > usecase, the /boot directory must be on a linux fs which understands
> > symlinks *if vmlinuz is used* - this is because the ESP partition's FAT
> > fs cannot use symlinks.
> >
> > The /efi directory *must* be on a FAT fs and contain the grubx64.efi, or
> > any other bootloader *.efi image.
> >
> > If kernels are copied manually and vmlinuz symlinks are not used then a
> > FAT
> > partition with mountpoint on /boot and containing the /boot/efi directory
> > will work as intended.
>
> Thanks for Peters explanation now it is clear to me how it works.

I think there's some misattribution here: I haven't explained anything in this
area - indeed I have some questions of my own.

> But I have a question, in Gentoo manual hand book
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks
> the instruction is to create 1 GiB partition for /efi

It's a suggestion, not an instruction; you don't have to follow it.

> Why so large, do others file system need it so much?
> In my case /efi take only 1%
> Filesystem Size Used Avail Use% Mounted on
> /dev/nvme0n1p1 1022M 280K 1022M 1% /efi

The idea is that you may want to install another system later, which may want
to install its own code in /efi. By all means shrink it if you think that's
unlikely and you need the space. Gparted on SysRescCD is ideal for this.

--
Regards,
Peter.

Re: New installation - not booting [ In reply to ]

antlists at youngman

Dec 6, 2023, 10:47 AM

Post #14 of 17 (343 views)

On 06/12/2023 14:56, Peter Humphreey wrote:
> The idea is that you may want to install another system later, which may want
> to install its own code in /efi. By all means shrink it if you think that's
> unlikely and you need the space. Gparted on SysRescCD is ideal for this.

I had the opposite problem - Windows created a tiny EFI partition and I
couldn't install linux ...

Cheers,
Wol

Re: New installation - not booting [ In reply to ]

peter at prh

Dec 7, 2023, 3:45 AM

Post #15 of 17 (343 views)

Re: New installation - not booting [ In reply to ]

Dec 7, 2023, 3:58 AM

Post #16 of 17 (343 views)

On Thursday, 7 December 2023 11:45:20 GMT Peter Humphrey wrote:
> On Wednesday, 6 December 2023 18:47:43 GMT Wols Lists wrote:
> > On 06/12/2023 14:56, Peter Humphreey wrote:
> > > The idea is that you may want to install another system later, which may
> > > want to install its own code in /efi. By all means shrink it if you
> > > think
> > > that's unlikely and you need the space. Gparted on SysRescCD is ideal
> > > for
> > > this.
> >
> > I had the opposite problem - Windows created a tiny EFI partition and I
> > couldn't install linux ...
>
> ...and you couldn't enlarge the partition because Windows then wouldn't
> boot!

You can enlarge and even move a Windows partition (boot system partition and/
or the main Windows OS C:\ drive partition), but you MUST either not change
the partition UUID or edit the BCD file with the new UUID numbers. Also, it
would be a good idea not to interfere with the MSR partition. Its been quite
a few years since I had to mess up with any of this so I'm not up to date with
the latest MSWindows boot requirements.

Re: New installation - not booting [ In reply to ]

Dec 7, 2023, 4:23 AM

Post #17 of 17 (342 views)