BG405 wrote: ⤴
Wed Jul 04, 2018 10:37 am
From the OP's signature: Windows 7 x64 ... & no mention of Linux
.. for someone who likes to be in control, what happens when support ends?
I might have read it wrong, but it looks like the OP is trying to reinstall stuff backed up from a 16.04 base, on to an 18.04 base.
Why not reinstall the kernel that worked & use that?
Otherwise, good luck with Arch and its "5th update"!
1. I changed the signature to Windows after Mint 19 forced me to install something I don't want.
2. Nothing of the kind. It was a clean install of Mint 19 ISO.
3. 19 seems to install with 4.15 and there is no way to install 4.13.
4. I found a way (finally, after several attempts on a VM) to trick 19 not to install the microcode. For unknown reason right after the welcome screen appears, if the user doesn't take any action the update started automatically in a few minutes. So when the installation was finished, I loaded the boot menu, pulled the LAN cable and booted the HDD with Linux. I did that to prevent it from updating. Then checked every new package carefully and if it contained the words kernel, header and microcode, I put it in the blacklist. Then allowed the update process to continue and now that there is no microcode, there's no black screen or emergency mode and Mint works as it should.
And just because I found a way to disable kernel update, I still don't think it's right to force users to install the microcode. Idk about other people but I for one don't wanna destroy my CPU with microcode. Linux has never needed a CPU microcode for it to run, so to me it's useless plus I read some articles saying the microcode could damage the CPU which is the other reason I don't want it.