Welcome! Log In Create A New Profile

Advanced

Can not connect to the network

Posted by SiliCAT 
Forum List Message List New Topic
SiliCAT
Can not connect to the network
January 20, 2018 02:38PM
I had two Pogoplug Mobile devices, one is used as NAS and one is for testing. The first one runs daily routine tasks for more than 1 year and everything is OK. and recently I'm thinking about upgrading its uboot and rootfs and kernel. So I found out the one I used for testing which I have laid aside for a long time, and planned to give the upgrading procedure a try.
But the box couldn't connect to the network.
Symptom: Can not connect to the network. The box's LED indicator light blinks green normally, the rj45 jack light flashes for a while and turns off. Since there is no connection, I can not login to see what happens.
I tried 4.12.1-kirkwood-tld-1-rootfs and 3.18.5-kirkwood-tld-1-rootfs, I got the same result.
I don't remember the uboot version of the box. Do I need to try 3.14.0-kirkwood-tld-1-rootfs? It is an old rootfs and hard to find it.
Any suggestion?
Thanks a lot.
Reply Quote
renojim
Re: Can not connect to the network
January 20, 2018 03:56PM
I can't answer your question, but can you boot it from the device your using to boot your other Pogoplug Mobile?
Reply Quote
SiliCAT
Re: Can not connect to the network
January 20, 2018 04:13PM
Yes, I can use it to boot another V4 (without USB3.0) device, with network connect. But perhaps the two devices don't have the same uboot.
Reply Quote
SiliCAT
Re: Can not connect to the network
January 20, 2018 06:09PM
I can't believe its network hardware is damaged for I just used it for several times and it worked fine. And just now I got some solid evidence for I remembered I set the uboot ipaddr as 172.16.16.117. 
fw_setenv ipaddr    '172.16.16.117'

After it booted, I was able to ping 172.16.16.117 for two or three minutes. So, the network adapter works.



Edited 1 time(s). Last edit at 01/20/2018 11:07PM by SiliCAT.
Reply Quote
bodhi
Re: Can not connect to the network
January 20, 2018 06:39PM
SiliCAT,

> But the box couldn't connect to the network.
> Symptom: Can not connect to the network. The box's
> LED indicator light blinks green normally, the
> rj45 jack light flashes for a while and turns off.
> Since there is no connection, I can not login to
> see what happens.

1. During booting, did the green LED stop blink and became solid green? or it kept blinking?

2. Is this rootfs on USB? Mount this rootfs on the working unit or on another Linux box and list these info. Assuming it is mounted as /media/sdb1. 

e2label /dev/sdb1
ls -lart /media/sdb1/
ls -lart /media/sdb1/boot
ls -lart /media/sdb1/dts/kirkwood*
cat /media/sdb1/etc/network/interfaces
cat /etc/udev/rules.d/70-persistent-net.rules 
cat /lib/udev/rules.d/75-persistent-net-generator.rules

Please the info in code tags here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
SiliCAT
Re: Can not connect to the network
January 20, 2018 11:44PM
Hi bodhi,
Thank you for your help.

1. Three or four minutes after the Pogoplug was turned on, the green LED stopped blink and became solid green. But could not see it from the ASUS-Merlin route. The log of Dnsmasq showed that there was no DHCPREQUEST.

