Solved Ahci

[seekermeister]

You are right in that an additional set of devices appear in IDE ATA/ATAPI Controllers with the Windows driver being used, but the nomenclature says nothing about it having anything to do with the Marvell Controller. Can I safely consider that it is the Marvel Controller that does appear there in a rather anonymous fashion?

 

[GeneO]

You are right in that an additional set of devices appear in IDE ATA/ATAPI Controllers with the Windows driver being used, but the nomenclature says nothing about it having anything to do with the Marvell Controller. Can I safely consider that it is the Marvel Controller that does appear there in a rather anonymous fashion?

Yes

 

[seekermeister]

Now this is really starting to make me feel foolish. I attempted to revert back to using the Windows driver by following what I had posted in Post #26, but after uninstalling the Marvell controller from the Device Manager, and rebooting, it did say that Windows was installing a driver for it, but checking in the Device Manager and in Devices And Printers, it appeared that it simply reinstalled the Marvell driver that I had just uninstalled. I searched for other means to uninstall the driver, but found nothing except the ATI Install Manager, which does have an uninstall function, but after it scanned, it listed nothing except the USB Filter driver. My scalp isn't itching, but I'm still scratching it a lot.

 

[GeneO]

If this is your boot drive, be careful in what I suggest here. First, try uninstalling the Marvell drivers from Programs and features in the control panel and reboot. If that doesn;t work or there is no Marvell software listed, then uninstall the Marvell driver from the device manager, making sure you check "uninstall software", then reboot. If you had a previous version of the Marvell driver, you may need to do this more than once. Unless you uninstall the Marvell software, it will use the Marvell driver. been there, done that

Reason I say be careful is once I ended up in the state boot was looking for the Marvell .sys driver and wouldn't boot.

 

[seekermeister]

You are right on target. Once you mentioned it, I remembered that is how I uninstalled the Marvell driver previously. Now it is back to the Windows driver state, and now I must decide whether to do the registry edit mentioned in your link.

 

[GeneO]

I did (regedit) because I had the same problem. Now I only use My Marvell (the SATA3 xx23 series) for DVD drives since it performs worse overall than my Intel SATA2 for my SSD.

 

[seekermeister]

I did (regedit) because I had the same problem. Now I only use My Marvell (the SATA3 xx23 series) for DVD drives since it performs worse overall than my Intel SATA2 for my SSD.

Considering the remarkable clarity of your previous posts, I'm puzzled by this one. Your phraseology leaves me guessing as to what you meant to say?

Another thing that makes me hesitate, is that the article in your link speaks of identifying the port or channel of the AHCI drive, which on the surface seems easy enough, but it also says that the number used in the registry is not necessarily the same as that used in the Device Manager. How can one be certain if they have used the right value?

EDIT: After rereading your last post a couple of times, I can now see that I wasn't reading it correctly. It kind of threw me when you spoke of DVD drives. I didn't know that they are connected to these controllers. Thought that only hard drives or SSDs would be.

 

[GeneO]

I did (regedit) because I had the same problem. Now I only use My Marvell (the SATA3 xx23 series) for DVD drives since it performs worse overall than my Intel SATA2 for my SSD.

Considering the remarkable clarity of your previous posts, I'm puzzled by this one. Your phraseology leaves me guessing as to what you meant to say?

Another thing that makes me hesitate, is that the article in your link speaks of identifying the port or channel of the AHCI drive, which on the surface seems easy enough, but it also says that the number used in the registry is not necessarily the same as that used in the Device Manager. How can one be certain if they have used the right value?

EDIT: After rereading your last post a couple of times, I can now see that I wasn't reading it correctly. It kind of threw me when you spoke of DVD drives. I didn't know that they are connected to these controllers. Thought that only hard drives or SSDs would be.

Yes, I have SATA DVD. I prefer my hard drives and SSD be on the Intel chipset SATA controller.

Well if you get the wrong one you can always change it. They don't change over time

In fact, you should be able to tell under the device manager -> IDE ATA/ATAPI controllers -> ATA Channel N -> Advanced Settings what drive is in channel N, if any. Also you can look at the drive properties to see which channel.

 

[seekermeister]

That sounds easy enough, but when I went through the list of channels, only 3 of them listed any devices, but for the ones listing hard drives, they all used the same ID...ATA Disk #1, operating under DMA Mode 6. Since I have 3 internal hard drives connected, how do I know which is which?

 

[GeneO]

Under device Manager -> disk drives if you click on a disk drive's properties tit doesn't show the channel under "Location: ..."?

 

[seekermeister]

Isn't that what is shown is the second screenshot above? My problem with that is since there are four controllers (not numbered), and each of them has a channel 0 and channel 1, the term "location 0" seems ambiguous to me, because there are 4 channel 0s, so what is location 0?

 

[GeneO]

Well, I guess I thought you knew which drives were plugged into which controller. I only have two channels on the Marvell, and that is the only controller I use the generic MS AHCI driver on so I guess it is easy for me to tell

 

[seekermeister]

I would imagine that my system would be easy for you to figure out, but my mind just doesn't work that way. Yes, I know which controller the AHCI drive is plugged into...the Marvell. Going by what you said previously, the Standard AHCI 1.0 Serial ATA Controller listed in the Device Manager must be the Marvell. However, when I select the properties of that controller, the location is given as PCI bus 1, device 0, function 0, which does not seem to correlate with the location given for the drive itself...Location 0 (Channel 1, Target 0, Lun 0). Perhaps this makes sense to you, but not I.

 

[GeneO]

What can I say? When you get down to the level of users being able to easily determine what ports disk drives or USB devices are attached to, Windows 7 kinda fall apart.

 

[seekermeister]

Okay, if I must experiment I will, but how does one know when it is right? I don't think that it will have any effect on performance...will it? Outside of it no longer displaying the drive in Devices And Printers, is there anything else to look for?

 

[GeneO]

Not to my knowledge.

 

[seekermeister]

I just ran the two regedits in the article linked, and the drive no longer appears in Devices And Printers, and the Standard AHCI 1.0 controller remains in IDE ATA/ATAPI controllers as before, so I guess this chore is now complete. Thanks again.