From: Kari Hameenaho <khaho@koti.soon.fi>
To: linux-kernel@vger.kernel.org
Cc: system_lists@nullzone.org
Subject: Re: Highpoint HPT370 not working in 2.4.18+ versions
Date: Thu, 2 Jan 2003 01:09:42 +0200 [thread overview]
Message-ID: <20030102010942.357248fc.khaho@koti.soon.fi> (raw)
system_lists@nullzone.org wrote:
>* BOOTing using 2.4.20 (or 2.4.21-pre2)
>--------------------
>...
>Linux agpgart interface v0.99 (c) Jeff Hartmann
>agpgart: Maximum main memory to use for agp memory: 96M
>agpgart: Detected Via Apollo Pro chipset
>agpgart: AGP aperture is 64M @ 0xd8000000
>Highpoint HPT370 Softwareraid driver for linux version ...
>NET4: Linux TCP/IP 1.0 for NET4.0
>IP Protocols: ICMP, UDP, TCP
>...
>
>You can notice how the driver for HPT is loaded but nothing is found.
>OF COURSE hde hdf etc is NOT found .. (at the begining of the boot).
Maybe you have selected only RAID part of HPT370 in your kernel config,
not the driver part at all.
RAID part in menuconfig (this seems to be on):
<*> Support for IDE Raid controllers (EXPERIMENTAL)
...
<*> Highpoint 370 software RAID (EXPERIMENTAL)
But you also need the driver, as in menuconfig (this seems to be off):
[*] HPT366/368/370 chipset support
Maybe the RAID part should not be selectable without the driver,
but when making own kernels you should know about many options
anyway.
---
Kari Hämeenaho
next reply other threads:[~2003-01-01 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 23:09 Kari Hameenaho [this message]
2003-01-02 21:51 ` Highpoint HPT370 not working in 2.4.18+ versions system_lists
-- strict thread matches above, loose matches on Subject: below --
2002-12-31 0:43 system_lists
2002-12-26 0:36 system_lists
2002-12-28 0:12 ` Scott McDermott
2002-12-30 9:10 ` system_lists
2002-12-30 13:10 ` Alan Cox
2002-12-30 23:54 ` system_lists
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=20030102010942.357248fc.khaho@koti.soon.fi \
--to=khaho@koti.soon.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=system_lists@nullzone.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