Leaderboard

Popular Content

Showing content with the highest reputation since 07/28/2021 in all areas

  1. Let us first pull you from the dark - we just added a new repo to the collection. "We think you're gonna love it"[tm] RedPill Load Without further ado: RedPill Loader Builder Repo is live - https://github.com/RedPill-TTG/redpill-load It's a loader image generator which we worked on for quite some time. From the start we have to apologize for using BASH - it was a mistake and if you look into the code you will understand why What it can do for you? However, it works. In short, it automates the following process in "normal" mode: Checks if the
    19 points
  2. I have made some tests. - Get a Backup of my 2 Drives from DSM 6.2.3-25426 junLoader Machine. - Make a redpill loader for 6.2.4 and create a new machine (proxmox) - attach the backup hdds to the new machine and startup - It comes the assistant and i update to 6.2.4 - WORKS - After that i build the redpill loader for DSM7 and replaced the 6.2.4 in the new machine and startup - it will hang forever at "------------bootup-smallupdate" - So i patched out this part from linuxrc.syno.impl and startup again - Now it works an the DSM7 Migratio
    10 points
  3. That's a lot of posts! You're quick and eager to test guys We're trying to sort out through the posts and it actually gets hard even at this stage to decipher bugs from questions while keeping each bug/missing feature flow separately. So in the future if you have obvious bugs with something exploding or not working on a specific platform but working on another etc please, can you add a ticket on GH? That way we can attach all files and screenshots for a given problem with all people reporting to a given issue. To make it simpler to separate and not create 101 topics at
    7 points
  4. The RedPill is back! As some of you may be aware a lot of research materials as well as the code for parts of the kernel module were pulled from GH. We're happy to report it's back and fully public! Before further ado we have a small sneak-peek of the current state: Repositories Both LKM code and the research materials are present in two repositories. Both are automatic forks from our internal serves and are updated few times a day. - RedPill LKM: contains the current version of the Linux kernel module source code along with implementation details description - D
    5 points
  5. As @smoojay mentioned this is the output from ttyS0 and ends up as expected - rest of it will be on ttyS1 for Linux v3 or ttyS2 for Linux v4. This is an issue with how synobios and DSM kernels are handling serial ports. There's a plan to make it work properly with 2 serial ports attached and "redirect" synobios to ttyS1. The current state is a byproduct of being a pre-alpha You're using GCC which is too new. Kernel v3 (which is 10 years old) has an official list of supported GCC versions and the newest is <sadness approaches> .... v4.9.2. This is why RedP
    4 points
  6. I think I should add that I have been building on WSL(2) On the Ubuntu 20.10. And it is working, so we can confirm WSL compatibility.
    3 points
  7. A person showed a screenshot of his successful installation of 7.0 in the telegram. In my further understanding, he used your redpill-lkm, but he used the 7.0 version of the code to make, the specific way is to use https:/ /github.com/SynologyOpenSource/pkgscripts-ng this repo, and built a 7.0 environment, I also tried to use ds.apollolake-7.0 to make redpill.ko, the following is the information obtained using modinfo: , but I directly put this redpill .ko is packaged into BootLoad using redpill-load and cannot install version 7.0. I don
    3 points
  8. @T-REX-XP I have written that i use a VM under Proxmox. And the virtio drivers for this are in this loader. I now have added my old Variables for Disk rearange in the user_config cmdline ("DiskIdxMap": "0F00", "SataPortMap": "15") and this is also working like before. For a very early Stage this loader works absolut fantastic Edit: The redpill only works with CPU "kvm64". When i switch to "Host" (i5-7260U) the redpill will crash. Then i have compiled the redpill again on the Proxmox7 Host itself... but no luck: invalid module format I think
    3 points
  9. Just FYI for those testing, probably unwise to display your serial number (even if it is generated), as it could theoretically give Synology a way to identify you/your IP/etc.
    2 points
  10. @GhostlyCrowd I also tested the toolchain. You are right, all is working fine. Build on latest Debian Bullseye Machine.
    2 points
  11. OK in the next Step i have used Backups from my two Harddisks from the old Xpenology Install and mountet this backups to the new redpill Xpenology and fired it up. The old Installation was detected and i selected migrate and installed the new DSM Version, reboot, all is fine, all Data are there
    2 points
  12. No, the internal nic is fine.
    2 points
  13. Thanks for all your work... Does it work on baremetal? Would it be possible to have a Plug and play loader, as jun's one?
    1 point
  14. I have ds3615 6.2.4 running on Proxmox, great job ThorGroup. I suppose that if I add the drivers *.ko in the EXT folder of the bootloader generator and I build a new image, I could use in a Baramental server, isn't it? or I'm wrong.
    1 point
  15. I've installed on Debian 8 extraoficial the jq 1.5 , it's working. Thank you loomes. I've used the following: wget https://github.com/stedolan/jq/releases/download/jq-1.5/jq-linux64 chmod +x jq-linux64 mv jq-linux64 $(which jq)
    1 point
  16. Никак, по крайней мере никто этим даже не заморачивался и вряд ли будет. Дрова в системе есть под USB стики.
    1 point
  17. Compiled lkm on Ubuntu 1404 desktop vm, loader on Debian 10. Upgraded (keep settings option) 25426 to 25556 ok. Installed Drive packages and Surveillance etc Auto shutdown/start ok Drive syncing with DSM7 on two real synos, testing ok so far HP N36L n360t network card 3615xs
    1 point
  18. - Outcome of the installation: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP MicroServer Gen8 [ Onboard NIC + Syba SATA III 4 Port PCI-e (SI-PEX40064 / Chipset: Marvell 88SE9215) ] - Additional comment: Manual Update
    1 point
  19. Just tested using their tool chain (apollolake-gcc493_glibc220_linaro_x86_64-GPL.txz) rather than Debian 8 with GNU GCC 4.9 and it does indeed work, built on Ubuntu 20.10 So this is probably the path of least resistance for this project is to use the proper tool chain as well. START /linuxrc.syno [ 2.343812] redpill: module verification failed: signature and/or required key missing - tainting kernel [ 2.345495] <redpill/redpill_main.c:23> ================================================================================================ [ 2.347283] <redpill/redpill_m
    1 point
  20. Была как то проблема с серваком, тоже супермикро, правда на простом линухе. Тоже зависал рандомно, не помню правда были ли перезагрузки. Долго искал проблему. Оказалась в сетевой (интел) или в её драйвере igb. Разрулил опциями (точно уже их не вспомню) TSO LSO LRO GRO, помоему повыключал их и помогло. Попробуйте и в сино порыть в эту сторону. Или попробуйте на этом железе развернуть другой линукс и убедитесь что в аппаратной части всё стабильно. PS. SMART кстати не сказать что в идеале, не криминал, но и не идеал... если это WDшник, почистите контакты на плате с обратной сто
    1 point
  21. i become this on Proxmox: START /linuxrc.syno [ 5.264284] redpill: module verification failed: signature and/or required key missing - tainting kernel [ 5.265523] module: redpill: Unknown rela relocation: 4 insmod: can't insert '/usr/lib/modules/rp.ko': invalid module format It boots and will find by find.synology but i cant install DSM (error 13) Ok got it working At first i compiled lkm on a debian buster (gcc8) and then Bullseye (gcc10) Machine. Then redpill dont work. Now i have compiled on a very old Wheezy Machine ( gcc4) and the loader itself o
    1 point
  22. two tips: 1, as @jumkeysaid, need boot from usb, in proxmox ,you can add agrs to /etc/pve/qemu-server/{VM_ID}.conf: args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/{VM_ID}/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5' But in proxmox, usually the boot image is converted to a boot disk through the qm command, so that the system files can be managed in the virtual machine management interface, and the method of adding args makes the startup of the virtual machine full of risks (for example, the virtual fi
    1 point
  23. E2C45CC9EEEE echo "args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/{VM_ID}/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=5'" >> /etc/pve/qemu-server/{VM_ID}.conf
    1 point
  24. OT Not from the Dark, From Asgard or From the Walhalla
    1 point
  25. Not an errors. Just Status notifiers/Commands goes to the PIC16F1829 According to: #define UART2_CMD_BUTTON_POWER 0x30 /* '0' */ #define UART2_CMD_SHUTDOWN 0x31 /* '1' */ #define UART2_CMD_BUZZER_SHORT 0x32 /* '2' */ #define UART2_CMD_BUZZER_LONG 0x33 /* '3' */ #define UART2_CMD_LED_POWER_ON 0x34 /* '4' */ #define UART2_CMD_LED_POWER_BLINK 0x35 /* '5' */ #define UART2_CMD_LED_POWER_OFF 0x36 /* '6' */ #define UART2_CMD_LED_HD_OFF 0x37 /* '7' */ #define UART2_CMD_LED_HD_GS
    1 point
  26. Just a thought. Has anyone engaged or shared this thread with ppl on XDA forums. There are a lot of eager devs looking for a new challenge. Who knows?
    1 point
  27. Установка и настройка DSM на основе версии 6.2.3 Ну вот, муки поиска позади и вы пришли к эпохальному решению создать сервер на основе Хрени.....)))) Надеюсь, что подошли к этому шагу с долей познаний и оценили свои возможности. Данный мануал является общим, без акцента на частные настройки и особенности применяемого вами железа, такие как настройки БИОС_а и хардово-софтовые нюансы вашего железа. Процедура описана на основе последней возможной (на данный момент) для установки версии DSM. Но она применима и на ранние версии DSM 6 . Более древние уже не помню )))
    1 point
  28. Yes. From the loader I chose to reinstall. He kept the raid and the file structure intact.
    1 point
  29. yes that would be next to try if that fails you could use a rescue linux, mount the raid1 system partitions (1st on every diks) and format that /dev/md0 (check if it contains the system before doing that, not so good to format you data volume) https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ with the system partiton empty it should be possible to make a reinstall without deleting data on your data volume if you want access to you data you could boot open media vault (a nas system) from a different source (like usd) and
    1 point
  30. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - AsRock C2550D4I - Additional comments: Updated directly from DSM Control Panel. Reboot required. Intel X540-T2 continues to work OOB.
    1 point
  31. dis you connect a monitor to check if its really starting (even better a 0-modem cable to check serial console) this atom hardware is known to die early because of a cpu flaw from intel, lost my C2550D4i board that way also dsm version and driver compatibility can cause problems too, like having 6.2.2 and updating to 6.2.3 (driver problem) or having dsm 6.1 (loader 1.02b) and updating to 6.2.x that would need a new loader 1.03b v15284 is dsm 6.1 so maybe you updated to 6.2.3 and need a now loader?
    1 point