It is a 2 Gigabyte USB and I am using Rufus 3.1.1320. I have been using the FAT format I will try FAT32

When I run Rufus it re-formats it as FAT and I get the same result. I am using a .img file for MS-DOS 6.22. The image file is 1.44mb which I believe is the source of the issue

OK I understand the problem now.

That is a 3 1⁄2-inch floppy disk image of MS-DOS 6.22, which has a capacity of 1.44MB and can only read FAT12 and FAT16 partitions.

I have just spent the last half hour trying to make a new 32GB MS-DOS bootable USB stick using FAT32 and have found another way (other than using Rufus with a 1.44MB floppy image).

I have supplied the HP USB Disk Storage Format Tool and the 3 required MS-DOS 7.1 files (which supports FAT32).

Just run the tool as Administrator (leave it on FAT32) and tick 'Create a DOS startup disk..' and browse to the MS-DOS folder.

Thank you so much! I will give it a go

Thank you so much - this worked for getting into MS DOS. Thought I would post my output from

go -r
 

:

MVF_MAG v1.0.0.2475
PACKAGE VERSION 2.3.0.1065
AUTOLOAD VERSION: 200018
LOADER VERSION: 21001008
BIOS VERSION: 1.0.0.1024
FIRMWARE VERSION: 2.3.0.1070
 
 

I then ran go -ra to backup my current image. I would like to confirm that you think the image you posted ImageA1 will work for my card with this additional information?

Actually one more question - really trying to do this right the first time - should I be using the files in BIOS_PG or UEFI_PG (in the upload you posted)?

Edit: I checked all four files against each other using vimdiff and they are identical it seems

When I run go -ra no file appears also

Okay I realized that what go -r is showing me is the *incoming* firmware/bios versions, etc, the ones I am going to install. go -r used to say Adapter_Count=0 but then I reseated the card, physically, went back into my bios and enabled the preboot splash screen, and now it properly reads out everything.

Weird, sadly my bios is already 1.0.0.1028 and my firmware is 2.3.0.1078. So I am getting hella blue screens of death with even the latest firmware etc.

So, just to try it, I replaced ImageA1.bin with your 1078 ImageA1 and ran the flasher, having backed up my image successfully. It said it wrote everything successfully and that the flash was successful, however when I rebooted the marvell splash screen didn't come up and now when I go back into ms-dos and run "go-r" it again says "Adapter Count = 0". I am not even sure I will be able to flash my backup in this state - have I bricked the card?

Was my mistake something to do with using the spilist.bin file you uploaded in that package alongside the 1078 image?

It sounds like the card is faulty if it is not being detected in BIOS every time the PC boots.

Did you buy the card new? Can you return it?

If mvf_mag can't see the SPI flash rom then you will need to use a programmer to flash the EEPROM.

Can you attach your backup so I can check if it is a complete image?

@chinobino sorry to bump an old thread. It's been a while since I've been on here, life and such ...

I'm trying to get this card working in unraid (it does work but only with VT-D / IOMMU disabled), but to no avail (iommu=pt command line parameter does not work either): https://www.sybausa.com/index.php?route=...product_id=1006 model SI-PEX40137. Seems to use the 9215 but I get messages: "No related flash info" when trying to backup the EEPROM with the packages you posted on the first page. I am using the MS-DOS packaged version you posted that works with FAT32 and USB.

Do you think a firmware update can even fix this? If so, any idea why it's not seeing the card? It seems like a kernel driver issue to me as Windows seems to boot it just fine with VT-D enabled.

Hi @nimaim I remember reading about Marvell controllers having issues with unraid here.

Although that was 5 years ago I presume the issue is still present going by what you've said, you still need to disable VT-D/IOMMU or use an older version of unraid that does not support IOMMU such as v5.

The Syba SI-PEX40137 is a special case chipset that utilises 2 x Marvell 9215 ICs connected via the ASMedia ASM1806 PCIe bridge, I would not recommend flashing the standard Marvell firmware for this card.

I read this thread (is this you?) and the advice given was to avoid PCIE x4 8 port Controllers and use an Intel RAID Expander RES2SV240 to save the hassle - it does however need a 4-pin molex to power it but I think it's a solid option.

Zitat von chinobino im Beitrag #43

---

Hi @nimaim I remember reading about Marvell controllers having issues with unraid here.

Although that was 5 years ago I presume the issue is still present going by what you've said, you still need to disable VT-D/IOMMU or use an older version of unraid that does not support IOMMU such as v5.

The Syba SI-PEX40137 is a special case chipset that utilises 2 x Marvell 9215 ICs connected via the ASMedia ASM1806 PCIe bridge, I would not recommend flashing the standard Marvell firmware for this card.

I read this thread (is this you?) and the advice given was to avoid PCIE x4 8 port Controllers and use an Intel RAID Expander RES2SV240 to save the hassle - it does however need a 4-pin molex to power it but I think it's a solid option.

---