From: Daniel Burrows <[EMAIL PROTECTED]>
To: Robert Cates <[EMAIL PROTECTED]>
CC: [email protected]
Subject: Re: cannot access machine after apt-get dist-upgrade
Date: Mon, 04 Jun 2007 06:27:43 -0700
MIME-Version: 1.0
Received: from murphy.debian.org ([70.103.162.31]) by
bay0-mc6-f15.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 4
Jun 2007 06:30:02 -0700
Received: from localhost (localhost [127.0.0.1])by murphy.debian.org
(Postfix) with QMQPid 9C1462E140; Mon, 4 Jun 2007 13:29:17 +0000 (UTC)
Received: from vms044pub.verizon.net (vms044pub.verizon.net
[206.46.252.44])by murphy.debian.org (Postfix) with ESMTP id 320662E160for
<[email protected]>; Mon, 4 Jun 2007 13:29:10 +0000 (UTC)
Received: from emurlahn.burrows.local ([71.112.26.136]) by
vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr
3 2006)) with ESMTPA id <[EMAIL PROTECTED]> for
[email protected]; Mon, 04 Jun 2007 08:29:21 -0500 (CDT)
X-Message-Info:
LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8QigGIQtU5Yvr3lK0P
Old-Return-Path: <[EMAIL PROTECTED]>
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on
murphy.debian.org
X-Spam-Level: X-Spam-Status: No, score=-5.5 required=4.0
tests=AWL,BAYES_00,FORGED_RCVD_HELO,LDOSUBSCRIBER,MAILTO_TO_SPAM_ADDR
autolearn=no version=3.1.4
X-Original-To: [email protected]
References:
<[EMAIL PROTECTED]><[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Rc-Virus: 2006-10-25_01
X-Rc-Spam: 2007-05-24_01
Resent-Message-ID: <[EMAIL PROTECTED]>
Resent-From: [email protected]
X-Mailing-List: <[email protected]> archive/latest/487457
X-Loop: [email protected]
List-Id: <debian-user.lists.debian.org>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe:
<mailto:[EMAIL PROTECTED]>
List-Unsubscribe:
<mailto:[EMAIL PROTECTED]>
Precedence: list
Resent-Sender: [EMAIL PROTECTED]
Resent-Date: Mon, 4 Jun 2007 13:29:17 +0000 (UTC)
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 04 Jun 2007 13:30:03.0469 (UTC)
FILETIME=[753A4FD0:01C7A6AC]
On Sun, Jun 03, 2007 at 11:58:55AM +0000, Robert Cates
<[EMAIL PROTECTED]> was heard to say:
> this is going to be my new server, so there's no GUI, only text mode,
and
> it gets all the way to the login prompt, but the machine will not take
> keyboard (USB, which is what I always used) input. As I was saying, I
can
> see during the bootup that the network cards are not started, but I
can't
> tell why, so I'm therefore also unable to access the machine per remote
SSH.
OK -- have you tried booting with init=/bin/sh? I'm betting you still
won't be able to type, but it might be worth a try. You could also try
booting a live CD and using it to examine the system logs for clues about
what's happening.
Here's another thought: have you been loading the USB/network modules
from
/etc/modules or from udev/hotplug?
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
Um, how do I set the boot option init=/bin/sh if I can't access the machine?
Well, I can't tell from where the USB/network modules are loading from. Is
this a difference between kernels 2.6.8 and 2.6.18?
I guess I'll probably have to use a Live CD, I was hoping though that maybe
somebody on the list already knows right where the problem is.
Robert
_________________________________________________________________
Dont miss your chance to WIN $10,000 and other great prizes from Microsoft
Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
