Leaderboard

Popular Content

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

  1. 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
    60 points
  2. Update time! Support for v4.4 kernel TL;DR: it now works with v4.4 After some of you took a stab at compiling the LKM for Linux v4.4 (presumably for DS918+ support) we did too. We didn't see any PRs besides a small patch from @jumkey (thanks!). However, the reality came to be much MUCH more complex, especially if we want to keep the consistent codebase for all kernels. So, it took 400 lines over 12 commits by 3 people: https://github.com/RedPill-TTG/redpill-lkm/compare/7f85cb2ceff44d6914135bf3841eb3cb2148af11...1abcbe13df39055dc8b925f74a00a75163157d60 However,
    20 points
  3. 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
  4. Update So a small update first: we've got the PCI emulation layer working! The PCI standard is truly an awful thing, which kernel developers found out too and put a fair warning on the top of their PCI docs: The world of PCI is vast and full of (mostly unpleasant) surprises. Since each CPU architecture implements different chip-sets and PCI devices have different requirements (erm, "features"), the result is the PCI support in the Linux kernel is not as trivial as one would wish. Linux doesn't have any high level APIs to add devices or buses. Because of this we h
    11 points
  5. 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
  6. 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
  7. 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
    7 points
  8. 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
  9. Here we go: TerraMaster Fx-422 BIOS mod by Vortex Enabled: - CSM Options - RTC Alarm Options To flash (use FreeDOS or something): AFUDOS.EXE BIOSMOD.ROM Enjoy. tm_422_biosmod_vtx.zip
    4 points
  10. 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
  11. 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
  12. @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
  13. You're not wrong of course, but hardware continues to improve and new features are no longer compatible. Since my 10th gen i3 wont work (plex transcoding, etc) I had to buy older stuff to get my desired outcome (4c/8t). That used i7-7700 and an older motherboard cost more than the i3-10100 and motherboard and it's technically slower. I've been using Xpenology since 5.x, I use it instead of something like Unraid or OpenMediaVault because I have official Synology units and love the ecosystem. Folks like IG88 and others have done standout work getting us compatibility drivers for newe
    3 points
  14. This is a bit OT, but we get what we get. Synology is selling you a 14nm 1st gen circa 2018 CPU as a new product. It's no mistake that older gen hardware tends to work better. And even if a platform were not supported under kernel 4.4.x, all Syno has to do is backport the kernel mods for that particular CPU/chipset/NIC and they could care less about other new hardware. I don't think the objective of redpill or any other loader should necessarily be to be compatible with ALL hardware, particularly the newest stuff. It's great if it can work out that way, but I would consider a l
    3 points
  15. Respect to everyone giving up their time to work on this
    3 points
  16. У меня HP Microserver N54L, проблема возникла с пятым хардом, не в корзине, он отдельно стоящий (или лежащий ))) , так вот начали харды Бэды выдавать.... Естественно поиски пошли по наиболее сложному пути. Правка кода, логи там всякие и прочая хренотень, ни разу не относящаяся к проблеме. И уже вытрахав себе мозг, решил проверить напряжение на Хардах. Так вот на этом, проблемном была просадка . В общем оказался переход Молекс - Сата. Заменил и всё в норме уже пару лет. На G8 схемотехника несколько иная, но если у вас проблема только в двух, конкретных слотах, то имеет смысл обра
    3 points
  17. 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
  18. @GhostlyCrowd I also tested the toolchain. You are right, all is working fine. Build on latest Debian Bullseye Machine.
    2 points
  19. 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
  20. No, the internal nic is fine.
    2 points
  21. Да завсегда на здоровье ....))) Обращайтесь...
    2 points
  22. Hi, everyone, Thanks for you patience. A new ds918 loader support 6.2/6.21 is uploaded. whats new: uefi issue fixed. i915 driver updated. link https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA (for DS918+) - v1.04b ---Beginning of addition by polanskiman--- link https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b link https://mega.nz/#!zcogjaDT!qIEazI49daggE2odvSwazn3VqBc_wv0zAvab6m6kHbA (for DS3617xs) - v1.03b Please read this topic to know what loader to chose
    2 points
  23. Hi Vortex, Not to worry about the instructions. I did some Youtube searches and found a method that worked. Managed to load up 6.1 on 1.02b. Everything works perfectly on first attempt. Very happy and thank you again for your help in doing this. You Da Man!
    2 points
  24. So whether we can establish a developer discussion group, similar to discord, telegram or others, I don’t know if this is compliant, I will try to establish one first, and welcome everyone to join so that we can iterate this project more efficiently. telegram: https://t.me/joinchat/eYcaYV4ywDY4MWU9
    2 points
  25. @ThorGroup To echo everyone else thus far, thanks a TON for your efforts on this. Exciting to see the community and development for new versions still alive. P.S. Really looking forward to a DSM v7 compatible solution, sign me up as a tester
    2 points
  26. Looking forward to this release however I do have a question users on Juns loader will they be able to upgrade to redpill without the need of starting from scratch etc? Also if you planning on making a website for this release etc I can host it for you free of charge as a thanks from the community just send me a PM
    2 points
  27. Buenas, Después de bastante tiempo que tiene este hilo, me vuelve a pasar lo mismo. Compré otro servidor igual (Microserver Gen8) e instalé ahí el DSM 6.20 y volví con el problema, con el WOL activado en BIOS y con la opción de Habilitar "WOL en LAN1" y "WOL en LAN2" activadas el servidor sólo levanta por WOL cuando al apagarlo, después apago la regleta de corriente donde está conectado, si no la apago no levanta. Pues lo que conseguido solucionar de nuevo, la otra vez debí dejarlo editado después de tantas pruebas y ni me di cuenta, pero el problema es que Xpenolo
    2 points
  28. in dont think so, synology had 7.0 preview/beta for DS3615xs and DS3617xs so people having installed that would not be able to downgrade back to 6.2.4 and should not be able to get 7.0 release? seems unlikely, maybe they will just wait a little longer for some units to release 7.0 [a litltle search on the internet and a few minutes later] "... DSM 7.0 final release for FS, SA, XS/XS+ and DVA series models is currently under development and will be available in Q4 (October – November – December) of 2021. ..." so there is no cpu problem as they will
    2 points
  29. POWERBUTTON_6.2-0002.SPK
    2 points
  30. Установка и настройка DSM на основе версии 6.2.3 Ну вот, муки поиска позади и вы пришли к эпохальному решению создать сервер на основе Хрени.....)))) Надеюсь, что подошли к этому шагу с долей познаний и оценили свои возможности. Данный мануал является общим, без акцента на частные настройки и особенности применяемого вами железа, такие как настройки БИОС_а и хардово-софтовые нюансы вашего железа. Процедура описана на основе последней возможной (на данный момент) для установки версии DSM. Но она применима и на ранние версии DSM 6 . Более древние уже не помню )))
    2 points
  31. 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
  32. I do not know if there is a fix. All I am saying is what he posted here.
    1 point
  33. Resolved thanks to VORTEX. Everything works great after he supplied a BIOS mod:
    1 point
  34. I have this https://www.amazon.de/-/en/10Gtek®-Gigabit-PCIE-Network-I350-T4/dp/B01H6NE4X2/ref=sr_1_3?crid=1LDVHK8KG489E&dchild=1&keywords=i350-t4&qid=1626087365&sprefix=I350%2Caps%2C244&sr=8-3 I pass this through and never had an issue with it (DS918+). i350 chips was launched in 2011. I do not see any reason not to be supported.
    1 point
  35. 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
  36. You can find more info here. I do not know if this post can answer all your questions... For now, while kiler129 still tries to make a new loader to support 6.2.4+ there is hope. He answered also questions about DSM 7... in the post he also said that Synology did not do this on purpose in order to stop XPE...they changed the kernel enough to break the loader. This is all they did and it was not in purpose... Anyway, read the post I believe you will find it very interesting and educational.
    1 point
  37. Bonjour, Je poste ici un solution (ou plutôt 2 selon votre cas) qui est connue et qui marche légalement pour disposer de Surveillance Station avec plus de 2 caméras. Le concept repose sur la fonction CMS de SS et le fait d'avoir n instances DSM virtualisés. En effet avec CMS, SS regroupe toutes les instances de SS en une seule interface et in fine 2 caméras par instance de SS. il va de soit que selon ce principe on peut avoir n caméras, mais il faut n/2 instances de DSM en parallèle. C'est le prix à payer pour ne pas avoir à payer le prix exorbitant des licences de caméras sup
    1 point
  38. you would need a extended driver set (extra/extra2.lzma) AND 918+ has a default limit of the last driver list was here, newer extra's will have at least this version, usually newer https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/ "NETWORK DRIVERS LIST - Click here to see (Reveal hidden contents)" you see X553 as supported with ixgbe.ko, i#m also sure you would find something about that board in the forum search the 2 nic limit is explained here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-fo
    1 point
  39. Since Let's Encrypt changed their API from v01 to v02 it isn't possible to request certificates when using DSM 6.1.X. Workaround: exchange the syno-letsencrypt module with a version from a DSM 6.2.X release. Preparations: enable SSH access on your box download this file (from an original DS920+, DSM 6.2.3-25426 Update 3), extract it and copy it to a shared folder of your NAS: https://mega.nz/file/889yCJ5S#Y3UtxPe_qQfRkpxQeALzsFEAIx_NDxLVx2FPLu9HT_I After you have downloaded the file mentioned open a SSH connection to your NAS Backup
    1 point
  40. Should we be concerned? Long term, with the intermediate updates not working? (assuming we already have backups and have all the functionality we need) Define concern? Is there anything that can be done with 6.2.4 that cannot be done with 6.2.3? The assumption has always been is that any update has the possibility of breaking the loader. Could DSM 6.2.3-25426 Update 3 possibly be the last safe Xpen Version for us using Jun's Loaders? Maybe. Is Jun still kicking around to come up with a possible solution? Or anyone else? Jun is the only one that can ans
    1 point
  41. So I leave 3 days on holidays and everyone forgets the rules... They are rather simple and stated just above the first post. All Off-Topic posts have been moved.
    1 point
  42. What other controllers are in the system? At least one virtual SATA controller for the loader, but do you have a second one? You will need to tweak your controllers, adjust SataPortMap and DiskIdxMap, or all of the above to correct it. https://xpenology.com/forum/topic/12470-how-to-play-around-with-hdd-mapping-with-sataportmap-and-diskidxmap/ If you see 1/2 of your HDD's and you are not out of slots, it's likely you have a port multiplier on your controller which is not supported. Post the controller type and someone here will know for sure.
    1 point
  43. Just a recap for those who'll want to try NVMe cache because all the thread is quite messy imho. The above shell script with DSM 6.2.3-25426 Update 2 (on DS918+ , indeed) does not work anymore. At least in my experience it leads in an incorrect state where the two NVMe are not recognised as the same and therefore they cannot be used for a necessary RAID 1 in case of R/W cache. The only thing is really working at the moment is a copy of the libsynonvme.so.1 to the right path. So put this file in a public zone of your volume (this is my case) or wherever you like and th
    1 point
  44. Came across this when trying to fix the same issue I was having with installing TrueNas. After several changes the one that worked for me was to make the following change in BIOS: Advanced>CSM Config> Boot option Filter (UEFI & Legacy) <this is the default> Storage = UEFI Other PCI devices = UEFI I then put my os drive in P0 then had the rest of my drives after that, but did did test this with TrueNas installed on a USB and had it in the internal header and it worked as well. I should note that I have the F5-221, but BIOs versi
    1 point
  45. kernel modules/drivers are specifically compiled for a kernel (-versions) and even distributions it's not like windows where you can download a driver somewhere and just put it in so don't take any *.ko file, stick it in and expect it to work if you haven't build the *.ko yourself or don't know exactly where it came from, expect it to fail I'm no expert but as there is no how-to here in the forum - lets start one hopefully other will correct and help refine or take over and rewrite it some steps are made in windows (osfmount) but will also possible in the chroot e
    1 point
  46. ну я это и имел в виду, думая, что DSM на хосте ESXI
    1 point
  47. Можно и так . Но, это уже два жужащих блока)) А VMware ESXI 6.5 это отдельная история никак не связанная с DSM, хотя есть задумки поставить DSM на VMware ESXI 6.5, на которой будут висеть некая серверная ось и DSM все в отдельных контейнерах, и посредством ТМ все будет доступно. При этом будет один системник, а DSM можно смело перегружать, туда даже андроид можна всунуть. Может сегодня попробую, отпишусь. В самом VMware ESXI 6.5 DSMу можно выделить вполне реальные не виртуальные диски. То есть в связке с DSM , будет работать еще какая нибудь система ( на выбор) и вс ена одном системни
    1 point
  48. либо дунднс начали предоставлять тоннели, либо ты не до конца постиг сетевую топологию провайдеров, в частности nat и серый ip
    1 point