[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 ? -- 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
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.
Guillaume Gardet wrote:
Hi,
-----Original Message----- From: Per Jessen <per@jessen.ch> Sent: 19 April 2020 10:39
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?
Hi Guillaume 12.48 was not dropped as I had a file named *.old in there - I also had my working DTB in here, and that was gone. The new 12.82 directory only had the openSUSE supplied DTB which does not work (sufficiently well). I was happy when I noticed the 12.48 directory, thinking I can just quickly copy the old DTB over .... -- Per Jessen, Zürich (19.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 22/04/2020 14:38, Per Jessen wrote:
Guillaume Gardet wrote:
Hi,
-----Original Message----- From: Per Jessen <per@jessen.ch> Sent: 19 April 2020 10:39
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?
Hi Guillaume
12.48 was not dropped as I had a file named *.old in there - I also had my working DTB in here, and that was gone.
The new 12.82 directory only had the openSUSE supplied DTB which does not work (sufficiently well).
I was happy when I noticed the 12.48 directory, thinking I can just quickly copy the old DTB over ....
Can you try if you put your custom dtb into /boot/dtb/current/ I suppose this directory does not get overwritten when updating the kernel. Would be nice to get feedback on this :) Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Matthias Brugger wrote:
Can you try if you put your custom dtb into /boot/dtb/current/ I suppose this directory does not get overwritten when updating the kernel.
Would be nice to get feedback on this :)
I'll see what I can do - I have a third nanopi that needs updating, I think. -- Per Jessen, Zürich (15.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Matthias Brugger wrote:
Can you try if you put your custom dtb into /boot/dtb/current/ I suppose this directory does not get overwritten when updating the kernel.
Would be nice to get feedback on this :)
I'll see what I can do - I have a third nanopi that needs updating, I think.
Looking at boot.script from the jeOS image: http://download.opensuse.org/ports/armv7hl/distribution/leap/15.0/appliances.... it does not look at /boot/dtb/current. On my nanopis, I have hardcoded 'fdtfile' = 'sun8i-h3-nanopi-neo-air.dtb', but I see no search order, only one 'ftdfolder' (= /boot/dtb) -- Per Jessen, Zürich (15.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Ah, this board still uses boot.script. We should switch it to standard distro boot, if the board supports it. That way, it will look for all defined folders: https://github.com/openSUSE/u-boot/commit/5637f1acf10c604ef8f25d43eb4d4fa1d6... Cheers, Guillaume
-----Original Message----- From: Per Jessen <per@jessen.ch> Sent: 28 April 2020 12:25 To: opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] keeping multiple kernels on ARM systems ?
Per Jessen wrote:
Matthias Brugger wrote:
Can you try if you put your custom dtb into /boot/dtb/current/ I suppose this directory does not get overwritten when updating the kernel.
Would be nice to get feedback on this :)
I'll see what I can do - I have a third nanopi that needs updating, I think.
Looking at boot.script from the jeOS image:
http://download.opensuse.org/ports/armv7hl/distribution/leap/15.0/appliances /openSUSE-Leap15.0-ARM-JeOS-nanopineo.armv7l-2018.07.02- Buildlp150.1.1.raw.xz.
it does not look at /boot/dtb/current. On my nanopis, I have hardcoded 'fdtfile' = 'sun8i-h3-nanopi-neo-air.dtb', but I see no search order, only one 'ftdfolder' (= /boot/dtb)
-- Per Jessen, Zürich (15.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- 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. N�����r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0�����Ǩ�
participants (3)
-
Guillaume Gardet -
Matthias Brugger -
Per Jessen