From mbarclay@u.washington.edu Mon Apr 29 14:14:35 2002
Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14])
	by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TLEVw3011176
	for <linux@reallists.u.washington.edu>; Mon, 29 Apr 2002 14:14:31 -0700
Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Apr 29 14:14:31 2002 -0700
Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5])
	by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TLEUre026152
	for <linux@lists.u.washington.edu>; Mon, 29 Apr 2002 14:14:30 -0700
Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18])
	by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TLETYB028125
	for <linux@u.washington.edu>; Mon, 29 Apr 2002 14:14:29 -0700
Received: FROM homer15.u.washington.edu BY mailscan-out3.cac.washington.edu ; Mon Apr 29 14:14:28 2002 -0700
Received: from localhost (mbarclay@localhost)
	by homer15.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TLESKH087240
	for <linux@u.washington.edu>; Mon, 29 Apr 2002 14:14:28 -0700
Date: Mon, 29 Apr 2002 14:14:28 -0700 (PDT)
From: matt william barclay <mbarclay@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.0204291311560.71342-100000@dante36.u.washington.edu>
Message-ID: <Pine.A41.4.44.0204291409320.50042-100000@homer15.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 29 Apr 2002, Michael Frank wrote:

>
> 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.

When booting direct from hda without lilo, it just kept dumping the CPU
registers without any warnings or debug info.

After dd'ing the kernel to /dev/hda I used rdev to set the root
filesystem.  I was following the steps in the bootdisk How-To.

> 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 =)

It is easier too!

.