the system boots fine, but the network doesn't work

This forum is for all other ARMv5 devices

the system boots fine, but the network doesn't work

Postby berli » Tue Jun 04, 2013 12:47 am

I strict follow the directions
http://archlinuxarm.org/platforms/armv6 ... 3-end-life
to operate every step, the system boots fine
but the network doesn't work
my pogoplug is pogoplug video
attachment is the details about the pogoplug
pogo.jpg
pogo.jpg (101.49 KiB) Viewed 3649 times

I have tried my best to fingure it out by searching many many related this issue topics
but it stills

the daemons' log
$this->bbcode_second_pass_code('', '
Dec 31 18:00:50 alarm dhcpcd[1056]: eth0: eth0: MTU restored to 1500
Dec 31 18:00:54 alarm dhcpcd[800]: eth0: carrier acquired
Dec 31 18:00:54 alarm dhcpcd[800]: eth0: rebinding lease of 192.168.1.103
Dec 31 18:00:54 alarm dhcpcd[800]: eth0: acknowledged 192.168.1.103 from 192.168
.1.1 `\377'
Dec 31 18:00:54 alarm dhcpcd[800]: eth0: leased 192.168.1.103 for 7200 seconds
Dec 31 18:00:54 alarm dhcpcd[1081]: eth0: eth0: MTU set to 576
Dec 31 18:00:55 alarm dhcpcd[800]: eth0: carrier lost
Dec 31 18:00:55 alarm dhcpcd[1100]: eth0: eth0: MTU restored to 1500
Dec 31 18:00:58 alarm dhcpcd[800]: eth0: carrier acquired
Dec 31 18:00:58 alarm dhcpcd[800]: eth0: rebinding lease of 192.168.1.103
Dec 31 18:00:58 alarm dhcpcd[800]: eth0: acknowledged 192.168.1.103 from 192.168
.1.1 `\377'
Dec 31 18:00:58 alarm dhcpcd[800]: eth0: leased 192.168.1.103 for 7200 seconds
Dec 31 18:00:58 alarm dhcpcd[1117]: eth0: eth0: MTU set to 576
Dec 31 18:00:59 alarm dhcpcd[800]: eth0: carrier lost
Dec 31 18:00:59 alarm dhcpcd[1136]: eth0: eth0: MTU restored to 1500
Dec 31 18:01:02 alarm dhcpcd[800]: eth0: carrier acquired
Dec 31 18:01:02 alarm dhcpcd[800]: eth0: rebinding lease of 192.168.1.103
Dec 31 18:01:02 alarm dhcpcd[800]: eth0: acknowledged 192.168.1.103 from 192.168
.1.1 `\377'
Dec 31 18:01:02 alarm dhcpcd[800]: eth0: leased 192.168.1.103 for 7200 seconds
Dec 31 18:01:02 alarm dhcpcd[1153]: eth0: eth0: MTU set to 576
Dec 31 18:01:03 alarm dhcpcd[800]: eth0: carrier lost
Dec 31 18:01:03 alarm dhcpcd[1172]: eth0: eth0: MTU restored to 1500
')

the kernel's log:
$this->bbcode_second_pass_code('', '
[ 1716.580000] eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
[ 1716.580000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1716.970000] Attempting to set new mtu 576
[ 1716.970000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 1716.980000] eth0: Resetting GMAC
[ 1716.980000] eth0: GMAC reset complete
[ 1716.990000] eth0: Setting Rx flow control thresholds for LAN port
[ 1717.540000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 1717.690000] Attempting to set new mtu 1500
[ 1717.700000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 1717.710000] eth0: Resetting GMAC
[ 1717.710000] eth0: GMAC reset complete
[ 1717.710000] eth0: Setting Rx flow control thresholds for LAN port
[ 1718.270000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 1720.770000] eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
[ 1720.770000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1721.160000] Attempting to set new mtu 576
[ 1721.160000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 1721.170000] eth0: Resetting GMAC
[ 1721.170000] eth0: GMAC reset complete
[ 1721.180000] eth0: Setting Rx flow control thresholds for LAN port
[ 1721.740000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
')

I have add the args "-A --noarp --noipv6rs" to /etc/con.d/dhcpd, it likes:
DHCPCD_ARGS="-q -A --noarp --noipv6rs"

but the issue always ...

any suggestion will appreciated!!
berli
 
Posts: 3
Joined: Sun Jun 02, 2013 3:10 pm

Re: the system boots fine, but the network doesn't work

Postby berli » Tue Jun 04, 2013 2:06 pm

the two commands solved the issue that bothers me several days
what a huge help for me
/sbin/depmod -a
/sbin/modprobe gmac


but so far I have n't known the cause??
berli
 
Posts: 3
Joined: Sun Jun 02, 2013 3:10 pm

Re: the system boots fine, but the network doesn't work

Postby xenoxaos » Tue Jun 04, 2013 8:09 pm

You do know that there was a recall on those due to a fire hazard...right?
Arch Linux ARM exists and continues to grow through community support, please donate today!
xenoxaos
Developer
 
Posts: 323
Joined: Thu Jan 06, 2011 1:45 am


Return to Community Supported

Who is online

Users browsing this forum: No registered users and 11 guests