From: Joseph V Moss <jmoss@ichips.intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] disabling nics in efi.
Date: Wed, 08 Jan 2003 21:50:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805646@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805644@msgid-missing>
Have you tried just using the 'ksdevice=eth2' option to tell anaconda to
use eth2 for the kickstart install?
> I have a bunch of HP rx2600 that have two internal nics (10/100Mbit and 1Gbit)
> and one external nic (1Gbit). Is it possible to disable the two internal
> ones in efi so linux won't see them? I tried to use the disconnect command
> in the efi shell, but they still keep showing up when I boot up linux.
> I used
> disconnect 4C
> disconnect 49
> and they report successful operation. Am I missing the point completely?
>
> I also tried the reserve= boot option to avoid linux to probe them, but that
> didn't work either. I probably computed the iobase and extents wrong. Do
> anyone know how to determine the correct parameters?
>
> The reason for wanting to disable the internal nics is that the redhat
> installer insists on fetching the kickstart file over eth0 when doing
> installations over the network and the external nic that I want to use
> becomes eth2.
>
> Any hints is greatly appreciated.
>
> Best regards,
> Roy.
> --
>
> The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
> phone:+47 77 64 41 07, fax:+47 77 64 41 00
> Roy Dragseth, High Performance Computing System Administrator
> Direct call: +47 77 64 62 56. email: royd@cc.uit.no
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
next prev parent reply other threads:[~2003-01-08 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 21:39 [Linux-ia64] disabling nics in efi Roy Dragseth
2003-01-08 21:50 ` Joseph V Moss [this message]
2003-01-08 21:52 ` Alex Williamson
2003-01-08 21:58 ` Roy Dragseth
2003-01-08 22:08 ` Roy Dragseth
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=marc-linux-ia64-105590709805646@msgid-missing \
--to=jmoss@ichips.intel.com \
--cc=linux-ia64@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