From: Timo Kokkonen <kaapeli@itanic.dy.fi>
To: Mark Knecht <markknecht@gmail.com>
Cc: Paul Hartman <paul.hartman@gmail.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: New Gentoo install on Intel Z68/i7-2600K system hangs after VFS:Mounted root...
Date: Sat, 18 Jun 2011 13:12:42 +0300 [thread overview]
Message-ID: <20110618101242.GA26761@itanic.dhcp.inet.fi> (raw)
In-Reply-To: <BANLkTinEhyN-i0N9QRpdjMUTpMCRiDMDdw@mail.gmail.com>
On 06.17 2011 14:40:21, Mark Knecht wrote:
> On Fri, Jun 17, 2011 at 12:01 PM, Mark Knecht <markknecht@gmail.com> wrote:
> > On Fri, Jun 17, 2011 at 11:54 AM, Paul Hartman <paul.hartman@gmail.com> wrote:
> >> On Fri, Jun 17, 2011 at 1:29 PM, Mark Knecht <markknecht@gmail.com> wrote:
> >>> We ran memtest86 for an hour. Completed a couple of passes with no
> >>> errors. Will run more later but no obvious memory problems seen.
> >>>
> >>> I installed 2.6.39-gentoo-r1. No change from 2.6.38-gentoo-r6.
> >>> Stops at the same place.
> >>>
> >>> I tried 2.6.39-gentoo-r1 with no kernel options, and with all
> >>> combinations of nousb and acpi=off. All 4 attempts quit at the same
> >>> place.
> >>
> >> Check out this forum post, this person's bootup seems to stop in the
> >> same place as yours. He was able to fix it by booting off a liveCD and
> >> manually creating device nodes. Maybe it's nothing, but probably worth
> >> looking at just in case it might help.
> >>
> >> https://www.linuxquestions.org/questions/gentoo-87/booting-stops-after-kernel-starts-883031/
> >>
> >
> > Argh!! I remember a post like that on the Gentoo list. I'll check if
> > out and give it a try.
> >
> > Thnaks,
> > Mark
> >
> Thanks again Paul. That was exactly the solution I needed.
>
> I remember this thread, or one like it, on the Gentoo-user list, but I
> didn't follow the thread. I just remember that the Gentoo tarball was
> not created correctly and these devices were left out. Adding them in
> solved all the problem.
There is also another solution for this. You can enable the devtmpfs
(and also the optioin to auto mount it during boot) in order to make
kernel create all necessary device nodes under the /dev
automatically. Then you don't need your distro to generate initial
device nodes prior starting udev. I don't know if the Gentoo devs have
somehow relied on devtmpfs because the recent stage tar balls don't
seem to contain the initial device nodes anymore.
-Timo
prev parent reply other threads:[~2011-06-18 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 3:11 Mark Knecht
2011-06-17 14:46 ` Paul Hartman
2011-06-17 14:57 ` Mark Knecht
2011-06-17 18:29 ` Mark Knecht
2011-06-17 18:54 ` Paul Hartman
2011-06-17 19:01 ` Mark Knecht
2011-06-17 21:40 ` Mark Knecht
2011-06-18 10:12 ` Timo Kokkonen [this message]
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=20110618101242.GA26761@itanic.dhcp.inet.fi \
--to=kaapeli@itanic.dy.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=paul.hartman@gmail.com \
/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®