Dnia 3 maja 2014 15:18 Ian Campbell <i...@hellion.org.uk> napisaƂ(a):
> It might be worth diffing a working and non-working dmesg. AFAIK the
> "Driver mv643xx_eth_port requests probe deferral" message you mention
> are not unusual with a new kernel (AIUI they are because the phy driver
> became modular, so the main driver needs to wait for it to load).

Hello,

Here is a dmesg from fresh stable release:

http://pastie.org/9140208

On non-working dmesg I see some entries with:

"No busn resource found for root bus, will use"
"libphy: PHY orion-mdio-mii:08 not found"

> I've had a look through the orion5x .config and nothing Eth or PHY
> related appears to be missing/turned off AFAICT.
> 
> It'd be worth trying the 3.14 kernel currently in unstable, if that
> doesn't work then I think the next step would be to report the issue to
> the upstream lists/maintainers.
> 
> Have you checked that /etc/network/interfaces, and the output of
> ifconfig, ethtool etc are correct (i.e. that there is no configuration
> issue)?

There were no changes in configuration.

Marek


--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/72e76bb7.2cb6f206.536692c6.b4...@o2.pl

Reply via email to