I have seen a similar problem with installing clients through an e1000 in the server. We never tried too hard to fix it, we just figured it was some strange hardware problem.
Jason >===== Original Message From Mace Skinner <[EMAIL PROTECTED]> ===== >Folks. Here's the situation...(my parents went away...) > >Anyways. Redhat 7.2. Oscar 1.3b3. Install went perfectly after the rpm.rpm and popt.rpm force. Nice work developers! (deleting nodes is nice now too!) > >Here is the problem. Server has eepro100 outside world NIC and e1000 inside world NIC. Standard RH7.2 came with e1000.o module so the card works. Nodes have onboard eepro100 NICs. I can add the MACs to the cluster just fine. I can get as far as the "Loading kernel..." but then it hangs and crashes something on the server to stop it from acknowledging anymore DHCP requests. So I thought it might have something to do with the e1000 card. So I swap my modules.conf file around along with my two ethernet cables (internal and external networks). Reboot the server and the node just flew! Installed everything no problems. What is going on? Does a node care what type of card the server has? Can I add e1000 support to the kernel that's being sent? > >Thanks in advance! > >Mace Skinner >U of Washington - Mech. Engr. > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Bringing you mounds of caffeinated joy. >http://thinkgeek.com/sf >_______________________________________________ >Oscar-users mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/oscar-users ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
