On Mon, 2014-04-28 at 15:27 +0200, tpsamw1 wrote: > Dnia 28 kwietnia 2014 12:57 Ian Campbell <i...@hellion.org.uk> napisał(a): > > Looks a bit like > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719680 which was > > thought to be fixed. Can you provide a full dmesg please. > > Hello, > > Full dmesg is available here: > > http://pastie.org/9119569
Thanks. I'm afraid I can't see any smoking guns in there. I notice that this is an orion5x based qnap, rather than one of the kirkwood ones which is all I have available/experience with. FWIW 3.13 and 3.14 work fine on kirkwood (not really useful information though). 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). 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)? Ian. > One more thing, cable is connected to 1000Mbit switch port, after > connecting it to 100Mbit switch port front led is blinking, but still I > can't connect to device. > > Best regards, > 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/1399123122.23380.162.ca...@dagon.hellion.org.uk