2. The rootfs is on the MicroSD card. It is mounted on another linux box as /dev/sda1 
root@raspberrypi:~# e2label /dev/sda1
rootfs
root@raspberrypi:~# ls -lart /mnt/flash.tmp/
total 96
drwxr-xr-x 11 root root  4096 Jan  1  1970 var
drwxr-xr-x  2 root root  4096 Jan  1  2011 sys
drwxr-xr-x  2 root root  4096 Jan 22  2012 proc
drwxr-xr-x  2 root root  4096 Jan 22  2012 home
drwx------  2 root root 16384 Feb 24  2012 lost+found
drwxr-xr-x 10 root root  4096 Feb 24  2012 usr
drwxr-xr-x  2 root root  4096 Feb 24  2012 srv
drwxr-xr-x  2 root root  4096 Feb 24  2012 opt
drwxr-xr-x  2 root root  4096 Feb 24  2012 media
drwxr-xr-x  5 root root  4096 Feb 24  2012 dev
drwxr-xr-x  2 root root  4096 Feb  8  2013 run
drwxr-xr-x  2 root root  4096 Feb 10  2015 mnt
drwxr-xr-x 21 root root  4096 Feb 17  2015 .
drwxr-xr-x 13 root root  4096 Feb 17  2015 lib
drwxr-xr-x  2 root root  4096 Feb 17  2015 bin
drwxr-xr-x  2 root root  4096 Feb 17  2015 sbin
drwxrwxrwt  2 root root  4096 Feb 24  2015 tmp
drwx------  4 root root  4096 Feb 24  2015 root
drwxr-xr-x 56 root root  4096 Sep 24  2015 etc
drwxr-xr-x  3 root root  4096 Sep 24  2015 boot
drwxr-xr-x  3 root root  4096 Jan 18 20:49 ..
root@raspberrypi:~# ls -lart /mnt/flash.tmp/boot/
total 35404
-rwxr-xr-x  1 root root 2865600 Feb  6  2015 zImage-3.18.5-kirkwood-tld-1
drwxr-xr-x  2 root root    4096 Feb  6  2015 dts
-rw-r--r--  1 root root 2019506 Feb  6  2015 System.map-3.18.5-kirkwood-tld-1
-rw-r--r--  1 root root  131204 Feb  6  2015 config-3.18.5-kirkwood-tld-1
-rwxr-xr-x  1 root root 2865600 Feb  6  2015 vmlinuz-3.18.5-kirkwood-tld-1
-rw-r--r--  1 root root 9460784 Feb  6  2015 linux-headers-3.18.5-kirkwood-tld-1_1_armel.deb
-rw-r--r--  1 root root 2865664 Feb  8  2015 uImage.orig
drwxr-xr-x 21 root root    4096 Feb 17  2015 ..
-rw-r--r--  1 root root 6535220 Feb 19  2015 initrd.img-3.18.5-kirkwood-tld-1
-rw-r--r--  1 root root 6535284 Feb 19  2015 uInitrd
-rw-r--r--  1 root root 2875692 Sep 24  2015 uImage
drwxr-xr-x  3 root root    4096 Sep 24  2015 .
root@raspberrypi:~# ls -lart /mnt/flash.tmp/boot/dts/kirkwood*
-rw-r--r-- 1 root root  9992 Oct 10  2014 /mnt/flash.tmp/boot/dts/kirkwood-rd88f6281-a1.dtb
-rw-r--r-- 1 root root  9944 Oct 10  2014 /mnt/flash.tmp/boot/dts/kirkwood-rd88f6281-a0.dtb
-rw-r--r-- 1 root root 10484 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-b3.dtb
-rw-r--r-- 1 root root 10720 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-d2net.dtb
-rw-r--r-- 1 root root  9698 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-cloudbox.dtb
-rw-r--r-- 1 root root 10154 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-db-88f6282.dtb
-rw-r--r-- 1 root root  9266 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-db-88f6281.dtb
-rw-r--r-- 1 root root 13199 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-dns320.dtb
-rw-r--r-- 1 root root 10037 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-dreamplug.dtb
-rw-r--r-- 1 root root 10180 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-dockstar.dtb
-rw-r--r-- 1 root root 13247 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-dns325.dtb
-rw-r--r-- 1 root root 21708 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds110jv10.dtb
-rw-r--r-- 1 root root 21728 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds109.dtb
-rw-r--r-- 1 root root 22516 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds111.dtb
-rw-r--r-- 1 root root 21752 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds210.dtb
-rw-r--r-- 1 root root 21668 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds209.dtb
-rw-r--r-- 1 root root 22656 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds212.dtb
-rw-r--r-- 1 root root 21688 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds409.dtb
-rw-r--r-- 1 root root 21680 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds409slim.dtb
-rw-r--r-- 1 root root 22520 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds411slim.dtb
-rw-r--r-- 1 root root 21668 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds411j.dtb
-rw-r--r-- 1 root root 22540 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds411.dtb
-rw-r--r-- 1 root root 10284 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-guruplug-server-plus.dtb
-rw-r--r-- 1 root root 21708 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ds212j.dtb
-rw-r--r-- 1 root root 11984 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-iomega_ix2_200.dtb
-rw-r--r-- 1 root root 11609 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-goflexnet.dtb
-rw-r--r-- 1 root root 10387 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-goflexhome.dtb
-rw-r--r-- 1 root root  9966 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-is2.dtb
-rw-r--r-- 1 root root 10637 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ib62x0.dtb
-rw-r--r-- 1 root root 10417 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-laplug.dtb
-rw-r--r-- 1 root root 12487 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-lschlv2.dtb
-rw-r--r-- 1 root root 12483 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-lsxhl.dtb
-rw-r--r-- 1 root root 11354 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-iconnect.dtb
-rw-r--r-- 1 root root 10484 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-mv88f6281gtw-ge.dtb
-rw-r--r-- 1 root root 10859 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-mplcec4.dtb
-rw-r--r-- 1 root root  8310 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-km_kirkwood.dtb
-rw-r--r-- 1 root root 12882 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-netgear_readynas_duo_v2.dtb
-rw-r--r-- 1 root root  9929 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ns2lite.dtb
-rw-r--r-- 1 root root  9962 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ns2.dtb
-rw-r--r-- 1 root root 13062 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-netgear_readynas_nv+_v2.dtb
-rw-r--r-- 1 root root 11405 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-net5big.dtb
-rw-r--r-- 1 root root 12848 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-nsa310.dtb
-rw-r--r-- 1 root root 12232 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-nsa310a.dtb
-rw-r--r-- 1 root root 10217 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ns2mini.dtb
-rw-r--r-- 1 root root 10821 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-net2big.dtb
-rw-r--r-- 1 root root 11395 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-openblocks_a6.dtb
-rw-r--r-- 1 root root 14262 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-nsa325.dtb
-rw-r--r-- 1 root root 13174 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-nsa320.dtb
-rw-r--r-- 1 root root 10249 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ns2max.dtb
-rw-r--r-- 1 root root  9469 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-openrd-base.dtb
-rw-r--r-- 1 root root 11487 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-openblocks_a7.dtb
-rw-r--r-- 1 root root  9625 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-openrd-ultimate.dtb
-rw-r--r-- 1 root root  9922 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-openrd-client.dtb
-rw-r--r-- 1 root root 10028 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-pogoplug_v4.dtb
-rw-r--r-- 1 root root 10228 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-pogo_e02.dtb
-rw-r--r-- 1 root root  9826 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-rd88f6281-z0.dtb
-rw-r--r-- 1 root root  9407 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-rd88f6192.dtb
-rw-r--r-- 1 root root  9881 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-rd88f6281-a.dtb
-rw-r--r-- 1 root root 21668 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-rs409.dtb
-rw-r--r-- 1 root root 22512 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-rs212.dtb
-rw-r--r-- 1 root root 10260 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-sheevaplug.dtb
-rw-r--r-- 1 root root 22540 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-rs411.dtb
-rw-r--r-- 1 root root 11423 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-t5325.dtb
-rw-r--r-- 1 root root 10361 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-sheevaplug-esata.dtb
-rw-r--r-- 1 root root 12211 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-topkick.dtb
-rw-r--r-- 1 root root 11282 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ts219-6282.dtb
-rw-r--r-- 1 root root 10394 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ts219-6281.dtb
-rw-r--r-- 1 root root 10358 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ts419-6281.dtb
-rw-r--r-- 1 root root 11246 Feb  5  2015 /mnt/flash.tmp/boot/dts/kirkwood-ts419-6282.dtb
root@raspberrypi:~# cat /mnt/flash.tmp/etc/network/interfaces
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
root@raspberrypi:~# cat /mnt/flash.tmp/etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)

