Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 12/12/2023 in all areas

  1. У новой матери нету скорее всего способа загрузки в старом режиме BIOS и отключение security boot не решит проблему. Загрузчик DSM 5.2 тогда еще не поддерживал UEFI поэтому и не грузится. Выход только один, создавайте новый загрузчик для режима UEFI, загружайтесь и делайте миграцию. Я бы для эксперимента подсунул чистый левый жесткий диск, установил систему, проверил что все работает. А потом создал заново загрузчик и подключил уже рабочие диски. DSM запросит миграцию с сохранением всех данных. Ну и про бекап не забывайте, вероятность что все данные накроются тоже имеется если у вас какой ни будь RAID 5.
    1 point
  2. you're right. Synology's original specifications for SA6400 are based on AMD Epyc CPU. iGPU transcoding is only available on Intel CPUs. You can see it as hacked to enable the use of Intel CPU in SA6400 and then transcode to Intel iGPU. SA6400, the only model in XPE that supports kernel 5, is considered advantageous and suitable for new hardware of the 11th generation or higher. There are continued reports of cases where 12th and 13th generation MOBOs, which did not work on XPE kernel 4 models, work on SA6400.
    1 point
  3. I think I need to explain: Yes, I was a little extreme at the time, because I roughly guessed who that person was. (A brand new account, so to speak, the account created specifically for the purpose of creating that issue) This is what makes me angry. So when he mentioned the open source agreement, I didn't think much about it. Since I can't publish it because the second release under the protocol requires public modification, I delete the repository and don't publish it. If someone else asks, I may not do this, and may even invite him to revise it together. In addition, as we all know, a month ago they were public. I changed it to non-public because 1. I unpacked the official drivers of all architectures and backed them up on github. Although this is nothing, I still don’t want to be retrieved. 2. I saw some very unhappy things( and don’t want to say more, related to the person who created the issue) In addition, and what I said on github, so I won’t go into details here. If anyone thinks I did something, just don't use it. From beginning to end, few people have seen me recommending others to use RR, because it doesn’t do me any good whether you use it or not. On the contrary, the more people use it, the more uneasy I feel. I am always afraid of being targeted by syno officials. But I just have a bit of perfectionism and always want to do better.
    1 point
  4. Sorry, everyone, Because I was accused of not disclosing all driver source codes, I decided to withdraw from this circle.
    0 points
×
×
  • Create New...