Looks like two options:
1) re-enable the 100Mbit adapter and have multiple networks. One for build/maintenance, and one for high performance communication. You could build with your 100Mbit adapter, and then have the option to push out configuration for the GigE adapter when your cluster is built. (references for GigE addresses would have to come first in the hosts file)
2) Get help from the SIS folks to assist you in getting the GigE module loaded at build time so you can leave the 100Mbit adapter out of the picture.
Jeremy
At 02:42 PM 1/9/2003 -0800, Jenny Aquilino wrote:
Hi,
I just ran into the same problem however I'm still stuck. I think my problem might be that my second ethernet adapter is gigabit and maybe the image that Oscar pushed out did not include gigabit drivers? On my master node the module that is getting loaded is e1000. Does anyone have any suggestions for how I might be able to include this driver in the initial miniroot image? When dhclient gets called it broadcasts over lo because the 100Mb ethernet line is disabled in the bios and I guess it doesn't detect the gigabit line. Thanks.
-Jenny =)
I've run into this issue before myself. My best solution to suggest would be what I did... disable the second ethernet adapter in the bios prior to building. However, since you're built already it probably won't matter. You'll just have to recollect/reassign the MAC if you ever wish to rebuild the node.
Jeremy
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
