|
|
Post by ttocs on Sept 8, 2020 16:08:48 GMT -5
Trying to see if there is a common theme for folks having Network Interface problems on the Generation 3 Processors.
Select a response that matches your experience with the NIC. If you don't know what Static IP is, then you are not using it. DHCP is the default setting on the processor.
|
|
|
|
Post by megash0n on Sept 8, 2020 16:14:47 GMT -5
Thank you good sir!
|
|
|
|
Post by megash0n on Sept 8, 2020 16:20:59 GMT -5
Something to note for correlation.. With VRO, the NIC doesn't have to go thru any power cycle. If it is working, it will work thru 100 reboots. It isn't until you flip the switch, or change to the other mode, that you get issues with each turn off and turn on. For those of us that couldnt use VRO until 1.9 I believe... This was an absolute nightmare. I would have already sold mine months ago had the VRO issues not been mostly resolved. The issue is no better today. The difference is that I can use VRO. So, once I fight with it for 10 mins, I'm good until it locks up or I have a power outage. All of these options are relevant, but you may have a lot of people wanting to vote both ways, or think they don't have a problem because they are only power cycling 1 out of 100 times they "reboot". I don't know how to vote. I have the issue almost all the time unless I am in VRO which just masks the underlying issue.
Edit: this is the hard part about polls on here. When you say " Works" Does that mean after you have fought with it or does this mean thru a full power cycle in each test case. If you count the number of seconds in a day, it's gonna work most of the time as long as you leave it in an up state. If we all did a full power cycle every 30 mins, we'd have very different results in this poll. I'm voting based on how it behaves when having to do a full power cycle which negates VRO. While relevant, it really isn't at the same time. It just sheds more light on the underlying issue. It also will show how many people don't actually trigger the issue as well. I might suggest adding one more option before this gets going. An option for, "I don't plug the NIC up"
|
|
|
|
Post by ttocs on Sept 8, 2020 17:01:13 GMT -5
My NIC has never failed on the XMC-2 and XMC-1. This includes all the different types of booting. The NIC sometimes has not acquired an IP address when the Emotiva supplied switch was used AND the EDNIB was connected and powered AND I was testing what works and what doesn't AND this was before DHCP was fixed and I was using Static IP, but these were rare events and I made notes when it happened, which is why I know it was the Emo switch/EDNIB combo that caused the fails - take the Emo switch out of the network and the processor has not failed to be able to use the network, so Dirac works all the time, the Emotiva iPhone App works all the time, etc.
IMO when DHCP got fixed with this FW and I stopped using Static IP the network function got more reliable. In fact I haven't tested the EmoSwitch/EDNIB combo for fails since the FW was released. I'll do that so I know. I connected the combo over last weekend when someone else was having a problem, but I couldn't duplicate the issue because nothing failed.
|
|
|
|
Post by idea53 on Sept 8, 2020 17:14:38 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select.
|
|
geebo
Emo VIPs 
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,204
|
Post by geebo on Sept 8, 2020 17:17:30 GMT -5
Mine always works whether using low power standby or video remains on.
|
|
|
|
Post by ttocs on Sept 8, 2020 17:31:59 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select. It never fails that something goes missing. Duly noted. In my defense, it's a lot of words, plus it's the fails which are the point of this. Now, where's that brain vitamin, hmmmmm.... |
|
|
|
Post by doc1963 on Sept 8, 2020 17:53:16 GMT -5
I use the VRO power mode exclusively. Can’t say with absolute certainty that my NIC never fails because, aside from Dirac setup, I don’t/won’t use it for anything. What I can say is when I look at the menus (which I do a lot), I have an IP address. When I ping it, it responds. So with those things considered, I guess I’m good...  |
|
|
|
Post by megash0n on Sept 8, 2020 18:00:00 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select. It never fails that something goes missing. Duly noted. In my defense, it's a lot of words, plus it's the fails which are the point of this. Now, where's that brain vitamin, hmmmmm.... haha. Youve done a fine job. It's hard to use these polls with some things. Especially when words have different context depending on the situation. |
|
|
|
Post by krauley on Sept 8, 2020 18:28:03 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select. +1 |
|
|
|
Post by ttocs on Sept 8, 2020 19:02:21 GMT -5
This series of boots is to test EmoSwitch with EDNIB connected and powered on and processor set to Low Power Standby. Then after the shutdown period restarted the processor.
Starting with the processor on and linked, EDNIB on and linked.
Shutdown and waited 5 seconds. No link. No Dirac. No App.
Shutdown again and waited 15 seconds. No link. No Dirac. No App.
Shutdown again and waited 25 seconds. No link. No Dirac. No App.
Shutdown again and waited 1 minute. Link success. Verified that Dirac can be enabled and the iPhone app works.
Shutdown again and waited about 8 seconds. No link. No Dirac. No App.
Shutdown again and waited 1 minute. Link success. Verified that Dirac can be enabled and the iPhone app works.
Shutdown again and waited 1 minute. Link success. Verified that Dirac can be enabled and the iPhone app works.
Shutdown again and waited 20 seconds. No link. No Dirac. No App.
Shutdown again and waited 5 minutes. No link. No Dirac. No App.
Shutdown again and waited 1 minute. Link success. Verified that Dirac can be enabled and the iPhone app works.
Now the EDNIB will be disconnected. The processor will remain connected to the EmoSwitch.
Shutdown again, unplugged the EDNIB, and waited 5 minutes. Link success. Verified that the iPhone app works.
Shutdown again, EDNIB still unplugged, and waited 10 minutes. Link success. Verified that the iPhone app works.
Shutdown again, EDNIB still unplugged, and waited 20 seconds. No Link. No App.
Shutdown again, EDNIB still unplugged, and waited 1 minute. Link success. Verified that the iPhone app works.
Now the EDNIB is plugged in while processor is on. EDNIB linked. Verified that Dirac can be enabled. It took about 30 seconds for the EDNIB to boot and the Dirac Enable checkbox to appear in the Menu (it won't appear while you watch, you need to back out of the Menu and go back in for it to refresh).
This points out some things.
For 100% reliability to Link, the EDNIB should not be connected all the time when using the EmoSwitch, just connect it when using Dirac.
With the EDNIB disconnected, the 1 minute wait time or longer is 100% reliable for the processor to acquire a link.
No matter what the combination of EDNIB or No EDNIB, waiting less than 1 minute is not reliable for the processor to acquire a link.
These reboots were consecutive.
This is with my processor, in my house, with my special electrons. YMMV
Router is Asus RT-AC68U with basic settings, DHCP used for everything.
|
|
|
|
Post by DellaDog on Sept 8, 2020 20:07:58 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select. +1 Except that it doesn’t. I’ve tried every combination; static IP, static IP assigned by the router, and DHCP. None work consistently and reliably. |
|
cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,914
|
Post by cawgijoe on Sept 8, 2020 21:26:48 GMT -5
I use the VRO power mode exclusively. Can’t say with absolute certainty that my NIC never fails because, aside from Dirac setup, I don’t/won’t use it for anything. What I can say is when I look at the menus (which I do a lot), I have an IP address. When I ping it, it responds. So with those things considered, I guess I’m good... Ditto |
|
LCSeminole
Global Moderator 
Res firma mitescere nescit.
Posts: 20,501
|
Post by LCSeminole on Sept 8, 2020 21:44:23 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select. +1 |
|
|
|
Post by AudioHTIT on Sept 8, 2020 22:33:38 GMT -5
Since somewhere around 1.9 I rarely if ever have NIC link issues (LPS). I also don’t have connectivity issues with Dirac or the EDNIB. What I do get is a loss of network service, typically when playing 4K/Atmos discs, or streaming same with TV. The only way I know this has happened is by trying to use the XMC-1 App while watching one of these types of shows. The App sees the RMC (good link), but the App functions are blank (no service), before and after watching the show the App works fine. Happened tonight with “Away” 4K/Atmos > Netflix App > TV4K > RMC-1.
|
|
geebo
Emo VIPs
"Too bad that all the people who know how to run the country are driving taxicabs and cutting hair"
Posts: 24,204
|
Post by geebo on Sept 9, 2020 6:27:20 GMT -5
Missing selection - "NIC works all of the time using Low Power Standby & DHCP." i.e. the choice that I would select. +1 |
|
KeithL
Administrator
Posts: 9,966
|
Post by KeithL on Sept 9, 2020 9:29:15 GMT -5
NOTE: THE ETHERNET PORT ON OUR PROCESSORS REALLY TAKES ABOUT THIRTY SECONDS (OR SLIGHTLY MORE) TO RESET.  This means that, if you flip that Power switch to fully off, wait ten seconds, then turn it back on again, THE ETHERNET PORT PROBABLY WILL NOT WORK. (Because you didn't wait long enough.) And, if you don't wait long enough, the rest of the processor will reboot just fine... But the Ethernet port will not reinitialize and so will not work... And you'll go crazy wondering why it worked a minute ago and now it doesn't... THAT'S WHY WE SAID TO WAIT THIRTY SECONDS.
|
|
|
|
Post by megash0n on Sept 9, 2020 10:50:36 GMT -5
NOTE: THE ETHERNET PORT ON OUR PROCESSORS REALLY TAKES ABOUT THIRTY SECONDS (OR SLIGHTLY MORE) TO RESET. This means that, if you flip that Power switch to fully off, wait ten seconds, then turn it back on again, THE ETHERNET PORT PROBABLY WILL NOT WORK. (Because you didn't wait long enough.) And, if you don't wait long enough, the rest of the processor will reboot just fine... But the Ethernet port will not reinitialize and so will not work... And you'll go crazy wondering why it worked a minute ago and now it doesn't... THAT'S WHY WE SAID TO WAIT THIRTY SECONDS. How about a cron job to check the network stack and initiate a restart if needed? Ugly.. But it works. Just a suggestion. |
|
KeithL
Administrator
Posts: 9,966
|
Post by KeithL on Sept 9, 2020 12:23:38 GMT -5
I'm afraid I don't know the exact details of what's going on inside in this case... (So I don't know if that would work or not...)
For those who like to back-seat engineer....
It is relatively common in simple digital devices to use a time constant to control a reset... Internally there is a capacitor or equivalent which is normally charged up to some voltage... When power is turned off this voltage discharges over several seconds... Then, when power is reapplied, it "holds down a reset line" for a few seconds... This ensures that "the reset remains in effect" until the supply voltage, and possibly other parts of the circuit, have reached stable operation... At that point "the reset is released and normal operation starts"... This is quite commonly accomplished using a simple capacitor or other device to add a few seconds of delay. (And, if you don't wait long enough for it to discharge, the timer never starts, so that reset never happens, and things don't start up properly.)
In some cases you may be able to issue a reset command later... But, in others, the delay circuit is hard wired to the "power-on reset" pin on a chip somewhere...
Note that, with Ethernet, there are a lot of other things going on as well.... (You have to get a Layer 2 connection so you can request an IP address, then DHCP an IP address, and so on...)
NOTE: THE ETHERNET PORT ON OUR PROCESSORS REALLY TAKES ABOUT THIRTY SECONDS (OR SLIGHTLY MORE) TO RESET. This means that, if you flip that Power switch to fully off, wait ten seconds, then turn it back on again, THE ETHERNET PORT PROBABLY WILL NOT WORK. (Because you didn't wait long enough.) And, if you don't wait long enough, the rest of the processor will reboot just fine... But the Ethernet port will not reinitialize and so will not work... And you'll go crazy wondering why it worked a minute ago and now it doesn't... THAT'S WHY WE SAID TO WAIT THIRTY SECONDS. How about a cron job to check the network stack and initiate a restart if needed? Ugly.. But it works. Just a suggestion. |
|
|
|
Post by megash0n on Sept 9, 2020 16:10:16 GMT -5
I'm afraid I don't know the exact details of what's going on inside in this case... (So I don't know if that would work or not...)
For those who like to back-seat engineer....
It is relatively common in simple digital devices to use a time constant to control a reset... Internally there is a capacitor or equivalent which is normally charged up to some voltage... When power is turned off this voltage discharges over several seconds... Then, when power is reapplied, it "holds down a reset line" for a few seconds... This ensures that "the reset remains in effect" until the supply voltage, and possibly other parts of the circuit, have reached stable operation... At that point "the reset is released and normal operation starts"... This is quite commonly accomplished using a simple capacitor or other device to add a few seconds of delay. (And, if you don't wait long enough for it to discharge, the timer never starts, so that reset never happens, and things don't start up properly.)
In some cases you may be able to issue a reset command later... But, in others, the delay circuit is hard wired to the "power-on reset" pin on a chip somewhere...
Note that, with Ethernet, there are a lot of other things going on as well.... (You have to get a Layer 2 connection so you can request an IP address, then DHCP an IP address, and so on...)
How about a cron job to check the network stack and initiate a restart if needed? Ugly.. But it works. Just a suggestion. I feel like I was just transported back to 1947 when transistors were invented..... |
|
