Hi Bernard
On Jan 15, 2006, at 4:39 PM, Bernard Li wrote:
Hi Charles:
I believe si_prepareclient uses the OS' kernel and generate a
compatible initrd.img based on your system.
Have you tried using the stock kernel/initrd.img which came with
SystemImager's boot-standard package to tftpboot? That might actually
work better.
yes, thats what kernel panics :( I did build from source though - i
just tried your prebuilt one and it panics too.
The modules.dep message can be ignored, it never interferred with
successful imaging of a system - we'll see about fixing that in the
future.
Ok, i assumed that was the root cause. The resulting problem as it
didn't see my sata card (adaptec I2O). This does work in production
though...
If that doesn't work, I recommend you try a newer version of
SystemImager, eg. 3.6.2 or the code in branches/3.6.x.
Mmh, maybe I lied - i should have said 3.6.3 :0 I have been using
systemimager-3.6.3-1.src.rpm off that site you linked me to. That
change anything you say above?
charles
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
