• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 306 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Network unreliable on DM6467T EVM

Helmut Forren
Mastermind 6805 points

 

When I restart my DM6467T EVM, sometimes the network is accessible and sometimes it's not.  The problem seems to occur randomly.

EDIT: Note that it works 100% when I interrupt U-Boot and type "ping 192.168.123.33" (my WRT610N router).  But then booting from there, Linux still fails most of the time, but not always.

When the network WORKS, I see the following during boot up:

 

ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.13.2) started
Sending discover...
Sending discover...
PHY: 1:01 - Link is Up - 1000/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.123.19...
Lease of 192.168.123.19 obtained, lease time 86400
adding dns 192.168.123.33
adding dns 192.168.254.254
done.

But when the network FAILS, I see this:

ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.13.2) started
Sending discover...
Sending discover...
PHY: 1:01 - Link is Up - 1000/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
No lease, failing
done.
Perhaps this is just a timing problem.  I know very little about linux configuration.  Is there a way to add another retry for "sending discover..." or is there a way to add a time delay between when the "link becomes ready" and "Sending discover..."?
Thanks very much,
Helmut

 

  • 0
    Mastermind 6805 points

    Still having problems.  Note just now I noticed "udhcpc (v1.13.2) started" line in bootup log.  I tried running from prompt myself, but after a successful network connect.  The command was found an discover got my IP address successfully.  So I rebooted.  As expected, this time the network failed again.  So I logged in as root and manually tried udhcpc again.  Well, it's still trying over and over again.  So I don't think it's a case of just trying udhcpc one more time.  There's something fundamentally wrong, and it's wrong probably 80% of the time.  That is, I have to reboot five times to get the network working.

    Note ping from interrupted U-boot is 100% reliable.

  • 0 in reply to Helmut Forren
    TI__Expert 5170 points

    Hi,

    Can you use static IP address and see whether the error goes away? To use static IP address, you need to modify the bootargs from U-Boot. You need to change ip=dhcp to ip=<static IP address> from u-boot to use static IP address.

    Regards, Sudhakar

  • 0 in reply to Sudhakar Rajashekhara
    Mastermind 6805 points

    Thanks very much for the advice.

    Note that I had no "ip=" spec in my bootargs at all, from prior testing.  Including "ip=dhcp" leads to a very time consuming timeout and then apparently a hang (I don't have enough patience).  Putting in "ip=192.168.123.19" leads surprisingly to the same behavior...  a very time consuming timeout and then apparently a hang.  (The boot log even says the same thing, suggesting it's trying to do dhcp.)

    I've tried "ip=off" before, and that didn't work.  The only thing that seems to work part of the time is no "ip=" setting at all.

    Note that when I do provide ip=dhcp or ip=192.168.123.19, the dhcp attempt occurs fairly early in the boot log on the terminal.  When I leave it out, however, it's not until fairly late that udhdpc (v1.13.2) is started, which sometimes works.

    And again, from U-Boot, ping 192.168.123.33 works every single time, no problem at all.