Package Base Details: linux-clear

Git Clone URL: (read-only)
Keywords: clear clearlinux intel kernel
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 19
Popularity: 1.638721
First Submitted: 2018-01-18 21:47
Last Updated: 2019-05-18 13:59

Pinned Comments

metak commented on 2018-01-22 01:49

1. Binaries available in my repo:
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 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 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.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

metak commented on 2019-04-17 21:50

@xuanruiqi Should be fixed now.

xuanruiqi commented on 2019-04-17 20:41

There's a problem with this version. If _subarch is set, then the line:

yes "$_subarch" | make oldconfig

will echo "_subarch" to the newly added interactive item:

Automatically load TTY Line Disciplines (LDISC_AUTOLOAD) [Y/n/?] (NEW)

and will cause infinite looping. The solution is of course unsetting _subarch temporarily.

metak commented on 2019-04-16 15:17

@longspear Never experienced it myself.

longspear commented on 2019-04-15 07:15

Hi there, is anyone else experiencing a recurring "ping: no buffer space available" error with this particular Kernel?

metak commented on 2019-04-09 15:28

@aorth If you're experiencing this issue only on linux-clear kernel it may be due to something clear specific? Dunno. Please link that lvm2 issue in your clearlinux-distribution github comment so that clear team can check it out if they haven't already.

aorth commented on 2019-04-09 13:28

@metak it looks like this issue will be fixed in LVM2. I'm not sure why it only affects me on linux-clear, though...

metak commented on 2019-04-04 16:58

@aorth Seems like this issue is already reported upstream. LVM Clearlinux takes a long time to shut down

aorth commented on 2019-04-04 15:55

@metak yeah I saw that thread. They seem to conclude that it's something related to LVM, and I am indeed using LVM on LUKS, though for me the issue only happens on linux-clear. The screen is black with a blinking cursor and eventually (maybe 90 seconds, I should actually time it) it says something about failing to unmount oldroot and then it reboots.

Edit: thanks @metak. I won't spam here anymore. Nice to know I'm not alone and that someone has even reported it upstream. For reference, here is the message that is spammed after the cursor blinks for ~90 seconds and it finally reboots:

[  116.123456] sd-umoun[1040]: Failed to unmount /oldroot: Device or resource busy
[  116.123456] sd-umoun[1041]: Failed to unmount /oldroot/dev: Device or resource busy
[  117.123457] reboot: Restarting system

metak commented on 2019-04-01 15:33

@aorth Have you checked this thread?

aorth commented on 2019-04-01 15:08

Does anyone get a blinking cursor for about one minute on shutdown? It's the one annoying thing that causes me to stop running linux-clear. Not sure if it's a systemd job waiting or something...