Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
error when booting Gentoo
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Tue Apr 18, 2023 7:15 pm    Post subject: Reply with quote

Angie_4444,

You can build the kernel if you chroot from some other linux.
USB tethering needs kernel support too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Tue Apr 18, 2023 7:55 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

You can build the kernel if you chroot from some other linux.
USB tethering needs kernel support too.


I know that. However, maybe I am missing a point, but I was advised to solve the problem in gentoo itself. https://forums.gentoo.org/viewtopic-t-1162897.html
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Tue Apr 18, 2023 8:16 pm    Post subject: Reply with quote

Angie_4444,

The steps to solve the original problem are to use EOS, if you have that handy, to fix your Gentoo.

Chroot into your Gentoo,
Code:
emerge genkernel
if you don't have it. Then
Code:
genkernel --all

Will build you a working gentoo kernel and initrd. They are matched pair.
Set up your bootloader to use that pair when you choose Gentoo from the boot loader menu.

Its OK to use the same /boot and /boot/EFI for all of your operating systems.
The alternatives will drive you insane.

Do not share any other code (beyond the boot loader) or horrible things can happen.

Once you can use that kernel and initrd to boot Gentoo, we can add in nvidia-drivers, wifi and anything else.
Build on what you know works. Then when (not if) it breaks, there is only a small problem space to search.
Keeping the potential problem space small makes for faster problem solving.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Thu Apr 20, 2023 11:56 am    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

The steps to solve the original problem are to use EOS, if you have that handy, to fix your Gentoo.

Chroot into your Gentoo,
Code:
emerge genkernel
if you don't have it. Then
Code:
genkernel --all

Will build you a working gentoo kernel and initrd. They are matched pair.
Set up your bootloader to use that pair when you choose Gentoo from the boot loader menu.

Its OK to use the same /boot and /boot/EFI for all of your operating systems.
The alternatives will drive you insane.

Do not share any other code (beyond the boot loader) or horrible things can happen.

Once you can use that kernel and initrd to boot Gentoo, we can add in nvidia-drivers, wifi and anything else.
Build on what you know works. Then when (not if) it breaks, there is only a small problem space to search.
Keeping the potential problem space small makes for faster problem solving.


I already had a problem with the first part. I emerged genkernel and it seemed to go alright. However, when I run genkernel all, I get this error:
Code:
 ERROR: compile_generic() failed to compile the "prepare" target!

One old thread suggested disabling the 64-bit kernel option, but it obviously didn't work.
Should I consider trying to re-install the system?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Thu Apr 20, 2023 5:53 pm    Post subject: Reply with quote

Angie_4444,

Code:
ERROR: compile_generic() failed to compile the "prepare" target!


That's the very first thing it does.

What is the output of
Code:
ls -l /usr/src

genkernel expect to find a symbolic link /usr/src/inux the points to a kernel source tree to be worked with..

Do you have both of those?

Reinstalling Gentoo only gives you opportunities to make more errors.
We need to understand the cause oy your problem an fix it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Thu Apr 20, 2023 7:38 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

Code:
ERROR: compile_generic() failed to compile the "prepare" target!


That's the very first thing it does.

What is the output of
Code:
ls -l /usr/src

genkernel expect to find a symbolic link /usr/src/inux the points to a kernel source tree to be worked with..

Do you have both of those?

Reinstalling Gentoo only gives you opportunities to make more errors.
We need to understand the cause oy your problem an fix it.


I see. I haven't found much information about it though. The output is:
Code:

total 12
drwxr-xr-x 12 root root 4096 Apr 14 07:25 initramfs
lrwxrwxrwx  1 root root   24 Apr 13 11:10 linux -> linux-6.1.22-gentoo-dist
drwxr-xr-x 27 root root 4096 Apr 13 11:03 linux-6.1.19-gentoo
drwxr-xr-x 26 root root 4096 Apr 20 11:41 linux-6.1.22-gentoo-dist


What I meant was that I wanted to format the partition and re-doing the entire installation.
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 21706

PostPosted: Thu Apr 20, 2023 8:22 pm    Post subject: Reply with quote

If you really want to throw it all away and start from the beginning, we cannot stop you - but as Neddy said, in almost all cases, that just gives you a chance to make a different mistake, and not to learn from the current problem. Therefore, we generally discourage wiping the system. One exception is if the system is so thoroughly broken that you are likely to replace it faster than you can repair it, and you cannot spare the time required for a repair. I am not convinced that your current problem is in that category, so my advice would be to continue working with Neddy to repair in place.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Thu Apr 20, 2023 8:35 pm    Post subject: Reply with quote

Hu wrote:
If you really want to throw it all away and start from the beginning, we cannot stop you - but as Neddy said, in almost all cases, that just gives you a chance to make a different mistake, and not to learn from the current problem. Therefore, we generally discourage wiping the system. One exception is if the system is so thoroughly broken that you are likely to replace it faster than you can repair it, and you cannot spare the time required for a repair. I am not convinced that your current problem is in that category, so my advice would be to continue working with Neddy to repair in place.

Thanks for saying that. It's not my first time installing Gentoo but it's definitely the first time I am trying to stick to it and make it work. I agree on the fact that this is a great opportunity to learn and to fix the system. I am indeed down to work on it and get better with Gentoo. Thanks for the answer.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Thu Apr 20, 2023 8:42 pm    Post subject: Reply with quote

Angie_4444,

I don't know what linux-6.1.22-gentoo-dist is so lets not use that,

Use eselect kernel to choose linux-6.1.19-gentoo as the kernel to build. Thats the well known gentoo-sources.
Its 6.1.19, so its a bug fix or two behind. That won't matter.

When all is well the symlink will show
Code:
lrwxrwxrwx  1 root root   24 <Date> linux -> linux-6.1.19-gentoo

Check that after the eselect kernel step.

When thats right, run
Code:
genkernel --all


-- edit --

Gentoo is not at all like a bathroom made by Apple.
With an Apple bathroom, you need a tap washer but Apple will only sell you a whole bathroom.

If you need a Gentoo tapwasher, we need to know the size of the tap and we can help fit it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Fri Apr 21, 2023 8:03 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

I don't know what linux-6.1.22-gentoo-dist is so lets not use that,

Use eselect kernel to choose linux-6.1.19-gentoo as the kernel to build. Thats the well known gentoo-sources.
Its 6.1.19, so its a bug fix or two behind. That won't matter.

When all is well the symlink will show
Code:
lrwxrwxrwx  1 root root   24 <Date> linux -> linux-6.1.19-gentoo

Check that after the eselect kernel step.

When thats right, run
Code:
genkernel --all


-- edit --

Gentoo is not at all like a bathroom made by Apple.
With an Apple bathroom, you need a tap washer but Apple will only sell you a whole bathroom.

If you need a Gentoo tapwasher, we need to know the size of the tap and we can help fit it.


Ok, I selected the linux-6.1.19-gentoo kernel and successfully ran genkernel. At the boot screen. under Advanced options for linux, I can select the linux-6.1.19-gentoo kernel. But it ends up in a kernel panic. I remember you told me about a system break, so I didn't investigate much further. The only thing advised after the genkernel compilation was to specify the root partition, but everything seemed ok to me.

Also, thanks for the analogy, I knew that, but still I could understand a lot
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Fri Apr 21, 2023 8:40 pm    Post subject: Reply with quote

Angie_4444,

You should not have got a panic like that.
Code:
genkernel  -all
builds you a matched kernel and initrd.
You should see both' in /boot with a timestamp shoving the build date/time.
It sounds like the initrd did not load. Had it done so, the problem would have dropped you to shell.

So three questions ...
What was the text of the message?
Tried to kill init!
unknown-block(x,y) ... what are the numbers x and y.

Does your grub.cfg try to load the initrd?

Did you rerun
Code:
grub-mkconfig -o /boot/grub/grub.cfg
to update grub.cfg?
See the /Handbook:
Notice that it says ...
Found linux image:
Found initrd image:

You need both lines for your 6.1.19 kernel and initrd set.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Fri Apr 21, 2023 9:35 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

You should not have got a panic like that.
Code:
genkernel  -all
builds you a matched kernel and initrd.
You should see both' in /boot with a timestamp shoving the build date/time.
It sounds like the initrd did not load. Had it done so, the problem would have dropped you to shell.

