Long story short: My Ethernet works intermittently on my Pi. I was able to trace when it failed. The consistent pattern is that the Ethernet works when the board is cool. When it warms up, the Ethernet quits. It does this every time. I am testing this by attempting to connect to the internet and failing of succeeding.
I'm starting to think that this is a Hardware problem. Is there any way I can test to make sure that it is in fact a hardware or software issue?
What I am using is:
OS: Raspian 2012-9-19
SD: SanDisk Ultra 8GB class 6
Pi: D14 removed, No mounting holes
Voltage TP!-TP2 4.85v minimum
Re: Ethernet Failure
dmesg
SBC with 32GB RAM: https://hardkernel.com
FAQ : https://raspberrypi.stackexchange.com
Unanswered: https://www.raspberrypi.org/forums/search.php?search_id=unanswered
FAQ : https://raspberrypi.stackexchange.com
Unanswered: https://www.raspberrypi.org/forums/search.php?search_id=unanswered
Re: Ethernet Failure
You could use a electronics cold spray on the LAN controller chip to see if this will help. Just a thought.....
Re: Ethernet Failure
You possibly are experiencing the 1v8 rail error. This causes the LAN9512 chip to overheat. Try cooling the LAN chip and see if this helps. If it does you might want to RMA it. Or you might just install a heatsink on it. Entirely up to you.
512MB version 2.0 as WordPress Server
Motorola Lapdock with Pi2B
Modded Rev 1.0 with pin headers at USB
http://rich1.dyndns.tv/
(RS)Allied ships old stock to reward its Customers for long wait!
Motorola Lapdock with Pi2B
Modded Rev 1.0 with pin headers at USB
http://rich1.dyndns.tv/
(RS)Allied ships old stock to reward its Customers for long wait!
Re: Ethernet Failure
I've measured the 5v0, 3v3, and 1v8 rails and they are all good. Even after the Ethernet fails
I've tried a couple times to get the Ethernet back up after it goes out and haven't been successful. The only thing that seems to help is shutting it down and restarting it after a while.
It does seem to have less issues now that the temperature of the room has dropped a few degrees to 20 C and I turned off the overclock.
It seems to go down when (cat /sys/class/thermal/thermal_zone0/temp) goes over around 46-47k and doesn't come back, even after the temperature drops.
I've tried a couple times to get the Ethernet back up after it goes out and haven't been successful. The only thing that seems to help is shutting it down and restarting it after a while.
It does seem to have less issues now that the temperature of the room has dropped a few degrees to 20 C and I turned off the overclock.
It seems to go down when (cat /sys/class/thermal/thermal_zone0/temp) goes over around 46-47k and doesn't come back, even after the temperature drops.
Re: Ethernet Failure
The temp you are measuring is the one of the Soc.
The chip that could possibly overheat is the other smaller usb hub/lan chip.
You could feel the 1.8V voltage regulator. If that stays cold it means that the lan chip is providing all the current on the 1.8V rail. It was designed to power it's internals only and nothing more.
Maybe your 1.8V regulator is defective so that the lan chip does all the work.
However, when the supply voltage drops, you can see the same thing happening.
Have you measured the TP1 - TP2 voltage when it fails as well?
Maybe something is heating up in the supply and the voltage starts to drop after a while.
Another thing you can do is adding the smsc95xx.turbo_mode=N to /boot/cmdline.txt.
I think this turns off full duplex operation and might make the chip run cooler.
The chip that could possibly overheat is the other smaller usb hub/lan chip.
You could feel the 1.8V voltage regulator. If that stays cold it means that the lan chip is providing all the current on the 1.8V rail. It was designed to power it's internals only and nothing more.
Maybe your 1.8V regulator is defective so that the lan chip does all the work.
However, when the supply voltage drops, you can see the same thing happening.
Have you measured the TP1 - TP2 voltage when it fails as well?
Maybe something is heating up in the supply and the voltage starts to drop after a while.
Another thing you can do is adding the smsc95xx.turbo_mode=N to /boot/cmdline.txt.
I think this turns off full duplex operation and might make the chip run cooler.