Hi guys,
As mentioned in the other thread about new kernel (basically to fix the dccp cve issue), I had a look at the 4.4.x branch, but thought also about a rebase to 4.9.x (also upstream LTS at kernel.org)
For AltArch (centos 7 i386), Johnny built a 4.9.13 kernel and so I reused it for armhfp It also makes sense to rebase to 4.9.x for rpi2/rpi3 as the rpi foundation also rebased to 4.9 and so confirmed to me that they don't maintain 4.4.x (even if they still accept Pull Requests).
So we have now 4.9.13 available for both rpi and generic.
The following /etc/yum.repos.d/testing-kernel.repo would do it :
[kernel-testing] name=CentOS Kernels for armhfp testing baseurl=https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/ enabled=0 gpgcheck=0
[firmware] name=firmware baseurl=https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/ enabled=1 gpgcheck=0
After that a simple yum update --enablerepo=kernel-testing would bring it to the node
For rpi, nothing to be done For the other boards, I've added an update-boot tool to automatically modify extlinux.conf. but you need the updated centos-userland-release pkg : https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-releas...
Worth noting that the actual 4.9.13 will *not* call it in the %post rpm transaction (yet) but if that tool works for everybody, we'll add it for newer kernels.
Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
Cheers,
This is not getting me this new kernel. I am currently running test 4.4.51-201. When I first did a yum update with this testing-kernel.repo added (and the old testing I used for 4.4.51 removed), I got the warning:
centos-kernel | 2.9 kB 00:00 Not using downloaded repomd.xml because it is older than what we have: Current : Sun Feb 26 09:04:27 2017 Downloaded: Thu Feb 16 01:10:20 2017
and then a list of 17 firmware modules to update; 15 iwl firmware and 2 linux-firmware rpms.
So I ran a 'yum clean all'. The date warning went away, but still only the 17 firmware modules. No kernel updates.
On 02/28/2017 04:28 AM, Fabian Arrotin wrote:
Hi guys,
As mentioned in the other thread about new kernel (basically to fix the dccp cve issue), I had a look at the 4.4.x branch, but thought also about a rebase to 4.9.x (also upstream LTS at kernel.org)
For AltArch (centos 7 i386), Johnny built a 4.9.13 kernel and so I reused it for armhfp It also makes sense to rebase to 4.9.x for rpi2/rpi3 as the rpi foundation also rebased to 4.9 and so confirmed to me that they don't maintain 4.4.x (even if they still accept Pull Requests).
So we have now 4.9.13 available for both rpi and generic.
The following /etc/yum.repos.d/testing-kernel.repo would do it :
[kernel-testing] name=CentOS Kernels for armhfp testing baseurl=https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/ enabled=0 gpgcheck=0
[firmware] name=firmware baseurl=https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/ enabled=1 gpgcheck=0
After that a simple yum update --enablerepo=kernel-testing would bring it to the node
For rpi, nothing to be done For the other boards, I've added an update-boot tool to automatically modify extlinux.conf. but you need the updated centos-userland-release pkg : https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-releas...
Worth noting that the actual 4.9.13 will *not* call it in the %post rpm transaction (yet) but if that tool works for everybody, we'll add it for newer kernels.
Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
Cheers,
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 02/28/2017 04:28 AM, Fabian Arrotin wrote:
Hi guys,
As mentioned in the other thread about new kernel (basically to fix the dccp cve issue), I had a look at the 4.4.x branch, but thought also about a rebase to 4.9.x (also upstream LTS at kernel.org)
For AltArch (centos 7 i386), Johnny built a 4.9.13 kernel and so I reused it for armhfp It also makes sense to rebase to 4.9.x for rpi2/rpi3 as the rpi foundation also rebased to 4.9 and so confirmed to me that they don't maintain 4.4.x (even if they still accept Pull Requests).
So we have now 4.9.13 available for both rpi and generic.
The following /etc/yum.repos.d/testing-kernel.repo would do it :
[kernel-testing] name=CentOS Kernels for armhfp testing baseurl=https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/ enabled=0 gpgcheck=0
[firmware] name=firmware baseurl=https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/ enabled=1 gpgcheck=0
After that a simple yum update --enablerepo=kernel-testing would bring it to the node
For rpi, nothing to be done For the other boards, I've added an update-boot tool to automatically modify extlinux.conf. but you need the updated centos-userland-release pkg : https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-releas...
Worth noting that the actual 4.9.13 will *not* call it in the %post rpm transaction (yet) but if that tool works for everybody, we'll add it for newer kernels.
Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
I just tried to install this on a server that is running with 4.4.42-202.
No update to the kernel. Only proposes the 17 firmware files.
So I suspect there is some problem with the date of this update, making it earlier than even 4.4.42-202.
Separate question about kernels.
When I *DO* update to a new kernel, do I have to reboot to be using the new kernel. Or are the new modules/libraries just called in while running? I never did figure this out...
thanks
On 01/03/17 14:21, Robert Moskowitz wrote:
On 02/28/2017 04:28 AM, Fabian Arrotin wrote:
Hi guys,
As mentioned in the other thread about new kernel (basically to fix the dccp cve issue), I had a look at the 4.4.x branch, but thought also about a rebase to 4.9.x (also upstream LTS at kernel.org)
For AltArch (centos 7 i386), Johnny built a 4.9.13 kernel and so I reused it for armhfp It also makes sense to rebase to 4.9.x for rpi2/rpi3 as the rpi foundation also rebased to 4.9 and so confirmed to me that they don't maintain 4.4.x (even if they still accept Pull Requests).
So we have now 4.9.13 available for both rpi and generic.
The following /etc/yum.repos.d/testing-kernel.repo would do it :
[kernel-testing] name=CentOS Kernels for armhfp testing baseurl=https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/
enabled=0 gpgcheck=0
[firmware] name=firmware baseurl=https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/
enabled=1 gpgcheck=0
After that a simple yum update --enablerepo=kernel-testing would bring it to the node
For rpi, nothing to be done For the other boards, I've added an update-boot tool to automatically modify extlinux.conf. but you need the updated centos-userland-release pkg : https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-releas...
Worth noting that the actual 4.9.13 will *not* call it in the %post rpm transaction (yet) but if that tool works for everybody, we'll add it for newer kernels.
Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
I just tried to install this on a server that is running with 4.4.42-202.
No update to the kernel. Only proposes the 17 firmware files.
So I suspect there is some problem with the date of this update, making it earlier than even 4.4.42-202.
Separate question about kernels.
When I *DO* update to a new kernel, do I have to reboot to be using the new kernel. Or are the new modules/libraries just called in while running? I never did figure this out...
thanks
You should verify your yum local metadata/cache, as I confirm that pkgs are there (https://buildlogs.centos.org/centos/7/kernel/armhfp/kernel-generic/Packages/) , and in repodata/metadata. (I updated a cubietruck through that method)
Yes, you of course have to reboot to use new kernel and new modules built/linked to that kernel
ARGH!!!
Look at your sample .repo that I just copied and pasted.
For kernels, you have enabled=0
I colored the line red below.
!!!!
I just did not look at it.
On 03/01/2017 11:00 AM, Fabian Arrotin wrote:
On 01/03/17 14:21, Robert Moskowitz wrote:
On 02/28/2017 04:28 AM, Fabian Arrotin wrote:
Hi guys,
As mentioned in the other thread about new kernel (basically to fix the dccp cve issue), I had a look at the 4.4.x branch, but thought also about a rebase to 4.9.x (also upstream LTS at kernel.org)
For AltArch (centos 7 i386), Johnny built a 4.9.13 kernel and so I reused it for armhfp It also makes sense to rebase to 4.9.x for rpi2/rpi3 as the rpi foundation also rebased to 4.9 and so confirmed to me that they don't maintain 4.4.x (even if they still accept Pull Requests).
So we have now 4.9.13 available for both rpi and generic.
The following /etc/yum.repos.d/testing-kernel.repo would do it :
[kernel-testing] name=CentOS Kernels for armhfp testing baseurl=https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/
enabled=0 gpgcheck=0
[firmware] name=firmware baseurl=https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/
enabled=1 gpgcheck=0
After that a simple yum update --enablerepo=kernel-testing would bring it to the node
For rpi, nothing to be done For the other boards, I've added an update-boot tool to automatically modify extlinux.conf. but you need the updated centos-userland-release pkg : https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-releas...
Worth noting that the actual 4.9.13 will *not* call it in the %post rpm transaction (yet) but if that tool works for everybody, we'll add it for newer kernels.
Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
I just tried to install this on a server that is running with 4.4.42-202.
No update to the kernel. Only proposes the 17 firmware files.
So I suspect there is some problem with the date of this update, making it earlier than even 4.4.42-202.
Separate question about kernels.
When I *DO* update to a new kernel, do I have to reboot to be using the new kernel. Or are the new modules/libraries just called in while running? I never did figure this out...
thanks
You should verify your yum local metadata/cache, as I confirm that pkgs are there (https://buildlogs.centos.org/centos/7/kernel/armhfp/kernel-generic/Packages/) , and in repodata/metadata. (I updated a cubietruck through that method)
On 01/03/17 17:53, Robert Moskowitz wrote:
ARGH!!!
Look at your sample .repo that I just copied and pasted.
For kernels, you have enabled=0
I colored the line red below.
!!!!
I just did not look at it.
Yes, and I did that for a good reason ... Also reason why the line after was "yum update --enablerepo=kernel-testing" ... ;-)
On 03/01/2017 12:25 PM, Fabian Arrotin wrote:
On 01/03/17 17:53, Robert Moskowitz wrote:
ARGH!!!
Look at your sample .repo that I just copied and pasted.
For kernels, you have enabled=0
I colored the line red below.
!!!!
I just did not look at it.
Yes, and I did that for a good reason ... Also reason why the line after was "yum update --enablerepo=kernel-testing" ... ;-)
That's what I get for doing it when tired. I did not read the embedded yum command
update in, and fixed the boot with:
sed -i -e s/4.4.51-201/4.9.13-203/g /boot/extlinux/extlinux.conf
Really have to figure out how to have a menu so that *IF* the new kernel does not boot, I can fallback...
hmmm. Got an idea.
Anyway, my mailserver test system is up on the new kernel. If it stays up, I will move on to my production systems...
Bob
Il 28/02/2017 10:28, Fabian Arrotin ha scritto:
Hi guys,
[...] Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
updated yesterday from kernel-4.4.41-v7.1.el7 on a rpi3 with wifi enabled. I admit that i have not done a deep search in the logs but so far all is working correctly tnx
On 03/01/2017 12:46 PM, dz00te wrote:
Il 28/02/2017 10:28, Fabian Arrotin ha scritto:
Hi guys,
[...] Any feedback is welcome, but for the kernel I'd like to push that asap to signing/release (so the more feedback, the faster we'll have it released) ;-)
updated yesterday from kernel-4.4.41-v7.1.el7 on a rpi3 with wifi enabled.
That is my one complaint on the CubieTruck uboot. They never got the embedded wifi and bluetooth working.
Well that and it is only a duo core, at some point I am going to have to get a Cubie5.
I admit that i have not done a deep search in the logs but so far all is working correctly
-
dz00te -
Fabian Arrotin -
Robert Moskowitz