Here are the basic steps that I used to get the e1000 working with the current setup (Rh7.3). I'm doing this from memory and in the interest of brevity I'm leaving out the fine details.
1) compile a minimal 2.4 kernel from the RedHat sources. Remove everything you don't need, but do make sure to compile the e1000 module and enable PACKET_FILTER and PACKET_SOCKET. 2) ungzip the SIS initrd.gz from the SIS distribution. Mount it using "mount -o loop initrd /mnt/initrd" 3) Copy the e1000.o driver into /mnt/initrd/lib/. 4) Copy insmod.static from /sbin/ to /mnt/initrd/sbin/ 5) Edit the /mnt/initrd/sbin/etc/init.d/rcS file, adding "insmod /lib/e1000.o" at the point where the loopback device (lo) is configured. I had problems with lockups on install, so I added "RxIntDelay=0" per the intel instructions (http://www.intel.com/support/network/adapter/1000/linux/e1000.htm). 6) unmount and gzip initrd 6) Make your boot floppy with "mkautoinstalldiskette -kernel=<your kernel" -initrd="<the new initrd.gz>". 7) Follow the normal instructions for OSCAR. Since the only changes are on the boot floppy everything else should work fine. This may or may not be easier than just going with CVS. I started out with the intention of sticking as closely as possible to the current "stable" code and came up with the solution. If there are better ways to handle the issue, I'd definitely be interested to hear them. Good luck, Vann On Wed, 2003-01-29 at 14:39, Michael Chase-Salerno wrote: > Unfortunately, there is no simple, painless procedure to integrate the > newer SIS code over older OSCAR. There were a fair number of changes > required to integrate SIS. It is currently in CVS and seems to be quite > stable, so if you are so inclined, I would suggest trying that before > attempting the integration yourself. A new release of OSCAR is coming > sometime in the next few weeks. > > Mike > > On Wed, 2003-01-29 at 14:19, [EMAIL PROTECTED] wrote: > > I have seen a few threads on Oscar 2.1 and the Intel gigabit driver and > > how to make it work with cloning the nodes with SIS 3.0, but I still > > haven't found a step by step process that outlines what to do. Seems > > there are a few others that are running into the same problem. When will > > we have a Oscar 2.x that has the SIS 3.0.0 release within the disti, > > without having to insert the SIS disti and making various changes to Oscar > > before creating the autoinstall diskette? > > > > I'm all for at present layering in the SIS 3.0 after the initial install > > of Oscar 2.1, like we have to do with Ganglia, if anyone has a painless > > procedure on how to go about this? I would appreciate the assistance. > > > > Thanks, > > > > Paul Bounds > > > > > > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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
