Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

20 hours ago, Penguin Power said:

Just to be clear, I have to copy modules + firmware to DSM's /lib/modules + /lib/firmware/tigon folder and don't have to do anything with RP loader/image file system correct?

 

yes, next would be insmod but you already tried that, check the log what the driver has to say when its loaded

syno's webgui might not show a new network adapter just because a driver is loaded (but it should when its loaded when booting)

 

20 hours ago, Penguin Power said:

Not sure if extra.lzma of loader for 6.2 have modules + firmware for 4.x kernel?

modules can't be used as 6.2 comes with another kernel version as 7.0

firmware would be the same but there should be no difference between to what you already have

 

 

21 hours ago, Penguin Power said:

On a fresh startup of the DSM, I see that tg3 modules gets loaded (because I have build with tg3 extension) but it fails to bring up interface because of possible missing firmware files. So for anything to try, I first have to rmmod tg3+libphy first and try insmod /lib/modules/tg3.ko+libphy after making sure firmware files exist at correct location.

 

What else can I try? 

if the driver is missing firmware then it might not be loaded but rmmod cant hurt

shortly i will have a replacement for my broken HP Pro 6305 and i will have a tigon3 again for testing that with 7.0

the other hardware i have around does not need any firmware files

Link to comment
Share on other sites

3 minutes ago, IG-88 said:

if the driver is missing firmware then it might not be loaded but rmmod cant hurt

shortly i will have a replacement for my broken HP Pro 6305 and i will have a tigon3 again for testing that with 7.0

the other hardware i have around does not need any firmware files

 

@IG-88

 dmesg | grep -i tg3
[    7.272124] tg3.c:v3.137 (May 11, 2014)
[    7.273188] libphy: tg3 mdio bus: probed
[    7.273250] tg3 0000:03:00.0: No PHY devices
[    7.273337] tg3 0000:03:00.0: Problem fetching invariants of chip, aborting
 

I can see that on fresh power up, libphy and t3 modules are getting loaded (even without /lib/firmware/tigon/xxx files). But even after copying firmware files, rmmod and insmod generates same error message as above.

 

Thanks @pocopico

# ln -s /bin/kmod /sbin/modinfo 

# ln -s /bin/kmod /sbin/depmod

# depmod -a

(no luck)

 

modinfo gives information of version number + dependancies for the tg3 module. I double checked that firmware files exist along with correct version number but still no go for bringing the interface up.

 

DSM 6.2 and TinyCore Linux have no problem with tg3 nic so definitely something small I am missing.

 

Thanks again guys!! Have a good day!!

Link to comment
Share on other sites

12 minutes ago, Kaneske said:

@pocopico

is TinyCore supposed to get 7.1-42250 3622xs+ support as easy as it is by now on 7.0.1-42218 or are there difficulties to get this done?

 

 

Well as always the build command relies on patches released by the repo owners. There is a well documented process for creating the patches on the fly but still the best way is to wait for the owners to update their repos.

 

 

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

On 3/26/2022 at 9:20 AM, giacomoleopardo said:

Hi everybody.

Specs:

  • ASRock Fatal1ty Z170 Gaming-ITX/ac (6 Intel SATA ports on board)
  • CPU: Intel® Core™ i3-7100 Processor
  • IGPU: Intel® HD Graphics 630
  • 4x 8TB HDDs Western Digital Red SHR (btrfs) (ports 0, 1, 2, 3)
  • 2x 1TB Raid 1 Sata SSDs Cache (ports 4, 5)
  • DSM 7.0.1 (42218) via TinyCore - USB bare metal

When Sata port 4 and/or 5 are connected it keeps giving this error in loop every 50-70 min, over and over again

 


[ 1037.717847]  [<ffffffff81436ee3>] ata_scsi_port_error_handler+0x133/0x1a30
[ 1037.718598]  [<ffffffff81432868>] ? ata_scsi_cmd_error_handler+0x118/0x190
[ 1037.718985]  [<ffffffff8143887b>] ata_scsi_error+0x9b/0xe0
[ 1037.719297]  [<ffffffff813f86f5>] scsi_error_handler+0xa5/0x530

 

