<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV>I guess it's not the same one. Do you have the proper kernel-BOOT image, and the proper version of anaconda? You might want to make sure that anaconda is up to date. I would check /usr/lib/anaconda-runtime/loader2/module-info (I'm not sure that location is correct, but it should be around there) to make sure that anaconda recognizes the card, and installs the correct module.</DIV><DIV> </DIV><DIV>Matt</DIV> <DIV><DIV>On 9-Apr-07, at 12:11 PM, Doug Rylaarsdam wrote:</DIV> <BLOCKQUOTE type="cite"><O:SMARTTAGTYPE namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"> <DIV class="Section1">Regarding the question that someone asked about which Broadcom devices were in the server (I’m currently missing that email to include here), this is the pci information. The tg3 driver was installed during the RHEL3u8 CD installation, so I’m suspecting that the tg3 is the driver at issue in the boot image for the network install. I’ve been able to do a network install of RHEL4u3 on this hardware, but not RHEL3u8.<O:P></O:P><O:P> </O:P>06:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3)<O:P></O:P> Subsystem: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet<O:P></O:P> Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 15<O:P></O:P> Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]<O:P></O:P> Memory at fdfe0000 (64-bit, non-prefetchable) [size=64K]<O:P></O:P> Capabilities: [40] PCI-X non-bridge device.<O:P></O:P> Capabilities: [48] Power Management version 2<O:P></O:P> Capabilities: [50] Vital Product Data<O:P></O:P> Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-<O:P></O:P><O:P> </O:P>06:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3)<O:P></O:P> Subsystem: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet<O:P></O:P> Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 10<O:P></O:P> Memory at fdfc0000 (64-bit, non-prefetchable) [size=64K]<O:P></O:P> Memory at fdfb0000 (64-bit, non-prefetchable) [size=64K]<O:P></O:P> Capabilities: [40] PCI-X non-bridge device.<O:P></O:P> Capabilities: [48] Power Management version 2<O:P></O:P> Capabilities: [50] Vital Product Data<O:P></O:P> Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-<O:P></O:P><O:P> </O:P>Thanks,<O:P></O:P>Doug<O:P></O:P><O:P> </O:P> <DIV> <DIV class="MsoNormal" align="center" style="text-align:center"> <HR size="2" width="100%" align="center" tabindex="-1"> </DIV>From: Shabazian, Chip [<A href="mailto:Chip.Shabazian@bankofamerica.com">mailto:Chip.Shabazian@bankofamerica.com</A>] Sent: Friday, April 06, 2007 2:35 PM To: <ST1:PERSONNAME w:st="on">Discussion list about Kickstart</ST1:PERSONNAME> Subject: RE: RHEL3U8 pxe install: no driver for Broadcom NIC?<O:P></O:P> </DIV><O:P> </O:P>Not sure why you are having this issue then. I would go back to Sun and tell them you need a driver disk (both IBM and HP supply driver disks in this scenario). You then simply load the driver during the build: dd=<A href="http://path">http://path</A>_to/disk.img<O:P></O:P> <O:P></O:P>Chip<O:P></O:P><O:P> </O:P> <DIV class="MsoNormal" align="center" style="text-align:center"> <HR size="2" width="100%" align="center" tabindex="-1"> </DIV>From: kickstart-list-bounces@redhat.com [<A href="mailto:kickstart-list-bounces@redhat.com">mailto:kickstart-list-bounces@redhat.com</A>] On Behalf Of Doug Rylaarsdam Sent: Friday, April 06, 2007 12:24 PM To: '<ST1:PERSONNAME w:st="on">Discussion list about Kickstart</ST1:PERSONNAME>' Subject: RE: RHEL3U8 pxe install: no driver for Broadcom NIC?<O:P></O:P>Yes, I’m using the same setup as my RHEL3U3 kickstarts. I’m using the same DHCP and tftp server. I’ve added the RHEL3U8 distribution to the kickstart server, and added a target in the pxelinux configuration with the vmlinuz kernel and initrd.img from the U8 distribution. For the network setup, the kickstart server uses a second NIC to support the kickstart clients. I simply connect the client machine directly to an unmanaged layer2 switch (Linksys EF4124), which is where the second interface on the kickstart server is also located.<O:P></O:P><O:P> </O:P>Doug<O:P></O:P><O:P> </O:P> <DIV> <DIV class="MsoNormal" align="center" style="text-align:center"> <HR size="2" width="100%" align="center" tabindex="-1"> </DIV>From: Shabazian, Chip [<A href="mailto:Chip.Shabazian@bankofamerica.com">mailto:Chip.Shabazian@bankofamerica.com</A>] Sent: Friday, April 06, 2007 2:01 PM To: <ST1:PERSONNAME w:st="on">Discussion list about Kickstart</ST1:PERSONNAME> Subject: RE: RHEL3U8 pxe install: no driver for Broadcom NIC?<O:P></O:P> </DIV><O:P> </O:P>Are you on the same switch and subnet that you have previously had good kickstarts from? This is USUALLY an error related to portfast and Cisco switches. The fact that the install works fine using the included driver when you build from CD adds to my suspicion that this is network, not NIC related.<O:P></O:P> <O:P></O:P>Chip<O:P></O:P><O:P> </O:P> <DIV class="MsoNormal" align="center" style="text-align:center"> <HR size="2" width="100%" align="center" tabindex="-1"> </DIV>From: kickstart-list-bounces@redhat.com [<A href="mailto:kickstart-list-bounces@redhat.com">mailto:kickstart-list-bounces@redhat.com</A>] On Behalf Of Doug Rylaarsdam Sent: Friday, April 06, 2007 11:36 AM To: <A href="mailto:kickstart-list@redhat.com">kickstart-list@redhat.com</A> Subject: RHEL3U8 pxe install: no driver for Broadcom NIC?<O:P></O:P>Hi,<O:P></O:P><O:P> </O:P>I am having a NIC driver problem with pxe kickstart of RHEL3 update 8 on some new hardware (Sun X2100 M2).<O:P></O:P><O:P> </O:P>The vendor documentation indicates that RHEL3 U7 or later has compatible drivers for this server. When I install RHEL3 U8 from CD, it works ok. When I attempt a pxe kickstart, it appears that the NIC driver is not compatible. I get the “no network device in choosenetworkinterface” message. I have been kickstarting RHEL3U3 for some time (on older hardware), so I think in general that I have a working pxe kickstart server environment.<O:P></O:P><O:P> </O:P>The NIC is a Broadcom device. The server vendor supplies the Broadcom drivers, but not in binary form for RHEL3 U8. Based on my limited understanding of how this works, I would need to build the tg3 driver from source against the boot kernel (2.4.21-47.ELBOOT) if I want to use the Broadcom NIC for a network install. Then I would need to add the new driver to the initrd image, or make it available as a driver disk. When I look inside the initrd image, the tg3.o driver is definitely not identical to the tg3.o driver from the CD install, although that doesn’t prove that the tg3 driver available during kickstart is incompatible with my hardware. <O:P></O:P><O:P> </O:P>Does it seem likely that RHEL3 U8 would contain a compatible driver for the Broadcom NIC for the 2.4.21-47.EL kernel, but that the driver for the boot kernel is not compatible? That seemed odd to me, so I thought I would ask the question before proceeding with building the driver from source, somewhat unfamiliar territory for me (especially building for boot kernels). Or might there be another cause to this problem? <O:P></O:P><O:P> </O:P>Thanks,<O:P></O:P><O:P> </O:P>Doug<O:P></O:P> </DIV> </O:SMARTTAGTYPE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Kickstart-list mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:Kickstart-list@redhat.com">Kickstart-list@redhat.com</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="https://www.redhat.com/mailman/listinfo/kickstart-list">https://www.redhat.com/mailman/listinfo/kickstart-list</A></DIV> </BLOCKQUOTE></DIV> </BODY></HTML>