(hope i put the right name here)
i did try the 3.0.0-1 package and that clearly stated,
when doing the insmod command, that it could not find a e1000.
therefore, dann ,you seem to be right , i would need a newer driver.
for now , in order to push my project a little further , i unhappyly deceided to switch to suse's autoyast feature (got it working already).
as soon as i get a little more ait to breath , i will again try to build sisimage from the sources, since i do have the sourcecode for the lan driver of the board.
thanks for your guidance anyway
Rony Sobiesiak
At 21:41 18.11.2003 -0700, you wrote:
On Wed, Nov 19, 2003 at 11:51:37AM +0800, Hong, Jie wrote: > I think you can try systemimager3.0.0-1 rpm package. > The e1000.o module is included in the initrd.img.
worth a shot - but that's probably older than the one he's trying.
> And it will be loaded without sys's hardware check. > Or you can manually add it to initrd.img. > BTW: I can't build it from source on RH EL2.9, it breaks > at jfsutil, while I succeed on RH7.3.
our jfsutils is upgraded in cvs, since older versions fail to build in some newer distros.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
