| View previous topic :: View next topic |
| Author |
Message |
klammerj
n00b
Joined: 19 Jan 2023
Posts: 18
|
 Posted: Sat Jul 20, 2024 4:12 pm Post subject: [SOLVED]intel-microcode fails to install microcode image |
 |
|
Good evening.
I tried to update the system to the noew profile today, and it failed.
the intel-microcode seems to be the showstopper.
after an emerge intel-microcode I get:
| Code: |
!!! copy /var/tmp/portage/sys-firmware/intel-microcode-20240514_p20240514/image/boot/intel-uc.img -> /boot/intel-uc.img failed.
!!! [Errno 1] Operation not permitted: b'/boot/intel-uc.img#new'
|
boot is:
| Code: |
/dev/sda1 /boot vfat rw,lazytime,nosuid,noatime,gid=25,fmask=0113,dmask=0002,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro 0 0
|
How to fix?
Last edited by klammerj on Tue Jul 23, 2024 12:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
netfab
Veteran
Joined: 03 Mar 2005
Posts: 1941
Location: 127.0.0.1
|
| Posted: Sun Jul 21, 2024 9:40 am Post subject: |
|
|
Hi,
Please post your emerge --info and the entire intel-microcode ebuild build.log containing the error. |
|
| Back to top |
|
|
pcmaster
Advocate
Joined: 04 Dec 2003
Posts: 2232
Location: Barcelona
|
| Posted: Sun Jul 21, 2024 12:42 pm Post subject: |
|
|
Make sure your /boot partition is mounted...
_________________
pcmaster |
|
| Back to top |
|
|
AndrewAmmerlaan
Developer
Joined: 25 Jun 2014
Posts: 363
Location: Nijmegen
|
| Posted: Sun Jul 21, 2024 1:26 pm Post subject: |
|
|
| Quote: | | gid=25,fmask=0113,dmask=0002 |
I suspect this is the issue.
The eclass enforces that /boot is mounted read-write, but these masks may interfere with the install. Please try again without these options.
By the way, if you don't need a microcode initramfs (e.g. because the microcode is built into the kernel), then you can safely disable the "initramfs" USE flag and then the ebuild will not write to /boot to begin with. The default setting for this flag was changed from disabled to enabled relatively recently.
_________________
OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
klammerj
n00b
Joined: 19 Jan 2023
Posts: 18
|
| Posted: Sun Jul 21, 2024 4:07 pm Post subject: |
|
|
| AndrewAmmerlaan wrote: | | Quote: | | gid=25,fmask=0113,dmask=0002 |
I suspect this is the issue.
The eclass enforces that /boot is mounted read-write, but these masks may interfere with the install. Please try again without these options.
By the way, if you don't need a microcode initramfs (e.g. because the microcode is built into the kernel), then you can safely disable the "initramfs" USE flag and then the ebuild will not write to /boot to begin with. The default setting for this flag was changed from disabled to enabled relatively recently. |
Yes, that fstab line is copypasta from an older fstab file. I've removed the gid=25. and disabled the initramfs useflags in intel-microcode and linux-firmware(it gave a similar error) for now. At the moment system is compiling. Will try reinstalling intel-microcode when the system is in a more acceptable shape. |
|
| 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
|
|
Kernel & Hardware
