Hello,
I am trying to image some servers, each with a e100 NIC (using PXE-boot): the PXE-boot phase succeeds, the boel kernel starts but then it can't detect the NIC, and obviously fails (when it tries to get its IP address). I tried with the kernel & initrd.img in system-imager 3.0.1-4 and 3.2.0-4.
We have also a number of servers with e1000 NICs, and never had this problem with them.
Any suggestion?
Thanks, Bernard
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Hello Bernard,
I had a similar problem with some boxes with e100 NICs.
As far as I remember, the NIC was detected (e100 driver is in the boel kernel). But the client failed to get an IP address from dhcp.
After the client booted the boel kernel from the net, cat /proc/pci showed that the NIC was on an IRQ that made no sense.
I think the reason was that APIC is configured in the boel kernel, but not e.g. in red hat's kernel.
One solution is to pass an option to the kernel in the pxelinux config file, I think "noapic" (not sure). But this did not work, so I solved it by turning off "APIC select" in BIOS.
This is my suggestion, hope it helps.
Matthias
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
