Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Ethernet Probe Order

Ethernet Probe Order

2006-01-06       - By Brian Long

 Back
Reply:     <<     11     12     13     14     15     16  

On Thu, 2006-01-05 at 17:09 -0500, Ed Griffin wrote:
> I am curious, as I have googled this to death, how to force a system to
> have the motherboard card be eth0 and eth1.  My configuration is as
> follows, a Dell PowerEdge 1850 with an add-on Intel Pro 1000 Quad Port
> card.  The quad port card gets found first and becomes eth0 through eth3
> and the motherboard cards end up as eth4 and eth5.  This has caused some
> problems during kickstarts and the like.  I am sure there is something I
> can pass via grub to the initrd to get this to go to the motherboard
> first but I just can't seem to decipher it.  The weird thing is that on
> a RHEL4 box it seems to behave the opposite, or to be more specific the
> way I want it to.

Ed,

Just another point to note: depending on whether you are running RHEL 3
i386 or x86_64, the probe order changes.  Arjan explained this about a
year ago.  It's because the i386 kernel in RHEL 3 does not use ACPI for
probing bus order, but the x86_64 kernel does.  x86_64 kernel can use
ACPI by default because they know all x86_64 motherboards support it.
They do not know this for all i386/i686 motherboards, so they stuck with
the other method (forget what it is).

On RHEL 4 with 2.6 kernel, both i386/i686 and x86_64 kernels probe in
the same order.

We have over 500 servers from a certain vendor that uses mainstream Tyan
2881 motherboards.  The onboard ports change order (eth0, eth1)
depending on if you load RHEL 3 i386 or x86_64.  What a pain in the
butt!  We got around this with hardware profiles in our make_bootdisk
perl CGI (http://kickstart-tools.sf.net).  If someone selects that
vendor's system for installation, we alter the ksdevice line in
syslinux.cfg depending on if they choose a i386 or x86_64-based
distribution for installation.

/Brian/

--
      Brian Long                      |         |           |
      IT Data Center Systems          |       .|||.       .|||.
      Cisco Linux Developer           |   ..:|||||||:...:|||||||:..
      Phone: (919) 392-7363           |   C i s c o   S y s t e m s

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list