[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug #1760] need to be able to exclude onboard eepro100 nic from being u
From: |
nobody |
Subject: |
[Bug #1760] need to be able to exclude onboard eepro100 nic from being used. |
Date: |
Wed, 20 Nov 2002 20:17:00 -0500 |
=================== BUG #1760: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1760&group_id=68
Changes by: Yoshinori K. Okuji <address@hidden>
Date: 2002-Nov-21 01:17 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Priority | None | Low
Bug Group | Action Request | Feature Request
------------------ Additional Follow-up Comments ----------------------------
For now, you must modify netboot/config.c. It would be
desirable to support multiple NICs (or at least support
choosing one of them), but nobody works on it.
Okuji
=================== BUG #1760: FULL BUG SNAPSHOT ===================
Submitted by: jus_albstmeijer Project: GNU GRUB
Submitted on: 2002-Nov-20 22:25
Category: Network Severity: Major
Priority: Low Bug Group: Feature Request
Resolution: None Assigned to: None
Status: Open Release: 0.92
Reproducibility: Every Time Planned Release:
Summary: need to be able to exclude onboard eepro100 nic from being used.
Original Submission: Hi,
I have a small problem.
I use pxegrub on a system with mutiple eepro100 nics.
One of the eepro100 nics is onboard.
The one with the PXE bootrom is a pci card.
When pxegrub starts, it probes and finds the onboard card.. This card is not
connected to the subnet where the tftpd server offers the menu.lst.. so pxegrub
stops.
Is there a way to exclude the onboard card from being probed by pxegrub? or can
I specify witch nic to use?
Follow-up Comments
*******************
-------------------------------------------------------
Date: 2002-Nov-21 01:17 By: okuji
For now, you must modify netboot/config.c. It would be
desirable to support multiple NICs (or at least support
choosing one of them), but nobody works on it.
Okuji
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1760&group_id=68