vusolo2 network issue

vu_duo · Mar 12, 2014

Hi,

I am testing latest BlackHole 2.0.9 and noticed following in the dmesg log.
The router used in Netgear Gigabit WNDR3700 connected to the stb with Cat6 cable (shielded).
Also tried Cat5 with same results. In Network configuration DHCP on and Static IP was tried , including
adding manually the name-server address. The problem still persists.
What I was able to do is to install a WiFi dongle and get the box working with that.
I would prefer wired gigabit - one of the reasons I purchased the box in first place.
Any pointers will be appreciated. Thank you

March 12 10:11:12 vusolo2 user.info kernel: ata1: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x100 irq 41
March 12 10:11:12 vusolo2 user.info kernel: ata2: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x180 irq 41
March 12 10:11:12 vusolo2 user.info kernel: brcmstb_nand: NAND controller driver is loaded
March 12 10:11:12 vusolo2 user.debug kernel: __clk_enable: network [1]
March 12 10:11:12 vusolo2 user.debug kernel: __clk_enable: enet [1]
March 12 10:11:12 vusolo2 user.debug kernel: bcm40nm_pm_genet_enable 00
March 12 10:11:12 vusolo2 user.crit kernel: Found PHY at Address 3
March 12 10:11:12 vusolo2 user.info kernel: Config GPHY through MDIO
March 12 10:11:12 vusolo2 user.debug kernel: __clk_disable: enet [0]
March 12 10:11:12 vusolo2 user.debug kernel: bcm40nm_pm_genet_disable 00
March 12 10:11:12 vusolo2 user.debug kernel: __clk_disable: network [0]
March 12 10:11:12 vusolo2 user.debug kernel: __clk_enable: network [1]
March 12 10:11:12 vusolo2 user.debug kernel: __clk_enable: moca_genet [1]
March 12 10:11:12 vusolo2 user.debug kernel: bcm40nm_pm_genet1_enable 00
March 12 10:11:12 vusolo2 user.debug kernel: __clk_enable: moca [1]
March 12 10:11:12 vusolo2 user.debug kernel: bcm40nm_pm_moca_enable 00
March 12 10:11:12 vusolo2 user.info kernel: ata1: SATA link down (SStatus 0 SControl 300)
March 12 10:11:12 vusolo2 user.info kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
March 12 10:11:12 vusolo2 user.err kernel: No PHY detected, not registering interface:1
March 12 10:11:12 vusolo2 user.debug kernel: __clk_disable: moca [0]
March 12 10:11:12 vusolo2 user.debug kernel: bcm40nm_pm_moca_disable 00
March 12 10:11:12 vusolo2 user.debug kernel: __clk_disable: moca_genet [0]
March 12 10:11:12 vusolo2 user.debug kernel: bcm40nm_pm_genet1_disable 00
March 12 10:11:12 vusolo2 user.debug kernel: __clk_disable: network [0]
March 12 10:11:12 vusolo2 user.warn kernel: bcmgenet: probe of bcmgenet.1 failed with error -5

vu_duo · Mar 12, 2014

Hi,

The dmesg log above probably can describe the situation why there is no IP address. Network restart was performed - including router reboot.

Then something interesting happened. Suddenly the static IP was recognized and when doing ifconfig in telnet I could see the Tx (transmitting) was working slowly. No packets showing in Rx side. The LAN connector is working (green led blinking very often and fast - the yellow blinking slowly)
This does not meant I could use the interface to ping outside the stb.

I am only asking the developers if this could be a kernel issue - problem with bcmgenet driver or a HW issue. Thank you

paolino · Mar 12, 2014

What is your "ping yourboxIP"?

vu_duo · Mar 12, 2014

Only wifi is working with IP address.
changing to ethernet, I can only ping loopback 127.0.0.1

My wifi net address is local 192.168.0.xxx

I suspect the stb ethernet is not picking the router DHCP leased address.

paolino · Mar 12, 2014

Normally I'm using WiFi, LAN only for tests, but I never had LAN problems (dual band GigaLAN modem router). I'm using only Static IP.
Are you sure, that you don't have IP conflicts (same IP for more devices), MAC filtering enabled, Subnet Mask,...?

PS: Is your LAN and router IP in this range? 192.168.0.xxx. If your router IP is 192.168.1.1, box has to be 192.168.1.xxx not 0.xxx

vu_duo · Mar 12, 2014

I will try with older router. Already eliminated any conflicts. For testing purposes stb was hooked directly (alone) to the gigabit router.
Also need to mention this router has been working without issues assigning DHCP addresses.
The only problem I am suspecting is that the bcmgenet driver is missing some functionality to properly work with this setup, or Hw is damaged ...
but that means the SoC is damaged as i do not see any other chip connected on the PCB between broadcom Soc and LAN connector.

vu_duo · Mar 13, 2014

Confirmed to be working with Linksys 10/100 router including DHCP enabled.

Pal Ryvaenge · Mar 13, 2014

Is cable "straight"? pin 1-2-3-6 goes straight through?

Also see if there is a firmware update for your router.

vu_duo · Mar 14, 2014

Thanks for answering - I have updated the router firmware, same result as before.
The phy chip (Rtl8211EG) which I learned is handling the gigabit connection might have an issue.
I will try to investigate under microscope.

The connection is not working as expected even at 100 full duplex. I am able to log in using terminal but not able to transfer files.
Back to wireless connection

