[AlSar]

Hello there, MSFN!


I was surprised that you don't have a thread about AMD chipsets, which are rather widely spread.

I think this topic is important and should be sticked.

------------------

My question is the following:

I have ASUS N61Da notebook with AMD RS880M/SB850 chipset.

I need Windows XP to be installed on this notebook.

Default XP Professional SP3 does not install with BSOD appearing after install files are copied to the hard disk.

Of cource, the integration of SATA driver is needed.

The problem is - I can't find the proper driver anywhere.

All drivers I've seen are suitable only for SB7xx series or older, the newest I have found are for SB78x-SB79x chipsets.

Can anybody help with this?



Thanks a lot,

AlSar.

[Fernando 1]

Hello AISar,

welcome at MSFN Forums!

You have announced to offer a guide regarding the integration of AMD's AHCI and RAID drivers, but I cannot find it.
Why did you choose such topic title?

If you have a system with an AMD Southbridge and just want to get help with the integration of the AHCI or RAID driver, you may take a look into >this< thread.

Regards
Fernando

[AlSar]

2 Fernando:

I think that AMD chipsets are a major issue and they need to be discussed as widely as Intel or nVidia ones.


Intel and nVidia topics have a standard name here, so I thought that it'll be good for me to start such a topic with similar name which can become a great FAQ.

Unfortunately, I'm not a big specialist in this question and I can provide others only with basics of nLite, which everybody here knows.

Maybe some other person will take the interest and contribute the thread for other AMD users


Thanks for you link, but as you see, it's about SB7xx series and I'm afraid I won't get help here.

But I'll read this one.


And something more: if you look attentively, you'll see that the second letter in my nickname is not capital "I", but a simple "L" - "l".


AlSar.

This post has been edited by AlSar: 24 February 2011 - 11:49 AM

[cdob]

AlSar, on 24 February 2011 - 09:54 AM, said:

I can't find the proper driver anywhere.

Try Catalyst Raid Drivers\SBDrv\SB8xx\RAID\XP http://sites.amd.com...ed_xp-32.aspx#3

[Fernando 1]

AlSar, on 24 February 2011 - 11:45 AM, said:

I think that AMD chipsets are a major issue and they need to be discussed as widely as Intel or nVidia ones.
Intel and nVidia topics have a standard name here, so I thought that it'll be good for me to start such a topic with similar name which can become a great FAQ.
Maybe some other person will take the interest and contribute the thread for other AMD users

So you started this thread for somebody else? Why do you think, that such a person, who is willing to write a guide about the integration of the AMD textmode drivers, is not able to start such thread her/himself?
Many users of this Forum, who need help with the integration of the AMD textmode drivers and read the topic of this thread, will be very disappointed about what you are offering within your start post.

So I think, that a change of the topic title of this thread will be much appreciated by all Forum users. You can easily do it by hitting the "Edit" and then the "Use Full Editor" button of your start post.

Regards
Fernando

[pluto2011]

I'm using a Intel-SSD (newest firmware) in a MSI-notebook with ID1510-mainboard and sb850-southbridge. I tried activating AHCI for WinXP with many different driver versions but up to now without success (BSODs after switching BIOS from IDE to AHCI-mode).

I posted a thread on MSI-forum documenting my steps but got no help. MSI-AHCI/WinXP-Thread.

XP-drivers I tried:

ahcix86.sys Version:

3.2.1548.37 (march 2010, "fernando-mod"-driver from >here<)
3.2.1540.75 (june 2010, taken from lenovo-website - name: "AMD AHCI Compatible RAID Driver for floppy installation")
3.2.1540.92 (sep 2010, from an amd-catalyst-driver called "11-3_xp32-64_raid")
3.3.1540.13 (march 2011, taken from newest catalyst-driver "11-5_xp32-64_raid")