# Unknown net device (/devices/platform/mv643xx_eth_port.0/net/eth0) (mv643xx_eth_port)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
root@raspberrypi:~# cat /mnt/flash.tmp/lib/udev/rules.d/75-persistent-net-generator.rules
# These rules generate rules to keep network interface names unchanged
# across reboots and write them to /etc/udev/rules.d/70-persistent-net.rules.

# variables used to communicate:
#   MATCHADDR           MAC address used for the match
#   MATCHID             bus_id used for the match
#   MATCHDRV            driver name used for the match
#   MATCHIFTYPE         interface type match
#   COMMENT             comment to add to the generated rule
#   INTERFACE_NAME      requested name supplied by external tool
#   INTERFACE_NEW       new interface name returned by rule writer

ACTION!="add",                          GOTO="persistent_net_generator_end"
SUBSYSTEM!="net",                       GOTO="persistent_net_generator_end"

# ignore the interface if a name has already been set
NAME=="?*",                             GOTO="persistent_net_generator_end"

# new predictable network interface naming scheme
# http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
IMPORT{cmdline}="net.ifnames"
ENV{net.ifnames}=="1",                  GOTO="persistent_net_generator_end"

# device name whitelist
KERNEL!="Eth*|ath*|Wlan*[0-9]|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
                                        GOTO="persistent_net_generator_end"

