TinyCore RedPill Loader Build Support Tool ( M-Shell )

[gericb]

59 minutes ago, Trabalhador Anonimo said:

Is it safe to go to 7.2.2-72806-1?

Can't speak to other experiences, but I did it through the Control Panel/Update and it went smoothly, no issues.  Of course, it's always a good idea to be sure you're running the most current version of Loader that you're using.  🤠

[Peter Suh]

12 hours ago, Trabalhador Anonimo said:

Is it safe to go to 7.2.2-72806-1?

 

verified.

[Biocef]

Hi,

I can't update from 7.2.1-69057 to 7.2.2-72803, the network doesn't come back.

If I boot in junior mode I have network, I can access the dsm installation screen but when rebooting, during the installation, the network still doesn't come back.

I tried with another USB key, same problem. Is there anything else I can try?

My motherboard is an ASRock H67M-ITX with a Realtek RTL8111E network chipset.

Thanks !

[-iliya-]

В 17.11.2024 в 05:53, Peter Suh сказал:

 

verified.

Hi Peter, thank you for loader.

How to activate hot plug HDD on LSI HBA for SA6400?

[Biocef]

Le 19/11/2024 à 15:10, Biocef a dit :

Hi,

I can't update from 7.2.1-69057 to 7.2.2-72803, the network doesn't come back.

If I boot in junior mode I have network, I can access the dsm installation screen but when rebooting, during the installation, the network still doesn't come back.

I tried with another USB key, same problem. Is there anything else I can try?

My motherboard is an ASRock H67M-ITX with a Realtek RTL8111E network chipset.

Thanks !

To clarify (I didn't find how to edit my post), I update via dsm, the nas restarts, I update the loader and at the next boot the network does not come back up.
Are there any changes on the driver side with the latest version of dsm?

[Peter Suh]

4 hours ago, Biocef said:

To clarify (I didn't find how to edit my post), I update via dsm, the nas restarts, I update the loader and at the next boot the network does not come back up.
Are there any changes on the driver side with the latest version of dsm?

 

Recently, there have been reports that the PING response is not working on the Realtek LAN module used in mshell,

 

so I am adding a function to use the RR module that has been stabilized more for the Realtek module instead.

 

Of course, the default will be the all-modules of tcrp-modules, which is exclusive to mshell, as before.

 

For those who think that there is a problem with this basic module, please re-select rr-modules and build the loader,

 

and the current final version of rr, 24.11.0, will be used.

 

If there is no problem with the existing module, there is no need to try this rr-modules.

 

If you are using SA6400, this process has already been applied.

This is because SA6400's all-modules is rr-modules itself.

 

 

[Peter Suh]

20 hours ago, -iliya- said:

Hi Peter, thank you for loader.

How to activate hot plug HDD on LSI HBA for SA6400?

 

I don't know much about hot plug either.

 

Didn't it work well in RR?

 

Please refer to AI's answer.

 

[Biocef]

Il y a 11 heures, Peter Suh a dit :

 

Recently, there have been reports that the PING response is not working on the Realtek LAN module used in mshell,

 

so I am adding a function to use the RR module that has been stabilized more for the Realtek module instead.

 

Of course, the default will be the all-modules of tcrp-modules, which is exclusive to mshell, as before.

 

For those who think that there is a problem with this basic module, please re-select rr-modules and build the loader,

 

and the current final version of rr, 24.11.0, will be used.

 

If there is no problem with the existing module, there is no need to try this rr-modules.

 

If you are using SA6400, this process has already been applied.

This is because SA6400's all-modules is rr-modules itself.

 

 

Thanks a lot, I'll try this next week !

[-iliya-]

В 26.11.2024 в 22:41, Peter Suh сказал:

 

I don't know much about hot plug either.

 

Didn't it work well in RR?

 

Please refer to AI's answer.

 

some time ago I used the TCRP bootloader and the 3622xs+ model, the LSI9300-i16 controller. It was originally an HBA, and I had hot-plug working, the controller BIOS does not have any additional settings on the Hot-Plug topic, but due to the 26-disk limitation.
I have exactly 26 of them, I had to switch to your bootloader and the SA6400 model.
Now when I remove a disk, it disappears from the list of disks, but when I put a new disk in its place, it does not appear until rebooting.
The problem is that sometimes i need to replace a faulty disk, but i cannot turn off the NAS.

[Biocef]

Le 26/11/2024 à 20:36, Peter Suh a dit :

 

Recently, there have been reports that the PING response is not working on the Realtek LAN module used in mshell,

 

so I am adding a function to use the RR module that has been stabilized more for the Realtek module instead.

 

Of course, the default will be the all-modules of tcrp-modules, which is exclusive to mshell, as before.

 

For those who think that there is a problem with this basic module, please re-select rr-modules and build the loader,

 

and the current final version of rr, 24.11.0, will be used.

 

If there is no problem with the existing module, there is no need to try this rr-modules.

 

If you are using SA6400, this process has already been applied.

This is because SA6400's all-modules is rr-modules itself.

 

 

Hi Peter,

Unfortunately there is no network either with rr-modules 😕

[Peter Suh]

On 11/19/2024 at 11:10 PM, Biocef said:

Hi,

I can't update from 7.2.1-69057 to 7.2.2-72803, the network doesn't come back.

If I boot in junior mode I have network, I can access the dsm installation screen but when rebooting, during the installation, the network still doesn't come back.

I tried with another USB key, same problem. Is there anything else I can try?

My motherboard is an ASRock H67M-ITX with a Realtek RTL8111E network chipset.

Thanks !

 

This phenomenon was a problem that persisted in the Jun loader during the DSM 6 era.

Since Synology is still stuck on the old version of kernel 4, I think this problem still persists.

I will tell you how to add r8169 to the blacklist as instructed by AI.

In the past, I tried manually installing the r8168 module as instructed by AI due to this problem in DSM6.

 

https://community.hetzner.com/tutorials/installing-the-r8168-driver

 

RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
This is an old chronic problem.
There is no fundamental solution to this problem in DSM 6, so many people have changed to Intel LAN cards.
It is true that it works well, but then it stops working strangely like that.

 

> A.I 's answer.

 

Yes, issues with the recognition of RTL8111H chipset network modules in Linux still occur. The default Linux kernel module (r8169) often does not work correctly with the RTL8111H NIC, leading to various network problems.

This is because Linux sometimes chooses the wrong kernel module to support this hardware, resulting in suboptimal performance or connectivity issues.

To resolve this, users often need to build and install the correct module manually. The recommended solution is to use the official Realtek driver (r8168) instead of the default r8169 module.

This can resolve issues such as capped sending rates and other network-related problems.It's important to note that while this issue persists for some users, newer Linux distributions with more recent kernel versions (e.g., Linux 5.3 and above) may have improved support for these Realtek chipsets. 

However, if problems are encountered, manual driver installation may still be necessary.

[Biocef]

Il y a 2 heures, Peter Suh a dit :

 

This phenomenon was a problem that persisted in the Jun loader during the DSM 6 era.

Since Synology is still stuck on the old version of kernel 4, I think this problem still persists.

I will tell you how to add r8169 to the blacklist as instructed by AI.

In the past, I tried manually installing the r8168 module as instructed by AI due to this problem in DSM6.

 

https://community.hetzner.com/tutorials/installing-the-r8168-driver

 

RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
This is an old chronic problem.
There is no fundamental solution to this problem in DSM 6, so many people have changed to Intel LAN cards.
It is true that it works well, but then it stops working strangely like that.

 

> A.I 's answer.

 

Yes, issues with the recognition of RTL8111H chipset network modules in Linux still occur. The default Linux kernel module (r8169) often does not work correctly with the RTL8111H NIC, leading to various network problems.

This is because Linux sometimes chooses the wrong kernel module to support this hardware, resulting in suboptimal performance or connectivity issues.

To resolve this, users often need to build and install the correct module manually. The recommended solution is to use the official Realtek driver (r8168) instead of the default r8169 module.

This can resolve issues such as capped sending rates and other network-related problems.It's important to note that while this issue persists for some users, newer Linux distributions with more recent kernel versions (e.g., Linux 5.3 and above) may have improved support for these Realtek chipsets. 

However, if problems are encountered, manual driver installation may still be necessary.

Thanks for the explanation, I think I understand (but I'm not used to Linux).

 

I tried to follow the tutorial without success (I'm not sure what I should do) :

"yum --enablerepo=elrepo install kmod-r8168" -> yum not found

"wget http://mirror.hetzner.de/tools/Realtek/drivers/r8168-8.046.00.tar.bz2" -> address no longer exists

"echo "blacklist r8169" >> /etc/modprobe.d/blacklist.conf" -> Can't create /etc/modprobe.d/blacklist.conf: nonexistent directory

 

What should I do exactly?

Edited 3 hours ago by Biocef

[Peter Suh]

36 minutes ago, Biocef said:

Thanks for the explanation, I think I understand (but I'm not used to Linux).

 

I tried to follow the tutorial without success (I'm not sure what I should do) :

"yum --enablerepo=elrepo install kmod-r8168" -> yum not found

"wget http://mirror.hetzner.de/tools/Realtek/drivers/r8168-8.046.00.tar.bz2" -> address no longer exists

"echo "blacklist r8169" >> /etc/modprobe.d/blacklist.conf" -> Can't create /etc/modprobe.d/blacklist.conf: nonexistent directory

 

What should I do exactly?

 

The explanation in this link is a guide that is possible on general Linux.
Synology is a custom Linux, so it will not work with general methods.
I tried the above, but r8169.ko was deleted, so the network that was working fine stopped.
Please do not try the example.

As far as I know, Synology doesn't have a solution yet.

Edited 2 hours ago by Peter Suh

[Biocef]

Ok, thanks for your help !
Maybe an n100 motherboard could replace mine and solve the problem.