Bug 201563
Summary: | macchiatobin, could not attach PHY (-19) | ||
---|---|---|---|
Product: | Drivers | Reporter: | alpha_one_x86 |
Component: | Network | Assignee: | drivers_network (drivers_network) |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | anton.feeds+kernel, theonedemon |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.18 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
alpha_one_x86
2018-10-29 20:44:27 UTC
up, some bugs in kernel 4.19.16 ``` [ 5.401915] mvpp2 f10f0000.ethernet eth0: Using hardware mac address 00:00:00:00:00:04 [ 17.784700] mvpp2 f10f0000.ethernet eth0: could not attach PHY (-22) [ 78.929793] mvpp2 f10f0000.ethernet eth0: could not attach PHY (-22) ``` dst file: https://pastebin.com/5gSkKwYK .config file: https://pastebin.com/Dw7abMz9 last kernel with work mvpp2 ethernet is 4.18.20, but not work in 4.19.1 i replace folder drivers/net/ethernet/marvell from kernel 4.18.20 to 4.19.1 and ethernet is working I'd like to add to this old issue, that it might be related to the Single-Shot board and an issue discussed on the official Macchiato forums (http://macchiatobin.net/forums/topic/kernel-vanilla/page/4/). The issue that causes these messages might be related to the armada kernel driver trying to access RJ45 specific instructions that won't be available (due to the Single-Shot board missing these physical ports). The official wiki on Macchiato Bin (http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+Kernel) mentions this briefly, and if anything this is more a shortcoming in the driver itself that it can not handle both setups. To verify that this is the issue, you can download the single-shot armada driver provided by macchiatobin/solidrun or - if you run Arch Linux ARM - this driver is pre-shipped and can be found at /boot/dtbs/marvel/armada-8040-mcbin-singleshot.dtb, which has to be re-named to /boot/dtbs/marvel/armada-8040-mcbin.dtb After a reboot, link should come up and iproute2 commands should work as expected. Hi, updated kernel + vanilla updated uboot + single dts have resolved issue |