@katoitalia what's the difference between intel-ucode and this package?
Search Criteria
Package Details: intel-ucode-clear 34110-1
| Git Clone URL: | https://aur.archlinux.org/intel-ucode-clear.git (read-only, click to copy) |
|---|---|
| Package Base: | intel-ucode-clear |
| Description: | Intel cpu microcode and i915 firmware used by Clear Linux |
| Upstream URL: | https://clearlinux.org/ |
| Keywords: | microcode |
| Provides: | |
| Submitter: | yw662 |
| Maintainer: | katoitalia |
| Last Packager: | katoitalia |
| Votes: | 7 |
| Popularity: | 0.053323 |
| First Submitted: | 2019-08-04 22:37 |
| Last Updated: | 2020-12-28 10:48 |
Dependencies (0)
Required by (5)
- arch-secure-boot (requires intel-ucode) (optional)
- archsysback (requires intel-ucode)
- cpuface-git (requires intel-ucode) (optional)
- linux-clear-bin (optional)
- sedutil (requires intel-ucode) (optional)
Sources (3)
Anonymous comment on 2020-12-11 18:47
katoitalia commented on 2020-12-11 14:06
@0day it is not a mandatory requirement
Anonymous comment on 2020-12-11 11:35
Should I use this package instead of intel-ucode if using linux-clear kernel?
Khaithang commented on 2020-11-21 13:41
Does it conflict with intel-ucode in extra repository link: - https://www.archlinux.org/packages/extra/any/intel-ucode/ i have three kernels (clear linux, linux zen and main kernel) i already have intel-ucode.img in my boot directory in loads for all the kernel. And i have the i915 firmware in the main and zen kernel but not in clear linux, should i remove the exisiting intel-code and put this version along with the i915 firmware in the clear linux menu in grub ?
Tjuh commented on 2020-09-26 21:24
Getting this kernel log message since I switched to mkinitcpio-zstd, linux-clear boots just fine though;
Initramfs unpacking failed: invalid magic at start of compressed archive
Funny thing is that this msg does not appear on linux-zen rebuilt with mkinitcpio-zstd.
katoitalia commented on 2020-08-13 08:58
add both
/intel-ucode.cpio
and
/i915-firmware.cpio.xz
to your bootloader as initrd.
Current version is 33600.
e.g. on systemd-boot
title KatoLinux 5.7
linux /vmlinuz-5.7-x86_64
initrd /intel-ucode.cpio
initrd /i915-firmware.cpio.xz
initrd /initramfs-5.7-x86_64.img
options root=UUID=XXX rw
katoitalia commented on 2020-07-12 16:11
well you should use i915-firmware.cpio.xz too
xstefen commented on 2020-07-11 23:06
For Grub2 Users, you can simply add the line GRUB_EARLY_INITRD_LINUX_CUSTOM="intel-ucode.cpio" to /etc/default/grub
Confirmed on my system when doing grub-mkconfig:
Found initrd image: /boot/intel-ucode.cpio /boot/initramfs-linux-zen.img
edit: I use nvidia
katoitalia commented on 2020-07-10 13:20
@programegg you could work and investigate on it further and provide us with your method or even a new package for your specific use case. This is the way.
programegg commented on 2020-07-08 21:12
Any suggestions on how to load these images when only a single initrd option is allowed like with a unified kernel image or older loaders like LILO?
With the traditional microcode its possible to cat /boot/intel-ucode.img /boot/initramfs-linux.img > /boot/initramfs-merged.img and then direct the bootloader to use the new merged .img file.
Is this concatenation still possible here even with the two different compressions for ucode and i915 plus the .img initramfs? Simply merging all three files using cat while disregarding compression type seems wrong but it does produce a bootable initramfs. Is there something to check in dmesg to actually check the ucode and i915 firmware are loading correctly? Thank you.
Pinned Comments
katoitalia commented on 2020-08-13 08:58
add both
/intel-ucode.cpioand/i915-firmware.cpio.xzto your bootloader as initrd.
Current version is 33600.
e.g. on systemd-boot
title KatoLinux 5.7linux /vmlinuz-5.7-x86_64initrd /intel-ucode.cpioinitrd /i915-firmware.cpio.xzinitrd /initramfs-5.7-x86_64.imgoptions root=UUID=XXX rw