So three questions ...
What was the text of the message?
Tried to kill init!
unknown-block(x,y) ... what are the numbers x and y.

Does your grub.cfg try to load the initrd?

Did you rerun
Code:
grub-mkconfig -o /boot/grub/grub.cfg
to update grub.cfg?
See the /Handbook:
Notice that it says ...
Found linux image:
Found initrd image:

You need both lines for your 6.1.19 kernel and initrd set.


I noticed few things are going wrong.

In the /boot folder there are only: custom-initramfs.cpio.gz and the grub folder.

The text is:
Code:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I can provide a pic, if more details are needed.

Yes, I did update grub, but it never said Found linux image: or Found initrd image: .
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sat Apr 22, 2023 2:58 pm    Post subject: Reply with quote

Angie_4444,

Your kernel and initrd should be installed in /boot.

Code:
grub-mkconfig -o /boot/grub/grub.cfg
looks in /boot and builds a grub.cfg with whatever it finds there.
If it didn't find anything, the lines
Code:
Found linux image:
Found initrd image:
will be absent, so that there is nothing to boot, with grub anyway.
That makes me want to ask how are you able to load a kernel to get a kernel panic.
Code:
unknown-block(0,0)
means that the kernel can't find any block devices ta talk to.

Can you post or pastebin
Code:
ls -lR /boot
please thats your boot as it appears in the chroot?
We need to undestand why your new kernel and initrd are not in /boot and where the kernel is that in actually being booted.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Sat Apr 22, 2023 3:43 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

Your kernel and initrd should be installed in /boot.

Code:
grub-mkconfig -o /boot/grub/grub.cfg
looks in /boot and builds a grub.cfg with whatever it finds there.
If it didn't find anything, the lines
Code:
Found linux image:
Found initrd image:
will be absent, so that there is nothing to boot, with grub anyway.
That makes me want to ask how are you able to load a kernel to get a kernel panic.
Code:
unknown-block(0,0)
means that the kernel can't find any block devices ta talk to.

Can you post or pastebin
Code:
ls -lR /boot
please thats your boot as it appears in the chroot?
We need to undestand why your new kernel and initrd are not in /boot and where the kernel is that in actually being booted.


I am then a little confused on why Grub even shows the several kernel options then.
Anyway, the output is:

Code:
ls -lR /boot
/boot:
total 8
-rw-r--r-- 1 root root  537 Apr 14 07:33 custom-initramfs.cpio.gz
drwxr-xr-x 2 root root 4096 Apr 22 15:40 grub

/boot/grub:
total 4
-rw------- 1 root root 2353 Apr 21 20:52 grub.cfg
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sat Apr 22, 2023 5:00 pm    Post subject: Reply with quote

Angie_4444,

The /boot/grub director should have lots of files for grub. There is no /boot/EFI either.

You have another /boot with an EFI somewhere that is being used, not your Gentoo /boot.
Mount your Gentoo. like you were going to chroot but do not do the chroot.
Run
Code:
df -hT
at that point and post the output.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Sat Apr 22, 2023 5:33 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

The /boot/grub director should have lots of files for grub. There is no /boot/EFI either.

You have another /boot with an EFI somewhere that is being used, not your Gentoo /boot.
Mount your Gentoo. like you were going to chroot but do not do the chroot.
Run
Code:
df -hT
at that point and post the output.


The grub part was indeed the one that caused me more difficulties while installing Gentoo. I thought it had worked though.

This is the output I got:

Code:
File system    Tipo      Dim. Usati Dispon. Uso% Montato su
devtmpfs       devtmpfs  4,0M     0    4,0M   0% /dev
tmpfs          tmpfs     7,8G  1,3M    7,8G   1% /dev/shm
tmpfs          tmpfs     3,1G  1,6M    3,1G   1% /run
/dev/nvme0n1p2 ext4      267G   79G    175G  31% /
/dev/loop0     squashfs  128K  128K       0 100% /var/lib/snapd/snap/bare/5
/dev/loop4     squashfs  3,4M  3,4M       0 100% /var/lib/snapd/snap/melonds/10
/dev/loop1     squashfs   64M   64M       0 100% /var/lib/snapd/snap/core20/1828
/dev/loop5     squashfs   57M   57M       0 100% /var/lib/snapd/snap/nightmayr-plasma-integration-5-2004/9
/dev/loop2     squashfs   64M   64M       0 100% /var/lib/snapd/snap/core20/1852
/dev/loop6     squashfs  768K  768K       0 100% /var/lib/snapd/snap/nightmayr-qgnomeplatform-qt5-2004/5
/dev/loop3     squashfs   92M   92M       0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop7     squashfs  356M  356M       0 100% /var/lib/snapd/snap/nightmayr-qt-5-15-4-2004/33
/dev/loop8     squashfs   50M   50M       0 100% /var/lib/snapd/snap/snapd/18357
/dev/loop9     squashfs   50M   50M       0 100% /var/lib/snapd/snap/snapd/18596
tmpfs          tmpfs     7,8G  9,4M    7,8G   1% /tmp
/dev/nvme0n1p1 vfat      999M  195M    804M  20% /efi
tmpfs          tmpfs     1,6G   80K    1,6G   1% /run/user/1000
/dev/nvme0n1p4 ext4      192G   13G    170G   7% /mnt/gentoo
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sat Apr 22, 2023 5:36 pm    Post subject: Reply with quote

Angie_4444,

What does
Code:
ls -lR /EFI
tell?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Sat Apr 22, 2023 5:56 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

What does
Code:
ls -lR /EFI
tell?


It says that it doesn't exist...
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sat Apr 22, 2023 6:15 pm    Post subject: Reply with quote

Angie_4444,

Oops. Its lower case efi ...
Code:
/dev/nvme0n1p1 vfat      999M  195M    804M  20% /efi

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Sat Apr 22, 2023 7:07 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

Oops. Its lower case efi ...
Code:
/dev/nvme0n1p1 vfat      999M  195M    804M  20% /efi


Yeah I am sorry, I should have guessed.
Code:

/efi:
totale 90580
drwxr-xr-x 3 root root     4096 13 apr 08.36 29eda348395345d9a0fd4c53d3d79880
-rwxr-xr-x 1 root root   249344  3 apr 23.40 config-6.1.22-gentoo-dist
drwxr-xr-x 6 root root     4096  2 apr 19.49 EFI
drwxr-xr-x 6 root root     4096 21 apr 16.49 grub
-rwxr-xr-x 1 root root 11032308 21 apr 16.48 initramfs-6.1.19-gentoo-x86_64.img
-rwxr-xr-x 1 root root 11022064 21 apr 13.24 initramfs-6.1.19-gentoo-x86_64.img.old
-rwxr-xr-x 1 root root 23768792  3 apr 23.40 initramfs-6.1.22-gentoo-dist.img
drwxr-xr-x 3 root root     4096 21 apr 23.25 loader
-rwxr-xr-x 1 root root  4043051 21 apr 16.26 System.map-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root  4043051 21 apr 15.44 System.map-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root  5829504  3 apr 23.40 System.map-6.1.22-gentoo-dist
-rwxr-xr-x 1 root root 10238368 21 apr 16.26 vmlinuz-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root 10238368 21 apr 15.44 vmlinuz-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root 12251808  3 apr 23.40 vmlinuz-6.1.22-gentoo-dist

/efi/29eda348395345d9a0fd4c53d3d79880:
totale 4
drwxr-xr-x 2 root root 4096 13 apr 08.36 6.2.10-arch1-1

/efi/29eda348395345d9a0fd4c53d3d79880/6.2.10-arch1-1:
totale 95400
-rwxr-xr-x 1 root root 25588895 13 apr 08.36 initrd
-rwxr-xr-x 1 root root 59595015 13 apr 08.36 initrd-fallback
-rwxr-xr-x 1 root root 12500160 13 apr 08.36 linux

/efi/EFI:
totale 16
drwxr-xr-x 2 root root 4096 31 mar 11.33 BOOT
drwxr-xr-x 2 root root 4096  2 apr 19.49 gentoo
drwxr-xr-x 2 root root 4096 15 feb 16.47 Linux
drwxr-xr-x 2 root root 4096 13 apr 08.36 systemd

