Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59204 > unrolled thread

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

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem Jean-Louis Mounier <jean-louis.mounier@laposte.net> - 2017-10-16 21:50 +0200
    Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem Karsten Merker <merker@debian.org> - 2017-10-16 23:00 +0200
      Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem Jean-Louis Mounier <jean-louis.mounier@laposte.net> - 2017-10-17 12:10 +0200
        Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem Karsten Merker <merker@debian.org> - 2017-10-17 20:40 +0200
      Bug#864562: u-boot: broken ethernet support on Olimex A20-Olinuxino-Micro Rev. J Karsten Merker <merker@debian.org> - 2017-12-07 20:30 +0100

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

Hello Karsten,

for some reasons, I changed my mail configuration and I discovered your 
last request very recently (!) Sorry for the delay. Now I keep an eye on 
the bug thru the bug web page.

I discovered a new installer release but the bug is still present.

Now the test :

=> gpio clear 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

[toc] | [next] | [standalone]

#59206

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 request very recently (!) Sorry for the
> delay.  Now I keep an eye on the bug thru the bug web page.
> 
> I discovered a new installer release but the bug is still
> present.
> 
> Now the test :
> 
> => gpio clear 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

Yes, that helps as it confirms that a change in u-boot alone is
enough to work around the issue in Linux as well (although it is
debateable whether the kernel should rely on the bootloader in
this case or not).  There has recently been an attempt to address
the issue in mainline u-boot, but that didn't work out as planned
and the patch got rejected:

https://lists.denx.de/pipermail/u-boot/2017-September/307778.html

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

[toc] | [prev] | [next] | [standalone]

#59211

Hello Karsten,

There may be an issue : yesterday evening, I only started the 
installation, just enough to verify the communication between the 
installer and the repositories. I didn't complete the installation.

Maybe I should try a (minimalist) installation and verify that the 
network 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 request very recently (!) Sorry for the
>> delay.  Now I keep an eye on the bug thru the bug web page.
>>
>> I discovered a new installer release but the bug is still
>> present.
>>
>> Now the test :
>>
>> => gpio clear 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
> Yes, that helps as it confirms that a change in u-boot alone is
> enough to work around the issue in Linux as well (although it is
> debateable whether the kernel should rely on the bootloader in
> this case or not).  There has recently been an attempt to address
> the issue in mainline u-boot, but that didn't work out as planned
> and the patch got rejected:
>
> https://lists.denx.de/pipermail/u-boot/2017-September/307778.html
>
> Regards,
> Karsten

[toc] | [prev] | [next] | [standalone]

#59216

On Tue, Oct 17, 2017 at 11:59:17AM +0200, Jean-Louis Mounier wrote:
> Le 16/10/2017 à 22:45, Karsten Merker a écrit :
> > On Mon, Oct 16, 2017 at 09:39:36PM +0200, Jean-Louis Mounier wrote:

> > > => gpio clear 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

> > Yes, that helps as it confirms that a change in u-boot alone is
> > enough to work around the issue in Linux as well (although it is
> > debateable whether the kernel should rely on the bootloader in
> > this case or not).  There has recently been an attempt to address
> > the issue in mainline u-boot, but that didn't work out as planned
> > and the patch got rejected:
> > 
> > https://lists.denx.de/pipermail/u-boot/2017-September/307778.html

> There may be an issue : yesterday evening, I only started the
> installation, just enough to verify the communication between
> the installer and the repositories.  I didn't complete the
> installation.
> 
> Maybe I should try a (minimalist) installation and verify that
> the network is still working when the system reboots !
> 
> Do you think it is necessary ?

On the A20, a reboot is always a "cold reset" (performed by the
SoC's watchdog), so on reboot u-boot performs exactly the same
initialization sequence as at power-on time.  If u-boot gets
changed to initialize PA17 properly during startup, I see no
reason why that shouldn't work on reboot as well, so there is
IMHO no reason to perform another full test installation right
now.  For the time being, we'll have to wait and see how the
attempts at getting support for board revision J into mainline
u-boot work out.

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

[toc] | [prev] | [next] | [standalone]

#59569 — Bug#864562: u-boot: broken ethernet support on Olimex A20-Olinuxino-Micro Rev. J

control: reassign 864562 u-boot-sunxi
control: retitle 864562 u-boot: broken ethernet support on Olimex A20-Olinuxino-Micro Rev. J
control: tags 864562 patch

On Mon, Oct 16, 2017 at 10:45:57PM +0200, Karsten Merker wrote:
> On Mon, Oct 16, 2017 at 09:39:36PM +0200, Jean-Louis Mounier wrote:

[Ethernet not working on Olimex A20-Olinuxino Micro Rev. J]
> > I discovered a new installer release but the bug is still
> > present.
> > 
> > Now the test :
> > 
> > => gpio clear 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
> 
> Yes, that helps as it confirms that a change in u-boot alone is
> enough to work around the issue in Linux as well (although it is
> debateable whether the kernel should rely on the bootloader in
> this case or not).  There has recently been an attempt to address
> the issue in mainline u-boot, but that didn't work out as planned
> and the patch got rejected:
> 
> https://lists.denx.de/pipermail/u-boot/2017-September/307778.html

Hello,

a patch to address this issue has finally been accepted today by
the upstream u-boot custodian for the sunxi platform, targeting
u-boot v2018.01:

https://patchwork.ozlabs.org/patch/833763/

Vagrant, could you include the patch in the next u-boot package
upload?

Regards,
Karsten
-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web