I'd guess that the default kernel parameter string is hosed. (It looks like it doesn't know where the initrd is). Can it boot if you type 'kernel initrd=initrd.img root=/dev/ram" at the boot prompt?
Nope. Still get the same error.
I've also cracked the ISO, and the diskette image on it (siboot.img), and have verified the syslinux.cfg, kernel, and initrd.img file names.
I've verified the kernel and initrd on the iso match those in /usr/share/systemimager/boot/i386/standard.
And, I've verified the syslinux.cfg file in the iso matches the default in /etc/systemimager/pxelinux.cfg/. I've even tried an old version of syslinux.cfg (from SI v2.0.1).
I tried an older version of syslinux (on my server).
I tried an older version of dosfsutils (on my server).
No dice.
Any other ideas?
-Brian
If so, then look for problems with the kernel boot string setup.
J
On Wednesday 28 April 2004 10:26 am, Brian Elliott Finley wrote:I'm wanting to do a 3.3 release, but when i do a:
sudo make install_server_all sudo mkautoinstallcd --arch i386 --flavor standard --out-file /usr/src/autoinstallcd.iso
When try to boot my vmware 4 box from it, it:
1) see's syslinux and the "welcome to systemimager" screen, then fails. Please see attached image...
Any ideas?
-Brian
--
---------------------------------------------------------
Brian Elliott Finley Argonne, MCS Division Phone: 630.631.6621 http://thefinleys.com
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
---------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Sisuite-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