jeopardizing the sleep/hibernation functions.

Leaving Sata ports 4 and 5 empty, doesn't give the problem, and the NAS goes to sleep as it should.

Any ideas?

I've found this 

https://www.kernel.org/doc/htmldocs/libata/ch03s05.html

Can anybody get something out of it? Honestly I don't know how to read it 

Link to comment
Share on other sites

1 hour ago, Penguin Power said:

 

@IG-88

 dmesg | grep -i tg3
[    7.272124] tg3.c:v3.137 (May 11, 2014)
[    7.273188] libphy: tg3 mdio bus: probed
[    7.273250] tg3 0000:03:00.0: No PHY devices
[    7.273337] tg3 0000:03:00.0: Problem fetching invariants of chip, aborting
 

I can see that on fresh power up, libphy and t3 modules are getting loaded (even without /lib/firmware/tigon/xxx files). But even after copying firmware files, rmmod and insmod generates same error message as above.

 

 

Google search seems to be pointing at needing - broadcom.ko module to be loaded along with libphy and tg3. Multiple reports of same error and the resolution was to load broadcom.ko before tg3.ko.

 

I checked https://github.com/pocopico/4.4.180plus-modules but unfortunately didn't found broadcom.ko

 

@pocopico ^ any help regarding this?

 

Thanks in advance!

 

Link to comment
Share on other sites

On 3/22/2022 at 1:01 PM, sam juan said:

anyone able to make WOL wake-on-lan worked for baremetal installs? tnx

Sent from my Pixel 6 Pro using Tapatalk
 

yay! so i was able to make Wake On Lan worked, both with lan1 and lan2;
1. make sure wol works prior building the loader; ie. boot in tinycore and shutdown, make sure you can wake it up;

2. during build, i used the actual mac1 and mac2 of my 2 nics in user_config.json

3. install and test wake-on-lan  - success!

Link to comment
Share on other sites

4 hours ago, pocopico said:

Hi All,

 

i need some testers for a new addition on rploader.sh.

 

You now have the option "postupdate" to process and update your junior (rd.gz/zImage) using the contents found under dsm root /.syno/patch.

 

To do so, you first perform an update using the DSM GUI to update pat from synology and then you go to TCRP to run

 

./rploader.sh update now

./rploader.sh backuploader now

./rploader.sh download <yourplatform>

./rploader.sh postupdate <yourplatform>

 

 Then if you previously had a "root not matched with junior" it should be fixed after postupdate process.

 

Please test and report any issues.

 

MAKE SURE your REPO supports the version you want to update TO before upgrading

 

 

 

 

 

 

i would like to try this but i just want to clarify if my understanding is correct. :D

with my current ds3622xs with 7.0.1-42218 baremetal, if i want 7.1.0-42621

1. download 7.1 pat from https://global.download.synology.com/download/DSM/release/7.1/42621/DSM_DS3622xs%2B_42621.pat?model=DS3622xs%2B&bays=12&dsm_version=7.1&build_number=42621&_ga=2.102639492.468865575.1648586076-1552442944.1645047990

2. manual DSM update inside DSM using the downloaded 7.1.0-42621 pat 

3. boot and select 3rd option (tinycore build)

4. run

./rploader.sh update now

./rploader.sh backuploader now

./rploader.sh download DS3622xsp

./rploader.sh postupdate DS3622xsp

 

tnx and pls be patient with me. ;)

 

Link to comment
Share on other sites

1 hour ago, sam juan said:

i would like to try this but i just want to clarify if my understanding is correct. :D

with my current ds3622xs with 7.0.1-42218 baremetal, if i want 7.1.0-42621

1. download 7.1 pat from https://global.download.synology.com/download/DSM/release/7.1/42621/DSM_DS3622xs%2B_42621.pat?model=DS3622xs%2B&bays=12&dsm_version=7.1&build_number=42621&_ga=2.102639492.468865575.1648586076-1552442944.1645047990

2. manual DSM update inside DSM using the downloaded 7.1.0-42621 pat 

