I agree, but don't tell me I'm on the block list like we're friends. I don't care about you and you don't care for me. No love lost. BOTTOM LINE!!!!!

4.19.0 is working fine for me so far on 14.2 (64 bit). I'm looking forward to getting back to an LTS kernel, since the latest issues of the 4.4 series through 4.14 were causing trouble with this machine. I'll be sure to post if I run into any problems.

1 members found this post helpful.

Now we can continue like civil adults. I don't hold grudges so lets move on.

I believe 32bit is the issue.

Patrick has now switched -current to 4.19, including 32 bit.

I'll continue with 4.18 until it's EOL, but really, the official 4.19 kernels are what people should use from now on, and I'll cease to offer 4.19.

Mr Chyld, the build problem is fundamentally a gcc-8.2.0 bug (nothing to do with the kernel per se), and the acceptable solution space is that the 'dusk' builds must be reproducible by anybody on a clean up-to-date installation of -current. But that's no longer relevant.

2 members found this post helpful.

4.19 ?

CONFIG_CRYPTO_SPECK=m

echo blacklist speck > /etc/modprobe.d/speck.conf

https://www.google.com/search?q="speck+kernel+module"

Ok. Thanks for your other builds.

1 members found this post helpful.

Maybe also post that in the requests in --current thread too?

Might it have anything to do with this news story?

https://www.phoronix.com/scan.php?pa...-Die-Speck-Die

Many thanks for all your hard work.
It is truly appreciated.
Both your 4.19 and Mr. Volkerding's 4.19 kernels have worked flawlessly.... so far.

the new kernel-4.19.0 performs perfectly well here, much better than the first 4.14.x ones.

1 members found this post helpful.

I see no reason for the Speck module to not be built. The use case for it is machines with CPUs that are so weak that the alternative to using Speck is not using encryption at all. Anyway, my understanding is that there's no need to blacklist it. It won't be used for anything unless the admin configures its use, and I don't believe anything currently wants to make use of it. There were plans to make it an option for dm-crypt, but it seems that's been abandoned.

If the upstream kernel developers choose to remove support for it, that would be fine by me. But I'm not likely to veto it here.

1 members found this post helpful.

That they have,

Please see the link in post #969, above.

2 members found this post helpful.

4.19 works fine here, Pat and his crew does a great job building slackware.

i mentioned the speck thing to raise awareness of the government wanting to insert things in to software and the NSA is the biggest snoops in the world, i read where the NSA approached Linus Torvalds about putting a back door in the kernel and Torvalds rejected the idea, and then things like this keep popping up like that little chip that china installs in computer motherboards for spying, it seems there is no getting away from various governments around the world wanting to snoop, and china has no problem stealing other people's ideas and using them to under sell competition so it might be a good idea to use a PC that is not connected to the internet in any way for designing any products you want to manufacture and sell otherwise you might find chinese knock-offs that look suspiciously a lot like your's for sale on amazon.com

1 members found this post helpful.

They do it anyway and have for years, long before anyone had heard of the Internet.
I once had the opportunity to talk to the inventor of a clever device used by just about every desktop computer. Among other things, I asked how he was doing financially. He replied that he was spending every cent paying lawyers to defend his copyright and it was a losing battle.
There is a large company in the U.S., located in the State of Washington, who has been known to steal an idea from another company, usually much smaller company, and then almost drive the smaller company out of business by burdening them with legal fees.
Greed knows no bounds or borders.

2 members found this post helpful.