| View previous topic :: View next topic |
| Author |
Message |
tld
Veteran
Joined: 09 Dec 2003
Posts: 1845
|
 Posted: Mon Jul 01, 2024 11:59 am Post subject: linux-firmware pre-merge complains about /boot/efi? [SOLVED] |
 |
|
This is a new one for me. I use sys-boot/refind for a boot loader. My /boot actually lives on my / partition, and my /dev/sda1 is my FAT formatted EFI partition.
I have a mount point for the EFI partition at /boot/efi, however I generally leave it unmounted....but in today's updates that's causing the pre-merge check errors:
| Code: | >>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/linux-firmware-20240610-r1
* Assuming you do not have a separate /boot partition.
* Assuming you do not have a separate /efi partition.
* Your /boot/efi partition is not mounted
* Please mount it and retry.
* ERROR: sys-kernel/linux-firmware-20240610-r1::gentoo failed (pretend phase):
* /boot/efi not mounted
*
* Call stack:
* ebuild.sh, line 136: Called pkg_pretend
* linux-firmware-20240610-r1.ebuild, line 78: Called mount-boot_pkg_pretend
* mount-boot.eclass, line 27: Called mount-boot_check_status
* mount-boot-utils.eclass, line 85: Called die
* The specific snippet of code:
* die -n "${partition} not mounted"
*
* If you need support, post the output of `emerge --info '=sys-kernel/linux-firmware-20240610-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-kernel/linux-firmware-20240610-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-kernel/linux-firmware-20240610-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-kernel/linux-firmware-20240610-r1/temp/die.env'.
* Working directory: '/var/tmp/portage/sys-kernel/linux-firmware-20240610-r1/empty'
* S: '/var/tmp/portage/sys-kernel/linux-firmware-20240610-r1/work/linux-firmware-20240610'
>>> Failed to emerge sys-kernel/linux-firmware-20240610-r1, Log file: |
It appears it would have tried to continue after that as well. I'm going to go ahead and mount it.
Does anyone know why that's apparently now required? Thanks in advance.
Tom
Last edited by tld on Mon Jul 01, 2024 1:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22685
|
| Posted: Mon Jul 01, 2024 12:29 pm Post subject: |
|
|
| A similar problem was reported in Failed to emerge sys-kernel/linux-firmware-20240610-r1. You may not have the same solution, but I found the post from AndrewAmmerlaan to be informative. USE=initramfs is default-enabled in recent versions of linux-firmware, and as I read that post, USE=initramfs controls whether this check is done (and some later work, which depends on the check succeeding). If you don't need the ebuild to do that later work, you could disable USE=initramfs. |
|
| Back to top |
|
|
tld
Veteran
Joined: 09 Dec 2003
Posts: 1845
|
| Posted: Mon Jul 01, 2024 1:04 pm Post subject: |
|
|
Thanks! That totally makes sense, and no, I don't need any iniramfs. Thanks!
Tom |
|
| Back to top |
|
|
|
|
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
|
|
Portage & Programming
