mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steven A. DuChene" <linux-clusters@mindspring.com>
To: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: newer non-distro kernels don't boot / unpack?
Date: Wed, 30 Sep 2009 11:55:54 -0400 (EDT)	[thread overview]
Message-ID: <3664891.1254326154501.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net> (raw)

OK, so after removing rhgb and quiet from the menu.lst
for this kernel the last few messages it prints are:

sdb:
sdb1 sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
XFS mounting filesystem sda3
VFS: Mounted root (xfs filesystem) readonly on device 8:3.
Freeing unused kernel memory: 416k freed
Warning: unable to open an initial console.

Since it does not seem to be reaching the init stage but
does seem to be finding the disks and mounting the filesystems
it is getting much further along than I thought. I guess
I have a problem with the console/terminal parts of the
kernel compile/configuration.


-----Original Message-----
>From: Arjan van de Ven <arjan@infradead.org>
>Sent: Sep 30, 2009 11:47 AM
>To: "Steven A. DuChene" <linux-clusters@mindspring.com>
>Subject: Re: newer non-distro kernels don't boot / unpack?
>
>first remove rhgb and quiet.. that way you get at least the kernel log
>on the screen... to see where you get stuck.
>
>
>-- 
>Arjan van de Ven 	Intel Open Source Technology Centre
>For development, discussion and tips for power savings, 
>visit http://www.lesswatts.org




             reply	other threads:[~2009-09-30 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 15:55 Steven A. DuChene [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-30 15:47 Steven A. DuChene
2009-09-30 15:42 Steven A. DuChene

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=3664891.1254326154501.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net \
    --to=linux-clusters@mindspring.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®