v1.0.1.0

[PeterSuh-Q3]

1.0.1.0 Upgrade from Tinycore version 12.0 (kernel 5.10.3) to 14.0 (kernel 6.1.2) 
to improve compatibility with the latest devices.

---

This discussion was created from the release v1.0.1.0.

[TheNighthawk99]

Hello,
I have been following this project for many months now and I wanna thank you for your great effort.
I have noted that the size of versions 1.0.1 and 1.0.0.5 are almost 4x the size of versions <1, which are about 200 MiB.
Why this big difference in terms of file size?

Thank you.
Regards.

[PeterSuh-Q3]

First of all, the basic size of the img file has increased from 1G to 1.5G.
And, the default content in the img file is gradually increasing.

The most important thing is that when creating this img file from a USB stick, "Win32 Disk Imager 1.0" is used, and the compression function of this tool is utilized.
When using compression, if there are any fragments in the partition contents of the USB stick, it seems to reduce compression efficiency.

I'm not sure how to collect the fragments of the USB stick partition.
If this becomes possible, compression efficiency will likely be improved.

[TheNighthawk99]

Many thanks for your reply.

[PeterSuh-Q3]

You have succeeded in making the gz compressed files lightweight.
It is available starting from the next version, v1.0.2.4.

https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v1.0.2.4

[Daniel042001]

Greetings,

Tried out recent release of 1.0.1.0 with Intel NUC6CAYH (J3455).
Encountered the following issue:
As photo illustrated,
upon successful installation of tcrp xpenology, during first boot,
before initializing DSM, right after 'no more display' countdown concluded,
this line appears, "rops_handle_POLLIN_netlink: DELADDR"

Corresponding to this piece of log, the network connection terminated, link status LEDs are turned off.

Waited for half an hour, it seems the network LEDs came back, however, network never recovers.
The NUC box can not ping through.

More interestingly, I have built another NUC6CAYH, the same model, two weeks ago, using 1.0.0.5 with flying colors.
I just simply repeated my steps with 1.0.1.0, and every tempts end up with "rops_handle_POLLIN_netlink: DELADDR" and network lights out.

Thanks in advance.

[PeterSuh-Q3]

The "rops_handle_POLLIN_netlink: DELADDR" message is not directly related to IP not being resolved.

I can't judge because I can't see the capture of the MAC address spoofing (switching between real MAC address and virtual MAC address) process above, but if you use spoofing to change the MAC address, the process of spoofing it again within DSM fixes the IP address within DSM. It plays a role.
However, I recently noticed that the attempted MAC spoofing addon within DSM was problematic.
https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/mac-spoof
Also, since this problem was confirmed, this addon will no longer be used, so MAC spoofing and IP address fixation within DSM are not supported.

So, like RR, I plan to no longer support MAC spoofing in TCRP-MSHELL.
Instead, I plan to provide a separate function to change the NIC's real MAC address directly to users who want to change it to a Synology genuine MAC address.
If it is difficult to change it directly within MSHELL, you may need to use a utility, which is a solution that is already available.

As you can see, if MAC address spoofing is only handled in the FRIEND kernel and not in DSM, it will only lead to confusion for users like you.
Since there is no spoofing within DSM, it is highly likely that an incorrect IP associated with the real MAC address is assigned to the actual DSM.

Sometimes, even if you don't do MAC spoofing, the IP address is not fixed even within the real MAC address.

I think I should guide you depending on which of these two cases you fall into.

First, please try using the IP address that changes through finds.synology.com.

[wirwolf]

Hello. I download vmdk image and i can not boot interface

[wirwolf]

Also, I flash tinycore-redpill.v1.0.1.0.m-shell.img to a USB drive and use it in VMware as SCSI disk but i also see this screen

[PeterSuh-Q3]

How much memory did you allocate to TC in your virtual environment?
It can also be a problem if the allocated memory is too low.

The above phenomenon occurs when the mydata.tgz file is not read properly at the "Loading extensions..." stage.

[gadkarisid]

Just wanted to say thanks for this project! I tried other tcrp VMDKs to build an Xpenology instance with no success, even after hours of troubleshooting. I was FINALLY able to get a working instance up with minimal effort using your project, so again, thanks!

[PeterSuh-Q3]

I'm glad it helped.
have a nice day.

[storm-99]

Using VMWare Fusion, configured TCRP fine - TCRP loader as IDE:0, data disk as SCSI:0
but failed to install DSM, tried DSM 7.1 and 7.2, same error (7.2 failed at 5x%, 7.1 failed at 4x%), any idea?

[PeterSuh-Q3]

redpill does not yet support IDE and SCSI storage devices.
Use only SATA (AHCI) or NVMe.

[storm-99]

SATA works!!!
BTW, how about HBA (pass through) cards likse LSI 2308 under ESXi 7.03?
Configed similarly, with SataPortMap=18 DiskIdxMap=0C00 (don't want to show the SATA TCRP loader), but DSM install failed at 6x%

[storm-99]

All sorted, got HBA card working. Need to convert the TCRP loader into flat vmdk in order to get the SATA working under ESXi.
One more thing, for DX3622xs, how to get the Storage Panel Size (Tower_8-bay) working?
When building the loader, I already chose "Storage Panel Size (Tower_8-bay)", but Overview->Drive information still shows 12 bays.
And thank you for the great work!!!!

[PeterSuh-Q3]

Try editing and running the scheduler as described at the end of this notice.

https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=449023

[storm-99]

Hi Peter,
It's me again. Anyone have problem with iSCSI? I can create iSCSI Lun and iSCSI Target fine, but just CANNOT map the iSCSI Target. It says
"LUN [veeamLUN-1] is not available due to load fail."

If I reboot, the iSCSI Target shows offline, BUT I can map the iSCSI Target.

Tried Thick and Think Provisioning, same outcome.

[storm-99]

I am using DS3622xs+, DSM 7.2.1-69057 Update 4, loader v1.0.2.4