Arch Linux User Repository

Information comment
This comment provides useful information about this package. Make sure to read it through, you won't regret it.

Repository URL
This package is hosted at sos!git. If you want to contribute to the package, you can do it here: https://git.staropensource.de/JeremyStarTM/aur-linux-clear

Issue handling
Please only submit issues in the package's repository if they aren't bug reports about the package or help requests. Please keep them to the AUR only. This prevents unnecessary signups.

Updates
I usually publish updates 0-3 days after a kernel release, depending on how busy I am.
If I however get wind of security-relevant updates or any vulnerabilities I will try to update the kernel as soon as possible and write a comment about the vulnerability/update. So make sure to subscribe to this package's comment mailing list.

PKGBUILD environment variable customization
The PKGBUILD file supports customization via environment variables. Here's a list of all of them:
- _makemenuconfig: Invokes make menuconfig (ncurses-based default configuration menu) before compilation starts
- _makenconfig: Invokes make nconfig (ncurses-based nicer configuration menu) before compilation starts
- _makexconfig: Invokes make xconfig (X11-based GUI configuration menu) before compilation starts
- _use_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _optimize_defconfig: Applies package maintainer-picked configuration changes to your defconfig. Only takes effect with _use_current being enabled
- _copyfinalconfig: Copies the final kernel configuration into the repository root as kconfig-new before compilation starts
- _localmodcfg: Only compiles modules found in modprobed-db's database (which decreases compilation time and kernel size)
- _use_llvm_lto: Compiles the kernel with LLVM instead of GCC. Should work, if not open an issue
- _subarch: Specifies the subarchitecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 41/MGENERIC_CPU (Generic x86-64), which is compatible with all amd64 processors. Must be a number or subarch name
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the MGENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset

All of these variables just need to be set for them to apply, except for _subarch and _debug. For more information please check their documentation inside the PKGBUILD file

GPG errors
If makepkg complains about invalid PGP keys, try running this command first: gpg --locate-keys torvalds@kernel.org gregkh@kernel.org sashal@kernel.org benh@debian.org. This command only needs to be executed once.

Build tool
If you want a dead simple way to compile this package, you can try out my build tool. It includes a few no nonsense changes to the kernel configuration and allows you to configure the PKGBUILD file in a simple manner and decrease build time. And if you don't want that, using makepkg as-is works fine too.

@metak Just adding the key, this error persists:

error: linux-clear: unsupported signature format
error: linux-clear-headers: unsupported signature format

It's necessary to add SigLevel = Never in order to error message disapear, but this is not a good practice.

@btd1337 You're supposed to download the key and then import it. It's all in the link in the pinned comment where it says 'Then, import the key.'

wget "http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/home_metakcahura_kernel_Arch_Extra_standard.key"
pacman-key --add home_metakcahura_kernel_Arch_Extra_standard.key

If you're still unable to import the key then just add SigLevel = Never before the Server = line for this repo in /etc/pacman.conf.

@Metak What's wrong?

sudo pacman-key --add http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/home_metakcahura_kernel_Arch_Extra_standard.key
gpg: can't open 'http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/home_metakcahura_kernel_Arch_Extra_standard.key': No file or directory
==> ERROR: A specified key file could not be added to the keychain.

sudo pacman-key --add  <http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/home_metakcahura_kernel_Arch_Extra_standard.key\>
zsh: arquivo ou diretório inexistente: http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/home_metakcahura_kernel_Arch_Extra_standard.key>

sudo pacman-key --lsign-key 50AAD02AEB1F61C9                                       1 ↵
  -> Locally signing the key 50AAD02AEB1F61C9...
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   7  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   7  signed:  89  trust: 1-, 0q, 0n, 6m, 0f, 0u
gpg: depth: 2  valid:  86  signed:  12  trust: 86-, 0q, 0n, 0m, 0f, 0u
gpg: next verification of the trusted database to 2019-10-12

error: linux-clear: unsupported signature format
error: linux-clear-headers: unsupported signature format

@btd1337 I've disabled the CONFIG_MODULE_SIG_FORCE, because many users build modules and to just make it easier. Try 5.2.9-4.

@metak I have this error during boot:

Failed to start Load Kernel Modules - systemd-modules-load.service

systemd-modules-load[2218]: Failed to find module 'speakup_soft'
systemd-modules-load[2218]: Failed to insert module 'vboxdrv': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxpci': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxnetadp': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxnetflt': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxdrv': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxnetadp': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxnetflt': Required key not available
systemd-modules-load[2218]: Failed to insert module 'vboxpci': Required key not available
systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Load Kernel Modules.

My /boot/default/grub file contains:

GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200n8 initcall_debug tsc=reliable no_timer_check noreplace-smp kvm-intel.nested=1 rootfstype=ext4,btrfs,xfs intel_iommu=igfx_off cryptomgr.notests rcupdate.rcu_expedited=1 rcu_nocbs=0-64 module.sig_unenforce rw"

module.sig_unenforce is as a second to last parameter. What am I doing wrong that step 3 doesn't work?

Thanks in advance!

UPDATE:

sudo vboxreload                                                                                                                                            ✔
Unloading modules: 
Loading modules: modprobe: ERROR: could not insert 'vboxnetadp': Required key not available
modprobe: ERROR: could not insert 'vboxnetflt': Required key not available
modprobe: ERROR: could not insert 'vboxpci': Required key not available
modprobe: ERROR: could not insert 'vboxdrv': Required key not available

SMBIOS messages are gone, thanks.

@btd1337 If you've already created $XDG_CONFIG_HOME/modprobed.db as per WIKI then you only have to set _localmodcfg=y. That's all.

What do this variable Pkgbuild, Line 57: _localmodcfg= needs?

Is this?

_localmodcfg=/home/myuser/.config/modprobed.db

@btd1337 I've updated the repo instructions in the pinned comment.

@Elanzer I've enabled CONFIG_DELL_SMBIOS_SMM=y, can you try the latest version?

I'm getting this message on boot:

dell_smbios: No SMBIOS backends available (wmi: -19, smm: -19) dell_smbios: No dell-smbios drivers are loaded

System is running fine, but still worries me. It's was fixed upstream, according https://github.com/clearlinux/distribution/issues/609

I think dell_smbios is set to user 'smm' but only 'wmi' is available with clear-linux