Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
Mogens Kjaer
mk at crc.dkWed Jun 13 08:14:04 UTC 2007
- Previous message: Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
- Next message: Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guolin Cheng wrote: > 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. You don't need a custom kernel to fix this problem. If the interface from which you've PXE booted is named eth1, you can fix the installation by appending "ksdevice=eth1" to the append line in the pxelinux.cfg/default file. 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 at crc.dk Homepage: http://www.crc.dk
- Previous message: Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
- Next message: Thanks -- RE: [CentOS] kickstart fails statically built custom kernel: anacondadoesn't honor static NIC/SATA driver in kernel?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list