From msfrank@u.washington.edu Mon Apr 29 13:36:20 2002
Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TKaHw3059774
	for <linux@reallists.u.washington.edu>; Mon, 29 Apr 2002 13:36:17 -0700
Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 29 13:36:17 2002 -0700
Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19])
	by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TKaHc6006464
	for <linux@lists.u.washington.edu>; Mon, 29 Apr 2002 13:36:17 -0700
Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17])
	by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TKaGMQ018459
	for <linux@u.washington.edu>; Mon, 29 Apr 2002 13:36:16 -0700
Received: FROM dante36.u.washington.edu BY mailscan-out2.cac.washington.edu ; Mon Apr 29 13:36:15 2002 -0700
Received: from localhost (msfrank@localhost)
	by dante36.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TKaF4U108082
	for <linux@u.washington.edu>; Mon, 29 Apr 2002 13:36:15 -0700
Date: Mon, 29 Apr 2002 13:36:15 -0700 (PDT)
From: Michael Frank <msfrank@u.washington.edu>
To: UW Linux Group <linux@u.washington.edu>
Subject: Re: dd and IDE CF drives
In-Reply-To: <Pine.A41.4.44.0204291241250.50042-100000@homer15.u.washington.edu>
Message-ID: <Pine.A41.4.44.0204291311560.71342-100000@dante36.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 29 Apr 2002, matt william barclay wrote:

> The booting problem is that you can't boot off an IDE device like you do a
> floppy device.  I installed lilo and it now works.
>
> Thanks for setting me straight on dd usage!

Are you sure you can't boot linux directly (without a bootloader)?  When
you booted your machine after writing the kernel to disk, did it boot at
all (did any diagnostics get printed), or did it fail with a kernel panic?
One potential problem with your setup, since it sounds like you compiled
the kernel on a different machine that what you ran the kernel on, is that
the root device would be incorrectly set.  if you got a kernel panic to
the effect of "root device not found on 0X:XX", then thats probably what
the problem was.

Anyways, having a bootloader like lilo or grub on the machine is
definitely better.  I'm just curious now whether my knowledge was correct
or not (and its gonna bug me because I don't have a machine to fiddle
with this kind of stuff on =)

Michael


-------------------------  .~.
Michael Frank              /v\
msfrank@u.washington.edu  // \\
------------------------ /(   )\
                          ^`~'^




.