I don't really trust any of the equipment I use. It's essential for me nonetheless.

And we stupidly and willingly followed the breadcrumbs because we were so entranced by all the toys . . .

I beg to disagree. The "essentials" are food, water and hopefully shelter. All the toys we play with are just the products of churning, deluded minds. And what a mess we make of it!

OK. I promise not to talk about AI use at all.
In return, please don't ask how I got the results that fast.... ;-)

I don't trust any AI, I try to use my Brain 1.0.

Who talked about trusting AI?
I don't really trust any of the equipment I use. It's essential for me nonetheless.

I think using AI is essential . . .

I beg to disagree. The "essentials" are food, water, air and hopefully shelter. All the toys we play with are just the products of churning, deluded minds. And what a mess we make of it!

I think using AI is essential, ...

I don't trust any AI, I try to use my Brain 1.0.

I think using AI is essential, but I have already seen several examples of such rabbit holes. We maybe could think of the current language models as generating advice not out of understanding but as good guesses of what knowledgeable persons could say. Therefore, we have to test at every step, only keeping modifications that make a difference - preferably understandable to us ;-)

A very warm welcome to you, to the worldwide community that is Linux! And most especially to Devuan which for 10 years running has been the best of Linux'es in my humble opinion. And kudos for a very innovative way to use AI to ease the transition too, nice work all around!

Still learning, but I'm glad I checked the logs. I'll revert the blacklist file now."

Indeed, that is what I understood.

Blacklisting probably has the added effect of keeping rogue agents from doing it.

Best,

A.

I discovered the intel-microcode was being blacklisted by default. Removing the intel-microcode-blacklist.conf was essential for CPU stability

Pretty sure that's not how that works, I believe it's there to stop the microcode from trying to update itself on every boot. But I could be wrong.

https://www.reddit.com/r/debian/comment … acklisted/

https://salsa.debian.org/kernel-team/li … config#L42

This is with the blacklist.conf file still in place:

root@devuan:/home/jack# dmesg | grep "microcode updated early to"
[    3.943872] microcode: microcode updated early to new patch_level=0x05000119

You can see it's been applied in early stage boot despite the blacklist file.

Don't believe everything AI tells you.

Can anyone confirm?

Essentially it's baked into initramfs alongside the other firmware, when you install new firmware the system runs update-initramfs and gens a new initrd.img, so the code is there and gets applied early in boot. The blacklist just stops subsequent attempts to update.

At least that's my understanding of it.