Hi all,

I've just decided to upgrade my Sarge server to Etch, which the process
itself seemed to go very smoothly, but now after rebooting it does not
bring up my eth0 and eth1, nor can I input any on the keyboard. In
other words, I'm now locked out.

The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
so I have both the original 2.6.8 as well as the new 2.6.18. Now,
regardless of which kernel I boot, I'm locked out. Is there a way I can
still access my machine? I'll like to avoid having to completely
re-install from fresh.

Thanks in advance,
Robert

__________________________________________________ _______________
More photos, more messages, more storage—get 2GB with Windows Live Hotmail.
http://imagine-windowslive.com/hotma...M_mini_2G_0507


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 05/31/2007 01:03 PM, Robert Cates wrote:
> Hi all,
>
> I've just decided to upgrade my Sarge server to Etch, which the process
> itself seemed to go very smoothly, but now after rebooting it does not
> bring up my eth0 and eth1, nor can I input any on the keyboard. In
> other words, I'm now locked out.
>
> The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> regardless of which kernel I boot, I'm locked out. Is there a way I can
> still access my machine? I'll like to avoid having to completely
> re-install from fresh.
>
> Thanks in advance,
> Robert
>

If you installed the 'bash_static' package, you can probably boot by
specifying it as a parameter to 'init' on the kernel command line. I
think it's done like so:

Linux init=/bin/bash-static

Please read this entire section:
http://www.debian.org/doc/manuals/re...h-tips.en.html

Also see this:
http://www.debian.org/doc/manuals/re...#s-un-bootable