Reg-file I used:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&cc_0106]
"Service"="ahcix86"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_00421B0A]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_00431B0A]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_0184107B]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_01FC1028]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_01FD1028]
"Service"="ahcix86"


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_02111025]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_02131025]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_02161025]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_021D1025]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_0611A0A0]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_0614A0A0]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_0FFF0FFF]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_100415BD]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_100515BD]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_101E1462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_10201462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_10221462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_10D11734]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_13E810CF]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_14F21043]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21231019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21241019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21341019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21351019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21361019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21411019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21421019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21811019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_21821019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_280A103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_2814103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_2A4E103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_2A51103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_2A89103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_3054103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_3055103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_305717AA]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_305817AA]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_30C2103C]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_43811002]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_43811019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_43811849]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_43821002]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_43821019]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_43821849]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_600E1695]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_600F1695]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_604C107B]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_6B311462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_6B321462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_71741462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_71751462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_72431462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_72441462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_72971462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_73261462]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_82311043]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_82321043]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#PCI\VEN_1002&DEV_4380&SUBSYS_81EF1043]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_B0031458]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_B0041458]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_B0051458]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4380&SUBSYS_D6028086]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4381&SUBSYS_43811002]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4391]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4392]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4393]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4392&CC_0104]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4391&CC_0106]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1002&DEV_4393&CC_0104]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1022&DEV_7802&CC_0104]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1022&DEV_7801&CC_0106]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#VEN_1022&DEV_7803&CC_0104]
"Service"="ahcix86"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86]
"Type"=dword:00000001
"Start"=dword:00000000
"Group"="SCSI miniport"
"ErrorControl"=dword:00000001
"ImagePath"="system32\\drivers\\ahcix86.sys"
"Tag"=dword:00000021
"DisplayName"="ATI AHCI Compatible RAID Controller"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface]
"5"=dword:0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface]
"1"=dword:0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface]
"2"=dword:0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\Device]
"NumberOfRequests"=dword:0x00000080

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Settings\CAM]
"EnableALPEDisableHotplug"=dword:0
"EnableCCC"=dword:1
"CCCTimeoutValue"=dword:10
"CCCCompletionValue"=dword:32
"NCQEnableDiskIDBits"=dword:0
"EnableHIPM"=dword:0
"EnableDIPM"=dword:0
"EnableHDDParking"=dword:0x00000001
"CAMTimeOutValue"=dword:0x00000005
"EnableAN"=dword:0x00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Enum]
"0"="PCI\\VEN_1002&DEV_4380&SUBSYS_82311043\\3&13c0b0c5&0&FA"
"Count"=dword:00000001
"NextInstance"=dword:00000001
 

Since the inf-files just add reg-entried in most cases, I just gathered the reg-keys from many inf-files and included them into my reg-file-version to raise the chance of success.

With nLite I tried three different drivers. One time the setup didn't find the hard disk. With driver no 2 and 3 (catalyst and fernando-mod) I got BSODs in textmode-setup when the message "starting windows" appears (after driver-copy).

Can somebody please help me finally integrating the right driver into XP. It can't be that difficult doing a manual driver installation. In worst case maybe even from outside (e.g. with a linux-boot-disk). It took me about three days up to now - I just wanna use my new notebook.

This post has been edited by pluto2011: 22 May 2011 - 11:25 AM

[pluto2011]

I think I found out how to convert a drivers .inf-file into a reg-file for manual driver-installation. Please take a look at the thread on MSI-Forum. Unfortunately I still didn't get AHCI to run. In the several ATI/AMD-Catalyst-packages are always the same AHCI/RAID-drivers.

The actual southbridge-version- and subversion-numbers are only viewable from within linux. In my case the reg-entries made by the inf-files of all tested xp-drivers doesn't match the new hardware. Propably they need to get modified manually, hence the self-made reg-file.

Please post here if other driver-downloads/versions are known. Up to now I found no running driver for the upcoming msi u270 with bios-upgrade and intel ssd. The included vista/win7-driver is using a sb7xx-driver. The built-in soutbridge is sb850. So...even more confusion.

This post has been edited by pluto2011: 24 May 2011 - 10:00 AM

[Sp0iLedBrAt]

There is a lot of content-specific information here, but yet, this being the nLite forum, let's just cover the standard questions:
1. Do you always start nLite with a fresh source (your Windows XP copied to your PC, manually or by nLite)?;
2. Do you integrate the AMD AHCI driver in TXT (text) mode? + which driver files are present in the folder (names, please);
3. Which system (OS) are you using when working with nLite?;
4. Can you please attach your Last Session.ini file (as written with large red letters at the top of this page)? It is located in the working folder with the source or in C:\Program Files\nLite\Presets

[pluto2011]

1) The XP-source was not fresh always. I don't remember it exactly. Maybe my first and my last attempt were from a clean source. In between are maybe one or two "unclean" attempts.

