Hi,
-----Original Message----- From: Per Jessen <per@jessen.ch> Sent: 19 April 2020 10:39 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] keeping multiple kernels on ARM systems ?
(repost from opensuse@o.o) I'm sure many have this feature enabled, just in case. Keeping multiple kernels and module versions around.
On one of my ARM systems, yesterday I ran an update "zypper patch" (Leap 15.0), which installed a new kernel 4.12.14-lp150.12.82-lpae, the old one being 4.12.14- lp150.12.48-lpae.
Both initrds were rebuilt, I have two kernels, two sets of modules - but my dtb was cleared out: /boot/dtb-4.12.14-lp150.12.48/ - empty apart from one file I had renamed to .old.
I use my own DTB, but this did not prevent the system from booting, instead it did stop the network from coming up (wifi device not correctly defined in the openSUSE supplied DTB). I had to climb some 10meters up a ladder to retrieve the box, disassemble it and put a serial console on it :-)
Question - the multiple kernels feature ought to have retained my dtb directory contents in /boot/dtb-4.12.14-lp150.12.48/ ? Or not ?
AFAIK, there is no multiversion support for DTB. And DTB should even be kernel version agnostic, but I know this is not really the case. Your /boot/dtb-4.12.14-lp150.12.48/ folder should have been dropped (if there was no *.old file inside) and a new /boot/dtb-4.12.14-lp150.12.82/ should have been created with the update of your DTB package. Is it missing? Cheers, Guillaume
-- Per Jessen, Zürich (17.3°C)
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.