/efi/EFI/BOOT:
totale 132
-rwxr-xr-x 1 root root 135168  2 apr 19.50 BOOTX64.EFI

/efi/EFI/gentoo:
totale 132
-rwxr-xr-x 1 root root 135168  4 apr 09.12 grubx64.efi

/efi/EFI/Linux:
totale 0

/efi/EFI/systemd:
totale 92
-rwxr-xr-x 1 root root 92160 10 apr 19.46 systemd-bootx64.efi

/efi/grub:
totale 68
drwxr-xr-x 2 root root  4096  2 apr 19.49 fonts
-rwxr-xr-x 1 root root  5865 21 apr 16.49 grub.cfg
-rwxr-xr-x 1 root root  1024  2 apr 19.49 grubenv
drwxr-xr-x 2 root root  8192  4 apr 09.12 locale
drwxr-xr-x 3 root root  4096  2 apr 19.49 themes
drwxr-xr-x 2 root root 40960  4 apr 09.12 x86_64-efi

/efi/grub/fonts:
totale 2340
-rwxr-xr-x 1 root root 2394618  4 apr 09.12 unicode.pf2

/efi/grub/locale:
totale 4636
-rwxr-xr-x 1 root root 128472  4 apr 09.12 ast.mo
-rwxr-xr-x 1 root root 128974  4 apr 09.12 ca.mo
-rwxr-xr-x 1 root root 120200  4 apr 09.12 da.mo
-rwxr-xr-x 1 root root  38902  4 apr 09.12 de_CH.mo
-rwxr-xr-x 1 root root 202735  4 apr 09.12 de@hebrew.mo
-rwxr-xr-x 1 root root 134690  4 apr 09.12 de.mo
-rwxr-xr-x 1 root root 168627  4 apr 09.12 en@arabic.mo
-rwxr-xr-x 1 root root 159227  4 apr 09.12 en@cyrillic.mo
-rwxr-xr-x 1 root root 159224  4 apr 09.12 en@greek.mo
-rwxr-xr-x 1 root root 182737  4 apr 09.12 en@hebrew.mo
-rwxr-xr-x 1 root root 140894  4 apr 09.12 en@piglatin.mo
-rwxr-xr-x 1 root root 124316  4 apr 09.12 en@quot.mo
-rwxr-xr-x 1 root root  43862  4 apr 09.12 eo.mo
-rwxr-xr-x 1 root root 131671  4 apr 09.12 es.mo
-rwxr-xr-x 1 root root 133874  4 apr 09.12 fi.mo
-rwxr-xr-x 1 root root 141758  4 apr 09.12 fr.mo
-rwxr-xr-x 1 root root 103937  4 apr 09.12 gl.mo
-rwxr-xr-x 1 root root 131597  4 apr 09.12 hr.mo
-rwxr-xr-x 1 root root 132613  4 apr 09.12 hu.mo
-rwxr-xr-x 1 root root  28647  4 apr 09.12 id.mo
-rwxr-xr-x 1 root root 118172  4 apr 09.12 it.mo
-rwxr-xr-x 1 root root  46005  4 apr 09.12 ja.mo
-rwxr-xr-x 1 root root  51360  4 apr 09.12 ko.mo
-rwxr-xr-x 1 root root   8417  4 apr 09.12 lg.mo
-rwxr-xr-x 1 root root 101913  4 apr 09.12 lt.mo
-rwxr-xr-x 1 root root 123256  4 apr 09.12 nb.mo
-rwxr-xr-x 1 root root 128251  4 apr 09.12 nl.mo
-rwxr-xr-x 1 root root  62029  4 apr 09.12 pa.mo
-rwxr-xr-x 1 root root 134665  4 apr 09.12 pl.mo
-rwxr-xr-x 1 root root  83737  4 apr 09.12 pt_BR.mo
-rwxr-xr-x 1 root root 133167  4 apr 09.12 pt.mo
-rwxr-xr-x 1 root root  48435  4 apr 09.12 ro.mo
-rwxr-xr-x 1 root root 172064  4 apr 09.12 ru.mo
-rwxr-xr-x 1 root root  94728  4 apr 09.12 sl.mo
-rwxr-xr-x 1 root root 170254  4 apr 09.12 sr.mo
-rwxr-xr-x 1 root root 128944  4 apr 09.12 sv.mo
-rwxr-xr-x 1 root root  84324  4 apr 09.12 tr.mo
-rwxr-xr-x 1 root root 179503  4 apr 09.12 uk.mo
-rwxr-xr-x 1 root root 137525  4 apr 09.12 vi.mo
-rwxr-xr-x 1 root root  87091  4 apr 09.12 zh_CN.mo
-rwxr-xr-x 1 root root  30762  4 apr 09.12 zh_TW.mo

/efi/grub/themes:
totale 4
drwxr-xr-x 2 root root 4096  2 apr 19.49 starfield

/efi/grub/themes/starfield:
totale 2868
-rwxr-xr-x 1 root root     836  4 apr 09.12 blob_w.png
-rwxr-xr-x 1 root root     178  4 apr 09.12 boot_menu_c.png
-rwxr-xr-x 1 root root     193  4 apr 09.12 boot_menu_e.png
-rwxr-xr-x 1 root root     193  4 apr 09.12 boot_menu_ne.png
-rwxr-xr-x 1 root root     103  4 apr 09.12 boot_menu_n.png
-rwxr-xr-x 1 root root     184  4 apr 09.12 boot_menu_nw.png
-rwxr-xr-x 1 root root     198  4 apr 09.12 boot_menu_se.png
-rwxr-xr-x 1 root root     102  4 apr 09.12 boot_menu_s.png
-rwxr-xr-x 1 root root     196  4 apr 09.12 boot_menu_sw.png
-rwxr-xr-x 1 root root      96  4 apr 09.12 boot_menu_w.png
-rwxr-xr-x 1 root root   19890  4 apr 09.12 COPYING.CC-BY-SA-3.0
-rwxr-xr-x 1 root root  153206  4 apr 09.12 dejavu_10.pf2
-rwxr-xr-x 1 root root  169029  4 apr 09.12 dejavu_12.pf2
-rwxr-xr-x 1 root root  185544  4 apr 09.12 dejavu_14.pf2
-rwxr-xr-x 1 root root  204012  4 apr 09.12 dejavu_16.pf2
-rwxr-xr-x 1 root root  193136  4 apr 09.12 dejavu_bold_14.pf2
-rwxr-xr-x 1 root root    1191  4 apr 09.12 README
-rwxr-xr-x 1 root root     197  4 apr 09.12 slider_c.png
-rwxr-xr-x 1 root root     265  4 apr 09.12 slider_n.png
-rwxr-xr-x 1 root root     269  4 apr 09.12 slider_s.png
-rwxr-xr-x 1 root root 1897028  4 apr 09.12 starfield.png
-rwxr-xr-x 1 root root     178  4 apr 09.12 terminal_box_c.png
-rwxr-xr-x 1 root root      94  4 apr 09.12 terminal_box_e.png
-rwxr-xr-x 1 root root     128  4 apr 09.12 terminal_box_ne.png
-rwxr-xr-x 1 root root     194  4 apr 09.12 terminal_box_n.png
-rwxr-xr-x 1 root root     210  4 apr 09.12 terminal_box_nw.png
-rwxr-xr-x 1 root root     126  4 apr 09.12 terminal_box_se.png
-rwxr-xr-x 1 root root     101  4 apr 09.12 terminal_box_s.png
-rwxr-xr-x 1 root root     123  4 apr 09.12 terminal_box_sw.png
-rwxr-xr-x 1 root root      97  4 apr 09.12 terminal_box_w.png
-rwxr-xr-x 1 root root    2249  4 apr 09.12 theme.txt

