All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Dennison <dennison@ssd.fsi.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Finding the list of NIC names
Date: Tue, 11 Jul 2006 14:30:03 -0500	[thread overview]
Message-ID: <44B3FC3B.5070305@ssd.fsi.com> (raw)
In-Reply-To: <44B3F285.3060509@corest.com>

Gerardo Richarte wrote:
> Marco Gerards wrote:
>   
>> Ted Dennison <dennison@ssd.fsi.com> writes:
>>   
>>     
>>> I tried looking through the sources too, but couldn't find anything
>>> enlightening. What am I missing?
>>>     
>>>       
>> GRUB 2 does not have networking support yet.  Better use GRUB Legacy.
>>     
Ah. That explains it.

> lots of strings describing the different supported netcards. However,
> your e1000 is not supported (although e100 is... are they compatible? I
> don't think so. If they are you'll need to hack the PCI identification
> values).
>   
I don't think so either. I did a search on the Intel site, and those 
cards have been discontinued for over 8 years now.

E1000 (aka Intel 8254X - series) is the interface that comes on pretty 
much every Intel-based motherboard's built-in NIC for at least the last 
3 years or so. Probably 8 years, since the last series was discontinued.

Anyway, thanks for the (apparently off-topic) help.

-- 
T.E.D.   Work     -  mailto:dennison@ssd.fsi.com
         Home     -  mailto:dennison@telepath.com (Yahoo: Ted_Dennison)
         Homepage -  http://www.telepath.com/~dennison/Ted/TED.html




  reply	other threads:[~2006-07-11 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 18:11 Finding the list of NIC names Ted Dennison
2006-07-11 18:51 ` Marco Gerards
2006-07-11 18:48   ` Gerardo Richarte
2006-07-11 19:30     ` Ted Dennison [this message]
2006-07-20 17:28       ` Michael Hordijk
2006-07-20 20:52         ` Gerardo Richarte

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=44B3FC3B.5070305@ssd.fsi.com \
    --to=dennison@ssd.fsi.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.