 
|
 |
|
Member |
 |
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
Croatia |
|
Posted:11/24/2010 11:34:00 PM |
|
| Very strange issue: P6X58D-E has 9128 Marvell controller (and it is on motherboard-checked!), but SATA3 Marvell BIOS indicates:
Vendor ID: 1B4B
Device ID: 9123
Revision ID: B1
BIOS version: 1.0.0.1019
Firmware version: 2.1.0.1413
When I try to flash a new firmware from http://www.station-drivers.com/page/marvell.htm flash tool says: “BIOS header and device ID don’t match!”, also “Incoming BIOS header is 0x91a3, current BIOS header is 0x9123”. It says that flashing is successful , but old version of BIOS and firmware version remains.
I don’t understand this!!! I know I have 9128, but BIOS and Device Manager indicates that 9123 is on motherboard. Please HELP!!!
|
|
|
|
Moderator |
 |
| Posts
:
95428 |
| Level
:
|
| Tech Points
:
20250 |
| From:
United States |
|
|
Posted:11/25/2010 12:47:00 AM |
|
Hi B..
The schematic that I have for that board shows an 88SE9123 controller....
|
|
|
| There are 10 kinds of people in the World...Those who understand binary, and those who dont! |
|
Member |
|
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
Croatia |
|
|
Posted:11/25/2010 1:20:00 AM |
|
| Thanks for replay Ulrich!
No, P6X68D-E has 88SE9128 (P6X68D-Premium version has 88SE9123). This says manual of this motherboard. Also, I found controller on motherboard, it has label 88SE9128. Every information about this board on internet (check it, please), and my eye view of controller give 100% correct information about it. But, Marvell BIOS says it is 88SE9123. Strange, isn't it!!!
I am confused!!!
|
|
|
|
Moderator |
 |