/efi/grub/x86_64-efi:
totale 3332
-rwxr-xr-x 1 root root  16016  4 apr 09.12 acpi.mod
-rwxr-xr-x 1 root root   1832  4 apr 09.12 adler32.mod
-rwxr-xr-x 1 root root   7832  4 apr 09.12 affs.mod
-rwxr-xr-x 1 root root   8328  4 apr 09.12 afs.mod
-rwxr-xr-x 1 root root   2024  4 apr 09.12 afsplitter.mod
-rwxr-xr-x 1 root root  21816  4 apr 09.12 ahci.mod
-rwxr-xr-x 1 root root    704  4 apr 09.12 all_video.mod
-rwxr-xr-x 1 root root   1368  4 apr 09.12 aout.mod
-rwxr-xr-x 1 root root   5128  4 apr 09.12 appleldr.mod
-rwxr-xr-x 1 root root   4368  4 apr 09.12 archelp.mod
-rwxr-xr-x 1 root root   8512  4 apr 09.12 ata.mod
-rwxr-xr-x 1 root root   6408  4 apr 09.12 at_keyboard.mod
-rwxr-xr-x 1 root root   2400  4 apr 09.12 backtrace.mod
-rwxr-xr-x 1 root root   9440  4 apr 09.12 bfs.mod
-rwxr-xr-x 1 root root   3064  4 apr 09.12 bitmap.mod
-rwxr-xr-x 1 root root   5248  4 apr 09.12 bitmap_scale.mod
-rwxr-xr-x 1 root root   2904  4 apr 09.12 blocklist.mod
-rwxr-xr-x 1 root root   3648  4 apr 09.12 boot.mod
-rwxr-xr-x 1 root root  48264  4 apr 09.12 bsd.mod
-rwxr-xr-x 1 root root   3080  4 apr 09.12 bswap_test.mod
-rwxr-xr-x 1 root root  26992  4 apr 09.12 btrfs.mod
-rwxr-xr-x 1 root root   2744  4 apr 09.12 bufio.mod
-rwxr-xr-x 1 root root   4248  4 apr 09.12 cat.mod
-rwxr-xr-x 1 root root   5640  4 apr 09.12 cbfs.mod
-rwxr-xr-x 1 root root   5552  4 apr 09.12 cbls.mod
-rwxr-xr-x 1 root root   3752  4 apr 09.12 cbmemc.mod
-rwxr-xr-x 1 root root   1504  4 apr 09.12 cbtable.mod
-rwxr-xr-x 1 root root   4384  4 apr 09.12 cbtime.mod
-rwxr-xr-x 1 root root   8728  4 apr 09.12 chain.mod
-rwxr-xr-x 1 root root   4496  4 apr 09.12 cmdline_cat_test.mod
-rwxr-xr-x 1 root root   2952  4 apr 09.12 cmp.mod
-rwxr-xr-x 1 root root   6232  4 apr 09.12 cmp_test.mod
-rwxr-xr-x 1 root root   3622  4 apr 09.12 command.lst
-rwxr-xr-x 1 root root   3160  4 apr 09.12 configfile.mod
-rwxr-xr-x 1 root root 135168  4 apr 09.12 core.efi
-rwxr-xr-x 1 root root   4256  4 apr 09.12 cpio_be.mod
-rwxr-xr-x 1 root root   4224  4 apr 09.12 cpio.mod
-rwxr-xr-x 1 root root   2480  4 apr 09.12 cpuid.mod
-rwxr-xr-x 1 root root   2032  4 apr 09.12 crc64.mod
-rwxr-xr-x 1 root root  18392  4 apr 09.12 cryptodisk.mod
-rwxr-xr-x 1 root root    936  4 apr 09.12 crypto.lst
-rwxr-xr-x 1 root root   6832  4 apr 09.12 crypto.mod
-rwxr-xr-x 1 root root   3848  4 apr 09.12 cs5536.mod
-rwxr-xr-x 1 root root   2528  4 apr 09.12 ctz_test.mod
-rwxr-xr-x 1 root root   2912  4 apr 09.12 datehook.mod
-rwxr-xr-x 1 root root   3104  4 apr 09.12 date.mod
-rwxr-xr-x 1 root root   2928  4 apr 09.12 datetime.mod
-rwxr-xr-x 1 root root  13168  4 apr 09.12 diskfilter.mod
-rwxr-xr-x 1 root root   2976  4 apr 09.12 disk.mod
-rwxr-xr-x 1 root root   1240  4 apr 09.12 div.mod
-rwxr-xr-x 1 root root   7808  4 apr 09.12 div_test.mod
-rwxr-xr-x 1 root root   2712  4 apr 09.12 dm_nv.mod
-rwxr-xr-x 1 root root   2912  4 apr 09.12 echo.mod
-rwxr-xr-x 1 root root   2040  4 apr 09.12 efifwsetup.mod
-rwxr-xr-x 1 root root  12640  4 apr 09.12 efi_gop.mod
-rwxr-xr-x 1 root root   6792  4 apr 09.12 efinet.mod
-rwxr-xr-x 1 root root   7032  4 apr 09.12 efi_uga.mod
-rwxr-xr-x 1 root root  24792  4 apr 09.12 ehci.mod
-rwxr-xr-x 1 root root   6144  4 apr 09.12 elf.mod
-rwxr-xr-x 1 root root   2088  4 apr 09.12 eval.mod
-rwxr-xr-x 1 root root   8560  4 apr 09.12 exfat.mod
-rwxr-xr-x 1 root root   2048  4 apr 09.12 exfctest.mod
-rwxr-xr-x 1 root root   8624  4 apr 09.12 ext2.mod
-rwxr-xr-x 1 root root   7512  4 apr 09.12 extcmd.mod
-rwxr-xr-x 1 root root   9808  4 apr 09.12 f2fs.mod
-rwxr-xr-x 1 root root   8688  4 apr 09.12 fat.mod
-rwxr-xr-x 1 root root  26488  4 apr 09.12 file.mod
-rwxr-xr-x 1 root root   2768  4 apr 09.12 fixvideo.mod
-rwxr-xr-x 1 root root  19112  4 apr 09.12 font.mod
-rwxr-xr-x 1 root root   4360  4 apr 09.12 fshelp.mod
-rwxr-xr-x 1 root root    219  4 apr 09.12 fs.lst
-rwxr-xr-x 1 root root  46464  4 apr 09.12 functional_test.mod
-rwxr-xr-x 1 root root   2280  4 apr 09.12 gcry_arcfour.mod
-rwxr-xr-x 1 root root   9264  4 apr 09.12 gcry_blowfish.mod
-rwxr-xr-x 1 root root  28176  4 apr 09.12 gcry_camellia.mod
-rwxr-xr-x 1 root root  14712  4 apr 09.12 gcry_cast5.mod
-rwxr-xr-x 1 root root  11744  4 apr 09.12 gcry_crc.mod
-rwxr-xr-x 1 root root  16320  4 apr 09.12 gcry_des.mod
-rwxr-xr-x 1 root root   3288  4 apr 09.12 gcry_dsa.mod
-rwxr-xr-x 1 root root   3928  4 apr 09.12 gcry_idea.mod
-rwxr-xr-x 1 root root   4008  4 apr 09.12 gcry_md4.mod
-rwxr-xr-x 1 root root   4464  4 apr 09.12 gcry_md5.mod
-rwxr-xr-x 1 root root   3000  4 apr 09.12 gcry_rfc2268.mod
-rwxr-xr-x 1 root root  20432  4 apr 09.12 gcry_rijndael.mod
-rwxr-xr-x 1 root root   7824  4 apr 09.12 gcry_rmd160.mod
-rwxr-xr-x 1 root root   3216  4 apr 09.12 gcry_rsa.mod
-rwxr-xr-x 1 root root  12504  4 apr 09.12 gcry_seed.mod
-rwxr-xr-x 1 root root  16344  4 apr 09.12 gcry_serpent.mod
-rwxr-xr-x 1 root root   8064  4 apr 09.12 gcry_sha1.mod
-rwxr-xr-x 1 root root   5104  4 apr 09.12 gcry_sha256.mod
-rwxr-xr-x 1 root root   5976  4 apr 09.12 gcry_sha512.mod
-rwxr-xr-x 1 root root  13152  4 apr 09.12 gcry_tiger.mod
-rwxr-xr-x 1 root root  33664  4 apr 09.12 gcry_twofish.mod
-rwxr-xr-x 1 root root  22784  4 apr 09.12 gcry_whirlpool.mod
-rwxr-xr-x 1 root root   9088  4 apr 09.12 geli.mod
-rwxr-xr-x 1 root root   8152  4 apr 09.12 gettext.mod
-rwxr-xr-x 1 root root  59224  4 apr 09.12 gfxmenu.mod
-rwxr-xr-x 1 root root   4304  4 apr 09.12 gfxterm_background.mod
-rwxr-xr-x 1 root root   7616  4 apr 09.12 gfxterm_menu.mod
-rwxr-xr-x 1 root root  16520  4 apr 09.12 gfxterm.mod
-rwxr-xr-x 1 root root   5232  4 apr 09.12 gptsync.mod
-rwxr-xr-x 1 root root 135168  4 apr 09.12 grub.efi
-rwxr-xr-x 1 root root  12360  4 apr 09.12 gzio.mod
-rwxr-xr-x 1 root root   7544  4 apr 09.12 halt.mod
-rwxr-xr-x 1 root root   8048  4 apr 09.12 hashsum.mod
-rwxr-xr-x 1 root root  10248  4 apr 09.12 hdparm.mod
-rwxr-xr-x 1 root root   1760  4 apr 09.12 hello.mod
-rwxr-xr-x 1 root root   3856  4 apr 09.12 help.mod
-rwxr-xr-x 1 root root   4392  4 apr 09.12 hexdump.mod
-rwxr-xr-x 1 root root  10136  4 apr 09.12 hfs.mod
-rwxr-xr-x 1 root root   4152  4 apr 09.12 hfspluscomp.mod
-rwxr-xr-x 1 root root  10912  4 apr 09.12 hfsplus.mod
-rwxr-xr-x 1 root root   8616  4 apr 09.12 http.mod
-rwxr-xr-x 1 root root   4240  4 apr 09.12 iorw.mod
-rwxr-xr-x 1 root root  12008  4 apr 09.12 iso9660.mod
-rwxr-xr-x 1 root root   8776  4 apr 09.12 jfs.mod
-rwxr-xr-x 1 root root  10392  4 apr 09.12 jpeg.mod
-rwxr-xr-x 1 root root   4760  4 apr 09.12 json.mod
-rwxr-xr-x 1 root root   6496  4 apr 09.12 keylayouts.mod
-rwxr-xr-x 1 root root   2872  4 apr 09.12 keystatus.mod
-rwxr-xr-x 1 root root   8000  4 apr 09.12 ldm.mod
-rwxr-xr-x 1 root root  45272  4 apr 09.12 legacycfg.mod
-rwxr-xr-x 1 root root  15816  4 apr 09.12 legacy_password_test.mod
-rwxr-xr-x 1 root root   8472  4 apr 09.12 linux16.mod
-rwxr-xr-x 1 root root  19136  4 apr 09.12 linux.mod
-rwxr-xr-x 1 root root   4528  4 apr 09.12 loadbios.mod
-rwxr-xr-x 1 root root   9000  4 apr 09.12 loadenv.mod
-rwxr-xr-x 1 root root   4688  4 apr 09.12 loopback.mod
-rwxr-xr-x 1 root root   7008  4 apr 09.12 lsacpi.mod
-rwxr-xr-x 1 root root   3568  4 apr 09.12 lsefimmap.mod
-rwxr-xr-x 1 root root   5152  4 apr 09.12 lsefi.mod
-rwxr-xr-x 1 root root   4304  4 apr 09.12 lsefisystab.mod
-rwxr-xr-x 1 root root   2832  4 apr 09.12 lsmmap.mod
-rwxr-xr-x 1 root root   6280  4 apr 09.12 ls.mod
-rwxr-xr-x 1 root root   7120  4 apr 09.12 lspci.mod
-rwxr-xr-x 1 root root   3704  4 apr 09.12 lssal.mod
-rwxr-xr-x 1 root root  20624  4 apr 09.12 luks2.mod
-rwxr-xr-x 1 root root   6424  4 apr 09.12 luks.mod
-rwxr-xr-x 1 root root  11776  4 apr 09.12 lvm.mod
-rwxr-xr-x 1 root root   6712  4 apr 09.12 lzopio.mod
-rwxr-xr-x 1 root root   4736  4 apr 09.12 macbless.mod
-rwxr-xr-x 1 root root  10624  4 apr 09.12 macho.mod
-rwxr-xr-x 1 root root   2712  4 apr 09.12 mdraid09_be.mod
-rwxr-xr-x 1 root root   2648  4 apr 09.12 mdraid09.mod
-rwxr-xr-x 1 root root   2560  4 apr 09.12 mdraid1x.mod
-rwxr-xr-x 1 root root   3032  4 apr 09.12 memdisk.mod
-rwxr-xr-x 1 root root   4200  4 apr 09.12 memrw.mod
-rwxr-xr-x 1 root root   5736  4 apr 09.12 minicmd.mod
-rwxr-xr-x 1 root root   5680  4 apr 09.12 minix2_be.mod
-rwxr-xr-x 1 root root   5576  4 apr 09.12 minix2.mod
-rwxr-xr-x 1 root root   5712  4 apr 09.12 minix3_be.mod
-rwxr-xr-x 1 root root   5608  4 apr 09.12 minix3.mod
-rwxr-xr-x 1 root root   5552  4 apr 09.12 minix_be.mod
-rwxr-xr-x 1 root root   5456  4 apr 09.12 minix.mod
-rwxr-xr-x 1 root root   9320  4 apr 09.12 mmap.mod
-rwxr-xr-x 1 root root   5216  4 apr 09.12 moddep.lst
-rwxr-xr-x 1 root root   2605  4 apr 09.12 modinfo.sh
-rwxr-xr-x 1 root root   3152  4 apr 09.12 morse.mod
-rwxr-xr-x 1 root root  43720  4 apr 09.12 mpi.mod
-rwxr-xr-x 1 root root   3592  4 apr 09.12 msdospart.mod
-rwxr-xr-x 1 root root   2312  4 apr 09.12 mul_test.mod
-rwxr-xr-x 1 root root  23672  4 apr 09.12 multiboot2.mod
-rwxr-xr-x 1 root root  20720  4 apr 09.12 multiboot.mod
-rwxr-xr-x 1 root root   6624  4 apr 09.12 nativedisk.mod
-rwxr-xr-x 1 root root  78784  4 apr 09.12 net.mod
-rwxr-xr-x 1 root root   4376  4 apr 09.12 newc.mod
-rwxr-xr-x 1 root root   9688  4 apr 09.12 nilfs2.mod
-rwxr-xr-x 1 root root 174352  4 apr 09.12 normal.mod
-rwxr-xr-x 1 root root   5536  4 apr 09.12 ntfscomp.mod
-rwxr-xr-x 1 root root  15048  4 apr 09.12 ntfs.mod
-rwxr-xr-x 1 root root   4224  4 apr 09.12 odc.mod
-rwxr-xr-x 1 root root   2128  4 apr 09.12 offsetio.mod
-rwxr-xr-x 1 root root  15344  4 apr 09.12 ohci.mod
-rwxr-xr-x 1 root root   2208  4 apr 09.12 part_acorn.mod
-rwxr-xr-x 1 root root   2520  4 apr 09.12 part_amiga.mod
-rwxr-xr-x 1 root root   2888  4 apr 09.12 part_apple.mod
-rwxr-xr-x 1 root root   4064  4 apr 09.12 part_bsd.mod
-rwxr-xr-x 1 root root   2568  4 apr 09.12 part_dfly.mod
-rwxr-xr-x 1 root root   2096  4 apr 09.12 part_dvh.mod
-rwxr-xr-x 1 root root   3152  4 apr 09.12 part_gpt.mod
-rwxr-xr-x 1 root root    111  4 apr 09.12 partmap.lst
-rwxr-xr-x 1 root root   2912  4 apr 09.12 part_msdos.mod
-rwxr-xr-x 1 root root   2416  4 apr 09.12 part_plan.mod
-rwxr-xr-x 1 root root   2160  4 apr 09.12 part_sun.mod
-rwxr-xr-x 1 root root   2416  4 apr 09.12 part_sunpc.mod
-rwxr-xr-x 1 root root     17  4 apr 09.12 parttool.lst
-rwxr-xr-x 1 root root   7192  4 apr 09.12 parttool.mod
-rwxr-xr-x 1 root root   2832  4 apr 09.12 password.mod
-rwxr-xr-x 1 root root   4328  4 apr 09.12 password_pbkdf2.mod
-rwxr-xr-x 1 root root   7352  4 apr 09.12 pata.mod
-rwxr-xr-x 1 root root   1824  4 apr 09.12 pbkdf2.mod
-rwxr-xr-x 1 root root   3352  4 apr 09.12 pbkdf2_test.mod
-rwxr-xr-x 1 root root   3424  4 apr 09.12 pcidump.mod
-rwxr-xr-x 1 root root  18968  4 apr 09.12 pgp.mod
-rwxr-xr-x 1 root root   3848  4 apr 09.12 play.mod
-rwxr-xr-x 1 root root  10496  4 apr 09.12 png.mod
-rwxr-xr-x 1 root root   2160  4 apr 09.12 priority_queue.mod
-rwxr-xr-x 1 root root   5480  4 apr 09.12 probe.mod
-rwxr-xr-x 1 root root   3680  4 apr 09.12 procfs.mod
-rwxr-xr-x 1 root root   3072  4 apr 09.12 progress.mod
-rwxr-xr-x 1 root root   1864  4 apr 09.12 raid5rec.mod
-rwxr-xr-x 1 root root   3320  4 apr 09.12 raid6rec.mod
-rwxr-xr-x 1 root root   3552  4 apr 09.12 random.mod
-rwxr-xr-x 1 root root   3008  4 apr 09.12 rdmsr.mod
-rwxr-xr-x 1 root root   2192  4 apr 09.12 read.mod
-rwxr-xr-x 1 root root   1520  4 apr 09.12 reboot.mod
-rwxr-xr-x 1 root root  77856  4 apr 09.12 regexp.mod
-rwxr-xr-x 1 root root  13584  4 apr 09.12 reiserfs.mod
-rwxr-xr-x 1 root root  26264  4 apr 09.12 relocator.mod
-rwxr-xr-x 1 root root   5512  4 apr 09.12 romfs.mod
-rwxr-xr-x 1 root root   6976  4 apr 09.12 scsi.mod
-rwxr-xr-x 1 root root   4648  4 apr 09.12 search_fs_file.mod
-rwxr-xr-x 1 root root   4768  4 apr 09.12 search_fs_uuid.mod
-rwxr-xr-x 1 root root   4712  4 apr 09.12 search_label.mod
-rwxr-xr-x 1 root root   5336  4 apr 09.12 search.mod
-rwxr-xr-x 1 root root  14456  4 apr 09.12 serial.mod
-rwxr-xr-x 1 root root    912  4 apr 09.12 setjmp.mod
-rwxr-xr-x 1 root root   2520  4 apr 09.12 setjmp_test.mod
-rwxr-xr-x 1 root root   8208  4 apr 09.12 setpci.mod
-rwxr-xr-x 1 root root   7696  4 apr 09.12 sfs.mod
-rwxr-xr-x 1 root root   2992  4 apr 09.12 shift_test.mod
-rwxr-xr-x 1 root root   8144  4 apr 09.12 signature_test.mod
-rwxr-xr-x 1 root root   3272  4 apr 09.12 sleep.mod
-rwxr-xr-x 1 root root   3008  4 apr 09.12 sleep_test.mod
-rwxr-xr-x 1 root root   8328  4 apr 09.12 smbios.mod
-rwxr-xr-x 1 root root   2968  4 apr 09.12 spkmodem.mod
-rwxr-xr-x 1 root root   9792  4 apr 09.12 squash4.mod
-rwxr-xr-x 1 root root   3160  4 apr 09.12 strtoull_test.mod
-rwxr-xr-x 1 root root  29320  4 apr 09.12 syslinuxcfg.mod
-rwxr-xr-x 1 root root   4768  4 apr 09.12 tar.mod
-rwxr-xr-x 1 root root    162  4 apr 09.12 terminal.lst
-rwxr-xr-x 1 root root   6584  4 apr 09.12 terminal.mod
-rwxr-xr-x 1 root root  19080  4 apr 09.12 terminfo.mod
-rwxr-xr-x 1 root root   1952  4 apr 09.12 test_blockarg.mod
-rwxr-xr-x 1 root root   3768  4 apr 09.12 testload.mod
-rwxr-xr-x 1 root root   7360  4 apr 09.12 test.mod
-rwxr-xr-x 1 root root   3416  4 apr 09.12 testspeed.mod
-rwxr-xr-x 1 root root   7312  4 apr 09.12 tftp.mod
-rwxr-xr-x 1 root root   5968  4 apr 09.12 tga.mod
-rwxr-xr-x 1 root root   2272  4 apr 09.12 time.mod
-rwxr-xr-x 1 root root   6200  4 apr 09.12 tpm.mod
-rwxr-xr-x 1 root root   1936  4 apr 09.12 trig.mod
-rwxr-xr-x 1 root root   3568  4 apr 09.12 tr.mod
-rwxr-xr-x 1 root root   1792  4 apr 09.12 true.mod
-rwxr-xr-x 1 root root  12064  4 apr 09.12 udf.mod
-rwxr-xr-x 1 root root   7848  4 apr 09.12 ufs1_be.mod
-rwxr-xr-x 1 root root   7688  4 apr 09.12 ufs1.mod
-rwxr-xr-x 1 root root   7688  4 apr 09.12 ufs2.mod
-rwxr-xr-x 1 root root   9864  4 apr 09.12 uhci.mod
-rwxr-xr-x 1 root root   5656  4 apr 09.12 usb_keyboard.mod
-rwxr-xr-x 1 root root  15544  4 apr 09.12 usb.mod
-rwxr-xr-x 1 root root  10976  4 apr 09.12 usbms.mod
-rwxr-xr-x 1 root root   2768  4 apr 09.12 usbserial_common.mod
-rwxr-xr-x 1 root root   3328  4 apr 09.12 usbserial_ftdi.mod
-rwxr-xr-x 1 root root   3656  4 apr 09.12 usbserial_pl2303.mod
-rwxr-xr-x 1 root root   2240  4 apr 09.12 usbserial_usbdebug.mod
-rwxr-xr-x 1 root root   5504  4 apr 09.12 usbtest.mod
-rwxr-xr-x 1 root root   8456  4 apr 09.12 video_bochs.mod
-rwxr-xr-x 1 root root   8840  4 apr 09.12 video_cirrus.mod
-rwxr-xr-x 1 root root   9920  4 apr 09.12 video_colors.mod
-rwxr-xr-x 1 root root  28144  4 apr 09.12 video_fb.mod
-rwxr-xr-x 1 root root   5208  4 apr 09.12 videoinfo.mod
-rwxr-xr-x 1 root root     41  4 apr 09.12 video.lst
-rwxr-xr-x 1 root root   8688  4 apr 09.12 video.mod
-rwxr-xr-x 1 root root   3584  4 apr 09.12 videotest_checksum.mod
-rwxr-xr-x 1 root root   5304  4 apr 09.12 videotest.mod
-rwxr-xr-x 1 root root   2328  4 apr 09.12 wrmsr.mod
-rwxr-xr-x 1 root root  10296  4 apr 09.12 xfs.mod
-rwxr-xr-x 1 root root  41728  4 apr 09.12 xnu.mod
-rwxr-xr-x 1 root root   3184  4 apr 09.12 xnu_uuid.mod
-rwxr-xr-x 1 root root   3024  4 apr 09.12 xnu_uuid_test.mod
-rwxr-xr-x 1 root root  19568  4 apr 09.12 xzio.mod
-rwxr-xr-x 1 root root   8392  4 apr 09.12 zfscrypt.mod
-rwxr-xr-x 1 root root  10448  4 apr 09.12 zfsinfo.mod
-rwxr-xr-x 1 root root  56680  4 apr 09.12 zfs.mod
-rwxr-xr-x 1 root root  78664  4 apr 09.12 zstd.mod

