I would like to try to add an entry to the simple.map.

When I ask the ESXi for the Device ID I get this:

05:13.00 RAID bus controller Mass storage controller: CMD Technology Inc SiI 3124 PCI-X Serial ATA Controller Class 0104: 1095:3124

Means my device ID is "1095:3124"

I overwrote one line and now I have "1095:3124 0000:0000 storage sata_sil24.o" there. Currently I can't reboot the server but I will do that later on.

If this is not working, I'll try to refer to the driver directly.

Thanks!

Big thanks to neutralspark and Dave.Mishchenko!!

My sata controller card is now recognized by ESXi very well. First I did the mistake and used 7zip and Notepad++ under Windows and edit the simple.map. After the reboot I always ran into a pink screen error

I got this working with an ubuntu live cd, downloaded and edited the simple.map file under this linux again, did the reboot and the sun was shinning again

Hi,

Can you help me build a driver for Supermicro AOC-SASLP-MV8? It uses Marvell 88SE6480 chipset. I have identified vendor id and device id as 11ab:6485. But I have no idea how to build the driver.

Thanks.

Sadly that chipset isn't supported by the Linux 2.6.20.24 sata_mv.o drivers, so support won't be forthcoming very quickly.

I saw that there is a folder on Linux 2.6.34.1 (drivers\scsi\mvsas) which seems to be the driver for this model but I don't know how to build them for esxi. Any suggestion?

If you look here - http://www.kernelcrash.com/blog/using-a ... 009/08/22/ - and the 3.5 page he mentions you'll get an idea of what's required to compile a driver for ESXi.

Similar to what cyntaxx, mentioned in his previous post, about not seeing the drive in VI client.

i am experiencing the same issue with the Sil3132 SATA PCIe card the OP reported working.

I was able to use his oem.tgz to load it on my ESXi 3.5 U4.

>lspci -p
Bus:Sl.F Vend:Dvid Subv:Subd ISA/irq/Vec P M Module Name
Spawned bus
00:00.00 8086:2588 1028:0180 V
00:01.00 8086:2589 0000:0000 11/ 11/0x71 A V
00:02.00 8086:258a 1028:0180 11/ / A V
00:28.00 8086:2660 0000:0000 11/ 11/0x71 A V
00:28.01 8086:2662 0000:0000 10/ 10/0x79 B V
00:29.00 8086:2658 1028:0180 9/ 9/0x81 A V usb-uhci
00:29.01 8086:2659 1028:0180 5/ 5/0x89 B V usb-uhci
00:29.02 8086:265a 1028:0180 3/ 3/0x91 C V usb-uhci
00:29.03 8086:265b 1028:0180 10/ 10/0x99 D V usb-uhci
00:29.07 8086:265c 1028:0180 9/ 9/0x81 A V ehci-hcd
00:30.00 8086:244e 0000:0000 004 V
00:31.00 8086:2640 0000:0000 V
00:31.01 8086:266f 1028:0180 11/ 11/0x71 A V vmhba0
00:31.02 8086:2652 8086:2652 5/ 5/0xa1 C V ata_piix vmhba1
00:31.03 8086:266a 1028:0180 10/ / B V
02:00.00 14e4:1677 1028:0180 11/ 11/0x71 A V tg3 vmnic0
03:00.00 1095:3132 1095:7132 10/ 10/0x79 A V vmhba2
04:00.00 9005:0285 1028:0291 11/ 11/0x71 A V vmhba3
04:01.00 1102:0004 1102:2002 10/ 10/0x79 A V
04:01.01 1102:7003 1102:0040 V
04:01.02 1102:4001 1102:0010 3/ 3/0x91 B V
04:02.00 10b7:9055 10b7:9055 3/ 3/0x91 A V


>lspci -v
03:00.00 RAID bus controller Mass storage controller: CMD Technology Inc SiI 3132 Serial ATA Raid II Controller [vmhba2]
Class 0104: 1095:3132

04:00.00 RAID bus controller Mass storage controller: Adaptec Adaptec SCSI [vmhba3]
Class 0104: 9005:0285

-So if the driver is detected. Why isnt it detected in the Storage Adapter list in VI client? I mean the output of lspci -p reports vmhba2. But that isnt reported in VI client.

Heres the simple.map from the OP.
1095:3132 0000:0000 storage sata_sil24.o

heres the:
pci.ids

3124 SiI 3124 PCI-X Serial ATA Controller
1095 3124 SiI 3124 PCI-X Serial ATA Controller
3132 SiI 3132 Serial ATA Raid II Controller
0242 SiI 3132 Serial ATA Raid II Controller (Adaptec-branded)


Thanks

Should this driver support port multiplier boxes?
I have managed to get it to install fine - but it does not seem to work with a couple of port multiplier boxes I have.

Thanks!
T

Thanks neuralspark for the HighPoint RocketRAID 2310 PCIe driver. I was able to copy the oem.tgz file over as oem2.tgz and modify the boot.cfg to load that file and now the server sees the controller with drives. Thanks again!

anybody able to speak to this? also, i know that these discussions have been geared towards esxi; will it work on straight esx?

thanks!

wally