LAN/NIC problem

[tkaiser]

tkaiser has a lot of knowledge.

Not regarding electrics/electronics and the stuff we're talking about. I only have some experiences. Made with a non-working board a few days ago. PSU/voltage was key.

Here the users are around that could help nailing down the problem. Unfortunately one person prevents that all the time. I can not write more since it gets deleted again. He censored a few hours ago the last try to encourage users to measure PHY_VDD33 on their boards while not using Fast Ethernet hacks/'fixes' (since then it's absolutely useless, this has to happen in GbE mode). That's the real problem unfortunately.

What are you talking about ?

... if you would bother to read my post directly above yours you would notice that I not only encouraged others to measure the PHY_VDD33 , but told them how I did that , and I gave you my results of that measurement ( in GbE mode ).  All voltages normal, solid, and stable.

To prove a claim to be false, all that is needed is one case.  I have proven that the VDD33 voltage is not the problem. Why do you keep insisting that it is?  This makes little sense.

Do YOU have a solution yet ?

Since the thread is opened again (thanks TL Lim for not allowing that Pine64 community gets totally destroyed) I will now post my answer here that got rejected some hours ago since you did what you do all the time: closing threads, censoring stuff, banning users.

"No, of course I don't have a solution, I'm just interested in finding the culprit. By following sources outside of this forum (here contribution is useless since censorship happens all the time -- please be aware that your actions are documented publicly so think first before deleting/censoring again!) you could really be able to understand that at least on one board there is a strong correlation between DC-IN (PSU used, method used, voltage fed) and GbE behaviour.
 
Therefore it would be really nice if people affected by the issue could measure PHY_VDD33 on their boards:

 
To get the idea whether there is a correlation on more than one board (if it helps you to understand: this is some sort of a poll -- you like polls don't you?). Possible results: No, there is none (search has to continue) or there is one.
 
Of course it's important that NO WORK-AROUND is used when these measurements happen (no destroyed cables, no ethtool 'fix'). And of course it doesn't play a role what you measured in your lab since it's about getting results from the field.
 
And all you do is constantly censoring everything that is beyond your imagination and discourage users to try this out ('I have proven that the VDD33 voltage is not the problem'). How did you do that and when? Isn't your board on its way to TL Lim: https://irclog.whitequark.org/linux-sunx...9#17502646; (or is he speaking of someone else?).
 
Anyway: I'm pretty confident that you don't get why it could be important to accept other issues than those your 'expert soldering eyes' are able to see. And that's the reason you should resign from your moderator role rather sooner than later."

We are collecting more GbE affected Pine A64+ boards and our hardware engineering team are focusing into this path. The focus point is on one inductor (ferrite bead) at one of the VDD power line to RTL8211 chip.

Thanks, that's interesting. I summarized my findings here (being absolutely no expert at all in this area, just trying different things out and documenting it): http://forum.armbian.com/index.php/topic...entry15432

BTW: In this thread alone 3 users haven been banned (temporarely), countless postings have been censored or completely deleted and all because one person who is enabled to act as a censor didn't accept that the whole issue could also be about 'environmental' conditions (the PSU being used). Congratulations!