/efi/loader:
totale 16
drwxr-xr-x 2 root root 4096 13 apr 08.36 entries
-rwxr-xr-x 1 root root    6 15 feb 16.47 entries.srel
-rwxr-xr-x 1 root root   93 15 feb 16.47 loader.conf
-rwxr-xr-x 1 root root   32 21 apr 23.25 random-seed

/efi/loader/entries:
totale 8
-rwxr-xr-x 1 root root 440 13 apr 08.36 29eda348395345d9a0fd4c53d3d79880-6.2.10-arch1-1.conf
-rwxr-xr-x 1 root root 467 13 apr 08.36 29eda348395345d9a0fd4c53d3d79880-6.2.10-arch1-1-fallback.conf
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sat Apr 22, 2023 8:25 pm    Post subject: Reply with quote

Angie_4444,

Long rambling post ahead.

The PC boot process was only ever designed to boot a single operating system.

By default amd64 EFI firmware loads the file EFI/Boot/bootx64.efi from the EFI system partition. That's your /dev/nvme0n1p1
You cannot change that, its a feature.
With tools like efibootmgr, its possible to add other options and change the preference order.
You don't really want to go into the firmware and change the boot order there. It takes a long time and some EFI firmware is broken in that department, so lets avoid that.

Here is your firmware default boot entry.
Code:
/efi/EFI/BOOT:
totale 132
-rwxr-xr-x 1 root root 135168  2 apr 19.50 BOOTX64.EFI


