Jump to content
XPEnology Community

flaky

Rookie
  • Posts

    3
  • Joined

  • Last visited

Posts posted by flaky

  1. 5 hours ago, pocopico said:

    Which platform are you building ? 

    DS3622xs+

    Motherboard: Supermicro X11SRM-VF

    CPU: 8core/8thread

    RAM: 128GB ECC

    HBA: LSI SAS3224

    Network: connectx-3

     

     

    I also tried ESXI with this guide

    VM boots and can install DSM with one virtual disk, but as soon as I add either one of the PCIE passthrough device (SAS3224 or connectx-3), it automatically shutdown.

     

    I see that during builds the ./rploader found driver for both devices.

     

    Here is my config:

    {
      "extra_cmdline": {
        "pid": "removed",
        "vid": "removed",
        "sn": "removed",
        "netif_num": "2",
        "mac1": "removed",
        "mac2": "removed",
        "SataPortMap": "11",
        "DiskIdxMap": "1000"
      },
      "synoinfo": {
        "internalportcfg": "0xffff",
        "maxdisks": "16",
        "support_bde_internal_10g": "no",
        "support_disk_compatibility": "no",
        "support_memory_compatibility": "no"
      },
      "ramdisk_copy": {}
    }

  2. Hi,

     

    I did a baremetal install with RedPill TinyCore loader. The installation finishes smoothly, DSM prompted reboots. Upon reboots, RPTC boots from usb, then after a while, the machine automatically shutdown. Any idea? I suspects it's a crash/kernel panic? Any log that I can look into? Thanks.

  3. On 12/4/2017 at 1:10 PM, IG-88 said:

    the chip on this is SAS3416, the driver for this chip would be mpt3sas

    916+ loader does not have this driver (for now)

     

    for testing i would use a system with a ahci sata and a single drive on that to install dsm, the controller would be just in its slot to see if the driver loads correctly (/var/log/...)

    as the chip seems to be newer and the kernel and mpt* divers in it are kind of old there is a good chance it will not work, in the kernel 3.10.102 (base of dsm 6.1) there is no controller id for this one, the newest in "our" kernel seems to be 0097

     

    
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 0094 ("SAS3108 PCI-Express Fusion-MPT SAS-3")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 0095 ("SAS3108 PCI-Express Fusion-MPT SAS-3")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 0096 ("SAS3004 PCI-Express Fusion-MPT SAS-3")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 0097 ("SAS3008 PCI-Express Fusion-MPT SAS-3")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 00aa
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 00ab ("SAS3516 Fusion-MPT Tri-Mode RAID On Chip (ROC)")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 00ac ("SAS3416 Fusion-MPT Tri-Mode I/O Controller Chip (IOC)")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 00ad
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 00ae ("SAS3508 Fusion-MPT Tri-Mode RAID On Chip (ROC)")
    vendor: 1000 ("LSI Logic / Symbios Logic"), device: 00af ("SAS3408 Fusion-MPT Tri-Mode I/O Controller Chip (IOC)")

     

    broadcom provides driver source and as i was already testing new mpt* drivers for the 916+ image i downloaded and compiled it

    driver builds and can be loaded in a vm, i expect it will do the same on 3615 and 3617

    PM me if you need a test-extra.lzma for this card and for what loader you want it

     

     

    Hi,

     

    Do you have a test driver for the chip SAS3416? I have a 9400-16i card that does not boot. I have tried your extra.lzma for ds3615 v4.8 but did not work.

     

    I am using Jun 1.02b loader for 3615xs model. Thank you.

     

    Sam

×
×
  • Create New...