Penguin Power

7.1 42661 Update 3 got released and it is supported using Xpenology. Not sure if the initial patch is still valid and adding "7.1 42661-3" works. Is it possible to check? I am unable to validate as my test DSM VM is unavailable.

Confirmed - Update 3 using below steps!! Thanks Everyone!! Manual update from the GUI within Synology from 7.1-42661 to U3 https://archive.synology.com/download/Os/DSM/7.1-42661-3 Then reboot, drop into TCRP and go with the following: ./rploader.sh update now ./rploader.sh fullupgrade ./rploader.sh postupdate broadwellnk-7.1.0-42661

Yes, I created a new 7.1 boot loader keeping the same Serial Number + Mac address and upgraded to 7.1 final

Requesting some help and clarification for "Upgrade" path. Currently running DS3622xs+ DSM 7.0.1-42218 and my goal is to upgrade to 7.1.0-42661 (Final release). Can I upgrade directly from DS3622xs+ DSM 7.0.1-42218 to 7.1.0-42661 (Final release)? or do I have to first upgrade to DS3622xs+ DSM 7.1.0-42621 (RC)? For DSM 7.1.0-42621 (RC) I can see that possible upgrade (using postupdate method) to DS3622xs+ DSM 7.1 RC ( 7.1.0-42621 ) using below steps ---------------------------------------- =>Download the DSM 7.1 PAT file from the Synology Download Center with 7.0.1 already installed. =>Update and restore in the synology DSM 7.0.1 to manually update. => Reboot to TinyCore =>./rploader.sh update now =>./rploader.sh backuploader now =>./rploader.sh download broadwellnk-7.0.1-42218 =>./rploader.sh 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 For DSM 7.1.0-42661 (Final) I can create [DS3622xs+] DSM 7.1 Boot Loader using below steps --------------------- ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS3622xs+ ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh build broadwellnk-7.0.1-42218 ./rploader.sh clean now ./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/master/redpill-misc/rpext-index.json ./rploader.sh build broadwellnk-7.1.0-42661 ./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now; Using newly created boot loader above, can I upgrade to DSM 7.1 final directly? Thanks everyone in advance!!

@pocopico ============================================== Broadwellnk-7.0.1-42218 DS3622xs+ (dmesg - after finishing installation) ============================================== [ 4.669636] tg3.c:v3.137 (May 11, 2014) [ 4.671035] libphy: tg3 mdio bus: probed [ 4.671098] tg3 0000:03:00.0: No PHY devices [ 4.671200] tg3 0000:03:00.0: Problem fetching invariants of chip, aborting @IG-88 Guess is that libphy could be the culprit for No PHY devices (as per his comment) Thanks

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!

@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!!

@IG-88 Thank you very much for the detailed explanation!! To verify content of my modules + firmware path, I executed below command. ➜ tg3-4.4.180plus-broadwellnk - strings tg3.ko | egrep -E "version|magic|firmware" %s: Trying to load TX cpu firmware which is 5705 No firmware running Failed to load firmware "%s" tg3_load_tso_firmware tg3_load_firmware_cpu tg3_load_5701_a0_firmware_fix firmware=tigon/tg3_tso5.bin firmware=tigon/tg3_tso.bin firmware=tigon/tg3.bin version=3.137 srcversion=0737AAA138EA5CF848588B8 vermagic=4.4.180+ SMP mod_unload tg3_load_firmware_cpu I used pocopico tg3+libphy modules from - https://github.com/pocopico/4.4.180plus-modules which I have copied to DSM's /lib/modules folder. and firmware from - https://github.com/pocopico/4.4.180plus-modules/tree/main/firmware which I have copied on DSM's /lib/firmware/tigon folder. I tried to "insmod" manually + tried rebooting DSM without any luck. (yes, after reboot file persist) After that I tried firmware files from kernel.org without any luck. Please note that, I am already up and running using 2nd nic card (r8168) and now I am trying to make my tg3 work. 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? Not sure if extra.lzma of loader for 6.2 have modules + firmware for 4.x kernel? 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? Thanks again in advance!!

Thank you to this wonderful community, I have finally upgraded my setup to "Broadwellnk-7.0.1-42218 DS3622xs+" Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz 32GB RAM 3 x SATA drives On-Board Nic = Tigon3 (BCM57788)* Used - tinycore-redpill.v0.4.6.img with SATA map port - "SataPortMap": "6", "DiskIdxMap": "00" (Note:-I also had issue of "Something went wrong and SATA ports have been disabled. The way I got around is by editing the grub prompt with "SataPortMap=1" which only detected one of my SATA disk + finished installation. After installation, I booted normally "keeping SAtaPortMap=6" which detected all 3 SATA disks) @pocopico Just want to bring to your notice that I am having issues using TG3 drivers. TinyCore Linux is able to detect the NIC and rploader build script was fetching TG3 driver from https://github.com/pocopico/rp-ext/blob/main/tg3/rpext-index.json. But unfortunately after reboot, no luck getting DHCP request. I tried mostly all other builds but encountered same issue. Bought a new PCIe Card which worked flawlessly for completing installation. Even now my setup is still not detecting On-Board Nic Tigon3 (BCM57788) and that was the reason I was not getting DHCP request initially. For your reference find below output for TG3 card initialization from ==================== tinycore-redpill Linux output ===================== root@box:/home/tc# dmesg | grep -i tg [ 1.399900] libphy: tg3 mdio bus: probed [ 1.414234] tg3 0000:03:00.0 eth1: Tigon3 [partno(BCM57788) rev 57780001] (PCI Express) MAC address d4:xx:xx:xx:xx:xx [ 1.414236] tg3 0000:03:00.0 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [ 1.414237] tg3 0000:03:00.0 eth1: dma_rwctrl[76180000] dma_mask[64-bit] ============================================== Broadwellnk-7.0.1-42218 DS3622xs+ (after finishing installation) ============================================== [ 4.669636] tg3.c:v3.137 (May 11, 2014) [ 4.671035] libphy: tg3 mdio bus: probed [ 4.671098] tg3 0000:03:00.0: No PHY devices [ 4.671200] tg3 0000:03:00.0: Problem fetching invariants of chip, aborting It sounds like tg3 driver is not getting loaded due to variation in chip!! Again, Thanks everyone!!