and you have a Gentoo boot entry
Code:
 /efi/EFI/gentoo:
totale 132
-rwxr-xr-x 1 root root 135168  4 apr 09.12 grubx64.efi


and a systemd boot entry.

Code:
/efi/EFI/systemd:
totale 92
-rwxr-xr-x 1 root root 92160 10 apr 19.46 systemd-bootx64.efi

Yon can only choose among those at boot time my going into the firmware which is not very user friendly.

The file grubx64.efi in the start of the grub boot loader. Grub can boot lots of different operating systems, even Windows, if its set up correctly.
It has a boot menu too, so that the choice can be made at boot time, without going into the firmware.

Approach requires the use of a single copy of the grub boot loader and a single grub.cfg that will boot all your operating systems.
Your kernel and initrd files can go anywhere that grub can read.
Its not all good news though. It can become a problem to update grub.cfg as every operating system needs to be able to update the whole thing or just its own entries.

There is another way. Grub can 'chainload' other boot loaders, even other copies of grub. You can have a master grub, with a menu that lists your operating systems. When you pick one, it loads anoter copy of grub from that operating system that shows the choices for that operating system.

Code:
-rwxr-xr-x 1 root root 11032308 21 apr 16.48 initramfs-6.1.19-gentoo-x86_64.img
-rwxr-xr-x 1 root root 11022064 21 apr 13.24 initramfs-6.1.19-gentoo-x86_64.img.old
-rwxr-xr-x 1 root root 23768792  3 apr 23.40 initramfs-6.1.22-gentoo-dist.img
-rwxr-xr-x 1 root root 10238368 21 apr 16.26 vmlinuz-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root 10238368 21 apr 15.44 vmlinuz-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root 12251808  3 apr 23.40 vmlinuz-6.1.22-gentoo-dist

