Gorgeous, thank you!
Search Criteria
Package Details: intel-ucode-clear 36610-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: | intel-ucode |
Submitter: | yw662 |
Maintainer: | katoitalia |
Last Packager: | katoitalia |
Votes: | 10 |
Popularity: | 0.001787 |
First Submitted: | 2019-08-04 22:37 (UTC) |
Last Updated: | 2022-07-17 10:46 (UTC) |
Dependencies (0)
Required by (4)
- arch-secure-boot (requires intel-ucode) (optional)
- archsysback (requires intel-ucode)
- linux-clear-bin (optional)
- sedutil (requires intel-ucode) (optional)
Sources (3)
RubenKelevra commented on 2022-04-17 21:24 (UTC)
katoitalia commented on 2021-10-17 19:18 (UTC)
this package hasn't been working for about half an hour as intel changed slightly how their files are stored on their servers, tweaked my script I use to generate the PKGBUILD and it works fine now
katoitalia commented on 2021-08-08 04:52 (UTC)
I'm sorry if this hasn't been working correctly in the past 3 hours, it's fixed now.
commented on 2020-12-11 18:47 (UTC)
@katoitalia what's the difference between intel-ucode and this package?
katoitalia commented on 2020-12-11 14:06 (UTC)
@0day it is not a mandatory requirement
commented on 2020-12-11 11:35 (UTC)
Should I use this package instead of intel-ucode if using linux-clear kernel?
Khaithang commented on 2020-11-21 13:41 (UTC)
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 (UTC)
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 (UTC) (edited on 2021-06-01 14:02 (UTC) by katoitalia)
This is the microcode for INTEL CPUs that you can find in Clear Linux
regular intel-ucode microcode found in official arch repos is often a few months behind intel-ucode-clear and might not have the same perks and optimizations as it follows a different release pipeline.
Click on "Show More.." for instructions...
- I only use systemd-boot.
- I will not provide how to procedures on bootloaders I do not test myself.
- I don't use grub or bootloaders other than systemd-boot, compatibility with other bootloaders is very much possible but untested.
- In previous comments you should be able to find how to make it work with grub.
- This package does not conflict with the intel-ucode package as you might use it to start a different kernel and they may coexist on different bootloader entries.
- This package is not suited for AMD CPUs or Intel-Mac computers even if they are x86_64 but if you are interested in submitting to the AUR an AMD or Intel-Mac compatible package, I will be able to provide you with the script I use to generate this package as starting point.
To make it work, add both:
/intel-ucode.cpio
and
/i915-firmware.cpio.xz
to your bootloader entry as initrd.
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
Pinned Comments
katoitalia commented on 2020-08-13 08:58 (UTC) (edited on 2021-06-01 14:02 (UTC) by katoitalia)
This is the microcode for INTEL CPUs that you can find in Clear Linux
regular intel-ucode microcode found in official arch repos is often a few months behind intel-ucode-clear and might not have the same perks and optimizations as it follows a different release pipeline.
To make it work, add both:
/intel-ucode.cpio
and/i915-firmware.cpio.xz
to your bootloader entry as initrd.
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
* EDIT: Update and clarifications