[fedora-arm] Android chroot - FATAL: kernel too old

[Samuel Rakitničan]

Dear list,

Just experienced a failed upgrade from Fedora 24 to Fedora 25 in a chroot environment on a android tablet. From what I understand these are coming from glibc not supporting specific android kernel. Not sure if there is something that can be done, but at least I am making a note about it.

Tablet is using Android 4.0.3 and uname -r gives "3.0.8+".

Best regards,

Samuel Rakitničan
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscrib

[Peter Robinson]

On 6 May 2017 14:57, "Samuel Rakitničan" <***@fedoraproject.org>
wrote:

Dear list,

Just experienced a failed upgrade from Fedora 24 to Fedora 25 in a chroot
environment on a android tablet. From what I understand these are coming
from glibc not supporting specific android kernel. Not sure if there is
something that can be done, but at least I am making a note about it.

Tablet is using Android 4.0.3 and uname -r gives "3.0.8+".


You'll need, from memory, at least a 3.6.x kernel due to systemd cgroups
requirements (and there could be other reasons too i don't remember). But
that isn't a new req, it's been around since ~ F22.

Sorry but you're very much on your own for kernels this ancient, most
android are on 3.18.x and they do 'work' to at least some level of work.

[Samuel Rakitničan]

Post by Peter Robinson
You'll need, from memory, at least a 3.6.x kernel due to systemd cgroups
requirements (and there could be other reasons too i don't remember). But
that isn't a new req, it's been around since ~ F22.

So in a chroot systemd is not running as there is no dbus running either.

Post by Peter Robinson
Sorry but you're very much on your own for kernels this ancient, most
android are on 3.18.x and they do 'work' to at least some level of work.

Umm then seems like all of my devices uses ancient kernels. Smartphone uses 3.4.5.

I particularly don't need any advanced features, as long as it works I am happy. This particular "feature" breaks the system entirely because any program that relies on glibc fails.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fe

[Samuel Rakitničan]

So, it appears that minimum requirement for glibc 2.24 that Fedora 25 uses is kernel 3.2, that would explain why my tablet fails.

[1] https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@list

[Peter Robinson]

On Sun, May 7, 2017 at 5:13 PM, Samuel Rakitničan

Post by Samuel Rakitničan
So, it appears that minimum requirement for glibc 2.24 that Fedora 25 uses is kernel 3.2, that would explain why my tablet fails.

Yep, and given it was released over 5 years ago I don't see that as
too arduous a requirement given some functionality already requires
3.6

Post by Samuel Rakitničan
[1] https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html
_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to a