All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Frustrating problem with natsemi (DP83815) ethernet
Date: Thu, 07 Jul 2005 03:11:08 +0000	[thread overview]
Message-ID: <42CC9D4C.2A815D0D@iswest.com> (raw)
In-Reply-To: <20050706124836.GB18695@legolas.on.net.mk>

Damjan wrote:
> 
> [Sorry if this is off-topic for this list, please advise me if there's a
> better place to ask this]
> 
> I have an embeded motherboard with 4 natsemi (DP8315) ethernet chips.
> I'm running a 2.6.9 kernel (I've tried 2.6.11 too) and a very minimal
> Slackware distribution.
> 
> Now about the problem:
> The network interfaces seem to NOT transmit anything when the interface
> is autonegotiated at 100Mbit-FD. I've forced the interfaces to
> half-duplex with mii-tool still nothing.
> 
> I see, with tcpdump, that packets are comming in (broadcasts and multicasts)
> and I see the packets that are supposed to go out of the interface. But
> nothing is recevied on the other side. I've tried to put the interfaces
> in a switch and with a cross-over cable to another PC.
> 
> I've also tried to mannually fix the MAC <-> IP address with "arp -s",
> thinking that maybe ARP is not working, still nothing - I see icmp
> requests enter the interface I see icmp replies go out of the interface,
> but nothing gets to the other side (PC).
> 
> I've tried all of the interfaces, I've tried enabling and disabling
> ACPI. The only modules I'have loaded are uhci-hcd and usbhid (since the
> computer doesn't have ps2 ports). 3 of the 4 interfaces don't share an
> IRQ with anything (cat /proc/interrupts).
> 
> If I force the interface to 10Mbit (either FD or HD) then everything works.
> 
> Now the stangest thing, I got the motherboard with some kind of
> basterized Debian installed on it. I couldn't understand it, so I backuped
> it up and installed my mini Slackware. I used the same kernel from the
> original distribution which has the ethernet driver compiled in. The
> original distribution is not setting any extra parameters in lilo.conf.
> And with that distribution hte interfaces work even at 100mbit.
> 
> I just can't find what that distribution does to make the interfaces work
> at 100mbit. Its not the kernel, I use the same one. Its not some
> parameters to the driver... I don't know what could be the problem.
> 
> So, any ideas???
> 
> --
> damjan | дамјан
> This is my jabber ID --> damjan@bagra.net.mk <-- not my mail address!!!

What have you tried?

What is the working distro _EXACTLY_?  "some kind of basterized Debian" is not
enough.  What does dmesg say about the DP8315?

Have you looked at the Debian ifconfig?

Is the same cable being used?  Same cable path?  I found a 10 Mb hub in a
customer setup that was hidden behind the next desk where the Bad Boy computer
plugged in.  The computer thought the connection was 100Mb but it would only
work at 10.

Sorry, gotta go.  Google the distro and DP8315.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-07-07  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 12:48 [LARTC] Frustrating problem with natsemi (DP83815) ethernet devices Damjan
2005-07-07  3:11 ` gypsy [this message]
2005-07-07  5:38 ` [LARTC] Frustrating problem with natsemi (DP83815) ethernet Michael Renzmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42CC9D4C.2A815D0D@iswest.com \
    --to=gypsy@iswest.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.