There's the Gentoo initrd and kernel files.

Was your /dev/nvme0n1p1 mounted at /mnt/gentoo/boot when you ran genkernel on Friday?
Code:
-rwxr-xr-x 1 root root  5865 21 apr 16.49 grub.cfg

That grub.cfg was updated just after the kernel build too.

Can you put that /efi/grub/grub.cfg onto a pastebin please, its a bit big for a post.

It's starting to look like its all there but you are booting he wrong firmware entry.
The output of
Code:
efibootmgr
will show that.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Sat Apr 22, 2023 9:15 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

Long rambling post ahead.

The PC boot process was only ever designed to boot a single operating system.

By default amd64 EFI firmware loads the file EFI/Boot/bootx64.efi from the EFI system partition. That's your /dev/nvme0n1p1
You cannot change that, its a feature.
With tools like efibootmgr, its possible to add other options and change the preference order.
You don't really want to go into the firmware and change the boot order there. It takes a long time and some EFI firmware is broken in that department, so lets avoid that.

Here is your firmware default boot entry.
Code:
/efi/EFI/BOOT:
totale 132
-rwxr-xr-x 1 root root 135168  2 apr 19.50 BOOTX64.EFI


and you have a Gentoo boot entry
Code:
 /efi/EFI/gentoo:
totale 132
-rwxr-xr-x 1 root root 135168  4 apr 09.12 grubx64.efi


and a systemd boot entry.

Code:
/efi/EFI/systemd:
totale 92
-rwxr-xr-x 1 root root 92160 10 apr 19.46 systemd-bootx64.efi

Yon can only choose among those at boot time my going into the firmware which is not very user friendly.

The file grubx64.efi in the start of the grub boot loader. Grub can boot lots of different operating systems, even Windows, if its set up correctly.
It has a boot menu too, so that the choice can be made at boot time, without going into the firmware.

Approach requires the use of a single copy of the grub boot loader and a single grub.cfg that will boot all your operating systems.
Your kernel and initrd files can go anywhere that grub can read.
Its not all good news though. It can become a problem to update grub.cfg as every operating system needs to be able to update the whole thing or just its own entries.

There is another way. Grub can 'chainload' other boot loaders, even other copies of grub. You can have a master grub, with a menu that lists your operating systems. When you pick one, it loads anoter copy of grub from that operating system that shows the choices for that operating system.

Code:
-rwxr-xr-x 1 root root 11032308 21 apr 16.48 initramfs-6.1.19-gentoo-x86_64.img
-rwxr-xr-x 1 root root 11022064 21 apr 13.24 initramfs-6.1.19-gentoo-x86_64.img.old
-rwxr-xr-x 1 root root 23768792  3 apr 23.40 initramfs-6.1.22-gentoo-dist.img
-rwxr-xr-x 1 root root 10238368 21 apr 16.26 vmlinuz-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root 10238368 21 apr 15.44 vmlinuz-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root 12251808  3 apr 23.40 vmlinuz-6.1.22-gentoo-dist

There's the Gentoo initrd and kernel files.

Was your /dev/nvme0n1p1 mounted at /mnt/gentoo/boot when you ran genkernel on Friday?
Code:
-rwxr-xr-x 1 root root  5865 21 apr 16.49 grub.cfg

That grub.cfg was updated just after the kernel build too.

Can you put that /efi/grub/grub.cfg onto a pastebin please, its a bit big for a post.

It's starting to look like its all there but you are booting he wrong firmware entry.
The output of
Code:
efibootmgr
will show that.


I remember having mounted /dev/nvme0n1p1 when I ran genkernel. If it's needed, I can re-run the command making sure of that.

Here it is the pastebin of grub.cfg: https://pastebin.com/Czzd1EUW

Also, efibootmgr:
Code:
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0001,0000,2001,2002,2003
Boot0000* EFI Hard Drive (SAMSUNG MZALQ512HALU-000L2)   PciRoot(0x0)/Pci(0xe,0x0)/NVMe(0x1,00-25-38-A4-11-C3-CA-29)/HD(1,GPT,485f1272-a5b7-094a-9e06-00fa6b8e0a60,0x1000,0x1f4000)RC
Boot0001* gentoo        HD(1,GPT,485f1272-a5b7-094a-9e06-00fa6b8e0a60,0x1000,0x1f4000)/File(\EFI\gentoo\grubx64.efi)
Boot0002* Linux Boot Manager    HD(1,GPT,485f1272-a5b7-094a-9e06-00fa6b8e0a60,0x1000,0x1f4000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sun Apr 23, 2023 10:40 am    Post subject: Reply with quote

Angie_4444,

Your pastebin shows a complete absence of boot stanzas. Its sort of what I expected.
Code:
### BEGIN /etc/grub.d/10_linux ###
 
### END /etc/grub.d/10_linux ###


It needs to contain at least one entry like
Code:
### BEGIN /etc/grub.d/10_linux ###

#6.2.1-gentoo
menuentry 'Gentoo GNU/Linux 6.2.1-gentoo' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-94a801cf-1a1b-443a-9dc9-348ed75d4f9a' {
        set gfxpayload=text
        insmod gzio
        insmod part_gpt
        insmod fat
        search --no-floppy --fs-uuid --set=root C33C-80D1
        echo    'Loading Linux 6.2.1-gentoo ...'
        linux   /6.2.1-gentoo root=/dev/vda2 ro net.ifnames=0 earlyprintk console=AMA0 console=ttyAMA0,115200n8 rcutree.use_softirq=0
        echo    'Loading Initramfs ...'
        initrd  /initramfs
}


