public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Madnux <madnux@skynet.be>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.x ( unable to open an initial console & unable to mount devfs, err: -5 )
Date: Thu, 23 Sep 2004 23:02:11 +0200	[thread overview]
Message-ID: <415339D3.2080206@skynet.be> (raw)
In-Reply-To: <47612A96-0CDB-11D9-BC62-000D9352858E@linuxmail.org>

Sorry but i'm not running udev !

I've run /sbin/MAKEDEV but it doesn't work anymore.

I still get "Unable to open an initial console"


I don't understand what's wrong ...




Felipe Alfaro Solana a écrit :

 > On Sep 22, 2004, at 22:57, Madnux wrote:
 >
 >> Hello,
 >>
 >>
 >> I have some problems with my kernel 2.6.7 and 2.6.8.1.
 >>
 >> I get this message « mount_devfs_fs(): unable to mount devfs, err: 
-5 » and then « unable to open an initial console » What's this ? What 
does « err: -5 » mean ?
 >>
 >> I tried with no devfs compiled in but i still have this error 
message « unable to open an initial console »
 >>
 >> Fortunatly, i had kept my old kernel ( 2.4.20 ) who have no devfs 
compiled in and it run very well for 7 months
 >>
 >>
 >> What's wrong with my system ?? Did i forget an option in the 
compilation ?
 >>
 >>
 >> I have looked everywhere about that problem until monday !
 >
 >
 >
 > I think you are running one of the latest udev snapshots from 
RawHide, and it erased some important device nodes from your "/dev" 
directory. I guess you'll need to run /sbin/makedev to recreate the 
missing devices files.



  reply	other threads:[~2004-09-23 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 20:57 2.6.x ( unable to open an initial console & unable to mount devfs, err: -5 ) Madnux
2004-09-22 21:06 ` Felipe Alfaro Solana
2004-09-23 21:02   ` Madnux [this message]
2004-09-23 22:45     ` Felipe Alfaro Solana

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=415339D3.2080206@skynet.be \
    --to=madnux@skynet.be \
    --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