From: war <war@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: copycat@jx165.net
Subject: HPT366/368/370 IDE/SCSI-EMULATION PROBLEMS (2.4.x)
Date: Tue, 22 Apr 2003 12:22:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0304221213510.25378@p300> (raw)
war@p300:~$ find /usr/src/linux-2.4.20/Documentation/ | grep -i hpt
war@p300:~$
The top of /usr/src/linux-2.4.20/drivers/ide/hpt366.c does not offer much
in terms of the documentation.
Hopefully my question is simple, why does this card only seem to work with
such a configuration?
I have 3 cards, 12 HDD.
If I try to boot with normal (no append), the box will sit there trying to
find the hard drives.
If I boot with the way most distros set it up (ie: sda=noprobe
sdb=noprobe) and so on, this works, but then it uses SCSI-EMULATION.
I am familiar with PROMISE BOARDS (100/133) and they do not have this
problem.
Is there something in particular one must do to achieve IDE access, to
have the kernel see the HDD's as IDE devices and not use SCSI-EMULATION
for HPT ROCKET ATA/100 cards?
Also, when you cat /proc/ide/hpt* it gives a segfault and the kernel
oopses, I've sent this e-mail a week or two ago.
So, to summarize:
Boot with IDE support only and no append, the box sits there looking for
the other IDE hard drives (using intel i845 chipset btw).
It looks forever, was on for 2 weeks, never found the disks.
Switched over to distro method, sda=noprobe,sdb=noprobe and so on for all
12 drives and testing with rh73/scsi-emulation/etc IS enabled, and the
kernel does a lot of running around and sets them up as SCSI devices.
Is it possible to have HPT rocket ATA/100 cards (3 of them) see hard
drives as IDE and not SCSI?
next reply other threads:[~2003-04-22 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 16:22 war [this message]
2003-04-22 16:08 ` Alan Cox
2003-04-22 17:12 ` war
2003-04-22 17:03 ` Måns Rullgård
2003-04-22 17:04 ` war
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=Pine.LNX.4.55.0304221213510.25378@p300 \
--to=war@lucidpixels.com \
--cc=copycat@jx165.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®