Hey All,
Is it safe to allow the 193 series kernel update now? Last time I tried
that my system refused to boot. I had to roll back to the 4.18.0-147
kernel to get my machine to reboot.
Since that happened I've been watching this mail list for
acknowledgement that the problem has been corrected while refusing the
kernel update. I may have missed the announcement that the issue was
resolved and the the update is now approved.
--
_
?v?
/(_)\
^ ^ Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/
****
I was successful in installing the latest updates on a Supermicro X10SRL-F motherboard with an E5-2630L v4 CPU that uses UEFI for boot. On Thu, Aug 13, 2020 at 9:24 PM Mark LaPierre <marklapier at gmail.com> wrote:> > Hey All, > > Is it safe to allow the 193 series kernel update now? Last time I tried > that my system refused to boot. I had to roll back to the 4.18.0-147 > kernel to get my machine to reboot. > > Since that happened I've been watching this mail list for > acknowledgement that the problem has been corrected while refusing the > kernel update. I may have missed the announcement that the issue was > resolved and the the update is now approved. > > -- > _ > ?v? > /(_)\ > ^ ^ Mark LaPierre > Registered Linux user No #267004 > https://linuxcounter.net/ > **** > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
On 8/14/20 12:23 AM, Mark LaPierre wrote:> Hey All, > > Is it safe to allow the 193 series kernel update now?? Last time I tried > that my system refused to boot.? I had to roll back to the 4.18.0-147 > kernel to get my machine to reboot. > > Since that happened I've been watching this mail list for > acknowledgement that the problem has been corrected while refusing the > kernel update.? I may have missed the announcement that the issue was > resolved and the the update is now approved. >Well, I let the kernel up date run. I haven't allowed the machine to reboot yet, but that's going to happen just after I send this. At the moment I'm running 4.18.0-147.8.1.el8_1.x86_64 #1 SMP -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****
On 8/13/20 11:23 PM, Mark LaPierre wrote:> Hey All, > > Is it safe to allow the 193 series kernel update now?? Last time I tried > that my system refused to boot.? I had to roll back to the 4.18.0-147 > kernel to get my machine to reboot. > > Since that happened I've been watching this mail list for > acknowledgement that the problem has been corrected while refusing the > kernel update.? I may have missed the announcement that the issue was > resolved and the the update is now approved. >It 'SHOULD' be good. We announced it over the same weekend it was broken. That does not mean every single combination of firmware, hardware, etc on every possible machine frm every manufacturer will work. But, we have had no reports of failure since the updates. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20200817/59ee113c/attachment.sig>
At 07:11 AM 8/17/2020, you wrote:>On 8/13/20 11:23 PM, Mark LaPierre wrote: > > Hey All, > > > > Is it safe to allow the 193 series kernel update now?? Last time I tried > > that my system refused to boot.? I had to roll back to the 4.18.0-147 > > kernel to get my machine to reboot. > > > > Since that happened I've been watching this mail list for > > acknowledgement that the problem has been corrected while refusing the > > kernel update.? I may have missed the announcement that the issue was > > resolved and the the update is now approved. > > > >It 'SHOULD' be good. We announced it over the same weekend it was broken. > >That does not mean every single combination of firmware, hardware, etc >on every possible machine frm every manufacturer will work. But, we >have had no reports of failure since the updates.Ummmm.............. except for apple hardware. My Mac-mini runs just file as long as this text: exclude=grub2* shim* mokutil is added to the end of the file /etc/yum.conf and executing yum -y update and rebooting works just fine. HOWEVER, if I remove that 'exclude' line from yum.conf, run 'yum update', and then reboot, the system is unbootable. I end up with a blank screen, no grub anything. I have also been unable to recover from this. Therefore, that exclude line stays. I'm sorry about the delay in responding; I wanted to verify this on a 'crash-and-burn' MacMini. David
Mark LaPierre
2020-Aug-20 02:44 UTC
[CentOS] CentOS 8 kernel-4.18.0-193 shim issue(SOLVED) at least for me
On 8/14/20 12:23 AM, Mark LaPierre wrote:> Hey All, > > Is it safe to allow the 193 series kernel update now?? Last time I tried > that my system refused to boot.? I had to roll back to the 4.18.0-147 > kernel to get my machine to reboot. > > Since that happened I've been watching this mail list for > acknowledgement that the problem has been corrected while refusing the > kernel update.? I may have missed the announcement that the issue was > resolved and the the update is now approved. >I ran the update and did the reboot last night. It was too late for me to report the results then. Thank you to the CentOS Team. Y'all are awesome. -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****