Jump to content
XPEnology Community

navhawk

Rookie
  • Posts

    6
  • Joined

  • Last visited

Posts posted by navhawk

  1. Hello, I have some trouble on my xpenology with intel xeon e-2278ge on proxmox, when I use it on baremetal it was the same.

    When I apply your patch "ch_cpuinfo" latest at the moment version 4.2.1-r01 it show correct info about processor but if I push "details" it forward me to this link and it is just an intel web.
     

    Спойлер

     

    newutility.thumb.jpg.3d560e41c3052275e435a5383462a2bd.jpg

    new.jpg.1f79ad7c57a9152129b56d4c4b2a43f2.jpg

     

    When I used old version "ch_cpuinfo" 3.3.1-r01 when I push "details" I forward to meto the search link with my processor name in a search bar where I can chouse correct processor.
     

    Спойлер

     

    oldutility.thumb.jpg.8d86f302ccef3e91f08f36bb478e476b.jpg

    old.jpg.d9a4bd2ed732ab0f61cddd1e78d229b0.jpg

     

    Спойлер

    root@dsm-test:/volume1/test# cat /proc/cpuinfo
    processor       : 0
    vendor_id       : GenuineIntel
    cpu family      : 6
    model           : 158
    model name      : Intel(R) Xeon(R) E-2278GE CPU @ 3.30GHz
    stepping        : 13
    microcode       : 0xea
    cpu MHz         : 3311.782
    cache size      : 16384 KB
    physical id     : 0
    siblings        : 1
    core id         : 0
    cpu cores       : 1
    apicid          : 0
    initial apicid  : 0
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 22
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology pni pclmulqdq vmx ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 arat md_clear arch_capabilities
    bugs            : spectre_v1 spectre_v2 spec_store_bypass swapgs taa srbds
    bogomips        : 6623.56
    clflush size    : 64
    cache_alignment : 64
    address sizes   : 39 bits physical, 48 bits virtual
    power management:

    May I ask you to look at the issue? Thank you.

    • Thanks 1
  2. В 04.03.2023 в 11:10, Igareok сказал:

    Hello. I need to use DSM 7.0.1

    I try to build loader for DS3615, or DS3622xs+, but its end with same error>

    [#] PAT file /home/tc/redpill-load/cache/ds3622xsp_42218.pat not found - downloading from https://global.download.synology.com/download/DSM/release/7.0.1/42218/DSM_DS3622xs+_42218.pat
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100  389M  100  389M    0     0  10.3M      0  0:00:37  0:00:37 --:--:-- 11.4M
    [#] Verifying /home/tc/redpill-load/cache/ds3622xsp_42218.pat file... [ERR]
    [!] Checksum mismatch - expected f38329b8cdc5824a8f01fb1e377d3b1b6bd23da365142a01e2158beff5b8a424 but computed a222d37f369d71042057ccb592f40c7c81e9b988a95d69fa166c7c2a611da99c
    
    *** Process will exit ***
    FAILED : Loader creation failed check the output for any errors

    And this problem persist only on 7.0.1-42218 and 7.0.1-42218-JUN version.

    Tried different USB sticks, different loader versions, different motherboards, every time - same error.

    Please help.

    The same issue with latest at the moment "tinycore-redpill-uefi.v0.9.4.5.img" for DS918+. Looks like synology changed the pat files with DSM_xxxxxx_42218 version and to fix the error "Checksum mismatch" during bilding process the checksum in installation script has to be updated but how to do it?.....

    Please help

  3. 7 часов назад, pocopico сказал:

     

    I suggest you backup your loader and create a TCRP one. You can use the latest TCRP to go through the postupdate process. 

    I tried to make 6.2.4-25556 bootloader with tinycore-redpill.v0.4.6. Even installtion was successull but after reboot dsm has the status "not installed". But at the same time 7.1 is working...

  4. В 24.01.2022 в 15:21, Laktor сказал:

    С tinycore-redpill, не прокатило на моей материнке, не умеет она в legacy

    ASrock 4105-itx DSM 918+ 6.2.3.

    У меня Asrock J5005 тоже не умеет грузиться в legacy, загрузка возможна только в UEFI. В итоге в ходе многочисленных попыток и "пересозданий" загрузчиков удалось загрузиться только с версией DSM 7.0.1, остальные не хотят грузиться в UEFI, а хотелось бы 6.2.4..... Поэтому пока остаюсь на Jun's loader 6.2.3-u3.

     

  5. 13 часа назад, Buny74 сказал:

    You have to make the first partition active otherwise it will not boot

    I have the same problem. The image which I made by using redpill-helper-v0.12 doesn't boot even if I made the first partition as active. I tried to use several usb sticks. Off course I recreated a new image for every usb sticks with correct vid-pid. But boot is not successfull yet... What else can be a problem?

    15 часов назад, Aigor сказал:

    but at this moment i have boot problem , neither usb stick or microsd with dsm7 are able to boot

     

    Were you able to boot finally?

×
×
  • Create New...