Re: Can't ping device...

---

Are these topics of interest to people on the slimp3-dev list? I figure
it might be so I'm replying to the list.

----

Amos,

We can narrow it down with the packet sniffer.  "Looking for server"
really means "sending ARP request". If you don't see an arp broadcast,
then there is possibly a problem with the transmit side of the Ethernet
interface. the first thing you should try is a different cable, but it
sounds like you've already tried that.

You can test the receive side by flood pinging the broadcase address. In
this case:

ping -fb 192.168.0.255  (as root)

Even if the player doesn't respond to the pings, you'll see a message on
the display if it's receiving them.

All the players are tested before they're shipped, and they're actually
quite rugged. I have prototypes that I've been lugging around in the car
for months, with no problems. Still, there have been two DOA units so far,
so it's no impossible that you have a hardware problem.

If it seems like there might be a problem with the Ethernet interface, try
gently flexing the board near the CS8900 chip. If there was a loose pin
then it might start working. Unfortunately hand soldering is not as
reliable as reflow.

Anyway, if there really is a problem with the player I will replace it,
no charge.


Sean


On Thu, 18 Oct 2001, Amos Hayes wrote:

>
> I just received number 68. I can not get the unit to respond to pings, nor
> will it ever get past "Looking for server - please wait". I have gone
> throungh the IP setup numerous times, tried plugging it into (and
> reconfiguring for) a couple different networks at home (one with a 10baseT
> hub - the other with a 100baseT switch), and pinging from different
> machines. Nothing.
>
> tcpdump doesn't show any traffic on the wire. The link light is on on the
> unit and the other led flashes for a bit after I power up and hit the left
> button. No sign of traffic on the hub either.
>
> If I'm doing something dumb, I can't figure out what. One of the sets of
> settings I tried was 192.168.000.005 192.168.000.006 255.255.255.000
> 192.168.000.001 in case that helps the debugging. I can't help but think
> it's a hardware problem at this stage though.
>
> Oh... and the display has yet to power down during any of this testing. I
> don't know if it's supposed to before talking to the server... would have
> thought so.
>
> Anyway, if anyone has any clues, I'd appreciate them.
>
> --
> Amos Hayes
> [email protected]
>
>
> To unsubscribe from this group, send an email to:
> [email protected]
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Pinpoint the right security solution for your company- Learn how to add 128- bit encryption and to authenticate your web site with VeriSign's FREE guide!
http://us.click.yahoo.com/yQix2C/33_CAA/yigFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/