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 ? -- Per Jessen, Zürich (15.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org