Ole: There are some adjustments you have to make to the kernel boot line to increase the size of the ram disk during boot. The kernel boot line I am using in the /tftpdir/pxelinux.cfg/C0A8BLAH (based on your hardware MAC address) is:
APPEND vga=extended initrd=initrd.img root=/dev/ram ramdisk_size=43000 tmpfs_size=1990M console=ttyS0,9600 console=tty1 console=ttyS0,9600 -----Original Message----- >From: Ole Holm Nielsen <[EMAIL PROTECTED]> >Sent: Apr 25, 2006 4:51 AM >To: [email protected] >Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: Re: Is there a SystemImager kernel for x86_64 containing Broadcom >drivers ? > >Following Steven's advice, I use SystemImager 3.6.3 on the IBM x326m. >I copied the kernel and initrd.img from the image's >/etc/systemimager/boot/ to /tftpboot on the server. When the x326m >boots on these files by PXE/TFTP, an error crops up when the root >filesystem is mounted (copied by hand from the install screen): > >RAMDISK: Compressed image found at block 0 >RAMDISK: incomplete write (-28 != 32768) 16777218 >VFS: Mounted root (etx2 filesystem) readonly. >Freeing unused kernel memory: 192k freed >attempt to access beyond end of device >ram0: rw=0, want=32776, limit=32768 >EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block - i >273 , block=16387 >Warning: unable to open an initial console >attempt to access beyond end of device >ram0: rw=0, want=40358, limit=32768 >(etc. etc. and then it freezes) > >It would appear that there is something wrong with the initrd.img >created by si_prepareclient (?). > >My Linux version is Redhat RHEL4 (actually the Centos 4.1 clone). >I should also add that my PXE/TFTP server has SystemImager 3.5.2, >but that should be unimportant for serving the kernel+initrd.img by TFTP. > >We really need to get this IBM node going with SystemImager, >so I wonder what the next thing to try out may be ? > >Thanks a lot, >Ole > >Steven A. DuChene wrote: >> I have used systemimager 3.6.3 to image some of our IBM e326m nodes here >> and I used the funtionality of the UYOK stuff to boot with the kernel >> already being >> used on the systems to boot to the systemimager install. Once you pull the >> image >> in /var/lib/systemimager/images/YOUR_IMAGE_NAME/etc/systemimager/boot/ >> there will be a kernel and a initrd.img file that should do the trick. On >> your imageserver >> use the si_mkbootserver command to properly set these up to be booted with. >> A command line sequence like: >> >> si_mkbootserver --interface=eth2 --kernel=PATH_TO_KERNEL_FILE/kernel >> --initrd=/PATH_TO_INITRD_FILE/initrd.img --tftpdir=/tftpboot >> --pxelinux=/usr/share/syslinux/pxelinux.0 --localdhcp=y >> >> is the syntax that worked for me. > >-- >Ole Holm Nielsen >Department of Physics, Technical University of Denmark ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
