Package Base Details: linux-clear

Git Clone URL: (read-only)
Keywords: clear clearlinux intel kernel
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 31
Popularity: 4.02
First Submitted: 2018-01-18 21:47
Last Updated: 2019-11-13 12:29

Pinned Comments

metak commented on 2018-01-22 01:49

1. Binaries available in my repo:
Server =$arch

Then, import the key:
Key-ID: pacman-key --recv-keys 50AAD02AEB1F61C9
Donwload and import the key: pacman-key --add /path/to/downloaded/keyfile

Last, sign the key. pacman-key --lsign-key 50AAD02AEB1F61C9

2. After install adjust your boot cmd line. ClearLinux uses clr-boot-manager which takes care of that. This is upstream default:
quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check noreplace-smp page_alloc.shuffle=1 rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs tsc=reliable rw 
3. For loading unsigned modules. (nvidia, virtualbox, etc.)

If secure boot is disabled just add module.sig_unenforce boot parameter. Otherwise, you'll have to build your kernel with CONFIG_MODULE_SIG_FORCE disabled.

4. Once again (as requested) the _subarch is set to native so for anyone who is building the binaries for redistribution should set it to number corresponding to Generic-x86-64.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

xuanruiqi commented on 2019-09-08 04:30

It seems that I need the cpio package to correctly build linux-clear. Maybe this is due to some kernel options I enabled, but not sure which ones.

metak commented on 2019-08-26 18:12

@btd1337 That's for archlinux Trusted Users and Developers, not some random aur maintainers. ;-)

btd1337 commented on 2019-08-25 21:24

@metak Why you don't use the Arch Servers? Like here:

metak commented on 2019-08-25 12:35

@btd1337 Hey. OpenSUSE Build Service support for archlinux is bad. I reported this issue years ago.
Basically, the build service triggered the package rebuild (after my last commit), but since there's no support for arch to increment pkrel +1 we end up with (invalid or corrupt package (checksum)).
The package itself is fine though. You can install it with pacman -U, but I do realize this is inconvenient. Maybe I should just remove the instructions for binaries if it's causing confusion/problems?

btd1337 commented on 2019-08-25 02:19

:: File /var/cache/pacman/pkg/linux-clear-5.2.9-6-x86_64.pkg.tar.xz is corrupt (invalid or corrupt package (checksum)).
Do you want to delete it? [Y / n] y
:: File /var/cache/pacman/pkg/linux-clear-headers-5.2.9-6-x86_64.pkg.tar.xz is corrupt (invalid or corrupt package (checksum)).
Do you want to delete it? [Y / n] y
error: failed to submit transaction (invalid or corrupted package)
Errors occurred and therefore no packages were updated.
Error installing repo packages

metak commented on 2019-08-18 22:36

@btd1337 That's because OpenSUSE Build Service "support" for pgp-signed repositories is broken.

btd1337 commented on 2019-08-18 22:28

@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.

metak commented on 2019-08-18 20:01

@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 ""
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.

btd1337 commented on 2019-08-18 19:04

@Metak What's wrong?

sudo pacman-key --add
gpg: can't open '': No file or directory
==> ERROR: A specified key file could not be added to the keychain.
sudo pacman-key --add  <\>
zsh: arquivo ou diretório inexistente:>
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

metak commented on 2019-08-18 12:43

@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.