All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub 1 troubleshooting, linux boot delayed problem
Date: Fri, 11 Jun 2004 16:15:56 +0200	[thread overview]
Message-ID: <200406111615.56874.okuji@enbug.org> (raw)
In-Reply-To: <600B91D5E4B8D211A58C00902724252C01BC06BB@piramida.hermes.si>

Your question is irrevalent with this list. Read the manual and/or the 
web site for information on where to use.

... Why do people send questions to this list again and again? Is it so 
unclear?

Okuji

On Friday 11 June 2004 10:48, David Balazic wrote:
> Hi!
>
> I found no other place, so I'll ask here.
>
> I have a problem booting linux with grub ( v 0.9.something ).
>
> I use the commands ( in the grub shell that boots from my HD ):
> root (hd0,0)
> kernel /vmlinuz-2.6.xxx ro root=dev/hda2
> initrd /initrd-2.xxx
> boot
>
> After entering the "boot" command, the screen is cleared and then
> nothing happens for 93 seconds.
> After that linux boot normally ( beginning with the message
> "Uncompressing linux..." and so on ).
> If I trim the kernel command line to only "kernel /vmlinuz-2.6.xxx
> ro" , then the delay is 10 seconds.
>
> If I change the operating mode of the IDE adapter in BIOS to RAID,
> then the delay is infinite ( I waited
> 8 hours ). Note that GRUB still loads andit can browse and "cat"
> files on the disk, so it is not a disk
> access problem.
>
> Can someone tell me how to find out what GRUB is doing after the
> "boot" command ?
> I tried to run "debug on" first, but it makes no change at all.
>
> Maybe this is a linux kernel problem.
>
> Any help appreciated !
>
> Regards,
> David Balažic
>
> P.S.: It is a Fedora Core 2 system, the exact version numbers are
> grub-0.94-5 , kernel-2.6.5-1.358
>
> P.P.S.: I know this is Red Hat related, but my question is general :
> What is happening between
> the GRUB "boot" command and linux printing "Uncompressing linux..." ?
> ---------------------------------------------------------------------
>------- -----------
> http://noepatents.org/           Innovation, not litigation !
> ---
> David Balazic                      mailto:david.balazic@hermes.si
> HERMES Softlab                 http://www.hermes-softlab.com
> Zagrebska cesta 104            Phone: +386 2 450 8851
> SI-2000 Maribor
> Slovenija
> ---------------------------------------------------------------------
>------- -----------
> "Be excellent to each other." -
> Bill S. Preston, Esq. & "Ted" Theodore Logan
> ---------------------------------------------------------------------
>------- -----------
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel



  parent reply	other threads:[~2004-06-11 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11  8:48 Grub 1 troubleshooting, linux boot delayed problem David Balazic
2004-06-11 13:20 ` P
2004-06-11 14:15 ` Yoshinori K. Okuji [this message]
2004-06-12 16:11   ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2004-06-11 13:29 David Balazic
2004-06-11 14:30 David Balazic
2004-06-11 14:56 ` Yoshinori K. Okuji
2004-06-12 10:55 David Balazic
2004-06-14  6:33 David Balazic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406111615.56874.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.