| 1 |
On Tuesday, 24 November 2020 21:51:53 GMT thelma@×××××××××××.com wrote: |
| 2 |
> I run gentoo installation from: |
| 3 |
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks |
| 4 |
> |
| 5 |
> parted -a optimal /dev/nvme0n1 |
| 6 |
> |
| 7 |
> Device Start End Sectors Size Type |
| 8 |
> /dev/nvme0n1p1 2048 6143 4096 2M BIOS boot |
| 9 |
> /dev/nvme0n1p2 6144 268287 262144 128M EFI System |
| 10 |
> /dev/nvme0n1p3 268288 1316863 1048576 512M Linux filesystem |
| 11 |
> /dev/nvme0n1p4 1316864 3907027119 3905710256 1.8T Linux filesystem |
| 12 |
|
| 13 |
I am not clear if this is a UEFI MoBo or not. If yes, you can use the UEFI |
| 14 |
boot manager, instead of Legacy BIOS and you do not need a 'BIOS boot |
| 15 |
partition'. If instead you will be booting this disk both in Legacy BIOS and |
| 16 |
UEFI modes, then leave the 'BIOS boot partition' as you have it. When you |
| 17 |
install GRUB in the MBR it will drop in there its Stage 2 binary code. |
| 18 |
|
| 19 |
|
| 20 |
> When I compiled kernel and run: make install |
| 21 |
> it complained not enough space on disk |
| 22 |
> |
| 23 |
> sh ./arch/x86/boot/install.sh 5.4.72-gentoo arch/x86/boot/bzImage \ |
| 24 |
> System.map "/boot" |
| 25 |
> cat: write error: No space left on device |
| 26 |
> make[1]: *** [arch/x86/boot/Makefile:155: install] |
| 27 |
> |
| 28 |
> /dev/nvme0n1p4 1.8T 3.5G 1.7T 1% / |
| 29 |
> cgroup_root 10M 0 10M 0% /sys/fs/cgroup |
| 30 |
> udev 10M 0 10M 0% /dev |
| 31 |
> tmpfs 16G 0 16G 0% /dev/shm |
| 32 |
> /dev/sda2 6.4M 6.4M 2.0K 100% /boot |
| 33 |
> |
| 34 |
> (sda2 - I think is a bootable USB) |
| 35 |
|
| 36 |
Your /boot mountpoint should be used for /dev/nvme0n1p2, if this is a UEFI |
| 37 |
installation. If as you report above /boot is on /dev/sda2 you have not |
| 38 |
followed the handbook correctly. In particular you have not mounted /dev/ |
| 39 |
nvme0n1p2 as /mnt/gentoo/boot before you chrooted into /mnt/gentoo. |
Archives