Code:
menuentry 'Gentoo GNU/Linux 6.2.1-gentoo'
is the text in the menu.
Code:
linux   /6.2.1-gentoo
linux tells grub that its a kernel /6.2.1-gentoo is the file name with respect to grubs root.
Code:
initrd  /initramfs
does the same thing for an initrd/initramfs.

efibootmgr:
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0001,0000,2001,2002,2003


Boot entry 0002 was used for this boot, had that not been found entries 0001,0000,2001,2002,2003 would have been tried in that order.

Boot Entry 0002 is
Code:
Boot0002* Linux Boot Manager    HD(1,GPT,485f1272-a5b7-094a-9e06-00fa6b8e0a60,0x1000,0x1f4000)/File(\EFI\systemd\systemd-bootx64.efi)

So that's your EFI\systemd\systemd-bootx64.efi file.

Gentoo would have been next as entry 0001 is
Code:
Boot0001* gentoo        HD(1,GPT,485f1272-a5b7-094a-9e06-00fa6b8e0a60,0x1000,0x1f4000)/File(\EFI\gentoo\grubx64.efi)

but we know that its grub.cfg is empty, so choosing that boot entry won't boot anything.

All the bits of Gentoo are there, so its so close ... I'll make another coffee than post some more. I need to think of a safe way to fix it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54300
Location: 56N 3W

PostPosted: Sun Apr 23, 2023 11:47 am    Post subject: Reply with quote

Angie_4444,

You have a Gentoo install and another install. The bits are a bit mixed up.
If this goes right, you will have two installs and choose between them in the firmware.
They will share the /dev/nvme0n1p1 partition but the files will be separate, so thats OK.

All the bits are there. We need to put them together.

Get into your Gentoo chroot but after /dev/nvme0n1p4 is mounted at /mnt/gentoo be sure that /dev/nvme0n1p1 is mounted at /mnt/gentoo/boot.
Enter the chroot.
Code:
ls -l /boot
should show
Code:
totale 90580
drwxr-xr-x 3 root root     4096 13 apr 08.36 29eda348395345d9a0fd4c53d3d79880
-rwxr-xr-x 1 root root   249344  3 apr 23.40 config-6.1.22-gentoo-dist
drwxr-xr-x 6 root root     4096  2 apr 19.49 EFI
drwxr-xr-x 6 root root     4096 21 apr 16.49 grub
-rwxr-xr-x 1 root root 11032308 21 apr 16.48 initramfs-6.1.19-gentoo-x86_64.img
-rwxr-xr-x 1 root root 11022064 21 apr 13.24 initramfs-6.1.19-gentoo-x86_64.img.old
-rwxr-xr-x 1 root root 23768792  3 apr 23.40 initramfs-6.1.22-gentoo-dist.img
drwxr-xr-x 3 root root     4096 21 apr 23.25 loader
-rwxr-xr-x 1 root root  4043051 21 apr 16.26 System.map-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root  4043051 21 apr 15.44 System.map-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root  5829504  3 apr 23.40 System.map-6.1.22-gentoo-dist
-rwxr-xr-x 1 root root 10238368 21 apr 16.26 vmlinuz-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root 10238368 21 apr 15.44 vmlinuz-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root 12251808  3 apr 23.40 vmlinuz-6.1.22-gentoo-dist


less -l /boot/grub/grub.cfg should show a file missing it boot stanzas. The
Code:
### BEGIN /etc/grub.d/10_linux ###
 
### END /etc/grub.d/10_linux ###


It those things are as predicted, continue. Otherwise, stop and post what you do get.

Rewrite grub.cfg
Code:
grub-mkconfig -o /boot/grub/grub.cfg

It should tell you that it found three kernel and three initrds.

If not, stop and post.
less -l /boot/grub/grub.cfg Will show
Code:
### BEGIN /etc/grub.d/10_linux ###

[Boot Stanzas here]

### END /etc/grub.d/10_linux ###

Will be filled in too. Is it?

Code:
emerge efibootmgr
if you don't have it.

Code:
efibootmgr -n 1
will set up the efivars to boot Gentoo on the next boot only.

Reboot to test. Its Gentoo all the way from the EFI Firmware now,

Seeing your three Gentoo kernel in the grub menu will be real progress.
Getting a "Something went wrong, dropping you to a shell" is OK. We need to know what the something is.
A login prompt is the icing on the cake. :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Angie_4444
n00b
n00b


Joined: 12 Apr 2023
Posts: 43

PostPosted: Sun Apr 23, 2023 12:48 pm    Post subject: Reply with quote

NeddySeagoon wrote:
Angie_4444,

You have a Gentoo install and another install. The bits are a bit mixed up.
If this goes right, you will have two installs and choose between them in the firmware.
They will share the /dev/nvme0n1p1 partition but the files will be separate, so thats OK.

All the bits are there. We need to put them together.

Get into your Gentoo chroot but after /dev/nvme0n1p4 is mounted at /mnt/gentoo be sure that /dev/nvme0n1p1 is mounted at /mnt/gentoo/boot.
Enter the chroot.
Code:
ls -l /boot
should show
Code:
totale 90580
drwxr-xr-x 3 root root     4096 13 apr 08.36 29eda348395345d9a0fd4c53d3d79880
-rwxr-xr-x 1 root root   249344  3 apr 23.40 config-6.1.22-gentoo-dist
drwxr-xr-x 6 root root     4096  2 apr 19.49 EFI
drwxr-xr-x 6 root root     4096 21 apr 16.49 grub
-rwxr-xr-x 1 root root 11032308 21 apr 16.48 initramfs-6.1.19-gentoo-x86_64.img
-rwxr-xr-x 1 root root 11022064 21 apr 13.24 initramfs-6.1.19-gentoo-x86_64.img.old
-rwxr-xr-x 1 root root 23768792  3 apr 23.40 initramfs-6.1.22-gentoo-dist.img
drwxr-xr-x 3 root root     4096 21 apr 23.25 loader
-rwxr-xr-x 1 root root  4043051 21 apr 16.26 System.map-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root  4043051 21 apr 15.44 System.map-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root  5829504  3 apr 23.40 System.map-6.1.22-gentoo-dist
-rwxr-xr-x 1 root root 10238368 21 apr 16.26 vmlinuz-6.1.19-gentoo-x86_64
-rwxr-xr-x 1 root root 10238368 21 apr 15.44 vmlinuz-6.1.19-gentoo-x86_64.old
-rwxr-xr-x 1 root root 12251808  3 apr 23.40 vmlinuz-6.1.22-gentoo-dist


less -l /boot/grub/grub.cfg should show a file missing it boot stanzas. The
Code:
### BEGIN /etc/grub.d/10_linux ###
 
### END /etc/grub.d/10_linux ###


It those things are as predicted, continue. Otherwise, stop and post what you do get.

Rewrite grub.cfg
Code:
grub-mkconfig -o /boot/grub/grub.cfg

It should tell you that it found three kernel and three initrds.

If not, stop and post.
less -l /boot/grub/grub.cfg Will show
Code:
### BEGIN /etc/grub.d/10_linux ###

[Boot Stanzas here]

### END /etc/grub.d/10_linux ###

Will be filled in too. Is it?

Code:
emerge efibootmgr
if you don't have it.

Code:
efibootmgr -n 1
will set up the efivars to boot Gentoo on the next boot only.

Reboot to test. Its Gentoo all the way from the EFI Firmware now,

Seeing your three Gentoo kernel in the grub menu will be real progress.
Getting a "Something went wrong, dropping you to a shell" is OK. We need to know what the something is.
A login prompt is the icing on the cake. :)


I am sorry, something is wrong. After running the less command, I get the entire output of grub.cfg, but the boot stanzas are there. Maybe I didn't have the partition mounted. Here's the new pastebin;https://pastebin.com/5tPd1YiD
I am sorry. Shall I continue with the efibootmgr command?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page Previous  1, 2, 3, 4  Next
Page 2 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum