[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Manually enabling a PCI-X card
- To: silug-discuss@silug.org
- Subject: Re: Manually enabling a PCI-X card
- From: Brian Elder <bri.elder@gmail.com>
- Date: Thu, 4 Jun 2009 15:12:04 -0500
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=+NNwfUOEGzN6kjXJYdY82tlIm90UUbzvfcf29/9Y6cE=; b=FoguYKc8MhXRBbw3dGoNodZ2ENN06U3b/HxB8K1CkFHIwDtGYCGAbsIXKaTLMUrD9l pQEQQAp2RLh33kwroIXl85101wE0ZvycQcAQ2pGsDJGKIOXToAh9iWgIISznAf152Omw TO3pxxUDs1QLlLrXKMnn5BVh71IRLWWaisONw=
- DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=t+6ZIaXa85Zo8PUNv8WIJSr7jzLuJ8Z0FarYx8O65UscQIbktlIfwPv7Mm54zDhhrO lqLvCRNO3dqCaWym/MFnpRuuIKzNpIcypM7oOMHqGbHlXV1aR7LGipdvqRXTUXVXekvi zGYfD4zwF9/C8EVvbh8j+4YEq4hba5ybNfOE4=
- In-Reply-To: <92FEF945-4712-411B-B4D5-5F1975C452BD@gmail.com>
- Organization: Southern Illinois Linux Users Group
- References: <1244135722.17986.16.camel@lion.protogeek.org> <92FEF945-4712-411B-B4D5-5F1975C452BD@gmail.com>
- Reply-To: silug-discuss@silug.org
- Sender: silug-discuss-owner@silug.org
Oh and sometimes the card won't even be initialized unless you have a
device plugged into it prior to POST.
Just thought of that...
~Brian
On Jun 4, 2009, at 2:55 PM, Brian Elder wrote:
> This may sound stupid, but you are sure the card is not DOA? Also,
> during POST, do you get any sort of BIOS from the card itself?
> Usually those types of cards have some sort of initialization before
> any OS loads and will show you devices that are connected to it.
> Your card may be different but just throwing that out there.
> ~Brian
>
>
> On Jun 4, 2009, at 12:15 PM, Robert G. (Doc) Savage wrote:
>
>> What follows may sound simple to someone (I hope). During the past
>> few
>> iterations of Fedora & Red Hat the automated process of hardware
>> device
>> discovery / driver installation has gotten so good that I seem to
>> have
>> forgotten how to do it manually.
>>
>> I recently purchased a 4-port eSATA card for my SuperMicro server
>> running RHEL5. For details see
>> http://www.cooldrives.com/saii3g4espcc.html.
>>
>> Unfortunately this card isn't identified during RHEL5u3 boot-time
>> discovery. According to the above web page, this card is based on the
>> Silicon Image Sil3124 chipset. According to
>> http://www.linux-ata.org/driver-status.html there's an open-source
>> driver available called sata_sil24.ko. It's supported by RHEL5u3,
>> so I
>> entered:
>>
>> # insmod /lib/modules/2.6.18.128.1.10.el5/kernel/drivers/ata/
>> sata_sil24.ko
>>
>> It apparently loads normally:
>>
>> # lsmod | grep sil24
>> sata_sil24 50373 0
>> libata 208721 2 sata_sil24,sata_nv
>>
>> I even remembered to add it to /etc/modprobe.conf:
>>
>> alias scsi_hostadapter2 sata_sil24
>>
>> OK... I've physically found a 64-bit PCI-X slot (last one!) and
>> installed the card. I've identified its chipset, found a supported
>> Linux
>> driver for that chipset, and installed it as a module. So far so
>> good.
>> What's the problem? Where's the beef? When I now run:
>>
>> # lspci -v
>>
>> there's no evidence that the card is now active even with the driver
>> installed. What step(s) have I forgotten?
>>
>> --Doc
>>
>>
>> -
>> To unsubscribe, send email to majordomo@silug.org with
>> "unsubscribe silug-discuss" in the body.
>
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.