cannot boot after latest updates

I updated my PC (HP Z210) with the latest updates, including the kernel, grub2 & the Intel microcode. Now it won’t boot.

I’m getting the message ‘Base address is zero, assuming no IPMI interface’ and nothing further.

It (now) also won’t boot to my openSUSE Leap 15.1 Gnome live USB stick (that worked before) but will boot to my Knoppix 7.7.1 USB stick.

I’ve fsck’ed the boot & root partitions - clean.

Any advice on how to get this booting again to the installed OS Leap 15.1?

Thanks
David

this is post-grub & during the linux init process. This exact sequence of messages is:

Booting 'openSUSE Leap 15.1'   <--- grub

Loading Linux 4.12.14-lp151.28.79-default ...
Loading initial ramdisk ...
    0.172993] Base address is zero, assuming no IPMI interface

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?

Are you booting UEFI or Legacy BIOS?

Is secure boot turned on? try it turned off.

How old is the Knoppix?

Can you try a Gecko Linux image (they are OpenSUSE 15.2 based) https://geckolinux.github.io/ try the static version - it is 15.2 based

xfce and mate are the smallest and look like the old Windows Vista desktop. Those images boot fine UEFI or Legacy BIOS like Knoppix.

49 months, but younger than his Sandy Bridge HP.

@jetojedno:

  1. Have you checked that the UEFI/BIOS is OK?
  2. 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.

Answers: SSD HD, 32GB RAM, no EFI (legacy boot), NVIDA GFX card / GPU

For anyone who has similar troubles:

  • 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. :slight_smile:

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.

IPMI is not needed. Disable it in BIOS.