<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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:<br>
<br>
centos-kernel | 2.9
kB 00:00 <br>
Not using downloaded repomd.xml because it is older than what we
have:<br>
Current : Sun Feb 26 09:04:27 2017<br>
Downloaded: Thu Feb 16 01:10:20 2017<br>
<br>
and then a list of 17 firmware modules to update; 15 iwl firmware
and 2 linux-firmware rpms.<br>
<br>
So I ran a 'yum clean all'. The date warning went away, but still
only the 17 firmware modules. No kernel updates.<br>
<br>
<div class="moz-cite-prefix">On 02/28/2017 04:28 AM, Fabian Arrotin
wrote:<br>
</div>
<blockquote
cite="mid:d91c4513-db52-db44-6b08-12fcaee688fc@centos.org"
type="cite">
<pre wrap="">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=<a class="moz-txt-link-freetext" href="https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/">https://buildlogs.centos.org/centos/7/kernel/$basearch/kernel-$kvariant/</a>
enabled=0
gpgcheck=0
[firmware]
name=firmware
baseurl=<a class="moz-txt-link-freetext" href="https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/">https://armv7.dev.centos.org/repodir/arm-kernels/linux-firmware-20170213/</a>
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 :
<a class="moz-txt-link-freetext" href="https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-release/7-3.1611.el7.centos.0.2/armv7hl/centos-userland-release-7-3.1611.el7.centos.0.2.armv7hl.rpm">https://armv7.dev.centos.org/repodir/c71611-updates-1/centos-userland-release/7-3.1611.el7.centos.0.2/armv7hl/centos-userland-release-7-3.1611.el7.centos.0.2.armv7hl.rpm</a>
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,
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Arm-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/arm-dev">https://lists.centos.org/mailman/listinfo/arm-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>