Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
Best regards, Thorsten
El 3/3/19 a las 12:24, Thorsten Holtkämper escribió:
Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
That looks bad!!!, you may even end up removing your current kernel. The sort -V seems to do what we need to, but this will be a problem until the last 4.14.xx is removed from the system. I'll try to build a new kernel later today, so we can start testing this.
Thanks for the report. Pablo.
Best regards, Thorsten
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
El 3/3/19 a las 13:24, Pablo Sebastián Greco escribió:
El 3/3/19 a las 12:24, Thorsten Holtkämper escribió:
Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
That looks bad!!!, you may even end up removing your current kernel. The sort -V seems to do what we need to, but this will be a problem until the last 4.14.xx is removed from the system. I'll try to build a new kernel later today, so we can start testing this.
Thanks for the report. Pablo.
Best regards, Thorsten
Just pushed a build with these changes https://git.stg.centos.org/rpms/raspberrypi2/c/94eb3c3ad1e3828a885cf5e5178fc...
When it finishes, it should appear here https://buildlogs.centos.org/c7-kernels.armhfp/raspberrypi2/ (it should be in a few hours)
Let me know if you can test and how it went.
Thanks.
Pablo.
Am 3. März 2019 18:15:37 schrieb Pablo Sebastián Greco pablo@fliagreco.com.ar:
El 3/3/19 a las 13:24, Pablo Sebastián Greco escribió:
El 3/3/19 a las 12:24, Thorsten Holtkämper escribió:
Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
That looks bad!!!, you may even end up removing your current kernel. The sort -V seems to do what we need to, but this will be a problem until the last 4.14.xx is removed from the system. I'll try to build a new kernel later today, so we can start testing this.
Thanks for the report. Pablo.
Best regards, Thorsten
Just pushed a build with these changes https://git.stg.centos.org/rpms/raspberrypi2/c/94eb3c3ad1e3828a885cf5e5178fc...
When it finishes, it should appear here https://buildlogs.centos.org/c7-kernels.armhfp/raspberrypi2/ (it should be in a few hours)
Let me know if you can test and how it went.
I could do some testing, but there is no new kernel at the given URL.
BR, Thorsten
Thanks.
Pablo. _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 05-Mar-19 00:15, Thorsten Holtkämper wrote:
Am 3. März 2019 18:15:37 schrieb Pablo Sebastián Greco pablo@fliagreco.com.ar:
El 3/3/19 a las 13:24, Pablo Sebastián Greco escribió:
El 3/3/19 a las 12:24, Thorsten Holtkämper escribió:
Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
That looks bad!!!, you may even end up removing your current kernel. The sort -V seems to do what we need to, but this will be a problem until the last 4.14.xx is removed from the system. I'll try to build a new kernel later today, so we can start testing this.
Thanks for the report. Pablo.
Best regards, Thorsten
Just pushed a build with these changes https://git.stg.centos.org/rpms/raspberrypi2/c/94eb3c3ad1e3828a885cf5e5178fc...
When it finishes, it should appear here https://buildlogs.centos.org/c7-kernels.armhfp/raspberrypi2/ (it should be in a few hours)
Let me know if you can test and how it went.
I could do some testing, but there is no new kernel at the given URL.
It's there, now.
BR
BR, Thorsten
Thanks.
Pablo. _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
<snip>
I could do some testing, but there is no new kernel at the given URL.
It's there, now.
BR
We had to rebuild several times, and add some extra fixes. In the typical case where you "add one, remove one" kernel, the %postun was being run after the %postin for the new one, and left the system with an older kernel running. We moved the %postin to %posttrans to fix this.
Pablo.
Hi Thorsten,
Thanks for the report. I'm the guy that originally wrote these lines ... I always knew that this issue was present, but was not aware of the '-V' option to sort. Therefore I never had a quick fix. I hoped that somebody would extend the "installkernel" script from grubby, so that it also works for raspberries. I don't think that will happen any more. Maybe we should have a look at how this works on raspbian.
@Pablo, I successfully tested building 4.19.27 from upstream. There are some minor changes: - github now gives error 500 on the files we normally use - the COPYING.linux file changed, so it needed a new location - the patch for selinux needed to be remade.
If interested, my patches and spec can be found here: https://github.com/redsleeve-linux/raspberrypi/tree/master/raspberrypi2
Jacco
On 3/3/19 4:24 PM, Thorsten Holtkämper wrote:
Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
Best regards, Thorsten
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
El 9/3/19 a las 14:52, Jacco Ligthart escribió:
Hi Thorsten,
Thanks for the report. I'm the guy that originally wrote these lines ... I always knew that this issue was present, but was not aware of the '-V' option to sort. Therefore I never had a quick fix. I hoped that somebody would extend the "installkernel" script from grubby, so that it also works for raspberries. I don't think that will happen any more. Maybe we should have a look at how this works on raspbian.
@Pablo, I successfully tested building 4.19.27 from upstream. There are some minor changes:
Good, It is in my to-do list, currently working on the other alternate kernels, that was next.
- github now gives error 500 on the files we normally use
Yeap, I've been bitten by that one, I think it is a problem in the github repo
- the COPYING.linux file changed, so it needed a new location
- the patch for selinux needed to be remade.
Ack
If interested, my patches and spec can be found here: https://github.com/redsleeve-linux/raspberrypi/tree/master/raspberrypi2
Sure, I intend to keep updating the 4.14.x (with 4.19.x as an alternate) until CentOS 7.7 comes out, and then make the switch to 4.19.
Jacco
Thanks. Pablo.
On 3/3/19 4:24 PM, Thorsten Holtkämper wrote:
Hi all,
kernel upgrades on the raspi sometimes end up with not the latest kernel being "activated" in the /boot directory. The reason for this is the kernel rpm postuninstall script of the old kernel that is removed:
postuninstall scriptlet (using /bin/sh): cp $(ls -1 /boot/kernel-*-*|tail -1) /boot/kernel7.img cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/*.dtb /boot/ cp $(ls -1d /usr/share/raspberrypi2-kernel/*-*/|tail -1)/boot/overlays/*.dtb* /boot/overlays/
It chooses the latest kernel version with "ls -1 /boot/kernel-*-*|tail -1" which fails for kernel versions that have different number of digits in the version string, e.g. 4.9 and 4.14 or 4.14.91 and 4.14.103.
An additional "sort -V" should fix the problem, i.e. "ls -1 /boot/kernel-*-*|sort -V|tail -1".
What do you think?
Best regards, Thorsten
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
been a while since that topic came up, but is there a centos 64 bit version for the Raspberrypi 3(b) ?
thanks,
Ron
If anyone need perfection, Simply NO.
On Wed, Mar 13, 2019 at 7:00 AM R C cjvijf@gmail.com wrote:
been a while since that topic came up, but is there a centos 64 bit version for the Raspberrypi 3(b) ?
thanks,
Ron
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Not much going on here (at least on my part), and sadly not a high priority, but it would be nice to have. I know the Fedora guys are working on the whole uboot/efi stuff, so it should be easier there. Once they have everything working in Fedora, it should be easier for us to backport, like we did in the past with much of the armhfp stuff.
Pablo
El 16/3/19 a las 05:31, Nick Howitt escribió:
What do you get if you don't need perfection? Also there was a post about UEFI firmware ported to Pi 3/3B+ platforms. Does this achieve anything to help? I saw someone else posted about trying to create an aarch64 EFI bootable iso but no one was able to respond.
Regards,
Nick
On 15/03/2019 16:03, Sayduzzaman Mohammad wrote:
If anyone need perfection, Simply NO.
On Wed, Mar 13, 2019 at 7:00 AM R C <cjvijf@gmail.com mailto:cjvijf@gmail.com> wrote:
been a while since that topic came up, but is there a centos 64 bit version for the Raspberrypi 3(b) ? thanks, Ron _______________________________________________ Arm-dev mailing list Arm-dev@centos.org <mailto:Arm-dev@centos.org> https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
ah, cool...
Well I work quite a bit with RHEL, Centos and some derivatives.. would be nice to have 64-bit version of Centos 7 for the raspberrypi3b+
Ron On 3/16/19 7:26 AM, Pablo Sebastián Greco wrote:
Not much going on here (at least on my part), and sadly not a high priority, but it would be nice to have. I know the Fedora guys are working on the whole uboot/efi stuff, so it should be easier there. Once they have everything working in Fedora, it should be easier for us to backport, like we did in the past with much of the armhfp stuff.
Pablo
El 16/3/19 a las 05:31, Nick Howitt escribió:
What do you get if you don't need perfection? Also there was a post about UEFI firmware ported to Pi 3/3B+ platforms. Does this achieve anything to help? I saw someone else posted about trying to create an aarch64 EFI bootable iso but no one was able to respond.
Regards,
Nick
On 15/03/2019 16:03, Sayduzzaman Mohammad wrote:
If anyone need perfection, Simply NO.
On Wed, Mar 13, 2019 at 7:00 AM R C <cjvijf@gmail.com mailto:cjvijf@gmail.com> wrote:
been a while since that topic came up, but is there a centos 64 bit version for the Raspberrypi 3(b) ? thanks, Ron _______________________________________________ Arm-dev mailing list Arm-dev@centos.org <mailto:Arm-dev@centos.org> https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
i am also looking for exactly 64-bit version of Centos 7 for the raspberrypi3b+
On Sun, Mar 17, 2019 at 6:57 AM R C cjvijf@gmail.com wrote:
ah, cool...
Well I work quite a bit with RHEL, Centos and some derivatives.. would be nice to have 64-bit version of Centos 7 for the raspberrypi3b+
Ron On 3/16/19 7:26 AM, Pablo Sebastián Greco wrote:
Not much going on here (at least on my part), and sadly not a high priority, but it would be nice to have. I know the Fedora guys are working on the whole uboot/efi stuff, so it should be easier there. Once they have everything working in Fedora, it should be easier for us to backport, like we did in the past with much of the armhfp stuff.
Pablo El 16/3/19 a las 05:31, Nick Howitt escribió:
What do you get if you don't need perfection? Also there was a post about UEFI firmware ported to Pi 3/3B+ platforms. Does this achieve anything to help? I saw someone else posted about trying to create an aarch64 EFI bootable iso but no one was able to respond.
Regards,
Nick
On 15/03/2019 16:03, Sayduzzaman Mohammad wrote:
If anyone need perfection, Simply NO.
On Wed, Mar 13, 2019 at 7:00 AM R C cjvijf@gmail.com wrote:
been a while since that topic came up, but is there a centos 64 bit version for the Raspberrypi 3(b) ?
thanks,
Ron
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing listArm-dev@centos.orghttps://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing listArm-dev@centos.orghttps://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing listArm-dev@centos.orghttps://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-
Jacco Ligthart -
Nick Howitt -
Pablo Sebastián Greco -
R C -
Sayduzzaman Mohammad -
Stephan GUILLOUX -
Thorsten Holtkämper