Jump to content
XPEnology Community

Search the Community

Showing results for tags 'sa6400'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 1 result

  1. @pocopico, @fbelavenuto It seems that you have selected the SA6400 as the test target model based on the current kernel 5.X. It is still known as ongoing. I think that solving the following SA3600 issues in advance will help develop the SA6400 as well. I'd like to find out what the SA3600 and SA6400 have in common and talk about future development of the SA6400 in this thread. I recently added the SA3600 based on the broadwellnk platform as a TCRP model by user request. As characteristic of broadwellnk, Device-tree is not used, RS B. Like the characteristics of the SA platform, it seems that the Marvel controller is not used as a virtual HBA. chatGPT's answer may not be accurate, but I referred to the following. [keyword : synology sa3600 dtb] The Synology SA3600 is a high-performance storage system designed for enterprise-level use. DTB (Device Tree Blob) is a binary file that contains the device tree data for a hardware device. It is used by the Linux kernel to identify and configure hardware devices during the boot process. The Synology SA3600 does not require a DTB file to operate, as it comes with its own customized Linux-based operating system that is pre-installed on the system. Therefore, you do not need to worry about the DTB file if you are using the Synology SA3600. However, if you are using a different hardware device that requires a DTB file, you may need to obtain the correct DTB file for that device and configure it properly in order for the device to function correctly with the Linux kernel. The process for obtaining and configuring a DTB file can vary depending on the specific device and operating system being used. [keyword : synology sa3600 virtual Marvell 88SE9235] I'm not sure I understand your question correctly. If you're asking about whether the Synology SA3600 can run virtual machines (VMs) using the Marvell 88SE9235 controller, then the answer is no. Also, I received an answer from chatGPT that sa3600 / sa6400 has a separate sas controller built in, but I can't find a history of answers related to this chipset. So, I modified platforms.h in the lkm of both models to refer to SA6400 as below. The only difference is is_dt, whether device tree is used or not. https://github.com/PeterSuh-Q3/redpill-lkm/blob/master/config/platforms.h#L299 { .name = "SA3600", .pci_stubs = { { .type = __VPD_TERMINATOR__ } }, .emulate_rtc = false, .swap_serial = false, .reinit_ttyS0 = true, .fix_disk_led_ctrl = true, .has_cpu_temp = true, .is_dt = false, .hwmon = { .sys_thermal = { HWMON_SYS_TZONE_REMOTE1_ID, HWMON_SYS_TZONE_LOCAL_ID, HWMON_SYS_TZONE_REMOTE2_ID }, .sys_voltage = { HWMON_SYS_VSENS_VCC_ID, HWMON_SYS_VSENS_VPP_ID, HWMON_SYS_VSENS_V33_ID, HWMON_SYS_VSENS_V5_ID, HWMON_SYS_VSENS_V12_ID }, .sys_fan_speed_rpm = { HWMON_SYS_FAN1_ID, HWMON_SYS_FAN2_ID }, .hdd_backplane = { HWMON_SYS_HDD_BP_NULL_ID }, .psu_status = { HWMON_PSU_NULL_ID }, .sys_current = { HWMON_SYS_CURR_NULL_ID }, } }, { .name = "SA6400", .pci_stubs = { { .type = __VPD_TERMINATOR__ } }, .emulate_rtc = false, .swap_serial = false, .reinit_ttyS0 = true, .fix_disk_led_ctrl = true, .has_cpu_temp = true, .is_dt = true, .hwmon = { .sys_thermal = { HWMON_SYS_TZONE_REMOTE1_ID, HWMON_SYS_TZONE_LOCAL_ID, HWMON_SYS_TZONE_REMOTE2_ID }, .sys_voltage = { HWMON_SYS_VSENS_VCC_ID, HWMON_SYS_VSENS_VPP_ID, HWMON_SYS_VSENS_V33_ID, HWMON_SYS_VSENS_V5_ID, HWMON_SYS_VSENS_V12_ID }, .sys_fan_speed_rpm = { HWMON_SYS_FAN1_ID, HWMON_SYS_FAN2_ID }, .hdd_backplane = { HWMON_SYS_HDD_BP_NULL_ID }, .psu_status = { HWMON_PSU_NULL_ID }, .sys_current = { HWMON_SYS_CURR_NULL_ID }, } }, I have build config.json and bsp like below in load config. https://github.com/PeterSuh-Q3/redpill-load/actions/runs/4385726864 https://github.com/PeterSuh-Q3/redpill-load/tree/master/config/SA3600/7.1.1-42962 Since it is a dual power model, I added the sa3600 to the lkm. https://github.com/PeterSuh-Q3/redpill-lkm/blob/master/shim/bios/bios_psu_status_shim.c#L35 I rebuilt the TCRP FRIEND v0.0.4 kernel. https://github.com/PeterSuh-Q3/tcrpfriend/actions/runs/4396437746 However, junior's /var/log/linuxrc.syno.log log shows an error log saying that the disk cannot be found as shown below. (eudev has been applied and the NIC works normally. The NIC works even with the existing method other than eudev.) All disk ready or timeout executed Disable all invalid HBA PHY! Failed to SYNOEnclosureInvalidHbaPhyControlHandler. Exit on error [1] DISK NOT INSTALLED... And, it seems to be the direct cause for this, but in junior's /var/log/messages log, the message below keeps repeating. Mar 13 01:38:40 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=broadwellnk&buildnumber=42962][7][] Mar 13 01:38:42 scemd: enclosure_host_enum.c:31 failed to use glob to find disk path:/sys/class/sas_host/host* Mar 13 01:38:42 scemd: enclosure_direct_host_enc_info_get.c:800 SYNOSAS: Error! no any non-optional HBA Mar 13 01:38:42 scemd: enclosure_direct_host_enc_info_get.c:1101 SYNOEnclosureHostValidHbaGet() failed. Mar 13 01:38:42 scemd: enclosure_list_enum.c:196 SYNOEnclosurePseudoEncInfoGet() failed. please wait it become ready[0x2000 file_get_key_value.c:80] Mar 13 01:38:42 scemd: enclosure_list_enum.c:418 Enum internal pseudo enclosure failed. Mar 13 01:38:42 scemd: enclosure_enum_by_valid_link.c:75 Fail to SYNOEnclosureListEnum(). Mar 13 01:38:42 scemd: enclosure_enum_by_valid_link.c:222 failed to enum enclosure lists Mar 13 01:38:42 scemd: enclosure_serialized_list_get.c:34 SYNOSAS: Failed to SYNOEnclosureValidLinkGetUntilReady Mar 13 01:38:42 scemd: enclosure_list_transfer_to_write.c:129 failed to get serialized ENCLOSURE_LIST Mar 13 01:38:42 scemd: enclosure_list_cache_update.c:30 failed to SYNOEnclosureSerializedListToFile, /run/synosas/encListTmp Mar 13 01:38:42 scemd: scemd.c:919 SYNOEnclosureListCacheUpdate failed Mar 13 01:38:42 kernel: [ 284.678629] <redpill/bios_shims_collection.c:60> mfgBIOS: nullify zero-int for VTK_SET_HDD_ACT_LED Which part needs more editing?
×
×
  • Create New...