<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[DriverPacks.net Forum - Intel DQ965GF Chipset & Marvell 61xx Marvell RAID Controller]]></title>
		<link>http://forum.driverpacks.net/viewtopic.php?id=1990</link>
		<description><![CDATA[The most recent posts in Intel DQ965GF Chipset & Marvell 61xx Marvell RAID Controller.]]></description>
		<lastBuildDate>Mon, 10 Sep 2007 16:31:02 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Intel DQ965GF Chipset & Marvell 61xx Marvell RAID Controller]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=14273#p14273</link>
			<description><![CDATA[<p>hi<br />the marvell drivers do not have that detail in the driver, which makes them somewhat &quot;generic&quot; ???<br />They also do NOT have subsys information, which makes them more than &quot;somewhat&quot; generic.</p><p>But, the CC_010* entries do show in other driver INFs, and driver&#039;s INF have details on AHCI or RAID.</p><p>in the past, I have removed generic INTEL HWID from an adaptec card driver which had specifics for the adaptec.<br />In this Marvel case, they are all generic. <br />Your solution works, and I doubt we can do little to fix it.</p><p>what you could perhaps also do is this.<br />If the intel is newer, edit the INTEL driver for this (adding specific HWID to it so it wins).<br />If it is older, I am afraid a newer generic will win.</p>]]></description>
			<author><![CDATA[null@example.com (Jaak)]]></author>
			<pubDate>Mon, 10 Sep 2007 16:31:02 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=14273#p14273</guid>
		</item>
		<item>
			<title><![CDATA[Re: Intel DQ965GF Chipset & Marvell 61xx Marvell RAID Controller]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=14266#p14266</link>
			<description><![CDATA[<p>The ID&#039;s in the first post were lifted from BÃ¢shrat the Sneaky&#039;s save_hwids batch file, and from the DPsFnshr.log file on the machine.<br />When building the machines, Windows always picks up the IDE controller as Marvell 61xx RAID controller. This stops Windows from burning CD&#039;s/DVD&#039;s.<br />Can you point me to where I can find the detail which includes the CC_0104 or CC_0101 entry?</p>]]></description>
			<author><![CDATA[null@example.com (tazmaniandevil)]]></author>
			<pubDate>Mon, 10 Sep 2007 11:53:00 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=14266#p14266</guid>
		</item>
		<item>
			<title><![CDATA[Re: Intel DQ965GF Chipset & Marvell 61xx Marvell RAID Controller]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=14263#p14263</link>
			<description><![CDATA[<p>tazmaniandevil<br />The Class ID&#039;s for RAID, AHCI and for IDE are different:<br />CC_0101 - IDE<br />CC_0104 - RAID<br />CC_0106 - AHCI.</p><p>So, Ven ID&#039;s for Marvell are:<br />PCI\VEN_11AB&amp;DEV_6101&amp;SUBSYS_610111AB&amp;CC_0104 - RAID<br />PCI\VEN_11AB&amp;DEV_6101&amp;SUBSYS_610111AB&amp;CC_0101 - IDE</p>]]></description>
			<author><![CDATA[null@example.com (Debugger)]]></author>
			<pubDate>Mon, 10 Sep 2007 10:19:18 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=14263#p14263</guid>
		</item>
		<item>
			<title><![CDATA[Intel DQ965GF Chipset & Marvell 61xx Marvell RAID Controller]]></title>
			<link>http://forum.driverpacks.net/viewtopic.php?pid=14261#p14261</link>
			<description><![CDATA[<p>Well done Intel. </p><p>The Ven ID for this chipset is <br />PCI\VEN_11AB&amp;DEV_6101&amp;SUBSYS_610111AB&amp;REV_B1\4&amp;AB208E&amp;0&amp;00E1: Standard Dual Channel PCI IDE Controller</p><p>The Ven ID for the Marvell 61xx Raid controller is <br />PCI\VEN_11AB&amp;DEV_6101&amp;SUBSYS_610111AB&amp;REV_B1\4&amp;AB208E&amp;0&amp;00E1: Marvell 61xx Marvell RAID Controller</p><br /><p>This itself is not a huge problem, the mainboard will work correctly. Our latest systems however have a SH-S182D dual layer DVD/RW-DVD Ram drive, which will not burn anything if Plug &#039;n Pray picks up the Marvell driver as the best match for the hardware. My workaround for this was to remove the Marvell driver from the driverpack, as we don&#039;t have any mobos on site with this RAID controller.</p><p>Are we the only users with this combination of hardware? <br /><strong>Edit:</strong> Hardware vendor is blaming driverpacks, which IMO are not the problem</p>]]></description>
			<author><![CDATA[null@example.com (tazmaniandevil)]]></author>
			<pubDate>Mon, 10 Sep 2007 09:09:08 +0000</pubDate>
			<guid>http://forum.driverpacks.net/viewtopic.php?pid=14261#p14261</guid>
		</item>
	</channel>
</rss>
