Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem

is still working when the system reboots ! Do you think it is necessary ? Regards Jean-Louis Mounier Le 16/10/2017 à 22:45, Karsten Merker a écrit : On Mon, Oct 16, 2017 at 09:39:36PM +0200, Jean-Louis Mounier wrote: for some reasons, I changed my mail configuration and I discovered your last

Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem

ear PA17 gpio: pin PA17 (gpio 17) value is 0 =>run bootcmd after that, the installer got IPV4 and IPV6 addresses wwith DHCP and then ran fine. Hope it helps Regards Jean-Louis Mounier

Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem

Hello Karsten, thank you for your investigations and sorry for the delay : I have many lives... here is the test result : U-Boot 2016.11+dfsg1-4 (Mar 27 2017 - 18:39:51 +) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-Olinuxino Micro I2C: ready

Bug#864562: Info received (Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem)

Hello, I've just read Olimex Blog and found the following text about my board (which is a J Release). /We are selling for some time already //A20-OLinuXino-MICRO //Rev.J where few

Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem

Hello Karsten, I installed Stretch on my A20 with the USB network interface. After a successfull minimal installation (on the Micro SD card), I configured eth0 and rebooted the system. The result is the same : the PHY is unable to get an IP address with DHCP. The problem witch

Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem

Hello Karsten, thank you for all your informations about A20 specifications. I will test them ASAP ! I guessI will spend time on uboot... However, I have a new information about Jessie on my A20-Olinuxino Micro. Yesterday night, I installed Jessie on my board using my USB-Ethernet

Bug#669052: [regression 3.2.12 - 3.2.14] r8169 driver not automatically loaded

Hello Jonathan, here it comes, Regards Jean-Louis Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jean-Louis Mounier jean-louis.moun...@laposte.net To: Debian Bug Tracking System sub...@bugs.debian.org Subject: initramfs-tools: none Package

Bug#669052: Bug 669052 : Re: [regression 3.2.12 - 3.2.14] r8169 driver not automatically loaded (Re: Bug...)

Hello Jonathan, sorry for my last subject line...I wrote it from my office and I should have think to include at least the bug number in the subject... modprobe r8169 : I should have think to do this obvious test ! :-! It works ! The sequence : modprobe r8169 ifup eth0 made my server

Bug#669052: [regression 3.2.12 - 3.2.14] r8169 driver not automatically loaded

Following your instructions, I did install linux-image-3.2.0-2-amd64 version 3.2.12-1 (after commenting the r8169 line in /etc/modules). uname -a gives : Linux morisson 3.2.0-2-amd64 #1 SMP Tue Mar 20 20:45:09 UTC 2012 x86_64 GNU/Linux (just for verification) The system comes faulty : the on

Bug#669052: linux-image-3.2.0-2-amd64: NIC RTL-8169 not loaded with last testing release

Package: linux-2.6 Version: 3.2.14-1 Severity: grave Justification: renders package unusable Hi, on Apr, 15, as I do almost every day, I did upgrade my testing release. The kernel 3.2.0-2-amd64 upgraded from 3.2.12-1 to 3.2.14-1. After reboot, my eth0 NIC is no longer detected. I installed