Jump to content
XPEnology Community

supajason

Transition Member
  • Posts

    10
  • Joined

  • Last visited

Posts posted by supajason

  1. Installing on baremetal (without GPU).

    ./rploader.sh update now
    ./rploader.sh serialgen DVA3221 now
    ./rploader.sh satamap now
    ./rploader.sh identifyusb now
    ./rploader.sh build denverton-7.0.1-42218

    Boots up and I'm able to select the pat file with completes without errors.

    Once it boots I get the recover screen:

    image.thumb.png.e16d8428ee94f47369b51388a5579654.png

    I just get into a loop after trying to recover and it loads the same page after rebooting/

    EDIT

    Ignore this I was using the wrong pat file....

  2. On 5/10/2022 at 7:24 PM, yeric79 said:

    la solution :

     

    mv -f /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-model.so.1.0 /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-model.so.1.0-bak
    wget https://cdn.jsdelivr.net/gh/jinlife/Synology_Photos_Face_Patch@main/libsynophoto-plugin-model.so -O /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-model.so.1.0
    chmod +x /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-model.so.1.0
    chown SynologyPhotos:SynologyPhotos /var/packages/SynologyPhotos/target/usr/lib/libsynophoto-plugin-model.so.1.0

    Utilisez-vous N54l ? si oui quel modèle utilises-tu ?
    Je suis sur DS3615xs et je n'ai pas de chance.
    Il suffit de réinitialiser et de réessayer.

  3. I'm having real trouble now using Esxi 6.5 with redpill-DS3615xs_6.2.4-25556.

    Looking at serial output it no longer shows that redpill is loaded.

     

    rp.ko is present in usr/lib/modules/ and I can lnsmod it

     

    It seems that the new method for loading rp.ko isn't working for me:

    [    4.983894] I/O scheduler elevator not found

     

    modprobe is located in the sbin folder and I can cat it's contents but when I try and run it I get permission denied.

     

    serial2.outserial1.out

     

     

  4. @RedwinX I'm getting the same issue; When I download the boot image from ESXi it's been formatted.

    When I click to install the pat file it shows (me anyway) 3 disks that be formatted. 2 yes but the 3rd must be the boot image so I'm guess the VID & PID are wrong(?)

     

    I'm going to run the loader again with the PID & VID from juns loader to see if that helps.....nope..no change

    I am using the original VMDK from juns loader that maps to the img file but that should matter right?

     

    Logs: https://pastebin.com/2szJ58zc

     

    image.png.7e7e99cb6dfcf4e225cc1386e1b0a316.pngimage.png.597028ffc54383734a0994f6354bb767.png

×
×
  • Create New...