I'm fairly sure the problem is that you have a realtek r8168 chipset NIC and the kernel is using the r8169 driver. This is a known issue with this NIC across many different Linux distro's including OE. PLease add your details to the existing issue ticket on github referencing this thread - I believe it's being looked at by the devs right now.

Thanks! I will add it to github.

Can I test this theory by installing the Generic 1.02, or will I face the same problem with that build?

You're welcome to try, but I believe this has been a problem for a long time, so I doubt it will make any difference. Let us know the results

hi, is not the kernel driver
i have the same kernel drive and the same nick

install generic build and test it... !

Note: i download the fusion version and my NT-A3500 hangup in the XBMC menu
i back to generic and is working fine again

please make this test from your pc
if you get a timeout then you have a physical problem
or poor performance from your switch / router

IP ADDRESS = my NT-A3500(192.168.1.14)
i am using a MSI-WIFI router as a switch for my home networks
XBOX360,PS3,WIFI,PC,LAPTOP,HTPC all connect to this router 10/100

C:\>ping 192.168.1.14 -l 4500

Pinging 192.168.1.14 with 4500 bytes of data:
Reply from 192.168.1.14: bytes=4500 time=1ms TTL=64
Reply from 192.168.1.14: bytes=4500 time=1ms TTL=64
Reply from 192.168.1.14: bytes=4500 time=1ms TTL=64
Reply from 192.168.1.14: bytes=4500 time=1ms TTL=64

C:\>ping 192.168.1.14 -l 15000

Pinging 192.168.1.14 with 15000 bytes of data:
Reply from 192.168.1.14: bytes=15000 time=3ms TTL=64
Reply from 192.168.1.14: bytes=15000 time=3ms TTL=64
Reply from 192.168.1.14: bytes=15000 time=3ms TTL=64
Reply from 192.168.1.14: bytes=15000 time=3ms TTL=64

C:\>ping 192.168.1.14 -l 30000

Pinging 192.168.1.14 with 30000 bytes of data:
Reply from 192.168.1.14: bytes=30000 time=5ms TTL=64
Reply from 192.168.1.14: bytes=30000 time=5ms TTL=64
Reply from 192.168.1.14: bytes=30000 time=5ms TTL=64
Reply from 192.168.1.14: bytes=30000 time=5ms TTL=64

C:\>ping 192.168.1.14 -l 65000

Pinging 192.168.1.14 with 65000 bytes of data:
Reply from 192.168.1.14: bytes=65000 time=11ms TTL=64
Reply from 192.168.1.14: bytes=65000 time=11ms TTL=64
Reply from 192.168.1.14: bytes=65000 time=11ms TTL=64
Reply from 192.168.1.14: bytes=65000 time=11ms TTL=64

Generic Build 1.0.2 Dharma
lspci -vvvv

Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: Foxconn International, Inc. Device 0e29
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 40
Region 0: I/O ports at e000
Region 2: Memory at d0004000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at d0000000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0300c Data: 4159
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 unlimited, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [d0] Vital Product Data
Unknown small resource type 00, will not decode more.
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 51-02-00-00-68-4c-e0-00
Kernel driver in use: r8169

In current OE the r8169 driver is loaded for everything. The driver will run on all 8168/8168 chips but some implementations of the 8168 chipset have performance and connectivity issues; Google "r8168 r8169 issue" and do some reading if you don't believe me. The fix requires adding the proper r8168 driver and patching the kernel to prevent overlap with the r8169 driver. This is being actively worked on but needs some careful testing to ensure we only fixed the right set of cards. Add your details to the github ticket and you'll be notified of any updates on the fix.

github.com/OpenELEC/OpenELEC.tv/commit/e...16be2fd8ab89a981a1c1

this will either go into the next nightly dev build or 1.95.2 depending on the whims of the release fairies

When I'm back home I will still put the info on github.

Thanks a ton for your help. I was about to send the device back to NewEgg, but since a fix is in the works I will hold on to it.

Thanks!

argj wrote:
I will try this as well, but I won't be able to post about it until tomorrow. Thanks!

argj, this did not resolve my problem. The videos were continually buffering.

Beta 2 appears to resolve the video buffering issue.

For sound I'm using asound.conf_fusion.sample with HDMI uncommented. The file has been renamed and put in the correct directory; however, sound is working for music, but is fuzzy for video.

When using the setup from the wiki, music is working but I still get a fuzzy sound for videos.

Update: I'm using the wiki asound.conf with settings of hdmi instead of custom. Sound is now working for both. I'm not sure if this is related or not, but about 20 minutes into a CD or playlist XBMC freezes. I'm testing without the background visualization to see if it's causing the screen freeze. Also, music volume is very loud compared to video. I'm sure this is a symptom of a misconfiguration on my part.

Any thoughts?