linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Hart" <af804@bfn.org>
To: linux raid <linux-raid@vger.kernel.org>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>
Subject: Re: 2.6.19-rc5: Can't get built-in raid support, modular works correctly
Date: Sat, 21 Jul 2007 01:06:28 +0900	[thread overview]
Message-ID: <46A0DD84.1050203@bfn.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707200613170.13189@p34.internal.lan>

Justin Piszcz wrote:

> I (normally) do not run -rcX release and I always compile in RAID 
> support and have not seen that issue; then again, I did not try 
> 2.6.19-rc5 that I can remember.

I've just discovered the problem (at 1 am of course).

I'm using Linux with my own custom kernel running on a quad Mac Pro (no 
Parallels, no Bootcamp, no Windows, no OS X etc, and hence no partition 
restrictions.....:-). Since this is an Intel Mac, running grub used to 
be a bit tricky owing to the A20 line problem, so I've been using lilo 
instead.
After building the kernel, I dutifully typed the following, as any good 
lilo believing kernel builder should:

lilo

This ended up placing the boot block on the root partition. I had 
previously told the Mac EFI boot loader to look for it on the MBR of my 
first SATA drive, which in this case is a very different location. What 
I should have used was:

lilo -b /dev/sda

It was booting the old kernel of course, which was the same version 
release as the rebuilt one.

(....slapping forehead.....)

All is working just as expected now.....:-)

Many Thanks for your comments........


      reply	other threads:[~2007-07-20 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 13:54 2.6.19-rc5: Can't get built-in raid support, modular works correctly J. Hart
2007-07-19 16:04 ` Justin Piszcz
2007-07-19 21:54   ` J. Hart
2007-07-20 10:13     ` Justin Piszcz
2007-07-20 16:06       ` J. Hart [this message]

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=46A0DD84.1050203@bfn.org \
    --to=af804@bfn.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).