# ignore Xen virtual interfaces
SUBSYSTEMS=="xen",                      GOTO="persistent_net_generator_end"

# ignore UML virtual interfaces
DRIVERS=="uml-netdev",                  GOTO="persistent_net_generator_end"

# ignore "secondary" raw interfaces of the madwifi driver
KERNEL=="ath*", ATTRS{type}=="802",     GOTO="persistent_net_generator_end"

# ignore "secondary" monitor interfaces of mac80211 drivers
KERNEL=="wlan*", ATTRS{type}=="803",    GOTO="persistent_net_generator_end"

# by default match on the MAC address and interface type
ENV{MATCHADDR}="$attr{address}"
ENV{MATCHIFTYPE}="$attr{type}"

# match interface dev_id
ATTR{dev_id}=="?*", ENV{MATCHDEVID}="$attr{dev_id}"

# These vendors are known to violate the local MAC address assignment scheme
# Interlan, DEC (UNIBUS or QBUS), Apollo, Cisco, Racal-Datacom
ENV{MATCHADDR}=="02:07:01:*", GOTO="globally_administered_whitelist"
# 3Com
ENV{MATCHADDR}=="02:60:60:*", GOTO="globally_administered_whitelist"
# 3Com IBM PC; Imagen; Valid; Cisco; Apple
ENV{MATCHADDR}=="02:60:8c:*", GOTO="globally_administered_whitelist"
# Intel
ENV{MATCHADDR}=="02:a0:c9:*", GOTO="globally_administered_whitelist"
# Olivetti
ENV{MATCHADDR}=="02:aa:3c:*", GOTO="globally_administered_whitelist"
# CMC Masscomp; Silicon Graphics; Prime EXL
ENV{MATCHADDR}=="02:cf:1f:*", GOTO="globally_administered_whitelist"
# Prominet Corporation Gigabit Ethernet Switch
ENV{MATCHADDR}=="02:e0:3b:*", GOTO="globally_administered_whitelist"
# BTI (Bus-Tech, Inc.) IBM Mainframes
ENV{MATCHADDR}=="02:e6:d3:*", GOTO="globally_administered_whitelist"
# Novell 2000
ENV{MATCHADDR}=="52:54:4c:*", GOTO="globally_administered_whitelist"
# Realtec
ENV{MATCHADDR}=="52:54:ab:*", GOTO="globally_administered_whitelist"
# Kingston Technologies
ENV{MATCHADDR}=="e2:0c:0f:*", GOTO="globally_administered_whitelist"


# ignore interfaces with locally administered or null MAC addresses
# and VMWare, Hyper-V, KVM, Virtualbox and Xen virtual interfaces
ENV{MATCHADDR}=="?[2367abef]:*",        ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:00:00:00:00:00",    ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:0c:29:*|00:50:56:*|00:05:69:*|00:1C:14:*", \
                                        ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:15:5d:*",           ENV{MATCHADDR}=""
ENV{MATCHADDR}=="52:54:00:*|54:52:00:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="08:00:27:*",           ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:16:3e:*",           ENV{MATCHADDR}=""

