couldn't find valid ramdisk image
Sorry for the previous message it was send in a wrong subject... so again. Hello, I trie to install suse8.0 using autoyast throught the network. The steps I use are the following: 1. the server has a directory /tftpboot. 2. In this directory are the linux, initrd and syslinux.cfg files, these are extracted from the suse8.0/disks/bootdisk (copied from the CD's) file using mount -oloop. 3. In syslinux.cfg I put the following lines: ====================== default autoyast # default label autoyast kernel linux append console=ttyS0,9800 console tty initrd=initrd \ autoyast=nfs://nfs_server/tftpboot/suse80/install.xml \ install=nfs://nfs_server/tftpboot/suse80 verbose 1 ======================== 4. Next I create a netboot file using mknbi-linux (which comes from netboot package): mknbi-linux -a "linuxrc=auto rw ramdisk_size=65536" -r initrd linux netboot 5. I boot from client, it loads the netboot file and after some messages I have the following error message: ... RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 4048k freed Root-NFS: No NFS server availble, giving up ... is there a problem with the initrd file ? Can some one help me ? Thanks ------------- Claude Arnold Laboratoire Emile Picard - UMR 5580 Université Paul Sabatier - UFR MIG 118, rte de Narbonne, 31062 TOULOUSE Cedex 4 Tél: 05.61.55.62.26 Fax: 05.61.55.82.00
1. Use mknbi-linux from the package mknbi 2. Better use the initrd from the suse/images/boot/ Anas * Claude Arnold <arnold@picard.ups-tlse.fr> [Feb 25. 2003 13:04]:
Sorry for the previous message it was send in a wrong subject... so again.
Hello,
I trie to install suse8.0 using autoyast throught the network. The steps I use are the following: 1. the server has a directory /tftpboot. 2. In this directory are the linux, initrd and syslinux.cfg files, these are extracted from the suse8.0/disks/bootdisk (copied from the CD's) file using mount -oloop. 3. In syslinux.cfg I put the following lines:
====================== default autoyast
# default label autoyast kernel linux append console=ttyS0,9800 console tty initrd=initrd \ autoyast=nfs://nfs_server/tftpboot/suse80/install.xml \ install=nfs://nfs_server/tftpboot/suse80 verbose 1
========================
4. Next I create a netboot file using mknbi-linux (which comes from netboot package): mknbi-linux -a "linuxrc=auto rw ramdisk_size=65536" -r initrd linux netboot
5. I boot from client, it loads the netboot file and after some messages I have the following error message:
... RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing initrd memory: 4048k freed Root-NFS: No NFS server availble, giving up ...
is there a problem with the initrd file ? Can some one help me ?
Thanks
------------- Claude Arnold
Laboratoire Emile Picard - UMR 5580 Université Paul Sabatier - UFR MIG 118, rte de Narbonne, 31062 TOULOUSE Cedex 4
Tél: 05.61.55.62.26 Fax: 05.61.55.82.00
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Hi, I use now mknbi-linux from etherboot-mknbi packages and I put the following append options: mknbi-linux --output netboot --append="linuxrc=auto rw ramdisk_size=65536\ autoyast=nfs://nfs_server/tftpboot/suse80/toshiba.xml\ install=nfs://nfs_server/tftpboot/suse80" linux initrd Now it will work. It seems that the syslinux.cfg in the server /tftpboot directory is not used by the boot process of the client (to boot the client I created a boot floppy with the boot1.bin tool from etherboot package). If I delete the autoyast and install options in the mknbi-linux command, the boot process don't find the info file. In which manner is the syslinux.cfg file used at the client boot process ? Thank for your help, ------------- Claude Arnold Laboratoire Emile Picard - UMR 5580 Université Paul Sabatier - UFR MIG 118, rte de Narbonne, 31062 TOULOUSE Cedex 4 Tél: 05.61.55.62.26 Fax: 05.61.55.82.00
participants (2)
-
Anas Nashif -
Claude Arnold