|
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. 06:04.0 Ethernet controller: Broadcom
Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3)
Subsystem: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 15
Memory at fdff0000 (64-bit, non-prefetchable) [size=64K]
Memory at fdfe0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable- 06:04.1 Ethernet controller: Broadcom
Corporation NetXtreme BCM5715 Gigabit Ethernet (rev a3)
Subsystem: Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 10
Memory at fdfc0000 (64-bit, non-prefetchable) [size=64K]
Memory at fdfb0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable- Thanks, Doug From: Shabazian, Chip
[mailto:Chip.Shabazian@xxxxxxxxxxxxxxxxx] 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=http://path_to/disk.img Chip From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On
Behalf Of Doug Rylaarsdam 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. Doug From: Shabazian, Chip
[mailto:Chip.Shabazian@xxxxxxxxxxxxxxxxx] 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. Chip From:
kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Doug Rylaarsdam Hi, I am having a NIC driver problem with pxe kickstart of RHEL3 update 8
on some new hardware (Sun X2100 M2). 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. 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. 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? Thanks, Doug |
