|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Jason Wright (jason
thought.net)Date: Wed Apr 04 2001 - 16:28:20 CDT
On Wed, Apr 04, 2001 at 05:06:23PM -0400, John del Valle wrote:
> hello Jason;
>
> problems still persist. here is what I am getting from generic
> kernel:
>
> ledma0 at sbus0 slot 5 offset 0x8400010: rev 2
> le0 at ledma0 offset 0x8c00000 pri 6: address 08:00:20:76:db:57
> le0: 16 receive buffers, 4 transmit buffers
> audiocs0 at sbus0 slot 4 offset 0xc000000 pri 9, softpri 4
> audio0 at audiocs0
> power-management at sbus0 slot 4 offset 0xa000000 not configured
> le1 at sbus0 slot 1 offset 0xc00000 pri 7: address 08:00:20:76:db:57
> le1: 16 receive buffers, 4 transmit buffers
>
Please people, ALWAYS send full dmesg output, not "relevant bits."
> as you can see the ether addresses for le0 and le1 are the
> same.
Welcome to the world of Sun. Most sbus ethernet cards do not have
unique MAC addresses, instead they use a single MAC address for the
-machine- (based on interpretation of the early ethernet stuff). This
is not a problem as long as they are on seperate segments.
> not only that, when I ifconfig the device up I get :
>
> Apr 4 15:57:16 shearer syslogd: /dev/:0: No such file or directory
Dunno what that is.
> Apr 4 15:57:16 shearer /bsd: le1: device timeout
>
Ah, this is a different problem that what I fixed, I believe. (Although
this card does need the updates in current because it's an 'le' without
a 'ledma' or 'lebuffer' in the middle). There are no
"failure to initialize" messages in dmesg are there?
--Jason L. Wright
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]