From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Krzysztof Baranowski <kgb@dione.ids.pl>
Cc: mj@ucw.cz, linux-kernel@vger.kernel.org,
NetDEV list <netdev@vger.kernel.org>
Subject: Re: PCI DEVICE ID PROBLEM and Intel Intergrated eth card - a bios bug (?)
Date: Wed, 4 Jan 2006 18:56:29 -0800 [thread overview]
Message-ID: <4807377b0601041856n3a9f53e8uf03dc330190432ea@mail.gmail.com> (raw)
In-Reply-To: <4807377b0601041854t4b1410fco5c307db6704e03f6@mail.gmail.com>
On 1/4/06, Krzysztof Baranowski <kgb@dione.ids.pl> wrote:
<snip>
> After the upgrade my network card disappeared from both Linux and Win.
>
> After short investigation I noticed one strange incosistency. Under
> the new BIOS the PCI device is reported as PCI VENDOR ID 1459 (
> which is gigabyte) DEV_ID 1019. However Windows driver for this
> card (the lates from both intel and gigabyte) is looking for
> VENDOR_ID 8086 (intel).
IMO, gigabyte should not have changed the vendor id. Effectively
they've said they will be the only ones supporting this hardware (not
intel). Generally subvendor and subdevice ids should be the only
thing changed by OEMs. Since it was changed by a bios upgrade i bet
its a bios bug and should be reported to gigabyte.
Until then you can hack your local kernel to get around it, but the
e1000 driver probably shouldn't change to support this device ID.
also, this is LKML and mentioning windows is just flame bait. :-)
jesse
parent reply other threads:[~2006-01-05 2:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4807377b0601041854t4b1410fco5c307db6704e03f6@mail.gmail.com>]
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=4807377b0601041856n3a9f53e8uf03dc330190432ea@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=kgb@dione.ids.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=netdev@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