wjz304

So I also hope that ARC will no longer borrow components and modules from RR.

There is too little information. Except that eth is an igc driver, nothing else is clear. I can only say: I don’t know. But it is recommended to try to install sa6400,

Need confirmation from @Peter Suh. I don’t know much about whether mshell has an automatic setting mechanism. If so, how to skip them?

Probably not, it just solves the problem of insufficient space that may occur during the installation process.

These 3 folders can be deleted，I'm thinking about adding it to the bootloader mkdir -p /mnt/md0 mount /dev/md0 /mnt/md0/ rm -rf /mnt/md0/@autoupdate/* rm -rf /mnt/md0/upd@te/* rm -rf /mnt/md0/.log.junior/* umount /mnt/md0/

or set maxdisks=17 internalportcfg=0x000001FE3F esataportcfg=0x0000000000 usbportcfg=0x00000001C0 to synoinfo

plz get `cat /etc/synoinfo.conf | grep *portcfg`

Most likely not caused by the network card

Questions about mac, DSM will read the mac set in cmdline after startup and set it to eth in sequence. So I blocked this process of DSM in RR 23.9.7. In this way, eth maintains its own mac, and syno's app will read the mac in cmdline for verification. They do not affect each other, because eth has a real mac, so wake-up and other functions are also normal. I think there is no need to modify the Mac. If you need to modify the Mac, the virtual environment can be modified directly on the upper virtual platform. The physical environment is best modified through official software and hardware.

Regarding the console, the base system tc of tcrp has a desktop, so the console is not turned on by default. The base system of RR does not have a desktop environment, so the default is console. You can search for articles related to opening the console in ubuntu for reference.

However, FS6400/HD6500 may support HBA. I have made the disk on the HBA appear in the system, but I don’t know the details of dts. I need time to guess.

Apart from supporting a lot of threads, there are no other features. According to the test, it should support 64 threads

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.

Sorry, everyone, Because I was accused of not disclosing all driver source codes, I decided to withdraw from this circle.

> Does latest release with fix to "acpid" fix this issue ? They should have nothing to do with each other, This modification is mainly related to power events.

The current update-check.sh has two functions, 1. Check whether the environment matches the new version, 2. Modify the changes. It is not recommended to upgrade from i18n to RR due to many factors. If you have not done a lot of configuration for booting and the DSM is the latest version, rewriting the bootloader disk and trying to restore booting will not affect the dsm system. For security reasons, you can also back up the current USB flash drive first, or try changing the USB flash drive. Because I am just one person, I often cannot think carefully. If the version span is too large, it may be more likely to be incompatible. This is one of the reasons why it is not recommended to directly upgrade from arpl-i18n to RR.

https://github.com/wjz304/rr/releases/tag/23.10.5 https://www.youtube.com/watch?v=C3fLIpaFpMs

"3 SATA drives port", "SSD is on port 5", I don't quite understand

And if you update DSM without updating RR, when a patch error is reported after restarting, the boot will be terminated. It is also possible to update RR at this time.

Whether you need to update RR when updating DSM depends on whether the official boot file has been modified. This is unpredictable, so I can't answer this question. I can only suggest that if you update DSM, it is best to update RR simultaneously. After RR is updated, it will be prompted to rebuild.

Migration is possible, but not recommended. https://github.com/wjz304/rr/releases/tag/23.10.5

You can pull a x86 of the same version_ 64 kernel, Check out the differences between the functions that reported errors, Perhaps there are more errors,

Oh, my fault, I mistakenly thought it was an arm,