mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "Joseph D. Wagner" <technojoecoolusa@charter.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.10 Can't Open Initial Console on FC3
Date: Fri, 31 Dec 2004 14:07:13 -0800	[thread overview]
Message-ID: <20041231140713.562f5f7a@lembas.zaitcev.lan> (raw)
In-Reply-To: <mailman.1104479591.3634.linux-kernel2news@redhat.com>

On Fri, 31 Dec 2004 00:31:38 -0600, "Joseph D. Wagner" <technojoecoolusa@charter.net> wrote:

> The newly compiled kernel gets through everything OK including mounting
> the root file system as read-only EXT3.  However, it freezes on the very
> last line, which says:
> 
>      Warning: unable to open an initial console

> I feel like an idiot for posting this.  I'm probably missing something obvious.

Man, I know the feeling. It's rather annoying that the message does not
tell what is happening, not even the errno. I was thinking about having
the attached patch submitted, but I don't know if it's worth it.

In case of FC3, the most common problem is that udev somehow fails to start.
I do not know what the precise mechanics of it, because /dev/console
exists in initrd images, but with all the crazy root pivoting it's
no wonder it's ineffective. Anyhow, if udev quits, open in the init/main.c
will fail with ENOENT.

The only solution I know is to do everything over again, and make sure
you copied right configuration from /boot/config-2.6.9-1.678_FC3, and that
your mkinitrd run created a sensible initrd image. Verify that udev runs
and if not, debug that.

-- Pete

diff -urp -X dontdiff linux-2.6.10-rc2-bk8/init/main.c linux-2.6.10-rc2-bk8-usb/init/main.c
--- linux-2.6.10-rc2-bk8/init/main.c	2004-11-16 17:03:37.000000000 -0800
+++ linux-2.6.10-rc2-bk8-usb/init/main.c	2004-11-27 14:04:06.000000000 -0800
@@ -691,6 +691,8 @@ static inline void fixup_cpu_present_map
 
 static int init(void * unused)
 {
+	int rc;
+
 	lock_kernel();
 	/*
 	 * Tell the world that we're going to be the grim
@@ -738,8 +740,8 @@ static int init(void * unused)
 	system_state = SYSTEM_RUNNING;
 	numa_default_policy();
 
-	if (sys_open((const char __user *) "/dev/console", O_RDWR, 0) < 0)
-		printk("Warning: unable to open an initial console.\n");
+	if ((rc = sys_open((const char __user *) "/dev/console", O_RDWR, 0)) < 0)
+		printk("Warning: unable to open an initial console (%d).\n", rc);
 
 	(void) sys_dup(0);
 	(void) sys_dup(0);

       reply	other threads:[~2004-12-31 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1104479591.3634.linux-kernel2news@redhat.com>
2004-12-31 22:07 ` Pete Zaitcev [this message]
2005-01-01 16:05 Joseph D. Wagner
2005-01-03  3:09 ` Colin Charles
  -- strict thread matches above, loose matches on Subject: below --
2004-12-31  6:31 Joseph D. Wagner
2004-12-31  5:00 Joseph D. Wagner
2005-01-01  7:13 ` Mike Houston

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=20041231140713.562f5f7a@lembas.zaitcev.lan \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=technojoecoolusa@charter.net \
    /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®