Bernard Li wrote on 06/05/2006 11:00:01 PM:
> It's possible that your hardware is too new and the e1000 module
> that came bundled with SystemImager 3.6.3's kernel does not support
> it.
It's possible, certainly, but I don't know that it's particularly *likely*. I'm trying to run this on an IBM xSeries 345 - surely nothing exotic; I think they're from 2003ish - and with the 3.6.3 release being March 2006, I suspect that a compatible driver ought to be in there already. (Is there a way I could check/find out?)
> You have 2 options:
> - Update to the latest SystemImager development code (I can build
> RPMs based on the latest SVN trunk, this will become 3.7.3 any day now)
I'd be glad to try them out if you do think it will make a difference...
as for the official release, out of curiosity, approximately what sort of an order of magnitude is "any day now"? This week, next week, this month, something not well-defined yet?
> - Use 3.6.3's "UseYourOwnKernel" functionality (search the mailing-
> list(s) for specific instructions on how to use it).
... but this is something I'm a little more hesitant to try immediately due to, well, a variety of concerns- among which is the fact that I think it would be better for what I'm working on to use something that differs from standard SIS components as little as possible.
_______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
