Kernel booting problem.

Kernel booting problem.

[Sri Ram Vemulpali]

Hi All,

I compiled my own kernel image with uclibc cross tool chain for x86
i686 arch. I am using grub as boot loader.

these are the following parameters I am giving.

kernel /bzImage ro root=/dev/VolGroup00/LogVol00 rhgb quiet init=/sbin/init
initrd /initrd.img  -----> this is cpio image of filesystem structure
with needed modules and lib

When I select at grub options to boot the kernel after reading bzImage
grub proceeds to initrd and stuck at initrd.
There is no output. I searched online and I found other kind of
problems. But this is something different.

Can anyone give some suggestions. Thanks in advance.

-- 
Regards,
Sri.

Kernel booting problem.

[Gabriel Prado de Moraes]

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 wrong though.


On Tue, Aug 28, 2012 at 10:42 PM, Sri Ram Vemulpali <sri.ram.gmu06@gmail.com
> wrote:

> Hi All,
>
> I compiled my own kernel image with uclibc cross tool chain for x86
> i686 arch. I am using grub as boot loader.
>
> these are the following parameters I am giving.
>
> kernel /bzImage ro root=/dev/VolGroup00/LogVol00 rhgb quiet init=/sbin/init
> initrd /initrd.img  -----> this is cpio image of filesystem structure
> with needed modules and lib
>
> When I select at grub options to boot the kernel after reading bzImage
> grub proceeds to initrd and stuck at initrd.
> There is no output. I searched online and I found other kind of
> problems. But this is something different.
>
> Can anyone give some suggestions. Thanks in advance.
>
> --
> Regards,
> Sri.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120828/aaa91562/attachment.html 

Kernel booting problem.

[Mulyadi Santosa]

Hi.....

On Wed, Aug 29, 2012 at 8:42 AM, Sri Ram Vemulpali
<sri.ram.gmu06@gmail.com> wrote:
> Hi All,
>
> I compiled my own kernel image with uclibc cross tool chain for x86
> i686 arch. I am using grub as boot loader.
>
> these are the following parameters I am giving.
>
> kernel /bzImage ro root=/dev/VolGroup00/LogVol00 rhgb quiet init=/sbin/init
> initrd /initrd.img  -----> this is cpio image of filesystem structure
> with needed modules and lib
>
> When I select at grub options to boot the kernel after reading bzImage
> grub proceeds to initrd and stuck at initrd.

zero output? I guess you must see output, even a bit....so, can you
post as much as you can see from the display?

if not, we're really shooting in the dark here...


-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

Kernel booting problem.

[Sri Ram Vemulpali]

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 getting created. I am not
sure why there are errors, 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.

The other erorr is, I have to change /etc/fstab config to tell which
device should be considered to mount as root. There was a wrong entry
"/dev/root", this device
do not exist in initrd image and grub do not create nor attach initrd
contents to /dev/root. Grub creates /dev/ram0 or /dev/ram or
/dev/initrd and attaches initrd contents
to this device. Kernel then reads contents from one of these devices
as root fs. After making these modifications, I saw grub able to boot
the kernel with initrd,

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 ideas.

Thanks in advance.

Regards,
Sri.

On Tue, Aug 28, 2012 at 11:20 PM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> Hi.....
>
> On Wed, Aug 29, 2012 at 8:42 AM, Sri Ram Vemulpali
> <sri.ram.gmu06@gmail.com> wrote:
>> Hi All,
>>
>> I compiled my own kernel image with uclibc cross tool chain for x86
>> i686 arch. I am using grub as boot loader.
>>
>> these are the following parameters I am giving.
>>
>> kernel /bzImage ro root=/dev/VolGroup00/LogVol00 rhgb quiet init=/sbin/init
>> initrd /initrd.img  -----> this is cpio image of filesystem structure
>> with needed modules and lib
>>
>> When I select at grub options to boot the kernel after reading bzImage
>> grub proceeds to initrd and stuck at initrd.
>
> zero output? I guess you must see output, even a bit....so, can you
> post as much as you can see from the display?
>
> if not, we're really shooting in the dark here...
>
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com



-- 
Regards,
Sri.

Kernel booting problem.

[Mulyadi Santosa]

On Wed, Aug 29, 2012 at 10:50 PM, Sri Ram Vemulpali
<sri.ram.gmu06@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.

really weird, but glad you solved it...and it's nice that you share it to us...

> There was a wrong entry
> "/dev/root", this device
> do not exist in initrd image and grub do not create nor attach initrd
> contents to /dev/root. Grub creates /dev/ram0 or /dev/ram or
> /dev/initrd and attaches initrd contents
> to this device. Kernel then reads contents from one of these devices
> as root fs.

IIRC, /dev/root is like generic name for the rootfs device. Sometimes
ago I checked kernel source and I conclude that it is a name actually
given when initramfs is mounted....but then kernel do pivot to real
root device in the disk

> 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 ideas.

i think in "man ssh", there is an option to force tty allocation.

Anyway, it's going OOT here...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

Kernel booting problem.

[Jonathan Neuschäfer]

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 ideas.

Which prompt is missing?
Can I assume ssh works?
If the hardware / video terminals aren't starting, I suggest having a
look at your init scripts (that's where getty and friends are started).

HTH,
	Jonathan Neusch?fer

Kernel booting problem.

[Sri Ram Vemulpali]

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 how we tell kernel to use ttyS0 over tty0.
Because in kernel config I selected was ttyS0 but it is using tty0.
Weird?

Thanks,
Sri.

On Wed, Aug 29, 2012 at 4:24 PM, Jonathan Neusch?fer
<j.neuschaefer@gmx.net> wrote:
> 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 ideas.
>
> Which prompt is missing?
> Can I assume ssh works?
> If the hardware / video terminals aren't starting, I suggest having a
> look at your init scripts (that's where getty and friends are started).
>
> HTH,
>         Jonathan Neusch?fer



-- 
Regards,
Sri.

Kernel booting problem.

[Jim Cromie]

On Wed, Aug 29, 2012 at 10:06 PM, Sri Ram Vemulpali
<sri.ram.gmu06@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 the ttyS0 to tty0.
>
> Once I changed this, I got login prompt.
>
> But I do not understand how we tell kernel to use ttyS0 over tty0.
> Because in kernel config I selected was ttyS0 but it is using tty0.

try console on boot-line

root at voyage:~# more /proc/cmdline
root=LABEL=ROOT_FS  console=ttyS0,115200n8  rootdelay=120 reboot=bios loglevel=8
 dynamic_debug.verbose=1

> Weird?
>
> Thanks,
> Sri.
>