kernel madness. And how others came to the same conclusion

_roman_ · 01-03-2018, 04:43 PM

Rant: Any kernels named 4.10, 4.11, 4.12, 4.13, 4.14 are ****. Sorry to use that word, but they are rubbish in any regards.

https://archives.gentoo.org/gentoo-d...bb2e0259f2ac3e

Quote:

We recently dropped the stable keywords for 4.14,
but 4.12 (the next stable in gentoo-sources) is no more
maintained from upstream.

The last update that 4.12 got from upstream was 2017-09-20,
and upstream is no more backporting security fixes since then.
Because of this, we will proceed to mask 4.12.

Keep in mind: If 4.14 works for you, you can keyword it and
continue to use it, if you need a more stable kernel, please
move to 4.9.

RANT: I'm in contact with one of the kernel.org guys. Considering his statement that my heimdall issue is not relevant. and only my cups issue counts. When I downgraded to 4.1 or 4.9.7x gentoo sources all my stuff suddenly worked. I could set again cpupower frequency-set -g powersave or -f 1200000 to get 3 hours out of my laptop accumulator again. kernel 4.12 broke hda_intel, that is a soundcard. kernel 4.14 has usb related issues regarding cups with two different printers here, and with heimdall an open source odin samsung protocol samsung tablet programmer. 4.10 had also issues with 4.11. honestly i forgot as this is dated software in my eyes and i stopped using that unstable software.

_roman_ · 01-03-2018, 04:48 PM

Note: Answering myself so no one has to bump my own topics:

https://forums.gentoo.org/viewtopic-...ighlight-.html

I respect tony as tony is a decent guy. well my forums.gentoo.org account is now banned, nevertheless I think I like his statements!

Quote:

Three months ago! How ancient! How old is the kernel that some Ubuntu user installed last year? I for one am rather sick of the "kernel of the week" obviously inadequately tested kernels coming out of kernel.org lately. Kernels used to be updated every six months to a year and 2.2 lasted quite a while alongside the radically different 2.4 The present kernels should be marked as "release candidates" by upstream rather than as "stable".

Because upstream is not issing updates anymore is no reason to mask a package, else half the tree would be masked. Have we fallen into the Microsoft update daily paradigm?

I agree on the release candidate status of kernel.org phrase of "stable: 4.14.11" or "
mainline: 4.15-rc6"

Only stable kernels are, because of extra policy on how to backport: "longterm: 4.9.74 2018-01-02"

I want to tell you this: Please consider using longterm branch 4.9.x or something similar. so you do not waste days fixing stuff which is caused by experimental kernels, like alpha status, from kernel.org named for example: "stable: 4.14.11" or "mainline: 4.15-rc6"

You will also get the bonus that nvidia-drivers will install without a fuss. A new kernel branch usually needs a patch for nvidia-drivers.

--

Quote:

https://lkml.org/lkml/2017/12/29/488

Quote:

> Good. I was not feeling so happy about this bug report, but now I can
> firmly just blame the gentoo compiler for having some shit-for-brains
> "feature".

Well you see here why I wanted to ditch gentoo earlier, as stated in one of my earlier posts.

gentoo devs are just cocky.

--

Enforcing PIE and other nonsense is just not worth when

I run a NSA based intel ivybridge notebook with
intel management engine
intel cpu bug in regards of access and writing to any memory section (fresh bug)
uefi hidden features
nsa based broadcom firmware backdoors (my wifi and ethernet)

The hardware can not be trusted anyway. so not worth using experimental gcc features which most likely breaks software at run time or during compilation.

when you use the gold linker you run in many other issues. kernel also fails to build with gold linker on certain versions. i hardly found any software which was programmed very well.