public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Colleen Beamer <colleen.beamer@gmail.com>
Subject: Re: [gentoo-user] Frozen after Upgrade
Date: Mon, 3 May 2010 16:56:04 +0200	[thread overview]
Message-ID: <201005031656.04901.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <g2n2db4be991005030730mce5efd1akc7fd18a1415361e8@mail.gmail.com>

On Monday 03 May 2010 16:30:53 Colleen Beamer wrote:
> > You said you did a system upgrade. Did this involve a kernel upgrade too?
> > 
> > If so, you are likely running into missing nvidia drivers in your new
> > /lib/modules/. So:
> > 
> > - reboot to single user maintenance mode.
> > - disable /etc/init.d/xdm
> > - remerge nvidia-drivers, making sure that /usr/src/linux point s to the
> > new kernel that is to be configured
> > - reboot
> > - enable /etc/init.d/xdm
> > - start xdm
> 
> New kernel was downloaded, but I did not upgrade the kernel.  If that
> was the situation, I wouldn't be able to load to my login screen - I
> would be booted back to the command line.  I get to the login screen,
> but then, everything is frozen - keyboard and mouse.

Oh yes, of course. Obvious in retrospect

> I don't understand what you mean by booting to a single user
> maintenance mode.  How do I do that?

At the grub menu, select the kernel you wish to boot. 
Press "e"
Move cursor to the "kernel" line
Press "e"
Move cursor to the end of the line. Append " 1" or " single"
Press <enter>
Press "b"

This will load the kernel and run a modified start-up sequence (not the 
regular init command). You get a root shell which is quite limited but usually 
adequate for repairing broken system. 

In a way, it's very similar to booting into a LiveCD without having to go and 
find the CD first



-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-05-03 14:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 13:31 [gentoo-user] Frozen after Upgrade Colleen Beamer
2010-05-03 13:40 ` Hazen Valliant-Saunders
2010-05-03 13:44   ` Colleen Beamer
2010-05-03 13:57     ` Philip Webb
2010-05-03 14:10       ` Dale
2010-05-03 20:13         ` CJoeB
2010-05-03 22:53           ` Dale
2010-05-03 14:26       ` Colleen Beamer
2010-05-04  9:56     ` Neil Bothwick
2010-05-03 13:41 ` Indexer
2010-05-03 13:47   ` Colleen Beamer
2010-05-03 13:58     ` Indexer
2010-05-03 14:04     ` Alan McKinnon
2010-05-03 14:30       ` Colleen Beamer
2010-05-03 14:56         ` Alan McKinnon [this message]
2010-05-03 15:06           ` KH
2010-05-03 15:10             ` Alan McKinnon
2010-05-03 16:22           ` Willie Wong
2010-05-03 16:41             ` Dale
2010-05-03 14:56         ` Hazen Valliant-Saunders
2010-05-03 14:07     ` Dale
2010-05-03 13:45 ` [gentoo-user] " Remy Blank
2010-05-03 13:49   ` Colleen Beamer
2010-05-03 14:40     ` Remy Blank
2010-05-03 15:09     ` Peter Humphrey
2010-05-03 16:04     ` Frank Steinmetzger

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=201005031656.04901.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=colleen.beamer@gmail.com \
    --cc=gentoo-user@lists.gentoo.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