3. boot and select 3rd option (tinycore build)

4. run

./rploader.sh update now

./rploader.sh backuploader now

./rploader.sh download DS3622xsp

./rploader.sh postupdate DS3622xsp

 

tnx and pls be patient with me. ;)

 

 

Actually all right but 4.

 

./rploader.sh update now

./rploader.sh backuploader now

./rploader.sh download broadwellnk-7.0.1-42218

 

For DS3622xs you need to add one more extension : 

 

so ./rploader ext broadwellnk-7.0.1-42218 add https://github.com/jumkey/redpill-load/raw/develop/redpill-misc/rpext-index.json

 

 

./rploader.sh postupdate broadwellnk-7.0.1-42218

 

Edited by pocopico
  • Like 2
Link to comment
Share on other sites

Hi

I think there might be an error with the rploader when running this:

58 minutes ago, pocopico said:

./rploader.sh backuploader now

the output is:
 

Quote

./rploader.sh: line 1183: syntax error near unexpected token '}'
./rploader.sh line 1183: '}'


Also the same error persists even when trying to build a dsm 7 image from scratch.

I hope this helps, if I have mistaken something, please correct me ;)

Edit: Before running the code,  I have already applied

Quote

sudo ./rploader.sh update now

 

Edited by octfoc
  • Like 1
Link to comment
Share on other sites

7 hours ago, pocopico said:

Hi All,

 

i need some testers for a new addition on rploader.sh.

 

You now have the option "postupdate" to process and update your junior (rd.gz/zImage) using the contents found under dsm root /.syno/patch.

 

To do so, you first perform an update using the DSM GUI to update pat from synology and then you go to TCRP to run

 

./rploader.sh update now

./rploader.sh backuploader now

./rploader.sh download <yourplatform>

./rploader.sh postupdate <yourplatform>

 

 Then if you previously had a "root not matched with junior" it should be fixed after postupdate process.

 

Please test and report any issues.

 

MAKE SURE your REPO supports the version you want to update TO before upgrading

 

 

 

 

 

 

I'm running 918p apollolake, the only 7.1 for me is 42621, and the only 7.1 I found was for 920p 42550 (jumkey)

 

Link to comment
Share on other sites

14 hours ago, D.S said:

It's curious. According to lspci information, you have one realtek lan and it's working, but the intel lan's driver is not loaded. You may try to add intel igb driver to see what result if R8152 is not an external USB lan.

I'm not sure why it says that about the intel lan, this box has 2 realtek nic, that must just be part of the chipset on this board. The NIC in this box are Realtek. When its on dsm623 and both ports work they are both Realtek

Link to comment
Share on other sites

18 hours ago, pocopico said:

 

There is an issue with the extension loading mechanism. If an extension that has duplicate dependency tries to get loaded it will fail and will fail into recover/install mode. Just add the one of the two modules (only the most required for install) then copy the usb r8152 module to /lib/modules and run :

 

# ln -s /bin/kmod /sbin/modinfo 

# ln -s /bin/kmod /sbin/depmod

# depmod -a

 

 

 

 

 

 

 

 

 

17 hours ago, pocopico said:

 

the last two warnings are expected. when you do a modprobe r8125 does it load ? you can check with lsmod |grep -i r8125

 

I downloaded the r8152.ko and put it /lib/modules

then ran the above commands

# ln -s /bin/kmod /sbin/modinfo 

# ln -s /bin/kmod /sbin/depmod

# depmod -a

# modprobe r8152

# lsmod |grep -i r8152

 

root@DS:/# lsmod |grep -i r8152
r8152                  35385  0
mii                     4227  2 r8152,r8169
usbcore               201223  10 etxhci_hcd,r8152,usblp,uhci_hcd,usb_storage,ehci_hcd,ehci_pci,usbhid,xhci_hcd,xhci_pci
root@DS:/#

 

those are the results, restarted the nas but still only have 1 nic lan, so no change? what am I doing wrong?

r8152addedpocopicocommands.thumb.jpg.0d7a5a7bd50cba664976693fcf38919f.jpg