2)Yes, in nlite they get listed as text-mode-drivers. When booting from nlite-cd and watching carefully, they also appear at the bottom-line during driver-copy-process, at the beginning of the setup. Which folder are you talking about? The drivers source-folder? Always the same: ahcix86.sys, ahcix86.inf, ahcix86.cat. Sometimes there is also an .oem-file and/or an .exe- or .msi-installer (which don't work because it needs to get started from a catalyst installer).

Files in the lenovo-driver-folder from last attempt (ahci for sb850): ahcix86, ahcix86.cat, ahcix86.inf, ahcix86.msi, ahcix86.sys


3)Windows XP SP2

4) See attachment.

I always use the "offer repair"-option in nlite's unattended-options. So, no unattended setup. I hope this doesn't cause the problem since I really don't wanna reinstall XP. Actually this is the reason for my .reg-file-attempts - I wann install the driver manually.

Attached File(s)

•  Last Session.ini (17.05K)
  Number of downloads: 7

[Sp0iLedBrAt]

1. ALWAYS start with a fresh source. That will avoid some really unnecessary errors.
2. Good. Now, I don't know if you noticed in Fernando's packs, but there always has to be another file TXTSETUP.OEM in the folder with the other AHCI files. It doesn't get integrated, but it contains the info needed for a successful integration. If present in any driver, use it. Do you remember using it when you tried Fernando's modded drivers?
The Last Session.ini looks ok as to the integration of the driver.

[pluto2011]

I don't know if I tried fernandos drivers for a nLite-install anyway, since they are modified. I only tried them for manual installation. However, the last lines of his .oem-file read:

id = "PCI\VEN_1002&DEV_4380&SUBSYS_B0041458", "ahcix86"
id = "PCI\VEN_1002&DEV_4380&SUBSYS_B0051458", "ahcix86"
id = "PCI\VEN_1002&DEV_4380&SUBSYS_D6028086", "ahcix86"
id = "PCI\VEN_1002&DEV_4381&SUBSYS_43811002", "ahcix86"
id = "PCI\VEN_1002&DEV_4391", "ahcix86"
id = "PCI\VEN_1002&DEV_4392", "ahcix86"
id = "PCI\VEN_1002&DEV_4393", "ahcix86"

[Config.ahcix86]
value = "", Tag, REG_DWORD, 1

...meaning: The driver seems to work for cards until

id = "PCI\VEN_1002&DEV_4393", "ahcix86"

my ahci-controller has the number 4394. So even fernandos-version for nlite propably needs to get modified to set the correct reg-entries. The question remains if the driver does support my hardware at all. So when having the choice between modified and unmodified driver, I actually prefere the unmodified version. I still have an sb7xx-driver in version 3.1.1540.127. It doesn't come with an .oem-file. Do you think I should create one? In contrast, the newest drivers (for sb8xx) from radeon-page do have an oem-file and my hardware isn't listed as well. The win7-drivers included with my notebook are for sb7xx. The built-in southbridge is sb850. I know this from cpu-z-diagnostic-tool.

-------------

Update:

I just integrated fernandos-driver in nlite: By default nLite only shows *.inf-files. I typed in "*.*" manually an selected the .oem-file. nLite now is listing:

Provider: Unknown, Mode: TXT - Napa_i386_ahci8086, Type: unknown, Version: unknown, Date: unknown.

Is this correct?

This post has been edited by pluto2011: 26 May 2011 - 04:43 AM

[Sp0iLedBrAt]

Quote

I don't know if I tried fernandos drivers for a nLite-install anyway, since they are modified.

Silly me, I thought you had tried them all with nLite. At this point, I'd suggest you PM Fernando and ask him to take a look next time he's here. Also, if there is any SUBSYS version, you should also add that here.
If the device number is DEV_4394, then you can't use pretty much anything from the reg entries in post #6, since most refer to DEV_4380, and none to DEV_4394.

Cheers

[pluto2011]

My idea is to just install all driver-components manually, reboot, switch to AHCI in BIOS and let windows boot up.

This seems to work for others, as I red in several forums, e.g. here.

No matter if nLite-method or not, I need to customize some inf/oem/reg- files to work together with the right driver. So a good question is: What driver-versions are out there? Which southbridge-version should they support? The versions I tested, I listed in post #4.

[cdob]

pluto2011, on 26 May 2011 - 04:37 AM, said:

my ahci-controller has the number 4394.

http://pci-ids.ucw.cz/read/PC/1002
http://cateee.net/lk.../SATA_AHCI.html

Quote

