public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurgen Botz <jurgen@botz.org>
To: linux-kernel@vger.kernel.org
Subject: eepro100.c & Intel integrated MBs
Date: Mon, 29 Oct 2001 08:53:15 -0800	[thread overview]
Message-ID: <11361.1004374395@nova.botz.org> (raw)

I recently discovered (as others have posted to the list) that the
currently included eepro100 driver doesn't work on Intel 815 (and
possibly other) integrated mainboards.  I stops working after a bit
of activity and in some circumstances totally locks up the machine.
For more details scan the archives, lots of people have run into
this.

I'm now using the e100 driver from the Intel web site, which works
perfectly, and light testing shows the Scyld (Don Becker) driver
to work as well.  The Intel driver seems to have an incompatible
license (noxious advertising clause?), but the Scyld drivers don't...
at least there isn't any license mentioned and of course many 
of the net drivers in the current kernel are just earlier versions
of the Scyld drivers.

815 MBs are pretty common, so getting a solution to this should
be pretty important.  I'm surprised that RedHat didn't include
the Scyld drivers in 7.2... these network lockups should present
a major support headache for them.

So what's the scoop?  Anyone have plans to fix this?

:j

-- 
Jürgen Botz                       | While differing widely in the various
jurgen@botz.org                   | little bits we know, in our infinite
                                  | ignorance we are all equal. -Karl Popper



             reply	other threads:[~2001-10-29 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 16:53 Jurgen Botz [this message]
2001-10-29 17:16 ` eepro100.c & Intel integrated MBs Ben Greear
2001-10-29 17:33   ` Arjan van de Ven
2001-10-29 17:49     ` Ben Greear
2001-10-29 18:01       ` Alan Cox
2001-10-29 18:52     ` J Sloan
2001-10-29 18:05   ` Alan Cox
2001-10-29 17:29 ` Alan Cox

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=11361.1004374395@nova.botz.org \
    --to=jurgen@botz.org \
    --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