Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 01/29/2022 in all areas

  1. hi. first of all thanks @pocopico for this great tool. finally i managed to create a uefi bootable flash drive. the steps are very easy but it took me about the whole day to figure out. after writing redpill tc loader image to your flash drive, you need a linux machine to add the uefi boot. in my case, i have a notebook with linux mint installed (latest edge edition). assuming that my flash drive was /dev/sdb, this is what i've done: Mount the filesystem: sudo mount -o umask=000 /dev/sdb1 /mnt Write the MBR and install the grub files required for legacy BIOS boot on the drive: (i don't know if this step is really needed but anyway it works) sudo grub-install --no-floppy --boot-directory=/mnt/boot --target=i386-pc /dev/sdb Install /EFI/BOOT/BOOTX64.EFI and other grub files required to load grub from a 64-bit UEFI firmware: sudo grub-install --removable --boot-directory=/mnt/boot --efi-directory=/mnt --target=x86_64-efi /dev/sdb Unmount the filesystem: sudo umount /dev/sdb1 after that, remove the flash drive and try it. for me, it worked at first try. no need to edit any other file. credits go to https://github.com/ndeineko/grub2-bios-uefi-usb for this helpful page without which I would never have succeeded.
    3 points
  2. I think this is not relevant. I have uploaded my libssutils.so (patched_40_cams) here for SurveillanceStation-x86_64-8.2.10-7310 The problem is that the value you modify there for the licences is checked. This means that conditions in the other libraries can no longer apply. This causes the services to terminate after a certain time. libssutils.so
    2 points
  3. das hier im board lebt davon das man seine informationen offen teilt, weitergibt und andere darauf aufbauen wenn jemand etwas dazu sucht und diesen thread ließt ... wenn du einen link hast dann rein damit, je mehr das lesen und probieren um so besser, nur so kommen wir zu einer ordentlichen howto
    2 points
  4. Все прокатывает. Читайте тему. Выше я писал про это. Проброса не будет. Работать ss будет только на виртуальной машине.
    1 point
  5. @pocopicoExcellent Job. Thanks a lot! After a litte while and understanding SataPortMap and DiskIdxMap my Dell T20 appears to run nicely on DSM 7 (previously 6.something) The output of the rploader script was providing 64 for SataPortMap and 0004 for DiskIdxMap - if I remember correctly. First controller 6, second controller 4 ports. So far, so correct but not all ports are in use. So I figured out for the first controller 4 drivers were in use and for the second 2 drivers plus 1 USB Key. I changed SataPortMap to 421 (4 drives on controller 1, 2 drives on controller 2 and 1 usb key) DiskIdxMap to 000406 (00 for drive 0-3, continuing 04 for the following 2 drives and 06 for the USB key) I hope I correctly remember the values (System is currently busy) and the values might help others. Thanks again!
    1 point
  6. As example: If I edit GetCamCnt() in the same way as from version 8.2.7-6222_(40_cams): /* ShmDBCache::GetCamCnt() */ undefined8 ShmDBCache::GetCamCnt(void) { return 0; } Then in the sscamerad (8.2.10) this condition fails here lVar4 = SSShmDBCacheAt(); if ((lVar4 != 0) && (iVar3 = ShmDBCache::GetCamCnt(), iVar3 < 1)) goto LAB_00421c80; iVar3 = UpdateSSCameradStatus(1,*(int *)(param_1 + 0x48)); lVar4 = (long)iVar3; if (iVar3 == 0) { In 8.2.7 (40cams), GetCamCnt is not used in the same way. Only one value was edited in the middle of the program: Original: cVar11 = '\x01'; uVar28 = lVar26 - *(long *)(__mutex_00 + 1) >> 0x3f; if ((long)((lVar26 - *(long *)(__mutex_00 + 1) ^ uVar28) - uVar28) < 0x15181) { cVar11 = __mutex_00[1].field_0x8; Patched: cVar11 = '\x00'; uVar28 = lVar26 - *(long *)(__mutex_00 + 1) >> 0x3f; if ((long)((lVar26 - *(long *)(__mutex_00 + 1) ^ uVar28) - uVar28) < 0x15181) { cVar11 = __mutex_00[1].field_0x8; @BemanCan you take a look at this too? I couldn't quite figure out what the modification does in 8.2.7. I have uploaded them all here: https://drive.google.com/drive/folders/1GE5DK60Zq9EswlYNrQ_E-8eGUaQivFHm?usp=sharing
    1 point
  7. @haydibe got it working on Proxmox by following this video. Thanks much for helping out so far! Technology and talents keep amazing us @pocopico 🙏
    1 point
  8. Aus Mangel an Kernel-Sourcen für DSM7 werden die Treiber-Module nach bestem Wissen und Gewissen von pocopico mit entsprechenden vanila Kernel kompiliert. Syno's Kernel sind ziemlich verbogen (bspw. wilde Patches und Backports die so nicht in den vanila Kerneln vorkommen), so dass Treiber-Module die mit einem vanila Kernel gebaut werden nicht immer zum Syno-Kernel passen.
    1 point
  9. Hallo! Zuerst THX für Dein Replay. 😀 Der Link von Dir war mir schon bekannt. Habe dort kreuz & quer alle möglichen Version ausprobiert. Es gab immer Festplattenfehler was auch hier im Redpill Thread öfters beschrieben wurde. Wenn ich sowie Du die Default Werte mit dem redpil-loader übernehme der ja genau die z.B. Sata-Werte des Mainboards ausließt kommt dieser Festplattenfehler. Habe dann einfach in der "user_config.json" Werte so zum testen aus dem Forum eingetragen. Und siehe da ich kam bis zu dem Punkt wo das *.pat File angefordert wurde. Er startet und nach 70% ist Schluß. Igendwie habe ich auch kein Bock mehr denn irgendwann verliert man die Lust. Aber man darf nicht vergessen es ist ein Test Projekt das sollte man unbedingt wissen. Auf jeden Fall TOP das es bei Dir klappt. 👍 cu-ya
    1 point
  10. @killseeker@synoxpe no. i didn't faced that error, sorry... i'm on an asrock j4005m that boot only from uefi. obviously i disabled secureboot. i've tried again with a different flash drive and it just works. at this time, i wrote the "tinycore-redpill.v0.4.4.img" image with rufus on windows. then i started a virtual machine with linuxmint edge 20.3 cinnamon x64 installed and followed the same steps that i posted previously. you clearly have to change "my" /dev/sdb with the right path pointing your device.
    1 point
  11. As it is more cosmetics you really don’t need it. It is interesting when you have more drives. Easier to find which one needs to be replaced …
    1 point
  12. Каталог /etc.default снести.
    1 point
  13. Hello Sbafs Non je n'ai pas installé open-vm-tools. Le l'avais fait pour les versions précédentes du DSM mais je n'avais pas trouvé cela utile pour mon usage. Ceci dit, la procédure de compilation est très bien faite et documentée. ça prend un peu de temps mais c'est sans problème de le faire. Oui Sabrina, je pense à faire un petit tutoriel très simple en partant de l'image que tu as réalisée. Bien à vous. Fred
    1 point
  14. I'm running DS3615xs DSM 7.0.1-42218 on my MicroServer Gen8 G1610T. I've compiled it from source a while ago and I remember it took me some trouble to figure out how to add a repository for the ethernet drivers. Anyways it has been running rock solid up until now, surveillance station, docker + portainer and even a Windows 10 VM and I'm very happy with it. Now I believe update DSM 7.0.1-42218 Update 1 and 2 are out now. What's the best way to build a new image (which includes the ethernet driver)?
    1 point
  15. Before build the loader you should to add the extension from jimmyGALLAND of acpid. ./rploader ext platform add https://github.com/jimmyGALLAND/redpill-ext/raw/master/acpid/rpext-index.json
    1 point
  16. DS918+ 7.0.1-42218 is working good on my bare metal, but synology photo face recognition is still not working even with real SN & Mac
    1 point
×
×
  • Create New...