# ignore Windows Azure Hyper-V virtual interfaces
ENV{MATCHADDR}=="00:03:ff:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:0d:3a:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:1d:d8:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:12:5a:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:17:fa:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:22:48:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:25:ae:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="00:50:f2:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="28:18:78:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="50:1a:c5:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="60:45:bd:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="7c:1e:52:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="7c:ed:8d:*", ENV{MATCHADDR}=""
ENV{MATCHADDR}=="dc:b4:c4:*", ENV{MATCHADDR}=""

# ignore Ravello virtual interfaces
ENV{MATCHADDR}=="2c:c2:60:*", ENV{MATCHADDR}=""

LABEL="globally_administered_whitelist"

# ibmveth interfaces have stable locally administered MAC addresses
SUBSYSTEMS=="ibmveth",                  ENV{MATCHADDR}="$attr{address}"

# S/390 interfaces are matched only by id
SUBSYSTEMS=="ccwgroup", \
        ENV{MATCHDRV}="$driver", ENV{MATCHID}="$id", \
        ENV{MATCHADDR}="", ENV{MATCHDEVID}=""

# terminate processing if there are not enough conditions to create a rule
ENV{MATCHADDR}=="", ENV{MATCHID}=="", ENV{INTERFACE_NAME}=="", \
                                        GOTO="persistent_net_generator_end"


# provide nice comments for the generated rules
SUBSYSTEMS=="pci", \
 ENV{COMMENT}="PCI device $attr{vendor}:$attr{device}"
SUBSYSTEMS=="pcmcia", \
 ENV{COMMENT}="PCMCIA device $attr{card_id}:$attr{manf_id}"
SUBSYSTEMS=="usb", \
 ENV{COMMENT}="USB device 0x$attr{idVendor}:0x$attr{idProduct}"
SUBSYSTEMS=="ccwgroup", \
 ENV{COMMENT}="S/390 device at $id"
SUBSYSTEMS=="ibmveth", \
 ENV{COMMENT}="LPAR virtual device at $id"
SUBSYSTEMS=="ieee1394", \
 ENV{COMMENT}="Firewire device $attr{host_id}"
ENV{COMMENT}=="", \
 ENV{COMMENT}="Unknown $env{SUBSYSTEM} device ($env{DEVPATH})"
ATTRS{driver}=="?*", \
 ENV{COMMENT}="$env{COMMENT} ($attr{driver})"


# ignore interfaces without a driver link like bridges and VLANs, otherwise
# generate and write the rule
DRIVERS=="?*", IMPORT{program}="write_net_rules"

# rename the interface if requested
ENV{INTERFACE_NEW}=="?*", NAME="$env{INTERFACE_NEW}"

LABEL="persistent_net_generator_end"

root@raspberrypi:~#



Edited 2 time(s). Last edit at 01/20/2018 11:46PM by SiliCAT.
Reply Quote
bodhi
Re: Can not connect to the network
January 21, 2018 12:41AM
Quote

After it booted, I was able to ping 172.16.16.117 for two or three minutes. So, the network adapter works.

That was u-boot reponse to the ping. Yes, so we know the netword card is working.

Quote

1. Three or four minutes after the Pogoplug was turned on, the green LED stopped blink and became solid green. But could not see it from the ASUS-Merlin route. The log of Dnsmasq showed that there was no DHCPREQUEST.

The kernel has started. Your problem is with the rootfs mounting. Only after the rootfs was mounted and started, the DHCP REQUEST will go out to the router.

The first thing I would do is checking the SD rootfs for error.

At the raspberrypi:~# 

umount /dev/sda1
e2fsck /dev/sda1
sync

And bring it back to the Pogo Mobile, power up.


----

Recommendation

Use a static IP for this rootfs that is the same as the ipaddr env to make it easier to verify. For example,

root@raspberrypi:~# cat /mnt/flash.tmp/etc/network/interfaces 
auto lo eth0
iface lo inet loopback
#iface eth0 inet dhcp
iface eth0 inet static
        address 172.16.16.117
        netmask 255.255.255.0
        gateway <ip of your router here>

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
SiliCAT
Re: Can not connect to the network
January 21, 2018 07:15AM
The result of the file system checking: 
root@raspberrypi:~# e2fsck /dev/sda1
e2fsck 1.43.4 (31-Jan-2017)
rootfs: clean, 14297/3907584 files, 419724/15630080 blocks


