Roughly a month ago I upgraded the kernel on my wandboard quad. The quad had been running kernel 4.17.19-200.fc28.armv7hl and was working properly.
However, when I upgraded to kernel 4.18.5-200.fc28.armv7hl I found that ethernet no longer worked. I reverted to kernel 4.17.19-200.fc28.armv7hl and ethernet was fine again.
I've tried several kernels since then, including the latest (4.18.13-200.fc28.armv7hl), with the same negative result.
When running kernel 4.18.13-200.fc28.armv7hl the console messages say that the link is up, however I am not able to ping anything on the local subnet.
I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1628209
Does anyone know of any driver changes that might account for this bug?
Steve
Hi Steve,
We've been looking at this for a while but have not been able to work out the issue.
Thanks for filing the bug, I'll leave some additional info there.
Paul
----- Original Message -----
Roughly a month ago I upgraded the kernel on my wandboard quad. The quad had been running kernel 4.17.19-200.fc28.armv7hl and was working properly.
However, when I upgraded to kernel 4.18.5-200.fc28.armv7hl I found that ethernet no longer worked. I reverted to kernel 4.17.19-200.fc28.armv7hl and ethernet was fine again.
I've tried several kernels since then, including the latest (4.18.13-200.fc28.armv7hl), with the same negative result.
When running kernel 4.18.13-200.fc28.armv7hl the console messages say that the link is up, however I am not able to ping anything on the local subnet.
I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1628209
Does anyone know of any driver changes that might account for this bug?
Steve
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org