Guolin Cheng
2007-Jun-08 18:18 UTC
[CentOS] kickstart fails statically built custom kernel: anaconda doesn't honor static NIC/SATA driver in kernel?
Kickstart fails for statically built custom booting kernel, although the custom kernel is built form the same version stock kernel source. My anaconda and kernel source are both of stock versions on Centos 5. At the kickstart 'F3' screen, the following error messages appear: Modules to insert tg3 ... ... ERROR: no network devices in choose network device! ERROR: no network drivers for doing kickstart ERROR: unable to bring up network. 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. Does this problem mean that kickstart/anaconda doesn't recognize NIC/SATA drivers statically built into booting kernel? Anaconda needs everything to exist in dynamic module form (*.ko in modules.cgz)? Thanks.
Mogens Kjaer
2007-Jun-09 12:49 UTC
[CentOS] kickstart fails statically built custom kernel: anaconda doesn'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 at crc.dk Homepage: crc.dk
Apparently Analagous Threads
- custom kernel for Centos 5 kickstart?
- CentOS 5.1 and HP DL145 G2 SATA server configured with Raid
- system-config-kickstart
- kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
- CentOS 5: rsyncd log problem