2004-11-19 20:06:53

by Jin Suh

[permalink] [raw]
Subject: [2.4.28] Enabling a SATA drive (sata_promise.o) with Promise Fastrak S150 TX2Plus SATA PCI card?

Hello,

I have a Dell 650/Linux-2.4.28 with a Promise Fastrak S150 TX2Plus SATA PCI
card with 2 250GB Western digital drives connected. Could anyone help me how to
enable the SATA drives? I had 2.4.25 one time and it showed me /dev/hde and
/dev/hdg but the new SATA driver should show as /dev/sdX, right?

I see libata.o and sata_promise.o modules. When I do "modprobe libata and
modprobe sata_promise", I got bunch of "Unresolved symbols". I also downloaded
ft3xx driver and didn't work too. Any idea? I rebooted the same machine with
Suse9.1 (2.6.x kernel). It loaded the libata.o and sata_promise.o and I could
see /dev/sda and /dev/sdb as SATA drives correctly.
I also have a Intel P5 ICH5, D875PBZ with 2 SATA ports. I also could not enable
the drives with ata_piix.o. Any helps would be appreciated.

Jin



2004-11-20 20:12:22

by Kenneth MacDonald

[permalink] [raw]
Subject: Re: [2.4.28] Enabling a SATA drive (sata_promise.o) with Promise Fastrak S150 TX2Plus SATA PCI card?

>>>>> "Jin" == Jin Suh <[email protected]> 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.