From: Bukie Mabayoje <bukiemab@gte.net>
To: Michael Gernoth <simigern@stud.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org,
Matthias Koerber <simakoer@stud.informatik.uni-erlangen.de>
Subject: Re: 2.4.29, e100 and a WOL packet causes keventd going mad
Date: Fri, 28 Jan 2005 12:05:15 -0800 [thread overview]
Message-ID: <41FA9AFB.28FB30BD@gte.net> (raw)
In-Reply-To: 20050128185402.GA7923@cip.informatik.uni-erlangen.de
Michael Gernoth wrote:
> On Fri, Jan 28, 2005 at 10:53:51AM -0800, Bukie Mabayoje wrote:
> > Do you know the official NIC product name e.g Pro/100B. I need to identify
> > the LAN Controller. There are differences between 557 (not sure if 557 can
> > do WOL), 558 and 559 how they ASSERT the PME# signal. Even the same chip have
> > differences between steppings.
>
> The chip is integrated on the motherboard. Its PCI ID is 8086:1039.
> lspci says: Intel Corp. 82801BD PRO/100 VE (LOM) Ethernet Controller (rev 81)
> If you want I can open up one of these machines tomorrow to look on the chip
> directly.
>
> Regards,
> Michael
Thanks got enough information....
next prev parent reply other threads:[~2005-01-28 19:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 16:48 2.4.29, e100 and a WOL packet causes keventd going mad Michael Gernoth
2005-01-28 18:53 ` Bukie Mabayoje
2005-01-28 18:54 ` Michael Gernoth
2005-01-28 20:05 ` Bukie Mabayoje [this message]
2005-01-30 0:13 ` Bukie Mabayoje
2005-01-29 18:18 ` Marcelo Tosatti
2005-01-30 12:15 ` Michael Gernoth
-- strict thread matches above, loose matches on Subject: below --
2005-01-30 17:18 David Härdeman
2005-01-31 3:47 ` Scott Feldman
2005-01-31 3:58 ` Nigel Cunningham
2005-01-31 5:00 ` Scott Feldman
2005-01-31 6:14 ` Nigel Cunningham
2005-01-31 9:08 ` Nigel Cunningham
2005-01-31 4:23 ` Bukie Mabayoje
2005-01-31 15:24 ` Marcelo Tosatti
2005-01-31 20:29 ` David Härdeman
2005-01-31 21:13 ` Bukie Mabayoje
2005-01-31 19:26 Brandeburg, Jesse
2005-01-31 20:57 ` Bukie Mabayoje
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=41FA9AFB.28FB30BD@gte.net \
--to=bukiemab@gte.net \
--cc=linux-kernel@vger.kernel.org \
--cc=simakoer@stud.informatik.uni-erlangen.de \
--cc=simigern@stud.uni-erlangen.de \
/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