Hi,

When I remove the card the system is working normally.

Sounds like the card may be faulty.

You mentioned that it wasn't working well in the first post, did it ever work properly?

Have you installed the latest Marvell Drivers? (1.2.0.1049)

Hello,
The card was working normally on my PC under intel

The problem is post-boot not related to Windows.

I do not think it's defective.

Go RMA to amazon (guarantee)

Sounds like a good idea.

I hope the replacement works like it should.

Its work !

Excellent!

Thanks for reporting back.

Hi @chinobino, I have a Marvell Sata 88SE9215 Chip Revision 11 (hence A1) that has been causing blue screens of death for my PC. I am using the latest drivers from station-drivers now, 1.2.0.1049 which is working better, but I still get the occasional BSOD and I am hoping that updating the firmware for the device will help. What you post above is for the 9230 correct? Will it work for 9215?

@lontanadascienza Yes it will work with the 9215.

Great thank you. I am having some trouble figuring out how to actually run the go.bat script however. My computer is 64bit, so it can't run the 16bit executable. I managed to create an MS DOS bootable usb stick, but then that can't see any of my hard drives (I guess because they are using SATA?). I'm sure I'm missing something stupid - how should I proceed?

Thanks!

@lontanadascienza

I would recommend to backup the existing firmware with the 'go -ra' command before you update to the newer firmware.

You should copy the go.bat script and the bin folder (it should contains three files; mvf_mag.exe, spilist.bin and the new firmware e.g ImageA1.bin) to the USB stick and update the card from MS DOS command line using the command 'go -v'

I uploaded the tool with the bin folder here if you need it - the tool comes with firmware 2.3.0.1070 so you will need to replace it with 2.3.0.1078 that I uploaded here.

Note that go.bat has been written for the 9230 (set hba_id=9230) so you will need to edit it in a text editor for the 9215 (i.e. set hba_id=9215).

You won't be able to see your hard drives from MS DOS as it doesn't have the required SATA controller driver.

The issue is I can't copy things to the USB because once I put MS-DOS 6.22 on it, it thinks it only has 1.44mb of space or something like that - so the files are too big. I've never made/had to use a DOS usb stick so maybe I am doing something very silly.


Edit: Are we certain that FreeDOS doesn't work? It seems like a much easier proposition.

You need to copy the files to the USB stick from Windows.

MS-DOS 6.22 is limited to 8 character folder/file name length.

If you type in dir /p you can see how your folder directory names are truncated (The switch /p views the directories one 'page' i.e screen at a time).

I don't think it's a naming issue it's a size issue. The properties of the drive say that its capacity is 1.44mb after flashing ms dos 6.22 using rufus. When I try to drag and drop the files in it says additional space needed.

What capacity is the USB flash drive? It is recommended to use FAT32 file system with a USB stick that is 32 GB or smaller.

What version of Rufus are you using?