Re: [Gumstix-users] Connect & Etherstix: not present(-19).

[Craig H. <cr...@gu...>]

On Dec 28, 2005, at 3:23 PM, Kevin Shaw wrote:

> Craig,
>
> Yes, this is entirely a factory bootloader and kernel.
>
> Unfortunately I'm traveling and only have access via usbnet in an
> audiostix now.  I can post the output in a few days if no solution
> appears on the listserv.
>
> About the module:
> I'm starting eth0 by default and the module is loaded automatically
> because eth0 is aliased to smc91x in modprobe.conf.
>
> I can repeat this whole scenario by unloading smc91x and
> gumxstix_smc91x, and then doing a manual 'ifup eth0'. The -19 message
> appears in the log whenever the module is loaded.
>
> Coincidentally, all behavior is the same without etherstix attached.
> hardware problem?

Could be -- the output from u-boot is the way to tell if the gumstix  
CPU can see the ethernet controller and whether it's able to talk to  
it correctly or not.  "md.l 04000300" will have u-boot dump the  
contents of memory at address 0x04000300, which is mapped in the CPU  
to the location where the ethernet controller lives.  The output from  
that command will show whether or not the data that the CPU reads  
from that location looks OK or not wrt what the output ought to be if  
the controller's working properly.  If the output looks OK, but  
things aren't working in linux, then likely it's a software problem,  
eg possibly a flash memory corruption issue, or something like that  
on the gumstix board.  If the output doesn't look OK, then likely  
something happened to the etherstix board, which would then probably  
need replacing.

C