On Wed, Aug 29, 2012 at 10:06 PM, Sri Ram Vemulpali
sri.ram.gm...@gmail.com wrote:
Thanks for the replies again.
This time the problem is in tty specification.
Kernel supports console=tty0 (virtual terminal), where as my inittab has
entry ::sysinit:/sbin/getty -L ttyS0 vt100. I have to change
Hi Guys,
Thanks for all the replies.
I resolved this problem yesterday night.
There are some couple of problems.
It seems the initrd cpio archive is not well formatted. I saw some
errors when I am unarchiving it to different dir for test purpose.
It saw some device files under /dev are not
On Wed, Aug 29, 2012 at 10:50 PM, Sri Ram Vemulpali
sri.ram.gm...@gmail.com wrote:
but when I used the following command
find . | cpio --quiet -H newc -o | gzip -9 -n /boot/imagefile.img
to make cpio archive of initrd, I do not see any errors in creating
device files,
when I unarchive it.
On Wed, Aug 29, 2012 at 11:50:00AM -0400, Sri Ram Vemulpali wrote:
Now the current problem is, I am stuck on, unable to get console. I
got stuck after sshd (I want dropbear daemon on my machine), it seems
sshd got started, but no prompt is displayed.
I think I should get console control. Any
Thanks for the replies again.
This time the problem is in tty specification.
Kernel supports console=tty0 (virtual terminal), where as my inittab has
entry ::sysinit:/sbin/getty -L ttyS0 vt100. I have to change the ttyS0 to tty0.
Once I changed this, I got login prompt.
But I do not understand
Sri, I'm not sure about this part:
root=/dev/VolGroup00/LogVol00
It Should be something like root=/dev/sda1 . I believe that VolGroup00
thing has to do with LVM something I'm not very familiar with but I don't
think the boot process will be able to understand LVM at that early
stage.
I might be
