Topic: 3ware 9650SX support
Hi,
I was looking for a way to add support for the 3ware 9650SX. Wondering if anybody has added it.
Thanks.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
Welcome to DriverPacks.
Do you have a link to this driver?
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: 3ware 9650SX support
Jaak wrote:
Welcome to DriverPacks.
Do you have a link to this driver?
Thanks
Here is the link
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
here was a test pack link.. tested in virtual PC
see lower for link to a new testpack made on 2007/09/30.
Last edited by Jaak (2007-10-01 06:53:24)
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
I had an error, uploaded fixed file.
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: 3ware 9650SX support
Jaak wrote:
I had an error, uploaded fixed file.
I can confirm the 3ware 9650SE controller is supported.
Thanks for getting this so quickly.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
Thanks.
I'm waiting for other reports about the other REQuests.
(I posted link to this topic in some in the hopes these people will test and provide feedback.)
You need us? We need you!
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
percsas error fixed
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: 3ware 9650SX support
Jaak,
The PERC5 driver for the Dell PowerEdge 2950 works great. Thanks...
Gary
- JakeLD
- Moderator, Sysprep & BartPE Master
- Offline
Re: 3ware 9650SX support
Thx for the feedback, I cant test it for you Jaak our server is gone. At least it works! thx.
Re: 3ware 9650SX support
ad\6 updated to 01/22/2007,7.00.00.06
That's fine, I believed my post http://forum.driverpacks.net/viewtopic.php?id=1944 already forgotten by the experts;-)
ad\6\c deleted (HWID edited into ad\6)
I'm not sure if this is the best solution since it invalidates the driver's signature. I would write a second *.inf-file (which is copy of the existing one except the HWIDs and strings) so that only the signature of the Compaq brand of this controller is invalid what happens anyway since the *.sys is newer then the Compaq *.cat.
And as a last point I would ask to cleanup ad\6 a little bit:
- txtsetup.oem not needed in driverpacks (it's function is ported to DriverPack_MassStorage_wnt5_x86-32.ini)
- the disklabel U320DSK1 is not needed
- MAXIO64K is not referenced in *.inf nor txtsetup.oem so its also not needed (for any unattended setup)
Thanks
Re: 3ware 9650SX support
I saw that there was an update for the Silicon Image 3112 cards. I tried the 7.09.4 MassStorage driverpack but it gives a 0x7B BSOD on both 4.x.79 and 4.x.83 BIOS regretfully. Text installation still recognizes the card as a SataRAID card.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
JSe wrote:
ad\6 updated to 01/22/2007,7.00.00.06
That's fine, I believed my post http://forum.driverpacks.net/viewtopic.php?id=1944 already forgotten by the experts;-)
ad\6\c deleted (HWID edited into ad\6)
I'm not sure if this is the best solution since it invalidates the driver's signature. I would write a second *.inf-file (which is copy of the existing one except the HWIDs and strings) so that only the signature of the Compaq brand of this controller is invalid what happens anyway since the *.sys is newer then the Compaq *.cat.
And as a last point I would ask to cleanup ad\6 a little bit:
- txtsetup.oem not needed in driverpacks (it's function is ported to DriverPack_MassStorage_wnt5_x86-32.ini)
- the disklabel U320DSK1 is not needed
- MAXIO64K is not referenced in *.inf nor txtsetup.oem so its also not needed (for any unattended setup)Thanks
ad\6 post was not forgotten. (it triggered the update)
But, you made me reread it, and I saw the two missing HWIDs were still missing.
I liked your suggestion about making an edited "copy" for that single compaq HWID.
(the other HWIDs this old driver had are still covered by the newest adaptec.)
I called it COMPQ320.INF.
-------------
Stiertje, can you post the HWIDS of that silicon chip you have?
And... what BIOS does it have?
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: 3ware 9650SX support
Jaak wrote:
I liked your suggestion about making an edited "copy" for that single compaq HWID.
(the other HWIDs this old driver had are still covered by the newest adaptec.)
The idea has been stolen from G\N\1 (nv4_disp.inf and nv4_go.inf) so at the end it is a driverpacks.net idea and not my one.
Re: 3ware 9650SX support
Jaak wrote:
Stiertje, can you post the HWIDS of that silicon chip you have?
And... what BIOS does it have?
The problem was reported some time ago in this forum post:
http://forum.driverpacks.net/viewtopic.php?id=1676
Anyway, here are my HWID's
===========
PCI Devices
===========
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_00F2&SUBSYS_98901462&REV_A2\4&102AC5BC&0&00F0: NVIDIA GeForce 6600
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
18 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&36CE346&0 : USB Root Hub
USB\ROOT_HUB\4&37090E00&0 : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0 : USB Root Hub
USB\VID_046D&PID_C517\5&DF9F058&0&2 : USB Composite Device
USB\VID_046D&PID_C517&MI_00\6&247A621&0&0000 : USB Human Interface Device
USB\VID_046D&PID_C517&MI_01\6&247A621&0&0001 : USB Human Interface Device
USB\VID_05E3&PID_0606\5&221832C9&0&2 : Generic USB Hub
USB\VID_05E3&PID_0702\5&221832C9&0&3 : USB Mass Storage Device
USBSTOR\DISK&VEN_TOSHIBA&PROD_MK4025GAS&REV_0811\6&38C08D00&0: TOSHIBA MK4025GAS USB Device
9 matching device(s) found.
=============
Input Devices
=============
HID\VID_046D&PID_C517&MI_00\7&29B49A7B&0&0000 : Logitech HID-Compliant Keyboard
HID\VID_046D&PID_C517&MI_01&COL01\7&149ECB2&0&0000 : Logitech HID-compliant Cordless Mouse
HID\VID_046D&PID_C517&MI_01&COL02\7&149ECB2&0&0001 : HID-compliant consumer control device
HID\VID_046D&PID_C517&MI_01&COL03\7&149ECB2&0&0002 : HID-compliant device
HID\VID_046D&PID_C517&MI_01&COL04\7&149ECB2&0&0003 : HID-compliant device
HID\VID_046D&PID_C517&MI_01&COL05\7&149ECB2&0&0004 : HID-compliant device
6 matching device(s) found.
============
ACPI Devices
============
ACPI\AUTHENTICAMD_-_X86_FAMILY_6_MODEL_8\_0 : AMD Athlon(tm) XP 2400+
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\PNP0000\3&13C0B0C5&0 : Programmable interrupt controller
ACPI\PNP0100\3&13C0B0C5&0 : System timer
ACPI\PNP0200\3&13C0B0C5&0 : Direct memory access controller
ACPI\PNP0303\3&13C0B0C5&0 : PS/2 Keyboard
ACPI\PNP0401\3&13C0B0C5&0 : ECP Printer Port (LPT1)
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0501\2 : Communications Port (COM2)
ACPI\PNP0700\3&13C0B0C5&0 : Standard floppy disk controller
ACPI\PNP0800\3&13C0B0C5&0 : System speaker
ACPI\PNP0A03\1 : PCI bus
ACPI\PNP0A06\3&473F1A46&0 : Extended IO Bus
ACPI\PNP0B00\3&13C0B0C5&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\3 : Motherboard resources
ACPI\PNP0C02\4 : Motherboard resources
ACPI\PNP0C04\3&13C0B0C5&0 : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNP0F13\3&13C0B0C5&0 : PS/2 Compatible Mouse
ACPI\PNPA000\4&5D18F2DF&0 : SCSI/RAID Host Controller
ACPI\PNPB006\3&13C0B0C5&0 : NVIDIA(R) nForce(TM) MIDI UART
ACPI\PNPB02F\3&13C0B0C5&0 : Standard Game Port
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : Advanced Configuration and Power Interface (ACPI) PC
26 matching device(s) found.At the moment the BIOS version is 4.2.83. S\4\B does not have an entry yet for this HWID. S\4 does have an entry, but that one also didn't work. The problem still remains that the card is recognized in textmode as a Raid device instead of a Base device.
BTW, did some research:
- PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 is in both S-4 and S-5, though TXTSETUP.SIF only gives the non-raid version. Same counts for PCI\VEN_1002&DEV_4379&SUBSYS_43791002 and PCI\VEN_1002&DEV_437A&SUBSYS_437A1002
- PCI\VEN_1095&DEV_3112&SUBSYS_31121095 is in S-4, but not in S-4-B
Don't know if it is usefull information though.
Re: 3ware 9650SX support
Try to detalise a HWID for RAID, and same HWID for BASE:
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0101 - for BASE
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0104 - for RAID
I think it must to help.
Re: 3ware 9650SX support
Debugger wrote:
Try to detalise a HWID for RAID, and same HWID for BASE:
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0101 - for BASE
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0104 - for RAIDI think it must to help.
I see what you mean. Didn't think about that.
Anyway, I integrated the latest drivers with nLite after the driverpacks integration, and that seems to work out fine. Maybe I can find out what exactly is different between my cd with only the driverpacks and my cd with manually integrated (well, nlited) si3112 driver. I hope to have some time tomorrow, so I will let you know if I see something different.
Greetz and goodnight.
Re: 3ware 9650SX support
Ok, got some info out of the TXTSETUP.SIF that is different. nLite makes some additions to the SIF file that makes it work.
[SourceDisksNames.x86]
1984= %cdname%,%cdtagfilei%,,"\i386\NLDRV\001"
[WinntDirectories]
1984= NLDRV\001
[SourceDisksFiles.x86]
si3112.cat = 1984,,,,,,,1984,0,0
si3112.inf = 1984,,,,,,,1984,0,0
si3112.sys = 1,,,,,,4_,4,1,,,1,4
si3112.sys = 1984,,,,,,,1984,0,0
silsupp.cpl = 1984,,,,,,,1984,0,0
SiRemFil.sys = 1,,,,,,4_,4,1,,,1,4
siremfil.sys = 1984,,,,,,,1984,0,0
siwinacc.sys = 1984,,,,,,,1984,0,0
[HardwareIdsDatabase]
PCI\VEN_1095&DEV_3112&SUBSYS_31121095 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_34238086 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_311215D9 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_B0021458 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_01661028 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_81E8104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_35121095 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_01661028 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_35121014 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_02B71014 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_B0021458 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_820B104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_145A1462 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_001F6409 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_9003104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_35121A5F = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_000E182D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_901B104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_3512131F = "Si3112"
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 = "Si3112"
PCI\VEN_1002&DEV_4379&SUBSYS_43791002 = "Si3112"
PCI\VEN_1002&DEV_437A&SUBSYS_437A1002 = "Si3112"
[SCSI.Load]
Si3112 = si3112.sys,4
Si3112 = SiRemFil.sys,4
[FileFlags]
si3112.sys = 16
SiRemFil.sys = 16
[SCSI]
Si3112 = "Silicon Image SiI 3x12 SATALink Controller for Windows XP/Server 2003"Of course almost all is in the file somewhere already, added by Driverpacks Base, and I don't know the significance of the [FileFlags] tab. Main thing is that the [SCSI.Load] additions are on top of the whole list. This means that they load before the rest, and I seem to recall some issue with SiI Raid devices where the solution was to let the Raid driver load before the Base driver
.......
Found where it was mentioned
7.04 (03 Apr 07)
Fixed
- ATI (Siliconimage) 3112 driver (Muiz)
- INI: [V-3] appeared twice (Jaak)
- INI: [H-1], fix for win2003 and XP. (also a Bart PE fix) (OverFlow & jtdoom)
- INI: make Silicon Image SiI3112r RAID mode drivers load before non-RAID (Jaak)
- INI: [IN-2-winnt-x86], added: "Intel ICP Vortex SCSI RAID" (Jaak).......
Anyway, 7.04 was the driverpack version where things were starting to go wrong, so it might be the problem.
Greetz
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
7095 test version is available.
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
GROANS.... setup error on my second testrig (which has silicon chip inside).
Virtual PC and a socket 478 with extreme CPU machine showed nothing extrordinary, but silicon failed just the same.
back to the drawing board.
Last edited by Jaak (2007-10-05 16:40:06)
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
here was a bad experimental pack for silicon image.
it got reworked, and link is in a later post.
-----------------------------------------------------------
the TXTmode sections for silicon Image, (ONLY in the in the INI) have HWIDs tagged with &CC_0101 or &CC_0104
If this works, it means we do not have to edit the driver's INF files to tag the &CC_010x to the HWIDs.
If it doesn't, it doesn't.
I am not going to volunteer to change all those INF files each time there is an update.
BUT, if this does work, it could mean that we have a solution for the overlap in those PATA/SATA and RAID drivers.
@ stiertje,
The driver for bios 4.x.83 has been made to NOT load HWIDs which are supported in an older driver, because there is reason to believe the driver intended for an older BIOS works on a newer BIOS.
The driver for a newer BIOS was reported to NOT work on an older BIOS.
Last edited by Jaak (2007-10-05 16:39:15)
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
OOPS.
I tried it on a machine with some silicon image chip, and 7096 halted during setup.
testfile 7096 and the experimental (which was based on 7096) will be pulled.
testfile 7094 is back online
Last edited by Jaak (2007-10-01 11:11:25)
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: 3ware 9650SX support
Jaak, do you release an experimental pack (with HWIDs tagged with &CC_0101 or &CC_0104) again?
Another question: how I can to determine sata bios version? (for SiI chip)
- Jaak
- Old Timer Rookie
- Offline
Re: 3ware 9650SX support
yes, I will do a new EXPERIMENTAL with CC_010x tagged HW ids.
I look at the screens while the machine powers up, and hit pause.
(you most likely have to change a BIOS setting so that the screens show.)
I believe there is a tool to read BIOS version, but do not remember the topic.
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: 3ware 9650SX support
Debugger wrote:
Jaak, do you release an experimental pack (with HWIDs tagged with &CC_0101 or &CC_0104) again?
Another question: how I can to determine sata bios version? (for SiI chip)
You can find the BIOS version in the properties of the Silicon Image Controler, which you can find under "hardware manager - SCSI controlers"