<div dir="ltr">Hi Nate <br><br> Autoconfiguration failure makes sense, but it's not a drivers issue: <br>1: It's a broadcom tg3 driver that is well supported in the kernel. <br>2: the kernel fetches successfully the kickstart configuration file I supply it in the command line and <br>
3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. <br>
4. Sniffing the network showed the following: the kernel fetches the kickstart file, fails to fetch 'product.img' file prints out the error message of being unable to fetch 'stage2.img' file and only when I press the 'OK' button in the HTTP setup window actually contacts the HTTP server and successfully fetches 'stage2.img' file. <br>
<br> My guess is that my configuration isn't handled properlly by anaconda, I just need to find out where (or change my configuration so that anaconda will handle it properly). <br> <br> I (out of haste of getting this email out) omitted the configuration files I use in the kickstart configuration. So here they are ...<br>
pxelinux.cfg/C0A80B02: <br>default ks<br>prompt 0<br>label ks<br> kernel vmlinuz<br> append initrd=initrd.img ramdisk_size=9216 ksdevice=bootif noapic acpi=off ks=<a href="http://192.168.11.1/kickstart/n002.ks">http://192.168.11.1/kickstart/n002.ks</a><br>
ipappend 2<br><br>kickstart configuration file: <br># Kickstart file automatically generated by anaconda.<br><br>install<br>lang en_US.UTF-8<br>keyboard us<br>network --device eth0 --bootproto static --ip <a href="http://192.168.11.2">192.168.11.2</a> --netmask <a href="http://255.255.255.0">255.255.255.0</a> --gateway <a href="http://192.168.11.1">192.168.11.1</a> --nameserver=<a href="http://192.168.11.1">192.168.11.1</a> --hostname <a href="http://n002.example.com">n002.example.com</a><br>
network --device eth1 --onboot no --bootproto dhcp --hostname <a href="http://n002.example.com">n002.example.com</a><br>network --device eth2 --onboot no --bootproto dhcp --hostname <a href="http://n002.example.com">n002.example.com</a><br>
network --device eth3 --onboot no --bootproto dhcp --hostname <a href="http://n002.example.com">n002.example.com</a><br>
<br>url --url <a href="http://192.168.11.1/source">http://192.168.11.1/source</a><br>rootpw --iscrypted ?????????????????????????????????<br>firewall --disabled<br>authconfig --enableshadow --enablemd5<br>selinux --disabled<br>
timezone --utc Asia/Jerusalem<br>bootloader --location=mbr --driveorder=sda --append="noapic acpi=off"<br># The following is the partition information you requested<br># Note that any partitions you deleted are not expressed<br>
# here so unless you clear all partitions first, this is<br># not guaranteed to work<br>zerombr<br>clearpart --all --drives=sda<br>part /boot --fstype ext3 --size=100 --ondisk=sda<br>.<br>.<br>.<br><br><br><br><div class="gmail_quote">
On Mon, Sep 1, 2008 at 5:03 PM, nate <span dir="ltr"><<a href="mailto:centos@linuxpowered.net">centos@linuxpowered.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Paolo Supino wrote:<br>
<br>
> Has anyone encounter this problem and has a solution for it?<br>
<br>
</div>Network autoconfiguration failed, most likely there is not<br>
a compatible driver for the network card in your system.<br>
<br>
If there is a driver disk for that NIC you can use that, what<br>
I typically have done in the past is build an updated driver from<br>
source and insert it into the installation program which is a<br>
fairly complicated process involving extracting the initrd, the<br>
modules.cgz inside of it, putting the compatible driver built<br>
against the same kernel into the modules config and recompressing<br>
the modules file, updating the pci device table for the new device,<br>
and rebuilding the initrd. Also adding a step in the %post section<br>
to install a compatible driver with whatever kernel the installer<br>
ends up installing so when the system reboots it has network<br>
connectivity.<br>
<br>
I also repeat the first part of the process where I insert the<br>
kernel, again in the stage 2 netinst.img? file(forgot off hand<br>
exactly what the file is called), it may not be required for<br>
network drivers, but I think it is for storage drivers, I forget,<br>
been a while since I had to do it.<br>
<br>
nate<br>
<br>
_______________________________________________<br>
CentOS mailing list<br>
<a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</blockquote></div><br></div>