On Fri, Feb 23, 2018 at 12:19:43PM +0000, Peter Robinson wrote:
> >
> > I've upgraded to kernel-4.15.3-300.fc27.aarch64 which landed in Fedora
> > 27 repos but the wired networking / DHCP still do not work with that
> > kernel.
> >
> > I don't have serial console to do interactive troubleshooting so
> > I don't really know what is happening there ... checking the journal
> > after I've rebooted back to 4.13.9-300.fc27.aarch64, there does not
> > even seem to be a record of boot into that 4.15.3, so the problem
> > likely isn't the networking at all -- the kernel simply does not boot.
>
> So 4.15.x has been solid for me on my two Pine64s which is the same
> SoC without the network issues I saw with 4.14.
>
> I can't even begin to debug it further, I'm sorry but if you're flying
> blind without a console I have zero ability to use telepathy to try
> and magically guess at the issues.
I understand.
To investigate some more, I flashed
Fedora-Minimal-Rawhide-20180220.n.0.aarch64.raw.xz with
kernel-4.16.0-0.rc2.git0.1.fc28.aarch64 and it boots and DHCPs fine.
I then flashed back Fedora-Minimal-27-1.6.aarch64.raw.xz and then
installed kernel{,-core,-modules}-4.16.0-0.rc2.git0.1.fc28.aarch64.rpm
(and of course updated /boot/dtb). After reboot, things do not work.
So then I've replaced the
/boot/initramfs-4.16.0-0.rc2.git0.1.fc28.aarch64.img which was
generated during the package installation (file size 18841270) with
the file from the Fedora-Minimal-Rawhide-20180220.n.0.aarch64.raw.xz
install (file size 52326700).
I've rebooted and things work.
So the problem seems to be the initramfs produced during package
installation, rather than the kernel per se.
In your tests with Pine64, do you do kernel rpm installations?
--
Jan Pazdziora
Senior Principal Software Engineer, OpenShift Security Team, Red Hat
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
