From: Kenneth MacDonald <kenny@holyrood.ed.ac.uk>
To: Jin Suh <jinssuh@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.28] Enabling a SATA drive (sata_promise.o) with Promise Fastrak S150 TX2Plus SATA PCI card?
Date: 20 Nov 2004 20:12:07 +0000 [thread overview]
Message-ID: <yqo7jog46w8.fsf@penguin.ucs.ed.ac.uk> (raw)
In-Reply-To: <20041119200331.53569.qmail@web41210.mail.yahoo.com>
>>>>> "Jin" == Jin Suh <jinssuh@yahoo.com> writes:
Jin> Hello, I have a Dell 650/Linux-2.4.28 with a Promise Fastrak
Jin> S150 TX2Plus SATA PCI card with 2 250GB Western digital
Jin> drives connected. Could anyone help me how to enable the SATA
Jin> drives? I had 2.4.25 one time and it showed me /dev/hde and
Jin> /dev/hdg but the new SATA driver should show as /dev/sdX,
Jin> right?
Jin> I see libata.o and sata_promise.o modules. When I do
Jin> "modprobe libata and modprobe sata_promise", I got bunch of
Jin> "Unresolved symbols". I also downloaded ft3xx driver and
Jin> didn't work too. Any idea? I rebooted the same machine with
Jin> Suse9.1 (2.6.x kernel). It loaded the libata.o and
Jin> sata_promise.o and I could see /dev/sda and /dev/sdb as SATA
Jin> drives correctly. I also have a Intel P5 ICH5, D875PBZ with
Jin> 2 SATA ports. I also could not enable the drives with
Jin> ata_piix.o. Any helps would be appreciated.
I had this problem when I was using an insmod from busybox compiled up
without the tainted kernel checking feature. the libata.o module is a
GPLONLY as far as I recall.
So, check your insmod/modprobe versions.
Kenny.
--
Desktop Services Team, EUCS.
University of Edinburgh, Scotland.
prev parent reply other threads:[~2004-11-20 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 20:03 Jin Suh
2004-11-20 20:12 ` Kenneth MacDonald [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=yqo7jog46w8.fsf@penguin.ucs.ed.ac.uk \
--to=kenny@holyrood.ed.ac.uk \
--cc=jinssuh@yahoo.com \
--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
Powered by JetHome