Mogens,
The Booting Sequence problem is described below:
Two types of NICs are installed on one machine, BIOS/PXE boots from one
type, but after that Linux/Kickstart kernel detect another type NIC as
eth0 and trying to install from that unconnected NIC.
A custom kernel is built to statically built-in the BIOS/PXE detected
NIC's driver into kernel, hoping to fix the problem in a hard way but
failed.
Kickstart/anaconda always try to load a .ko driver for each detected NIC
types, so when the driver is static built (into kernel), the Kickstart
process hangs because it can not locate/load the related .ko module
file.
I have fixed the problem in a non-standard way, not very elegant but
works.
By the way, the suggested 'noprob,nonet' and 'device eth0
<module1>:<module2>:...' combination doesn't work at all for my case --
since the latter is defined in a ks.cfg but my ks.cfg needs to be
downloaded from network.
--Guolin
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
Behalf Of Mogens Kjaer
Sent: Saturday, June 09, 2007 5:49 AM
To: CentOS mailing list
Subject: Re: kickstart fails statically built custom kernel:
anacondadoesn't honor static NIC/SATA driver in kernel?
Guolin Cheng wrote:
...
> The network card driver tg3 is statically built into custom kernel to
> fix NIC driver loading sequence problem( I have mixed type NICs on
> these boxes), so there is no tg3.ko in my rolled modules/modules.cgz
> file.
Could you explain "loading sequence problem"?
Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk@xxxxxx Homepage: http://www.crc.dk
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