vu_duo · Mar 18, 2014

I am not giving up on LAN connection

So after some investigation I have found something which can bring back the Gbps connection.

Code:

http://www.amazon.com/gp/product/B00CRGJ95C?&tag=shopwiki-us-20&linkCode=as2&camp=1789&creative=9325

As a bonus 3 USB 3.0 ports available for vtuner / hard drive expansion. Ordered one today.
In preparation for that, patch included.

Edit by moderator: No Live Links, Please!

blackstalker · Mar 19, 2014

I also have solo2 wired gbps ethernet link problems which I think is faulty hardware or BH driver related.
Would it be possible to some how for example install the original driver?

paolino · Mar 19, 2014

What issue? http://www.vuplus-community.net/board/threads/vuplus-windows-7.16995/page-2#post-131135

fatalizer · Mar 22, 2014

i've solo2 with DGND3700v1. its your same router but mine has xdsl modem... and i've no problem with 60m cat5 ethernet

vu_duo · Mar 26, 2014

So far usb 1Gbps connection working great

(definitive router is not defective.) Also added two usb dvb-s2 in the available ports.

Code:

eth0: no IPv6 routers present
eth0: Link down
ADDRCONF(NETDEV_UP): eth1: link is not ready
ax88179_178a 1-1.1:1.0: eth1: ax88179_178a - Link status is: 1
ax88179_178a 1-1.1:1.0: eth1: Write medium type: 0x013f
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
ax88179_178a 1-1.1:1.0: eth1: link up, 1000Mbps, full-duplex, lpa 0xCDE1
eth1: no IPv6 routers present
root@vusolo2:~# ifconfig
eth0  Link encap:Ethernet  HWaddr 00:1D:EC:00:4A:FB
  inet6 addr: fe80::21d:ecff:fe00:4afb/64 Scope:Link
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:4577 (4.4 KiB)

eth1  Link encap:Ethernet  HWaddr 00:0A:CD:22:93:41
  inet addr:192.168.0.107  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::20a:cdff:fe22:9341/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:171 errors:0 dropped:4 overruns:0 frame:0
  TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:12239 (11.9 KiB)  TX bytes:29908 (29.2 KiB)

lo  Link encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:169 errors:0 dropped:0 overruns:0 frame:0
  TX packets:169 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:12798 (12.4 KiB)  TX bytes:12798 (12.4 KiB)

root@vusolo2:~# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=64 time=0.852 ms
64 bytes from 192.168.0.1: seq=1 ttl=64 time=0.559 ms
64 bytes from 192.168.0.1: seq=2 ttl=64 time=0.560 ms
64 bytes from 192.168.0.1: seq=3 ttl=64 time=0.561 ms
64 bytes from 192.168.0.1: seq=4 ttl=64 time=0.560 ms
64 bytes from 192.168.0.1: seq=5 ttl=64 time=0.554 ms
64 bytes from 192.168.0.1: seq=6 ttl=64 time=0.525 ms
64 bytes from 192.168.0.1: seq=7 ttl=64 time=0.521 ms
64 bytes from 192.168.0.1: seq=8 ttl=64 time=0.522 ms
64 bytes from 192.168.0.1: seq=9 ttl=64 time=0.522 ms
64 bytes from 192.168.0.1: seq=10 ttl=64 time=0.548 ms
64 bytes from 192.168.0.1: seq=11 ttl=64 time=0.533 ms
64 bytes from 192.168.0.1: seq=12 ttl=64 time=0.526 ms
^C
--- 192.168.0.1 ping statistics ---
13 packets transmitted, 13 packets received, 0% packet loss
round-trip min/avg/max = 0.521/0.564/0.852 ms
root@vusolo2:~# ping yahoo.com
PING yahoo.com (206.190.36.45): 56 data bytes
64 bytes from 206.190.36.45: seq=0 ttl=42 time=108.692 ms
64 bytes from 206.190.36.45: seq=1 ttl=42 time=98.075 ms
64 bytes from 206.190.36.45: seq=2 ttl=42 time=91.522 ms
64 bytes from 206.190.36.45: seq=3 ttl=42 time=91.301 ms
64 bytes from 206.190.36.45: seq=4 ttl=42 time=97.445 ms
^C
--- yahoo.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 91.301/97.407/108.692 ms

vu_duo · Dec 31, 2014

Just a followup on the issue - vuplus have released a patch for some troubled routers.
:notworthy:

Code:

http://code.vuplus.com/gitweb/?p=vuplus_openvuplus;a=blob;f=meta-bsp/vusolo2/recipes/linux/linux-vuplus-3.13.5/linux-bcm_ethernet.patch;h=8be5b495990c99615c329545c0aa8169126b4a7a;hb=6907ca5bf3e3580f17748e8c7cf2ff218c0e613c

vusolo2 network issue

vu_duo

Vu+ Newbie

vu_duo

Vu+ Newbie

paolino

Vu+ User+++

vu_duo

Vu+ Newbie

paolino

Vu+ User+++

vu_duo

Vu+ Newbie

vu_duo

Vu+ Newbie

Pal Ryvaenge

Vu+ Newbie

vu_duo

Vu+ Newbie

vu_duo

Vu+ Newbie

Attachments

blackstalker

Vu+ Newbie

paolino

Vu+ User+++

fatalizer

Vu+ Newbie

vu_duo

Vu+ Newbie

vu_duo

Vu+ Newbie