That is the info center inside dsm7 obviously showing the lan as usb which it is not.

 

This is # lspci -nnQk

root@DS:/# lspci -nnQk
0000:00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [8086:5af0] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b)
        DeviceName:  Onboard IGD
        Subsystem: Intel Corporation Device [8086:2212]
        Kernel driver in use: i915
0000:00:0e.0 Audio device [0403]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster [8086:5a98] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:0f.0 Communication controller [0780]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine [8086:5a9a] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:12.0 SATA controller [0106]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: ahci
0000:00:13.0 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 [8086:5ad8] (rev fb)
        Kernel driver in use: pcieport
0000:00:13.2 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 [8086:5ada] (rev fb)
        Kernel driver in use: pcieport
0000:00:14.0 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 [8086:5ad6] (rev fb)
        Kernel driver in use: pcieport
0000:00:14.1 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 [8086:5ad7] (rev fb)
        Kernel driver in use: pcieport
0000:00:15.0 USB controller [0c03]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI [8086:5aa8] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: xhci_hcd
0000:00:1f.0 ISA bridge [0601]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface [8086:5ae8] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:1f.1 SMBus [0c05]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: i801_smbus
>>>>>>>>>>>>>>>>>0000:02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)<<<<<<<<<<<<<<<<<<<<<<<
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
        Kernel driver in use: r8169
0000:03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
        Subsystem: ASMedia Technology Inc. Device [1b21:1060]
        Kernel driver in use: ahci
0000:04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
        Subsystem: ASMedia Technology Inc. Device [1b21:1060]
        Kernel driver in use: ahci
0001:00:12.0 SATA controller [0106]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3]
0001:00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 [8086:5ad8]
0001:00:14.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 [8086:5ad6]
0001:00:15.0 USB controller [0c03]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI [8086:5aa8]
0001:00:16.0 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 [8086:5aac]
0001:00:18.0 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 [8086:5abc]
0001:00:19.0 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6]
        DeviceName:  Onboard LAN
0001:00:19.2 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6]
0001:00:1f.0 SMBus [0c05]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4]
0001:00:1f.1 SMBus [0c05]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4]
0001:01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)
0001:02:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
0001:03:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
root@DS:/#

Clearly shows the Realtek is pci not usb, so the usb nic is not being seen? or am I wrong?

 

Edited by phone guy
added lspci results
Link to comment
Share on other sites

11 hours ago, pocopico said:

 

What is your platform ? and what is supported by the repo owners. E.g. dododefi has 7.1.0-62621 for DS3622xsp while jumkey has 7.1-42550 for DS920+ etc 

 

you can verify checking the contents of the folders :

 

https://github.com/jumkey/redpill-load/tree/develop/config

 

and 

 

https://github.com/dogodefi/redpill-load/tree/develop/config/

 

 

 

 

 

 

Do you know if somewhere is available repo for DS3622xsp but for broadwellnk-7.0.1-42218 Update 2/3 ?  

 

Link to comment
Share on other sites

For anyone with a test DVA3221, i have tested succesfully the TCRP two stage upgrade to 7.1.0-42621.

 

Please proceed with caution and only on test systems.

 

The process is :

- Manual upgrade using DSM to 7.1 RC
- On reboot, select to boot tinycore redpill
- While on TCRP run the following

 

./rploader.sh update now
./rploader.sh backuploader now
./rploader.sh download 
./rploader.sh download denverton-7.0.1-42218
./rploader.sh postupdate denverton-7.0.1-42218

 
Fix the acpi systemd issue otherwise DSM will shutdown on access

 

./rploader.sh mountdsmroot now

sed -i 's/^acpi-cpufreq/# acpi-cpufreq/g' /mnt/dsmroot/usr/lib/modules-load.d/70-cpufreq-kernel.conf && cat /mnt/dsmroot/usr/lib/modules-load.d/70-cpufreq-kernel.conf

 

for people NOT having an NVIDIA card the following sould also be performed otherwise DSM will shutdown on access

Remove both lines on :  /mnt/dsmroot/usr/lib/modules-load.d/70-syno-nvidia-gpu.conf