vendor: 1002 ("ATI Technologies Inc"), device: 4394 ("SB700/SB800 SATA Controller [SATA and FC Enabled]")

Add 4394 to txtsetup.oem and ahcix86.inf and try ahcix86.sys 3.1.1540.127.
Integrate drivers to source XP and ignore driver singning.

Quote

My idea is to just install all driver-components manually, reboot, switch to AHCI in BIOS and let windows boot up.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&cc_0106]
"Service"="ahcix86"

from post #6 may match or not.
Does "SATA and FC Enabled" refers to AHCI compatibleID CC_0106?
Which compatibleID use your machine?

[pluto2011]

Wow. These links are...informative.

Quote

Does "SATA and FC Enabled" refers to AHCI compatibleID CC_0106?
Which compatibleID use your machine?

I don't understand your question. What are compatibleID and CC_0106? Do you mean subsystem? According to the linux-output my subsystem is 1462:1096.

The exact output of "lspci -vvnn" is reading this:

Quote

"00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4394] (rev 40) (prog-if 01 [AHCI 1.0])
Subsystem: Micro-Star International Co., Ltd. Device [1462:1096]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 96
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at f190 [size=8]
Region 1: I/O ports at f180 [size=4]
Region 2: I/O ports at f170 [size=8]
Region 3: I/O ports at f160 [size=4]
Region 4: I/O ports at f150 [size=16]
Region 5: Memory at feb4c000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [70] SATA HBA v1.0 InCfgSpace
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: ahci
Kernel modules: ahci"

[pluto2011]

This was the last .reg-file I did try:

AHCI-manual-injection-sb8xx.reg:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1002&dev_4394&subsys_14621096]
"Service"="ahcix86"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86]
"Type"=dword:00000001
"Start"=dword:00000000
"Group"="SCSI miniport"
"ErrorControl"=dword:00000001
"ImagePath"="system32\\drivers\\ahcix86.sys"
"tag"=dword:00000019
"DisplayName"="ATI AHCI Compatible RAID Controller"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface]
"5"=dword:1
"2"=dword:1
"1"=dword:1


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\Device]
"NumberOfRequests"=dword:80

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Settings\CAM]
"EnableALPEDisableHotplug"=dword:ffffffff
"EnableCCC"=dword:0
"CCCTimeoutValue"=dword:10
"CCCCompletionValue"=dword:32
"NCQEnableDiskIDBits"=dword:00000000
"EnableHIPM"=dword:ffffffff
"EnableDIPM"=dword:00000000
"EnableHDDParking"=dword:1
"CAMTimeOutValue"=dword:5
"EnableAN"=dword:1
"EnableAPS"=dword:0


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ahcix86\Enum]
"0"="PCI\\VEN_1002&DEV_4394&SUBSYS_14621096\\3&13c0b0c5&0&FA"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[cdob]

pluto2011, on 26 May 2011 - 12:43 PM, said:

00:11.0 SATA controller [0106]

This indicates CC_0106 and refers to AHCI mode.

pluto2011, on 26 May 2011 - 01:05 PM, said:

This was the last .reg-file I did try:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet

Do not mix ControlSet001 and CurrentControlSet.
ControlSet001 may map to CurrentControlSet or another number. Use CurrentControlSet at running windows always.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1002&dev_4394]
"Service"="ahcix86"

There is no need to use subsys at a SB800

And try ahcix86.sys 3.3.1540.13

This post has been edited by cdob: 26 May 2011 - 01:34 PM

[Sp0iLedBrAt]

Even this version 3.3.1540.13 doesn't have DEV_4394 in TXTSETUP.OEM or ahcix86.inf.

[cdob]

ftp://ftp.tyan.com/d....125_2k3_32.zip

txtsetup.oem

Quote

[HardwareIds.SCSI.oem]
id = "PCI\VEN_1002&DEV_4391&CC_0106", "amdsata"
id = "PCI\VEN_1002&DEV_4394&CC_0106", "amdsata

"
That's amdsata.sys.

[pluto2011]

Finally some change in situation: The drivers get recognized by windows when I right-click on a controller in device-Manager and choose "update driver". However, no matter which controller I choose, the system crashes with BSOD after reboot and changing to AHCI. Back in IDE-mode the system still crashes until I choose "use last known workig configuration". So it seems windows is using the driver but without success (in both modes). Could it be this is a Win2k3-driver and not one for XP?

This post has been edited by pluto2011: 27 May 2011 - 04:26 AM