A static IP doesn't work. 
root@raspberrypi:/mnt/flash.tmp/etc/network# cat interfaces
auto lo eth0
iface lo inet loopback
#iface eth0 inet dhcp
iface eth0 inet static
        address 172.16.16.117
        netmask 255.255.255.0
        gateway 172.16.16.254


Ping from my laptop windows: 
Pinging 172.16.16.117 with 32 bytes of data:
Reply from 172.16.16.117: bytes=32 time=2ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Request timed out.
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=2ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=2ms TTL=128
Reply from 172.16.16.117: bytes=32 time=1ms TTL=128
Reply from 172.16.16.117: bytes=32 time=2ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.
Reply from 172.16.16.202: Destination host unreachable.

Thanks a lot.
-SiliCAT
Reply Quote
SiliCAT
Re: Can not connect to the network
January 21, 2018 08:59AM
I tried to use netconsole but I couldn't interact with uBoot. 

nc -l -u -p 6666 &
nc -u 172.16.16.117 6666

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:   3

I used MintLinux LiveCD on a USB Flash Drives at my laptop.
I remembered I was able to enter interactive mode years ago. I forgot the setting and environment I used at that time.
Reply Quote
bodhi
Re: Can not connect to the network
January 21, 2018 12:32PM
SiliCAT,

> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47
> -0700)
> Pogoplug V4
> gcc (Debian 4.9.2-10) 4.9.2
> GNU ld (GNU Binutils for Debian) 2.25
> Hit any key to stop autoboot: 3

That's a good sign to see netconsole! Try 

nc -ulp 6666 172.16.16.117 6666

Is there important stuff on this rootfs? can you use a brand new rootfs such as Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Jul 2017) ?

Netconsole will not help in trooubleshooting rootfs mounting problem. To see this problem clearly, serial console is needed. However, it is still good to confirm that the kernel has started using netconsole.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 01/21/2018 12:34PM by bodhi.
Reply Quote
SiliCAT
Re: Can not connect to the network
January 21, 2018 06:40PM
Hi bodhi,
Thank you for your suggestions and with them finally the Pogo is back to work now.
In fact I've tried the 4.12.1 rootfs (24 Jul 2017) yesterday, and failed.
So, today when I saw the light became solid green and there was no new client showed up on the list of the router, I turned the power off quickly.
I had to check the uboot environment again to see if I can find something wrong.
And the netconsole did work by 
mint@mint ~ $ nc.traditional -u -p 6666 172.16.16.117 6666
(I should write it down in case I forgot it again)
I got into the interactive mode and printed all my settings. then I ran 
Pogov4> run bootcmd
Amazing the Pogo came back to work after that.

I restarted it for several time and tested it in different network environment and looks like it is stable now.
I still couldn't figure out the reason that caused the problem, but I'm happy to see the Pogo goes back to work.
Anyway, Let's move on, I'll try to update the uboot, hope everything goes smoothly.

-SiliCAT
Reply Quote
SiliCAT
Re: Can not connect to the network
January 21, 2018 09:08PM
The problem showed up again and I'm testing.
Reply Quote
SiliCAT
Re: Can not connect to the network
January 22, 2018 07:40AM
It's my fault caused the problem. I unpacked the rootfs.tar.bz2 file on an ext4 partition.
Now I've got a brand new rootfs-4.12.1 with kernel-4.14.1, I'm going to update the uboot.



Edited 1 time(s). Last edit at 01/22/2018 09:38AM by SiliCAT.
Reply Quote
bodhi
Re: Can not connect to the network
January 22, 2018 02:19PM
SiliCAT Wrote:
-------------------------------------------------------
> It's my fault caused the problem. I unpacked the
> rootfs.tar.bz2 file on an ext4 partition.
> Now I've got a brand new rootfs-4.12.1 with
> kernel-4.14.1, I'm going to update the uboot.

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: