Hi Kenneth: You or your client will need to build in the relevant kernel driver or driver module. Oscar builds images using systemimager, so you are going to need to incorporate this into the the Oscar build process. I would suggest looking to build the relevant kernel RPM, and then using the kernel_picker script (page 29 of 57 on the installation pdf). Make sure the relevant driver is installed and functional in that kernel RPM. You can simply install the same version of Linux as on the head node, and manually install the new kernel to test it. If it works, insert the new kernel in as indicated. With regards to the broadcomm adaptor, could you have them run some version of linux on the failing client, and do an lspci -v and send it back to the group? It would help to know which broadcomm NIC is being dealt with... There are bcm4400 drivers in the latest kernels, and there are some bcm5700 drivers out there as well. You would need to add those in specifically. Joe On Wed, 2003-10-15 at 15:11, Kenneth Geisshirt wrote: > Hi > > I have a client who has bought a brand new cluster - 32x Dell 1750. The > master node is running Red Hat 9, but when a node is going to be > installed using Oscar 2.3.1 my client gets the following error message: > > ServerWorks CSB5: detected chipset, but driver not compiled in! > tg3: Problem fetching invariants of chip, aborting. > > Apparently, the problem has something to do with the Broadcom ethernet > adaptor. > > Please give me some suggestions to work with. > > Thanks > Kneth -- Joseph Landman, Ph.D Scalable Informatics LLC email: landman@scalableinformatics.com web: http://scalableinformatics.com phone: +1 734 612 4615