Hi Sylvia, On Tuesday 28 November 2006 22:50, Sylvia Gelman wrote: > Hi Erich, > > > > I have seen such issues only with nodes which had multiple ethernet > > interfaces. The cable needed to be plugged into the other connector. > the nodes have also a murinet card and an onboard intel card (eth0) > we had tried a lot of things but nothing really helped. So we don´t know > what to try now, build an own kernel?
So besides the myrinet card you have one or two ethernet interfaces? If you have two, you should try plugging the cable into the other port. > > The e100 driver is usually included in the systemimager kernel, the dhcp > > request from the client node shows that you actually do have an eth0 > > interface. > the e100 driver should work also, so why isn´t it loaded? Is it possible > to define more modules like insmod=e100 when the image is built? >From the config file for the install kernel: CONFIG_EEPRO100=y CONFIG_E100=y So these drivers are compiled into the kernel, not available as modules. > What are the possibilities in the command line of the client? Could we > load any more modules? Try "busybox -h". Before you got the IP from DHCP you have no modules available. The modules come with the boel_binaries.tar.gz. If you have problems you can also use the UYOK (use your own kernel) option in the "Setup networking" menu. You can only use that if the master and slaves hardware is the same. Regards, Erich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
