From: Vid Strpic <vms@bofhlet.net>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: "Rahsheen Porter Sr." <microrahsheen@comcast.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: HPT366 ate my IDE controllers
Date: Fri, 5 Dec 2003 09:56:17 +0100 [thread overview]
Message-ID: <20031205085617.GD3042@home.bofhlet.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Thu, Dec 04, 2003 at 10:51:40PM -0500, Gene Heskett wrote:
> On Thursday 04 December 2003 21:15, Rahsheen Porter Sr. wrote:
> >So my root partition, which resides on /dev/hde1 with 2.4.20,
> > becomes /dev/hda1. And my extra partitions that were on /dev/hdg
> > are on /dev/hdc. This wouldn't be a problem accept that what was on
> > /dev/hda and hdc are now gone.
> >What would cause the kernel to totally ignore the built in
> > controllers?
> I'd bet a small amount that there is something in the bios you've set
> that is making that decision for you. Probably a boot offboard
> controllers first or some such.
It's CONFIG_BLK_DEV_OFFBOARD, in the kernel. But the behavior I noticed
is, with that kernel option, system assigns hda for the first disk on
the second controller (Promise here, not HPT, but that shouldn't matter
at all), and the drives on the motherboard controller get hde and so on.
Is OP sure that kernel really doesn't see the drives at all? And
ofcourse if turning off CONFIG_BLK_DEV_OFFBOARD in the kernel fixes the
problem...
--
vms@bofhlet.net, IRC:*@Martin, /bin/zsh. C|N>K
Linux moria 2.6.0-test11 #2 Wed Nov 26 23:12:44 CET 2003 i686
09:52:17 up 7 days, 23:54, 1 user, load average: 0.75, 0.75, 0.68
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-12-05 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 8:56 Vid Strpic [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-05 2:15 HPT366 ate my IDE controllers Rahsheen Porter Sr.
2003-12-05 3:51 ` Gene Heskett
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=20031205085617.GD3042@home.bofhlet.net \
--to=vms@bofhlet.net \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=microrahsheen@comcast.net \
/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