Legend has it that that Woody install CD (#1) allowed you to use it as a
rescue disk by specifying certain boot parameters:

rescue root=/dev/sda1

The Sarge install CD #1 didn't have this feature, but I think it is back
in Etch; I did have to rescue an Etch system recently using the Etch
install CD, but the procedure was different; I remember selecting
"rescue" from a menu.

I've had an unbootable system before, and it's not necessarily fun. I've
always been able to fix it using some combination of rescue disks and
installation/uninstallation of certain packages.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates wrote:
> Hi all,
>
> I've just decided to upgrade my Sarge server to Etch, which the process
> itself seemed to go very smoothly, but now after rebooting it does not
> bring up my eth0 and eth1, nor can I input any on the keyboard. In
> other words, I'm now locked out.
>
> The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> regardless of which kernel I boot, I'm locked out. Is there a way I can
> still access my machine? I'll like to avoid having to completely
> re-install from fresh.

can you ssh in?

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGXz/raIeIEqwil4YRAtC/AJ9PRZ4C2zEAXo1lLgo/OJ6kzn3hewCfQ7q8
yAbJ9sA8zo/K321so4ZbSjg=
=unS2
-----END PGP SIGNATURE-----

On Thu, May 31, 2007 at 02:36:45PM -0700, Andrew Sackville-West wrote:
> On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates wrote:
> > I've just decided to upgrade my Sarge server to Etch, which the process
> > itself seemed to go very smoothly, but now after rebooting it does not
> > bring up my eth0 and eth1, nor can I input any on the keyboard. In
> > other words, I'm now locked out.
> >
> > The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> > so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> > regardless of which kernel I boot, I'm locked out. Is there a way I can
> > still access my machine? I'll like to avoid having to completely
> > re-install from fresh.
>
> can you ssh in?

Probably not with eth*.

Although you can't input to the keyboard, can you see the boot messages
scrolling by? Do they provide any clews? Can you boot up the install
CD in rescue mode and read /var/log/dmesg and /var/log/boot? What about
connecting a spare computer to the serial port and issuing a console=
line to the kernel at boot so you can log messages there? What about
booting in rescue, and adding a line to inittab to give you a getty on
the serial line and see if you can log in that way?

Doug.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates <cates58@hotmail.com> was heard to say:
> I've just decided to upgrade my Sarge server to Etch, which the process
> itself seemed to go very smoothly, but now after rebooting it does not
> bring up my eth0 and eth1, nor can I input any on the keyboard. In
> other words, I'm now locked out.
>
> The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> regardless of which kernel I boot, I'm locked out. Is there a way I can
> still access my machine? I'll like to avoid having to completely
> re-install from fresh.

It sounds like you can access your bootloader. Have you tried booting
with init=/bin/sh and poking around that way?

When you say you can't input anything on the keyboard -- what is
displayed on the screen? Is it showing a graphical login, a text-mode
login, or something completely different?

Daniel


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi,

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.

Thanks for your ,
Robert



>From: Daniel Burrows <dburrows@debian.org>
>To: Robert Cates <cates58@hotmail.com>
>CC: debian-user@lists.debian.org
>Subject: Re: cannot access machine after apt-get dist-upgrade
>Date: Fri, 01 Jun 2007 16:33:05 -0700
>MIME-Version: 1.0
>Received: from murphy.debian.org ([70.103.162.31]) by
>bay0-mc11-f2.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Fri, 1
>Jun 2007 17:31:18 -0700
>Received: from localhost (localhost [127.0.0.1])by murphy.debian.org
>(Postfix) with QMQPid 9F4482E24F; Sat, 2 Jun 2007 00:30:18 +0000 (UTC)
>Received: from vms046pub.verizon.net (vms046pub.verizon.net
>[206.46.252.46])by murphy.debian.org (Postfix) with ESMTP id DB02B2E509for
><debian-user@lists.debian.org>; Sat, 2 Jun 2007 00:30:05 +0000 (UTC)
>Received: from [127.0.1.1] ([71.112.26.136]) by vms046.mailsrvcs.net (Sun
>Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id
><0JIZ00IPBG21FHRE@vms046.mailsrvcs.net> for debian-user@lists.debian.org;
>Fri, 01 Jun 2007 19:30:02 -0500 (CDT)
>X-Message-Info:
>LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8Qi gGIQtU5Yvr3lK0P
>Old-Return-Path: <dburrows@debian.org>
>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,LDOSUBSCRIBER,MAILTO_TO_SPAM_A DDR autolearn=no
>version=3.1.4
>X-Original-To: debian-user@lists.debian.org
>References: <BAY115-F193D547B2905FEF704B364A22D0@phx.gbl>
>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: <1JTr0.A.n4E.SoLYGB@murphy>
>Resent-From: debian-user@lists.debian.org
>X-Mailing-List: <debian-user@lists.debian.org> archive/latest/487269
>X-Loop: debian-user@lists.debian.org
>List-Id: <debian-user.lists.debian.org>
>List-Post: <mailto:debian-user@lists.debian.org>
>List-: <mailto:debian-user-request@lists.debian.org?subject=>
>List-Subscribe:
><mailto:debian-user-request@lists.debian.org?subject=subscribe>
>List-Unsubscribe:
><mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
>Precedence: list
>Resent-Sender: debian-user-request@lists.debian.org
>Resent-Date: Sat, 2 Jun 2007 00:30:18 +0000 (UTC)
>Return-Path: bounce-debian-user=cates58=hotmail.com@lists.debian.org
>X-OriginalArrivalTime: 02 Jun 2007 00:31:19.0105 (UTC)
>FILETIME=[5682AB10:01C7A4AD]
>
>On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates
><cates58@hotmail.com> was heard to say:
> > I've just decided to upgrade my Sarge server to Etch, which the process
> > itself seemed to go very smoothly, but now after rebooting it does not
> > bring up my eth0 and eth1, nor can I input any on the keyboard. In
> > other words, I'm now locked out.
> >
> > The last thing I did was installed kernel/linux image 2.6.18 (with SMP),
> > so I have both the original 2.6.8 as well as the new 2.6.18. Now,
> > regardless of which kernel I boot, I'm locked out. Is there a way I can
> > still access my machine? I'll like to avoid having to completely
> > re-install from fresh.
>
> It sounds like you can access your bootloader. Have you tried booting
>with init=/bin/sh and poking around that way?
>
> When you say you can't input anything on the keyboard -- what is
>displayed on the screen? Is it showing a graphical login, a text-mode
>login, or something completely different?
>
> Daniel
>
>
>--
>To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact
>listmaster@lists.debian.org
>

__________________________________________________ _______________
Make every IM count. Download Messenger and join the i’m Initiative now.
It’s free. http://im.live.com/messenger/im/home...e=TAGHM_June07


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 06/03/2007 06:58 AM, Robert Cates wrote:
> Hi,
>
> 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.
>
> Thanks for your ,
> Robert
>
>
>

http://search.yahoo.com/search?p=deb...h+usb+keyboard

Visit the second link and search for "USB keyboard"


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Jun 03, 2007 at 11:58:55AM +0000, Robert Cates <cates58@hotmail.com> 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, May 31, 2007 at 08:43:35PM -0400, Douglas Allan Tutty wrote:
> On Thu, May 31, 2007 at 02:36:45PM -0700, Andrew Sackville-West wrote:
> > On Thu, May 31, 2007 at 06:03:06PM +0000, Robert Cates wrote:
> > > I've just decided to upgrade my Sarge server to Etch, which the process
> > > itself seemed to go very smoothly, but now after rebooting it does not
> > > bring up my eth0 and eth1, nor can I input any on the keyboard. In

--------------------^^^^^^^^^^^


> >
> > can you ssh in?
>
> Probably not with eth*.

D'oh! sometimes I amaze myself.

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGZF3iaIeIEqwil4YRArewAJ9sEinYA4mqFWQvIfWeK5 zBqZ5McACeMApI
n1KTldNP9OMJqRzl4RwYOy8=
=9nux
-----END PGP SIGNATURE-----

>From: Daniel Burrows <dburrows@debian.org>
>To: Robert Cates <cates58@hotmail.com>
>CC: debian-user@lists.debian.org
>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
><debian-user@lists.debian.org>; 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 <0JJ400EAO5GWFZ22@vms044.mailsrvcs.net> for
>debian-user@lists.debian.org; Mon, 04 Jun 2007 08:29:21 -0500 (CDT)
>X-Message-Info:
>LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8Qi gGIQtU5Yvr3lK0P
>Old-Return-Path: <dburrows@debian.org>
>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: debian-user@lists.debian.org
>References:
><20070601233305.GB10295@alpaca><BAY115-F22DF8F781818189A3CE2CA2220@phx.gbl>
>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: <IEG3xC.A.iHD.tOBZGB@murphy>
>Resent-From: debian-user@lists.debian.org
>X-Mailing-List: <debian-user@lists.debian.org> archive/latest/487457
>X-Loop: debian-user@lists.debian.org
>List-Id: <debian-user.lists.debian.org>
>List-Post: <mailto:debian-user@lists.debian.org>
>List-: <mailto:debian-user-request@lists.debian.org?subject=>
>List-Subscribe:
><mailto:debian-user-request@lists.debian.org?subject=subscribe>
>List-Unsubscribe:
><mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
>Precedence: list
>Resent-Sender: debian-user-request@lists.debian.org
>Resent-Date: Mon, 4 Jun 2007 13:29:17 +0000 (UTC)
>Return-Path: bounce-debian-user=cates58=hotmail.com@lists.debian.org
>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
><cates58@hotmail.com> 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 debian-user-REQUEST@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact
>listmaster@lists.debian.org
>

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

__________________________________________________ _______________
Don’t 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Robert Cates a écrit :
>
>> From: Daniel Burrows <dburrows@debian.org>
>> To: Robert Cates <cates58@hotmail.com>
>> CC: debian-user@lists.debian.org
>> 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 <debian-user@lists.debian.org>; 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
>> <0JJ400EAO5GWFZ22@vms044.mailsrvcs.net> for
>> debian-user@lists.debian.org; Mon, 04 Jun 2007 08:29:21 -0500 (CDT)
>> X-Message-Info:
>> LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8Qig GIQtU5Yvr3lK0P
>> Old-Return-Path: <dburrows@debian.org>
>> 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: debian-user@lists.debian.org
>> References:
>> <20070601233305.GB10295@alpaca><BAY115-F22DF8F781818189A3CE2CA2220@phx.gbl>
>>
>> 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: <IEG3xC.A.iHD.tOBZGB@murphy>
>> Resent-From: debian-user@lists.debian.org
>> X-Mailing-List: <debian-user@lists.debian.org> archive/latest/487457
>> X-Loop: debian-user@lists.debian.org
>> List-Id: <debian-user.lists.debian.org>
>> List-Post: <mailto:debian-user@lists.debian.org>
>> List-: <mailto:debian-user-request@lists.debian.org?subject=>
>> List-Subscribe:
>> <mailto:debian-user-request@lists.debian.org?subject=subscribe>
>> List-Unsubscribe:
>> <mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
>> Precedence: list
>> Resent-Sender: debian-user-request@lists.debian.org
>> Resent-Date: Mon, 4 Jun 2007 13:29:17 +0000 (UTC)
>> Return-Path: bounce-debian-user=cates58=hotmail.com@lists.debian.org
>> 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
>> <cates58@hotmail.com> 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 debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>>
>
> 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
>
The "init=/bin/sh" could be modified during the OS choice (grub ou lilo)
if you have one. With grub, edit the boot option with "e" and modify the
launch line with "e" too, add at the end of line "init=/bin/sh" and
valid by enter then boot with "b". With lilo, just select the boot
option and add at the end of line "init=/bin/sh". This solution is
available if you have a boot menu and if your keyboard is detected... Be
careful that nothing is mounted except the root partition which is in
read-only mode. /proc filesystem isn't mounted too !!!

I can suggest you to boot with a liveCD and paste here log files as
/var/log/syslog for example.

If you have a initrd, you should use it. You can create a shell script
(with liveCD) and launch it at boot time with
"init=/path/to/shell/script". This script can be use to load modules,
make "pause" to see the errors, and try to store datas somewhere (usb
disk ?). Don't forget to chmod u+x the script shell or you will need a
new liveCD boot (believe my experience)....

Hope this can you

Christophe
> __________________________________________________ _______________
> Don’t 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jun 04, 2007 at 07:16:54PM +0000, Robert Cates <cates58@hotmail.com> was heard to say:
> >On Sun, Jun 03, 2007 at 11:58:55AM +0000, Robert Cates
> ><cates58@hotmail.com> 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?
>
> Um, how do I set the boot option init=/bin/sh if I can't access the machine?

Oh, sorry -- you said you were booting different kernels, so I figured
you had access to the bootloader. Never mind then.

> 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'm not sure, but I doubt it's the kernel upgrade that caused your
problems (since they persist in both kernels). I think the udev/hotplug
protocol did change a few times, but I couldn't tell you how -- however,
the code in udev did change (version 0.056-3 -> version 0.105-4), and
if udev broke *and* udev was loading your USB keyboard driver, that could
explain the problem.

My general hunch is that something in the userspace toolchain that loads
your modules is broken, but I don't know what (for all I know it's as
simple as that you need to run depmod -a).

Daniel


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org