From: Eugene San <eugenesan@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Davicom 9102AF (dmfe) / Alladin V IDE(ali15xx) on sparc64(v100/Netra-x)
Date: Mon, 09 May 2005 01:42:16 +0200 [thread overview]
Message-ID: <427EA3D8.1060001@gmail.com> (raw)
Probem with Davicom91xx ethernet NIC on sparc64(v100/Netra-x) is well
known (google ::dmfe+sparc).
The problem is that specific driver (dmfe) can be loaded but once used
couses errors on PCI/sabre and at the end couses Kernel Panic.
Some pepole advice using (tulip) wich loads but fails to work normaly:
it works at ~10Mbps in 10BaseT4 mode while all other modes brings
huge amount of carierr/TX errors and VERY low throuput(sometimes less
then 50Kbps) and after some time at mid/high load driver fails
with some kind of TX errors.
Another problem is with DMA on Alladin V wich used on thoses machines.
Usualy kernel unable to boot if strated without ide=nodma. If DMA
set-on after boot is often couses data loses.
Bothe problems well known for a long time but somehow not treated till now.
The problems exists in kernels since 2.4.17 up to latest 2.6.11 ( all
versions in that range tested by me :-( )
I wonder if there anything that can be done to make those sparc64
machines usable with linux.
Thanks ahead.
reply other threads:[~2005-05-08 22:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=427EA3D8.1060001@gmail.com \
--to=eugenesan@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome