Hi, First of all thanks to the help being rendered to me.
Michael, The output after i run lilo with -t -v -v as options
root@roct /root]# chroot /mnt/hdc1 lilo -t -v -v LILO version 21, Copyright 1992-1998 Werner Almesberger
Reading boot sector from /dev/hdc Invalidating cache entry for /dev/hdb (0x0340) Created temporary device /tmp/dev.0 (0x0340) Removed temporary device /tmp/dev.0 (0x0340) Warning: /dev/hdc is not on the first disk Merging with /boot/boot.b Created temporary device /tmp/dev.0 (0x0340) Removed temporary device /tmp/dev.0 (0x0340) Secondary loader: 8 sectors. Created temporary device /tmp/dev.0 (0x0340) Removed temporary device /tmp/dev.0 (0x0340) Boot image: /boot/zImage2 Created temporary device /tmp/dev.0 (0x0340) Removed temporary device /tmp/dev.0 (0x0340) Setup length is 4 sectors. Mapped 817 sectors. Added linux * Map file size: 8192 bytes. The boot sector and the map file have *NOT* been altered.
As you have suggested ,I have created hdc and hdc1 Same problem appeared when i booted with the flash It showed me "LI"
Thanks Ravi
Michael Svetlik wrote:
On Tuesday 20 May 2003 13:24, you wrote:
Hi Michael, chroot /mnt/ /sbin/lilo -t -v -V shows me LILO VERSION 21
Attention: you have a capital V in there, means, lilo should output its version, and then exit. Ty again with 2 '-v's.
After lilo is run, the following error occured:
open: /dev/hdc1 cant open Not a file or directory
You dont have the device node ? Make one: $ mknod /mnt/dev/hdc b 22 0 $ mknod /mnt/dev/hdc1 b 22 1
Just to be online:
On which IDE channel does - or should - your machine find its boot device ? It must be IDE1/Slave, according to your lilo.conf below. Do you change any configuration - cabling and / or BIOS setup, before booting from flash ?
The lilo.conf at /mnt/etc/ looks like this
boot=/dev/hdc1 install =/boot/boot.b image=/boot/bzImage label=linux1 read-only
Try 'lba32', additionally.
Regards, Ravi
Michael Svetlik wrote:
Ravi,
you should check the Troubleshooting section in LILO's User_Guide.ps, usually in /usr/share/doc/lilo-<version>/doc, especially section 5.2.1 LILO start message. Many people recommend to run LILO using $ chroot /mnt /sbin/lilo <any switches> instead of 'lilo -r'. What does a $ chroot /mnt /sbin/lilo -t -v -v throw onto stdout ?
Michael
On Monday 19 May 2003 12:14, Ravi wrote:
Hi All, I gone through the thread "about compact flash" I too face a similar porblem.It is glad to see a fruitful result for this discussion. Please help me out too. My need demands me ext2 filesystem,unfortunately ,I found that syslinux doesnot support ext2. http://syslinux.zytor.com/faq.php#bootable
The procedure i followed is as listed
1.Kept the 16 MB flash onto the IDE slot 2.bash# mke2fs -m0 /dev/hdc1 bash# mount /dev/hdc1 /mnt 3.Took a minimised compiled Kernel 4.bash#mkdir /mnt/boot 5.copied a bzImage /mnt/boot/ 6.bash# cp /boot/boot.b /mnt/boot/ 7.cp -dpR entire filesystem to /mnt (except for boot directory) 8.bash# cd /mnt/etc 9.edited lilo accordingly 10.bash# lilo -r /mnt
After running lilo i booted my box with flash. The booting struck showing LI Any help is much appreciated. Thanks in advance Regards, Ravi
--
The views presented in this mail are completely mine. The company is not responsible for whatsoever. ------------------------------------------------------------------------ Ravi Kumar CH Rendezvous On Chip (i) Pvt Ltd Hyderabad, India Ph: +91-40-2335 1214 / 1175 / 1184
ROC home page <http://www.roc.co.in>
-- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