| Posts
:
10077 |
| Level
:
|
| Tech Points
:
10861 |
| From:
Sweden |
|
|
Posted:11/25/2010 2:07:00 AM |
|
Hi BobyOS.
Your motherboard, P6X58D-E, has the 88SE9128 controller, no question about it.
Perhaps you can contact Marvell to sort out the problem, and let us know how it goes.
I previously thought that the fact that the wrong Device Id was reported, was due to the fact that the 9123 and 9128 controllers share the same driver packet, and that the wrong Device Id not really mattered.
Apperently that is not the case.
|
|
|
| ASUS Z97-WS (BIOS 2704) -- Intel i7-4790K -- Noctua NH-U14S -- 16GB (2x8GB) Corsair Vengeance Pro 1866MHz 9-10-9-27 2T 1.5V -- iGPU -- System drive: Samsung 950 PRO (NVMe) 256GB on Hyper M.2 x4 Mini card -- storage RAID 0 on 2x120GB Intel SSD 520 (6Gbs), storage on RAID 1, 2x250GB/16MB Seagate Barracuda 7200.10 SATA2, additional storage 1x250GB/16MB -- DVD-RW ASUS DRW-24F1ST -- all storage drives on Intel Z97 controller -- Antec P180B -- Corsair HX750 PSU -- Windows 10 PRO x64 1607,14393.447 in UEFI mode -- Chipset Device Software 10.1.1.14 -- IRST 14.8.0.1042, 950 PRO M.2 SSD and storage SSDs and HDDs all GPT partition formatted -- IE11 |
|
Member |
|
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
Croatia |
|
|
Posted:11/25/2010 3:09:00 AM |
|
| Hi Hiker.
The reason that first I put the post here is my opinion of the problem and that is: BIOS of Marvell controller is in EEPROM memory beside the 88SE9128 controller, which I recognize at the motherboard. The Marvell firmware is a part of the main motherboard’s BIOS. I think this is not a problem of Marvell flashing software, but the ASUS motherboard BIOS problem (of course, I could be wrong). After post here, I will check this out with Marvell.
Does anyone who has this motherboard reads the same Marvell controller information’s as I do (with Ctrl+M )!?
|
|
|
|
Moderator |
|
| Posts
:
95428 |
| Level
:
|
| Tech Points
:
20250 |
| From:
United States |
|
|
Posted:11/25/2010 5:31:00 AM |
|
Quote:
Author: Posted: 11/25/2010 1:20:00 AM
Thanks for replay Ulrich! No, P6X68D-E has 88SE9128 (P6X68D-Premium version has 88SE9123). This says manual of this motherboard. Also, I found controller on motherboard, it has label 88SE9128. Every information about this board on internet (check it, please), and my eye view of controller give 100% correct information about it. But, Marvell BIOS says it is 88SE9123. Strange, isn't it!!! I am confused!!! |
Hi B..
The IC that is on your board is an 88SE9128... you can see that printed right on the chip. Asus used the 9123 for some time on these boards but with problems and it was changed.
The VEN number in your operating system registry should list the part...
HKey_Local_Machine, System, CurrentControlSet, Enum, PCI
You should see a listing of VEN identifiers.. and if you expand each one, one at a time, and highlight what you get after the expansion, you should be able to find the controller... and find out how the system identifies it.
|
|
|
| There are 10 kinds of people in the World...Those who understand binary, and those who dont! |
|
Member |
|
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
Croatia |
|
|
Posted:11/25/2010 10:09:00 PM |
|
| I'm almost 100% certain about what is the problem !? The problem is with some motherboard’s revision’s, where the EEPROM memory (I2C, or SPI) which is put on the board to “explain” OS which SATA controller is there (in this case wrong VEN_1B4B&DEV_9123), also includes BIOS ver 1.0.0.1019, has a wrong data about it. The Asus itself must solve this problem, the Marvell firmware upgrade gets information’s about which controller you have on motherboard. The same issue as LCD monitor tells OS its name (it has small EEPROM at input cable). The name is wrong!!! And Marvell flashing software can ‘t change vendor and device ID, because it was “explained” by ASUS motherboard. The new 0405 BIOS didn’t solve the problem, also. Because this problem is not common with all P6X68D-E boards (other way, all people would write about it), I have this revision with “wrong” SATA controller. But, the solution I don’t know, without ASUS. Of course, I could be wrong (hopefully). Thanks again Ulrich and Hiker!!!
|
|
|
|
Moderator |
|
| Posts
:
10077 |
| Level
:
|
| Tech Points
:
10861 |
| From:
Sweden |
|
|
Posted:11/26/2010 7:14:00 AM |
|
Hi BobyOS.
This is messy!
I look at http://www.station-drivers.com/page/marvell.htm at the bottom of the page, and I see this update for Marvell 9123/9128:
Driver 9123/9128: 1.0.00.1047
Firmware: 1.0.0.1407 & 2.1.0.1504
mvflash: 1.0.0.2429
HostBIOS: 1.0.0.1027
There is also a modded version (undocumented) of the firmware update (1.0.0.1407/2) & (2.1.0.1504/1).
If it's at all possible to get the identification correct, 9123 => 9128, perhaps an engineering version of the flash tool is required, a version that ignores the chips id, and just updates the firmware.
Someone at ASUS or Marvell must be able to clarify this!
|
|
|
| ASUS Z97-WS (BIOS 2704) -- Intel i7-4790K -- Noctua NH-U14S -- 16GB (2x8GB) Corsair Vengeance Pro 1866MHz 9-10-9-27 2T 1.5V -- iGPU -- System drive: Samsung 950 PRO (NVMe) 256GB on Hyper M.2 x4 Mini card -- storage RAID 0 on 2x120GB Intel SSD 520 (6Gbs), storage on RAID 1, 2x250GB/16MB Seagate Barracuda 7200.10 SATA2, additional storage 1x250GB/16MB -- DVD-RW ASUS DRW-24F1ST -- all storage drives on Intel Z97 controller -- Antec P180B -- Corsair HX750 PSU -- Windows 10 PRO x64 1607,14393.447 in UEFI mode -- Chipset Device Software 10.1.1.14 -- IRST 14.8.0.1042, 950 PRO M.2 SSD and storage SSDs and HDDs all GPT partition formatted -- IE11 |
|
Member |
|
| Posts
:
4 |
| Level
:
|
| Tech Points
:
2 |
| From:
Canada |
|
|
Posted:1/7/2011 5:19:00 AM |
|
| You're right BobyOS. I have the same issue with my recent Rampage III Formula.
Marvell bios window (ctrl+m): Device Id 9123 instead of 9128
Waiting for a new Asus bios to fix that.
|
|
|
|
VIP Member |
|
| Posts
:
215 |
| Level
:
|
| Tech Points
:
231 |
| From:
United States |
|
|
Posted:1/7/2011 9:08:00 PM |
|
I have also started a thread about this issue a while ago. I can confirm through device manager/Hardware ID and the registry entries mentioned above the device id is 9123.
|
|
|
| Z87-PRO / i7-4770K 4.3 GHz / NH-D14 / 4x4GB G.Skill 1600 / OCZ Vector / OCZ Vertex 4 256 SSD / EVGA GTX 670 / OCZ ZX850 / X-Fi Titanium Fatal1ty Professional Series / LG DVD/Blu-ray / PB278Q / Logitech G700 and G110 / HAF X / Win7 Professional x64 SP1 |
|
|
|
|
|
|