LAN/NIC problem - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: PINE A64(+) (https://forum.pine64.org/forumdisplay.php?fid=4) +--- Forum: Pine A64 Hardware, Accessories and POT (https://forum.pine64.org/forumdisplay.php?fid=32) +---- Forum: Ethernet Port (https://forum.pine64.org/forumdisplay.php?fid=39) +---- Thread: LAN/NIC problem (/showthread.php?tid=835) |
RE: LAN/NIC problem - waldo - 09-30-2016 (09-29-2016, 07:39 PM)stepw Wrote: Doesn't look like slave/master role is of any impact on RTL8211E PHY. I can force slave or master mode on the NIC of the connected PC and PINE64 PHY reports corresponding opposite role, but packet loss persists when pinging from PINE64 to the connected device. Forcing role on PINE64 PHY also results in correct role on both sides, also of no effect on the problem.smart thinking thanks for busting my dreams Well, that takes us back to the fact that is seems these boards realy ARE broken from a HW point of view. I'm starting to question the sanity of keeping production going at this point .... shouldn't this get fixed first ? //waldo RE: LAN/NIC problem - jandvs - 10-05-2016 I received a replacement board for the one I sent to TM Lim a couple of weeks ago. This one works perfect. Full GBe. No packet loss. Mark, I mentioned to you a few weeks ago about the crystal on my old board was upside down compared to the one on my friends working board. I noticed that this one has it mounted like on my friends board. Not like it was on my defective board. Still have no idea if that has anything to do with the cost of tea in china (or anything actually relevant). RE: LAN/NIC problem - amc2012 - 10-05-2016 I also finally got a working one. The first replacement also suffered from the issue, but the most recent one has GbE working great. What is the "crystal?" Going to look at some pics of my old board compared to this one. RE: LAN/NIC problem - jandvs - 10-05-2016 (10-05-2016, 05:13 PM)amc2012 Wrote: I also finally got a working one. The first replacement also suffered from the issue, but the most recent one has GbE working great. It's a little silver oval in the center of the board, just above the A64 processor. I have no idea if the orientation of it makes a lick of difference. It's just an observation on my board it was mounted the same direction as the processor. On my friends and another working board, it's upside down compared to the processor. This new board also has it upside down compared to the processor. RE: LAN/NIC problem - pfeerick - 10-05-2016 (10-05-2016, 08:27 PM)jandvs Wrote:(10-05-2016, 05:13 PM)amc2012 Wrote: I also finally got a working one. The first replacement also suffered from the issue, but the most recent one has GbE working great. If it is just a crystal, orientation (left to right, right to left) doesn't make any difference - they are not a polarised component. RE: LAN/NIC problem - androsch - 10-06-2016 (10-05-2016, 05:13 PM)amc2012 Wrote: I also finally got a working one. The first replacement also suffered from the issue, but the most recent one has GbE working great. Also received my replacement board for the bad one sent to tllim some weeks ago for testing. BUT, bad news, new board has the same problems regarding GbE as before, so no improvement :-( Just exchanged the board (using same PSU, SD card and cable as with the working developer board from tkaiser) and speed was dropping to nearly zero. Putting it to a fixed 100mbps port was stable and reliable as before, so FastEthernet is fine, GbE not working. Hope tllim and the hardware guys can work out the real problem with our bad boards (they should have a sufficient amount of that now) and solve this issue... RE: LAN/NIC problem - waldo - 10-27-2016 Apparently ... the RX/TX vallues are under scrutiny ... again ... has anyone ever tried the script i wrote to see if it becomes better for any of you ? I only went downhill for me .... (10-25-2016, 07:17 PM)tllim Wrote:(10-25-2016, 07:08 PM)endotronic Wrote: Hey all, I found this thread while searching for ways to get GigE working on my Pine64 2GB. I'm not quite sure I have the latest longsleep kernel, but I did just install the most recent one I could find the other day: RE: LAN/NIC problem - tllim - 10-31-2016 (10-27-2016, 11:32 AM)waldo Wrote: Apparently ... the RX/TX vallues are under scrutiny ... again ... Our experience is need to disable the RX delay, this can be implement thru hardware method: discover the LED2_RXDLY line pull up resistor to pul down or software method, program the RX control register: phy_write(phydev, 0x28, 0xd591);//only enable TX. Somehow, setup the RX delay to 0 not same as disable RX delay. This finding also puzzle me. ... TL Lim LAN/NIC problem - androsch - 11-01-2016 Can someone give a instruction for noobs please? Maybe longsleep with a new kernel or a detailed setup for the dtb-file? Edit: Sorry, just noticed longsleep already provided a new kernel, thanks to him, will check out later. Thanks to Simon, great job! RE: LAN/NIC problem - stepw - 11-01-2016 Wow, 0x28 PHY/MII register doesn't even exist, so phy_write(phydev, 0x28, 0xd591);//only enable TX. call is not valid According to longsleep's driver patch, the following calls are actually used: Code: + phy_write(phydev, 0x1f, 0x0007);//sel ext page That sequence is more feasible and does appear to improve TX performance, but RX is still garbage on my Pine64. My iperf3 tests under armbian: 100Mbps link: Pine64->PC TCP: 96Mbps UDP: 96Mbps generated 96Mbps received PC->Pine64 TCP: 96Mbps UDP: 96Mbps generated 96Mbps received 1Gbps link, with RX/TX delay (e.g. CONFREG = 0x8577 = 0b1000010101110111) Pine64->PC TCP: 500kbps UDP: 670Mbps generated 50Mbps received PC->Pine64 TCP: 1.16kbps UDP: 900Mbps generated 0kbps received 1Gbps link, without RX/TX delay (e.g. CONFREG = 0xd591 = 0b1101010110010001) Pine64->PC TCP: 500Mbps UDP: 690Mbps generated 690Mbps received PC->Pine64 TCP: 1.5Mbps UDP: 900Mbps generated 20Mbps received Interestingly, some of the changed CONFREG bits are not even in Realtek's data sheet. Changing TX/RX delay (bits 1 and 2) alone doesn't make a difference. This still doesn't look like something that can be fixed in software |