All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: linux-console@vger.kernel.org
Subject: Warning: unable to open an initial console.
Date: Mon, 25 Oct 2010 16:30:16 -0500	[thread overview]
Message-ID: <4CC5F6E8.10704@freescale.com> (raw)

Hi,

I'm trying to write a console/tty driver, and I need help.  When the kernel
boots, I can see that console output is working through my driver.  However,
after the initial kernel boot, my console stops working.  Here are the relevant
parts of the boot log:

Using P4080DS HV machine description
Memory CAM mapping: 256/256 Mb, residual: 0Mb
Linux version 2.6.34-6506-00741-gbd4ea2b-dirty (b04825@efes) (gcc version 4.4.1
(Sourcery G++ Lite 4.4-194) ) #33 SMP Mon Oct 25 16:20:20 CDT 2010
Found initrd at 0xc1300000:0xc3b00000
...
Kernel command line: console=ttyEHV
...
console [ttyEHV0] enabled
...
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Warning: unable to open an initial console. -19
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) readonly on device 1:0.
Freeing unused kernel memory: 236k init

And this is where it stops.

As you can see, I have a console, and then I lose it.  What could cause this to
happen?

On the surface, it appears that init can't open /dev/console, but I can't figure
out what the root cause is.

-- 
Timur Tabi
Linux kernel developer at Freescale


             reply	other threads:[~2010-10-25 21:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 21:30 Timur Tabi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-26 11:05 Warning: unable to open an initial console Gerard van den Bosch
2017-05-26 11:27 ` Andrea Adami
2017-05-26 13:52   ` Gerard van den Bosch
2017-05-26 14:20     ` Ayoub Zaki
2017-05-26 14:27       ` Gerard van den Bosch
2017-05-26 14:35         ` Ayoub Zaki
2017-05-26 15:07           ` Gerard van den Bosch
2009-09-30 17:24 Steven A. DuChene
2009-09-30 17:05 Steven A. DuChene
2009-09-30 17:44 ` Arjan van de Ven
2007-04-02 19:04 Tom Strader
2007-04-02 22:49 ` Chris Wedgwood
2007-04-02 23:20   ` Tom Strader
2007-04-03  1:34     ` young dave
2007-04-03 18:35       ` Tom Strader
2007-04-04  1:53         ` young dave
2007-04-05 15:57           ` Tom Strader
2000-11-02 15:11 John Jones
2000-11-02 17:33 ` Matthew Locke

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=4CC5F6E8.10704@freescale.com \
    --to=timur@freescale.com \
    --cc=linux-console@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 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.