and reboot 

Edited by pocopico
  • Like 5
  • Thanks 2
Link to comment
Share on other sites

15 minutes ago, pocopico said:

For anyone with a test DVA3221, i have tested succesfully the TCRP two stage upgrade to 7.1.0-42621.

 

Please proceed with caution and only on test systems.

 

The process is :

- Manual upgrade using DSM to 7.1 RC
- On reboot, select to boot tinycore redpill
- While on TCRP run the following

 

./rploader.sh update now
./rploader.sh backuploader now
./rploader.sh download 
./rploader.sh download denverton-7.0.1-42218
./rploader.sh postupdate denverton-7.0.1-42218

 
Fix the acpi systemd issue otherwise DSM will shutdown on access

 

./rploader.sh mountdsmroot now

sed -i 's/^acpi-cpufreq/# acpi-cpufreq/g' /mnt/dsmroot/usr/lib/modules-load.d/70-cpufreq-kernel.conf && cat /mnt/dsmroot/usr/lib/modules-load.d/70-cpufreq-kernel.conf

 

for people NOT having an NVIDIA card the following sould also be performed otherwise DSM will shutdown on access

Remove both lines on :  /mnt/dsmroot/usr/lib/modules-load.d/70-syno-nvidia-gpu.conf


and reboot 

 

Thank you !

 

screenshot_1648620234.png

  • Like 1
Link to comment
Share on other sites

I was able to install DSM 7.1 on 3622xsp using above instructions on my custom build computer ( Asus Z170I-PRO with Intel i5 6600K, 8GB RAM, some HDD/SSD and one M2 nvme Samsung SM961 drive) and Dell Perc H310 SAS controller flashed to HBA_9211_8i_IT.

 

I updated form DSM 7.0.1-42218 as @pocopico mentioned in post https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=272479

 

The main problem was that after an updated I had some critical messages about storage pool 1/ volume 1 and SSD cache, so I removed and recreated new one. 

I would like add that storage pool is on disk no 1 which is connected to motherboard SATA AHCI controller. 

The other two are connected to the SAS9211_8i controller, but I have not had on them any volumes on their storage pools created. It's hard to verify now what it would be if I had. The second problem is with my nvme cache I cannot setup or even use Secure Erase. That option doesn't work, and finally I am not able to turn on write cache on the disks which are connected to SAS controller, but I do not know if this was before. I guess, was the same. I am attaching some print screens. 

If somebody wants me to test something please let me know, this is my test computer so I can do whatever   ;) 

 

I also wanted do some test on my VM but I wasn't able to update, I had some errors. 

 

 Thanks @pocopico for your work. 

03.PNG

02.PNG

04.PNG

05.PNG

06.PNG

07.PNG

  • Thanks 2
Link to comment
Share on other sites

For anyone with a test DS3615xs, i have tested succesfully the TCRP two stage upgrade to 7.1.0-42621.

 

Please proceed with caution and only on test systems until process is reported stable 

 

The process is :

 

- Manual upgrade using DSM to 7.1 RC
- On reboot, select to boot tinycore redpill

- FOR NOW, Only dogodefi repo has the config files for ds3615xs_42621 so change your custom_config.json for bromolow repo to that.
- While on TCRP run the following

 

./rploader.sh update now
./rploader.sh backuploader now

./rploader.sh clean now (IF your repo was already set to dogodefi you can skip that)
./rploader.sh download bromolow-7.0.1-42218
./rploader.sh postupdate bromolow-7.0.1-42218

 
Fix the acpi systemd issue otherwise DSM will shutdown on access (check with systemctl list-units --state failed), You will have to perform that after the first succesfull DSM reboot.

 

./rploader.sh mountdsmroot now

sed -i 's/^acpi-cpufreq/# acpi-cpufreq/g' /mnt/dsmroot/usr/lib/modules-load.d/70-cpufreq-kernel.conf && cat /mnt/dsmroot/usr/lib/modules-load.d/70-cpufreq-kernel.conf

 

Edited by pocopico
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...