linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Rohloff <rohloff@in.tum.de>
To: epic@scyld.com, linux-kernel@vger.kernel.org
Subject: epic100.c, SMC EtherPower II, SMC83c170/175 "EPIC"
Date: Mon, 3 Sep 2001 13:04:04 +0200	[thread overview]
Message-ID: <20010903130404.B1064@lxmayr6.informatik.tu-muenchen.de> (raw)

Hello,

I have got a "[SMC] 83C170QF" adaptor in my computer and I wasn't
able to use the driver which is in linux-2.4.9.

The sympotms are lot's of messages of this in /var/log/messages:
"kernel: eth0: Too much work at interrupt, IntrStatus=0x008d0004"

This seems to be a known problem; at least I found other people
complaining about the same message in their kernel logs.
The problem has different severity for different people. 
I wasn't able to get the card working at all (basically the
computer hung, while trying to mount several NFS directories).

After searching the web for further information I was able
to obtain a patched version, which was modified Heiko Boch. 
It seems this version is an older linux-2.4.x driver with 
some additional patches.

This version works without glitches on my system with a 
vanilla linux-2.4.9 kernel. 

The homepage of Heiko Boch doesn't seem to exist anymore, so
for all people who use this card and have the above problem,
I put his modified version of epic100.c on my home page at
www.in.tum.de/~rohloff (look for epic100.c). 

I hope that after some testing someone can have a look over
this version, who really can tell what the essential differences
compared to the version in linux-2.4.9 are.

Perhaps this will lead to a working linux-2.4.xx version in the future.

so long
  Ingo

             reply	other threads:[~2001-09-03 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 11:04 Ingo Rohloff [this message]
2001-09-07 14:01 ` epic100.c, SMC EtherPower II, SMC83c170/175 "EPIC" Ingo Rohloff
2001-09-07 14:03   ` epic100.c, gcc-2.95.2 compiler bug! Ingo Rohloff
2001-09-07 14:13     ` antirez
2001-09-07 14:26       ` Jakub Jelinek

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=20010903130404.B1064@lxmayr6.informatik.tu-muenchen.de \
    --to=rohloff@in.tum.de \
    --cc=epic@scyld.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;
as well as URLs for NNTP newsgroup(s).