What you posted isn’t much to go on. Are you using an SSD, or a HDD for booting the installed system? It should have some impact on the times in dmesg, affecting where any particular messages may appear in the init process.
I looked in dmesg on an Intel PC and an AMD PC and couldn’t find string IPMI on either. Maybe it’s specific to your older Intel CPU or IGP? Can you find it booted to Knoppix?
Do you find acpi anywhere on your kernel cmdline for any of the three distros?
Have you tried any of Grub’s advanced boot options?
Does an openSUSE Leap Installation
USB or DVD boot? 1. From an Installation
USB or DVD – does running a Filesystem Check form the Rescue System on the Installation medium find anything?
Hi, apologies for long silence. It’s been a bast*rd of a week.
Thanks for your questions - they pointed me towards the right answer, once I’d been distracted from looking in the wrong place. Defect was a bad initrd following a dkms module build.
add nosplash debug to the grub boot line and delete splash, splash=* and quiet, if found. This is best done editing (e) from the grub boot menu
check boot log. The giveaway in mine was the start of the dracut initqueue hook followed many seconds later by dracut-initqueue timeouts
boot from a newly downloaded latest live USB stick for the same OS distribution (15.1 in my case), using UEFI boot, & do the normal mounts & chroot to get back into your system
remove, build & install the kernel modules
mkinitrd -i initrd-<version> -k vmlinuz-<version> & check there are no errors. These names should match the existing files in /boot
reboot & keep fingers crossed.
Thanks again
David
p.s. yes, I know it’s an old box. But it works. Upgrade is for when I have £500 & a day free which can’t be used for something better. That hasn’t been true ever during the past year.