asdbya Posted December 13, 2022 Share #576 Posted December 13, 2022 8 минут назад, Orphée сказал: I had to use V2V converter to convert vmdk file to FLAT esxi VMDK. I used the same way and got the same two files. tinycore-redpill.v0.9.3.0-flat.vmdk tinycore-redpill.v0.9.3.0.vmdk Quote Link to comment Share on other sites More sharing options...
asdbya Posted December 13, 2022 Share #577 Posted December 13, 2022 well...that's what I have: also the configuration of HDD: and then Do you have the same config? Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 13, 2022 Share #578 Posted December 13, 2022 (edited) 4 minutes ago, asdbya said: well...that's what I have: also the configuration of HDD: and then Do you have the same config? Check your BIOS VM settings (boot order) Or delete your VM and start again (it happened to me once) Edit : change from EFI to Legacy BIOS Edited December 13, 2022 by Orphée 1 Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted December 13, 2022 Share #579 Posted December 13, 2022 (edited) 26 минут назад, asdbya сказал: well...that's what I have: also the configuration of HDD: and then Do you have the same config? Make sure you have 2 sata disks, 1st (0:0) with vmdk, 2nd (0:1) for the system, and try Legacy bios as Orphee suggested, and yes I downloaded vmdk 0.9.3.0 from Pocopico repository, also you can try 0.9.2.9.vmdk, and make sure at the Boot menu to use SATA boot, not USB Edited December 13, 2022 by dimakv2014 Quote Link to comment Share on other sites More sharing options...
asdbya Posted December 13, 2022 Share #580 Posted December 13, 2022 25 минут назад, Orphée сказал: Edit : change from EFI to Legacy BIOS that's the solution. thanks. Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted December 13, 2022 Share #581 Posted December 13, 2022 Только что, asdbya сказал: that's the solution. thanks. 2 минуты назад, asdbya сказал: that's the solution. thanks. Grats mate 1 Quote Link to comment Share on other sites More sharing options...
asdbya Posted December 13, 2022 Share #582 Posted December 13, 2022 10 минут назад, dimakv2014 сказал: Make sure you have 2 sata disks, 1st (0:0) with vmdk, 2nd (0:1) for the system btw... I used: 0:0 and 1:0 and it worked. than I added HDD3 for storage under SATA 1:1 Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted December 13, 2022 Share #583 Posted December 13, 2022 1 минуту назад, asdbya сказал: btw... I used: 0:0 and 1:0 and it worked. than I added HDD3 for storage under SATA 1:1 As long as 0:0 for vmdk it will work ) 1 Quote Link to comment Share on other sites More sharing options...
wot Posted December 23, 2022 Share #584 Posted December 23, 2022 (edited) Hello I'm trying to boot DVA1622 in ESXi 8.0 but no matter what I do the existing new disk stay in blank... I did try v0.9.2.9 and v0.9.3.0 same result... Edited December 23, 2022 by wot Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 24, 2022 Share #585 Posted December 24, 2022 22 hours ago, wot said: Hello I'm trying to boot DVA1622 in ESXi 8.0 but no matter what I do the existing new disk stay in blank... I did try v0.9.2.9 and v0.9.3.0 same result... Someone already reported the same issue. I don't remember if this is one the forum it on GitHub. But the "solution" from last report was too revert back to ESXi 7.x Unless you find a workaround... Maybe the disk is too small for ESXi 8.0... you could try to raise its size. Quote Link to comment Share on other sites More sharing options...
tc2 Posted January 4, 2023 Share #586 Posted January 4, 2023 DVA1622 AI works on VM After I had successfully make AI working on the baremetal NUC 6 Skill Canyon, I am now able to make it working on ESXi 6.7 on the Quartz Canyon nuc9vxqnx w/ GPU passthough for Intel UHD 630. I guess it's due to a Pro version of NUC with Xeon processor that supports with Vt-D. My next step would be passthough a Quadro P2000 for DVA3221 in VM on the same ESXi box as soon as it arrives. 2 Quote Link to comment Share on other sites More sharing options...
pafftis Posted January 5, 2023 Share #587 Posted January 5, 2023 Good afternoon, I have an intel nuc on a j3455 processor. I want to install xpenology dva1622. Can you tell me if face recognition, cars will work correctly? At the moment I have 6.4.4 xpenology installed on my mini PC. Does it make sense to switch? Quote Link to comment Share on other sites More sharing options...
Valk Posted January 6, 2023 Share #588 Posted January 6, 2023 Hey guys. Struggling to find any info on my topic: how to force switch my video output to Local Display of SS instead of showing me Redpill Loader final screen with kernel booting? It kinda got itself going on my other MB that had HDMI out but the one I am using right now only has VGA out and it just shows redpill loader. Quote Link to comment Share on other sites More sharing options...
teslaweiler Posted January 6, 2023 Share #589 Posted January 6, 2023 Hi everybody, I am trying to create Face Recognition task but this message appear and it does't allow me to create the task. "Unable to perform this operation because the network connection is unstable or the system is busy. Please try again later" Thank you All for any help Quote Link to comment Share on other sites More sharing options...
Valk Posted January 7, 2023 Share #590 Posted January 7, 2023 19 hours ago, Valk said: Hey guys. Struggling to find any info on my topic: how to force switch my video output to Local Display of SS instead of showing me Redpill Loader final screen with kernel booting? It kinda got itself going on my other MB that had HDMI out but the one I am using right now only has VGA out and it just shows redpill loader. I am gonna answer myself so it would stay here for future ref. So you gotta have i915 driver gpu support (Haswell or newer Intel gen cpu, 4th gen and up to 10) and AMDs are not compatible at all. My Atom 2550 is too old it looks like. Although my other MB with 1037u Celeron is 3rd gen and local display works. See this post Quote Link to comment Share on other sites More sharing options...
mattlh Posted January 11, 2023 Share #591 Posted January 11, 2023 (edited) Le 06/01/2023 à 19:35, teslaweiler a dit : Hi everybody, I am trying to create Face Recognition task but this message appear and it does't allow me to create the task. "Unable to perform this operation because the network connection is unstable or the system is busy. Please try again later" Thank you All for any help same problem here esxi 6.5 hp gen7 micro server Turion 6go allocated Edited January 11, 2023 by mattlh Quote Link to comment Share on other sites More sharing options...
dimakv2014 Posted January 11, 2023 Share #592 Posted January 11, 2023 5 минут назад, mattlh сказал: same problem here esxi 6.5 hp gen7 micro server Turion 6go allocated This problem was answered many times in this topic. 1. Intel cpus with igpu 4th gen and up till 10gen (preferably Intel HD 5** and up), no AMD support. 2. If you have required hardware and want to use AI through ESXi or other hypervisor you should passthrough igpu. 1 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted February 26, 2023 Share #593 Posted February 26, 2023 (edited) Hello, @pocopico Would you need dmesg and lspci from real DVA1622 ? Edit : Running 9th gen i915, (need to unload/reload module at boot) But seems not working for AI with Surveillance Station. /var/log/messages flooded with : 2023-02-26T20:51:07+01:00 DVA1622 coredump[7733]: Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz] size [8263098] 2023-02-26T20:51:07+01:00 DVA1622 coredump[7749]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [16167180] 2023-02-26T20:51:16+01:00 DVA1622 coredump[7789]: Process synofaced[7785](/volume1/@appstore/SurveillanceStation/synoface/bin/synofaced) dumped core on signal [6]. Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synoface/bin/synofaced ] 2023-02-26T20:51:16+01:00 DVA1622 coredump[7809]: Process synodvad[7797](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [6]. Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2023-02-26T20:51:17+01:00 DVA1622 coredump[7789]: Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz] size [8262795] 2023-02-26T20:51:17+01:00 DVA1622 coredump[7809]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [16166536] 2023-02-26T20:51:26+01:00 DVA1622 coredump[7859]: Process synofaced[7855](/volume1/@appstore/SurveillanceStation/synoface/bin/synofaced) dumped core on signal [6]. Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synoface/bin/synofaced ] 2023-02-26T20:51:26+01:00 DVA1622 coredump[7875]: Process synodvad[7860](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [6]. Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2023-02-26T20:51:27+01:00 DVA1622 coredump[7859]: Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz] size [8262615] 2023-02-26T20:51:27+01:00 DVA1622 coredump[7875]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [16167024] Edited February 26, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
reboot Posted February 27, 2023 Share #594 Posted February 27, 2023 On 10/27/2022 at 12:16 AM, dimammx said: OK Going to answer my own question here The issue was faulty memory stick. So a little PSA: if you have an issue and there is no other apparent reason for AI not to work, Check your RAM for errors I have installed on bare metal with Intel® Core™ i5-10400T Processor which has Intel® UHD Graphics 630 iGPU. AI applications in SS do not work. All I read suggest that this iGPU should compatible with AI in SS. Here are the messages from surveillance.log. Feb 27 09:47:28 [13019][13022][ss-service][notice] ssdaemonmonitord.cpp:54:CheckDaemon(): Daemon [faced] stopped abnormally, auto restart. Feb 27 09:47:29 [13019][13022][ss-service][notice] ssdaemonmonitord.cpp:54:CheckDaemon(): Daemon [dvad] stopped abnormally, auto restart. You suggested checking RAM, I am wondering how? Thanks. Quote Link to comment Share on other sites More sharing options...
Orphée Posted February 27, 2023 Share #595 Posted February 27, 2023 I'm still trying to understand how I did but I made HDMI screen work with DVA1622 on my proxmox VM : Maybe it always worked but I just never tested it correctly. I'm using a 9th iGPU so it seems Surveillance AI features aren't working, but at least, direct screen streaming works 1 Quote Link to comment Share on other sites More sharing options...
reboot Posted February 28, 2023 Share #596 Posted February 28, 2023 On 1/4/2023 at 1:10 PM, tc2 said: DVA1622 AI works on VM After I had successfully make AI working on the baremetal NUC 6 Skill Canyon, I am now able to make it working on ESXi 6.7 on the Quartz Canyon nuc9vxqnx w/ GPU passthough for Intel UHD 630. I guess it's due to a Pro version of NUC with Xeon processor that supports with Vt-D. My next step would be passthough a Quadro P2000 for DVA3221 in VM on the same ESXi box as soon as it arrives. I think we have the same iGPU, Intel® UHD Graphics 630. I am wondering how did you make the AI work? Quote Link to comment Share on other sites More sharing options...
Orphée Posted February 28, 2023 Share #597 Posted February 28, 2023 (edited) 1 hour ago, reboot said: I think we have the same iGPU, Intel® UHD Graphics 630. I am wondering how did you make the AI work? So you think it is that easy ? What's your Device ID ? same as on this screenshot ? 3E9B ? Because 3E9B is part of default i915 driver available in geminilake / dva1622 kernel. If like me you are using a addon (3E98 in my case) to run an non genuine module (10th gen ?) then how can you be sure Surveillance Station AI will work with it ? Spoiler : it does not work for me. You may want to look at : /var/packages/SurveillanceStation/target/local_display.default/usr/lib/dri/iHD_drv_video.so If you are good at reverse engineering you probably will find something. Not even sure this is were you look at. Edit : Have fun : (4554.4575): Signal SIGABRT code SI_TKILL (Sent by tkill system call) originating from PID 4554*** WARNING: Unable to verify timestamp for libc-2.26.so libc_2_26+0x3566f: 00007f7a`3b6e766f ?? ??? 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify timestamp for libpthread-2.26.so *** WARNING: Unable to verify timestamp for libtbb.so.2 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 421 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 572 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 452 Key : Analysis.Init.Elapsed.mSec Value: 122839 Key : Analysis.Memory.CommitPeak.Mb Value: 55 FILE_IN_CAB: @synodvad.synology_geminilake_dva1622.42962.core EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007f7a3b6e766f (libc_2_26+0x000000000003566f) ExceptionCode: e0534947 ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000006 Parameter[1]: fffffffffffffffa FAULTING_THREAD: 00004575 PROCESS_NAME: synodvad ERROR_CODE: (NTSTATUS) 0xe0534947 - <Unable to get error code text> EXCEPTION_CODE_STR: e0534947 EXCEPTION_PARAMETER1: 0000000000000006 EXCEPTION_PARAMETER2: fffffffffffffffa STACK_TEXT: 00007f78`de7fad68 00007f7a`3b6e766f libc_2_26+0x3566f STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 23 ** ; kb SYMBOL_NAME: libc_2_26+3566f MODULE_NAME: libc_2_26 IMAGE_NAME: libc-2.26.so FAILURE_BUCKET_ID: LINUX_SIGNAL_SIGABRT_CODE_0xfffffffa_e0534947_libc-2.26.so!Unknown OSPLATFORM_TYPE: x64 OSNAME: Linux 0.0 FAILURE_ID_HASH: {c3092974-4f98-9eb0-0467-98c0f42d6a08} Followup: MachineOwner Edited February 28, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
Orphée Posted March 1, 2023 Share #598 Posted March 1, 2023 Ok, So I progressed a bitwith SS AI with 9th/10th gen CPU. I had to modify the addons from @fbelavenuto https://github.com/fbelavenuto/arpl-addons/blob/main/i915-10th/install.sh I added (3E98 is my IGPU : 0000:01:00.0 Display controller [0380]: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e98]) : #!/usr/bin/env ash if [ "${1}" = "late" ]; then echo "Installing 10th Gen iGPU firmware and drivers" tar -zxvf /addons/i915.tgz -C /tmpRoot/ rmmod i915 insmod /tmpRoot/usr/lib/modules/i915.3E98.ko fi rebuilt the addon package geminilake-4.4.180.tgz for i915-10th folder inside /mnt/p3/ partition.. and removed / built the loader / re-added i915-10th / rebuilt the loader again to make sure my modified addon was added Then at next boot, the module was unloaded/reloaded at early stage : ... [ 3.821039] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:1d.7-1/input0 [ 3.877073] usb 9-1: new full-speed USB device number 2 using xhci_hcd [error]Failed to open /dev/dri/card0 [ 3.989391] clocksource: Switched to clocksource tsc [ 4.014618] Got empty serial number. Generate serial number from product. [ 4.017126] input: Mini Keyboard as /devices/pci0000:00/0000:00:1e.0/0000:05:02.0/0000:07:1b.0/usb9/9-1/9-1:1.0/0003:1997:2433.0002/input/input4 [ 4.069218] evbug: Connected device: input4 ( Mini Keyboard at usb-0000:07:1b.0-1/input0) [ 4.070141] hid-generic 0003:1997:2433.0002: input: USB HID v1.01 Keyboard [ Mini Keyboard] on usb-0000:07:1b.0-1/input0 [ 4.073172] input: Mini Keyboard as /devices/pci0000:00/0000:00:1e.0/0000:05:02.0/0000:07:1b.0/usb9/9-1/9-1:1.1/0003:1997:2433.0003/input/input5 [ 4.125356] evbug: Connected device: input5 ( Mini Keyboard at usb-0000:07:1b.0-1/input1) [ 4.126321] Get empty minor:104 [ 4.126816] hid-generic 0003:1997:2433.0003: input,hiddev0: USB HID v1.01 Mouse [ Mini Keyboard] on usb-0000:07:1b.0-1/input1 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 insmod: can't insert '/lib/modules/etxhci-hcd.ko': File exists Insert n[ 13.848453] geminilake_synobios: module license 'Synology Inc.' taints kernel. [ 13.849448] Disabling lock debugging due to kernel taint et driver(Mindspeed only)... [ 13.854971] synobios open /dev/ttyS1 success [ 13.855499] Fail to get disk 1 led type [ 13.856008] Fail to get disk 2 led type [ 13.856602] 2023-2-28 23:41:57 UTC [ 13.857067] synobios: load, major number 201 [ 13.857623] Brand: Synology [ 13.857981] Model: DVA-1622 [ 13.858356] This is default settings: set group disks wakeup number to 1, spinup time deno 1 [ 13.859461] synobios cpu_arch proc entry initialized [ 13.860117] synobios crypto_hw proc entry initialized [ 13.860708] synobios syno_platform proc entry initialized Starting /usr/syno/bin/synocfgen... /usr/syno/bin/s[ 13.864869] Module [geminilake_synobios] is removed. y[ 13.865578] synobios: unload nocfgen returns 0 addons.sh called with params patches Adjust disks related configs automatically - patches maxdisks=1 [error]Failed to open /dev/dri/card0 /addons/model.dts:6.21-12.7: Warning (unit_address_vs_reg): /internal_slot@1: node has a unit name, but no reg or ranges property /addons/model.dts:13.16-20.7: Warning (unit_address_vs_reg): /usb_slot@1: node has a unit name, but no reg or ranges property /addons/model.dts:21.16-28.7: Warning (unit_address_vs_reg): /usb_slot@2: node has a unit name, but no reg or ranges property /addons/model.dts:29.16-36.7: Warning (unit_address_vs_reg): /usb_slot@3: node has a unit name, but no reg or ranges property /addons/model.dts:37.16-44.7: Warning (unit_address_vs_reg): /usb_slot@4: node has a unit name, but no reg or ranges property /addons/model.dts:45.16-52.7: Warning (unit_address_vs_reg): /usb_slot@5: node has a unit name, but no reg or ranges property /addons/model.dts:53.16-60.7: Warning (unit_address_[ 14.104410] md: md0 stopped. vs_reg): /usb_slot@6: [ 14.105664] md: bind<sata1p1> node has a unit name[ 14.106695] md/raid1:md0: active with 1 out of 2 mirrors , but no reg or ranges prop[ 14.108369] md0: detected capacity change from 0 to 8589869056 erty /addons/model.dts:61.16-68.7: Warning (unit_address_vs_reg): /usb_slot@7: node has a unit name, but no reg or ranges property /addons/model.dts:69.16-76.7: Warning (unit_address_vs_reg): /usb_slot@8: node has a unit name, but no reg or ranges property /addons/model.dts:77.16-84.7: Warning (unit_address_vs_reg): /usb_slot@9: node has a unit name, but no reg or ranges property /addons/model.dts:85.17-92.7: Warning (unit_address_vs_reg): /usb_slot@10: node has a unit name, but no reg or ranges property /addons/model.dts:93.17-100.7: Warning (unit_address_vs_reg): /usb_slot[ 14.137159] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities @11: node has a unit name, but no reg or ranges property /addons/model.dts:101.17-108.7[ 14.142117] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) : Warning (unit_address_vs_reg): /usb_slot@12: node has a unit name, but no reg or ranges property /addons/model.dts:109.17-116.7: Warning (unit_address_vs_reg): /usb_slot@13: node has a unit name, but no reg or ranges property /addons/model.dts:117.17-124.7: Warning (unit_address_vs_reg): /usb_slot@14: node has a unit name, but no reg or ranges property /addons/model.dts:125.17-132.7: Warning (unit_address_vs_reg): /usb_slot@15: node has a unit name, but no reg or ranges property /addons/model.dts:133.17-140.7: Warning (unit_address_vs_reg): /usb_slot@16: node has a unit name, but no reg or ranges property /addons/model.dts:141.17-148.7: Warning (unit_address_vs_reg): /usb_slot@17: node has a unit name, but no reg or ranges property /addons/model.dts:149.17-156.7: Warning (unit_address_vs_reg): /usb_slot@18: node has a unit name, but no reg or ranges property /addons/model.dts:157.17-164.7: Warning (unit_address_vs_reg): /usb_slot@19: node has a unit name, but no reg or ranges property /addons/model.dts:165.17-172.7: Warning (unit_address_vs_reg): /usb_slot@20: node has a unit name, but no reg or ranges property /addons/model.dts:173.17-180.7: Warning (unit_address_vs_reg): /usb_slot@21: node has a unit name, but no reg or ranges property /addons/model.dts:181.17-188.7: Warning (unit_address_vs_reg): /usb_slot@22: node has a unit name, but no reg or ranges property /addons/model.dts:189.17-196.7: Warning (unit_address_vs_reg): /usb_slot@23: node has a unit name, but no reg or ranges property /addons/model.dts:197.17-204.7: Warning (unit_address_vs_reg): /usb_slot@24: node has a unit name, but no reg or ranges property /addons/model.dts:205.17-212.7: Warning (unit_address_vs_reg): /usb_slot@25: node has a unit name, but no reg or ranges property /addons/model.dts:213.17-220.7: Warning (unit_address_vs_reg): /usb_slot@26: node has a unit name, but no reg or ranges property /addons/model.dts:221.17-228.7: Warning (unit_address_vs_reg): /usb_slot@27: node has a unit name, but no reg or ranges property /addons/model.dts:229.17-236.7: Warning (unit_address_vs_reg): /usb_slot@28: node has a unit name, but no reg or ranges property /addons/model.dts:237.17-244.7: Warning (unit_address_vs_reg): /usb_slot@29: node has a unit name, but no reg or ranges property /addons/model.dts:245.17-252.7: Warning (unit_address_vs_reg): /usb_slot@30: node has a unit name, but no reg or ranges property /addons/model.dts:253.17-260.7: Warning (unit_address_vs_reg): /usb_slot@31: node has a unit name, but no reg or ranges property /addons/model.dts:261.17-268.7: Warning (unit_address_vs_reg): /usb_slot@32: node has a unit name, but no reg or ranges property /addons/model.dts:269.17-276.7: Warning (unit_address_vs_reg): /usb_slot@33: node has a unit name, but no reg or ranges property /addons/model.dts:277.17-284.7: Warning (unit_address_vs_reg): /usb_slot@34: node has a unit name, but no reg or ranges property /addons/model.dts:285.17-292.7: Warning (unit_address_vs_reg): /usb_slot@35: node has a unit name, but no reg or ranges property /addons/model.dts:293.17-300.7: Warning (unit_address_vs_reg): /usb_slot@36: node has a unit name, but no reg or ranges property /addons/model.dts:301.17-308.7: Warning (unit_address_vs_reg): /usb_slot@37: node has a unit name, but no reg or ranges property /addons/model.dts:309.17-316.7: Warning (unit_address_vs_reg): /usb_slot@38: node has a unit name, but no reg or ranges property /addons/model.dts:317.17-324.7: Warning (unit_address_vs_reg): /usb_slot@39: node has a unit name, but no reg or ranges property /addons/model.dts:325.17-332.7: Warning (unit_address_vs_reg): /usb_slot@40: node has a unit name, but no reg or ranges property /addons/model.dts:333.17-340.7: Warning (unit_address_vs_reg): /usb_slot@41: node has a unit name, but no reg or ranges property /addons/model.dts:341.17-348.7: Warning (unit_address_vs_reg): /usb_slot@42: node has a unit name, but no reg or ranges property '/etc/model.dtb' -> '/run/model.dtb' System Disk: (not supported in junior mode) Internal Disk 01: /dev/sata1 Esata port count: 0 USB Device 01: 02: 03: 04: 05: 06: 07: 08: 09: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module Assemble args: -u cf345a4c:8b1b14ed:58f5c97e:a6a675f7 /dev/sata1p1 mdadm: /dev/md0 has been started with 1 drive (out of 2). Partition Version=9 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot [ 14.463119] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 14.467268] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota ------------upgrade Begin upgrade procedure [ 14.528991] loop: module loaded [ 14.549703] EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities [ 14.570521] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) Failed to found any patch No upgrade file found [error]Failed to open /dev/dri/card0 ============upgrade ------------bootup-smallupdate mkdir: can't create directory '/tmpRoot/proc': File exists mkdir: can't create directory '/tmpRoot/sys': File exists mkdir: can't create directory '/tmpRoot/dev': File exists Try bootup smallupdate No patch exist. Skip Packed Bootup SmallUpdate Sparse files don't exist. Skip Sparse Bootup SmallUpdate Finished synoautonano ============bootup-smallupdate Wait 2 seconds for synology manufactory device [error]Failed to open /dev/dri/card0 [error]Failed to open /dev/dri/card0 Tue Feb 28 23:42:00 UTC 2023 addons.sh called with params jrExit /dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 root: Start backing up logs in junior mode [ 17.832441] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 17.836693] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 17.913286] VFS: opened file in mnt_point: (/dev), file: (/null), comm: (linuxrc.syno.im) umount: can't unmount /dev: Device or resource busy umount: /etc/mtab: No such file or directory [ 17.927513] VFS: opened file in mnt_point: (/dev), file: (/null), comm: (linuxrc.syno.im) linuxrc.syno executed successfully. Post init mount: mounting none on /dev failed: Device or resource busy [ 17.949857] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 17.953806] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1,prjquota,rootprjquota grep: /tmpRoot/usr/share/init/tty.conf: No such file or directory addons.sh called with params late '/etc/udev/rules.d/50-usb-realtek-net.rules' -> '/tmpRoot/usr/lib/udev/rules.d/50-usb-realtek-net.rules' Adjust disks related configs automatically - late Copying /etc.defaults/model.dtb '/etc/model.dtb' -> '/tmpRoot/etc/model.dtb' '/etc/model.dtb' -> '/tmpRoot/etc.defaults/model.dtb' Creating service to exec ethtool '/usr/sbin/ethtool' -> '/tmpRoot/usr/sbin/ethtool' Installing 10th Gen iGPU firmware and drivers usr/ usr/lib/ usr/lib/modules/ usr/lib/modules/i915.9BA8+9BC8.ko usr/lib/modules/i915.9BC5.ko usr/lib/modules/i915-42962-official.ko usr/lib/modules/i915.3E98.ko [ 18.105226] Module [i915] is removed. [ 18.144756] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 18.145440] [drm] Driver supports precise vblank timestamp query. [ 18.145999] i915 0000:01:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment) [ 18.146817] [drm] Failed to find VBIOS tables (VBT) [ 18.148928] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 18.153757] [drm] Initialized i915 1.6.0 20171222 for 0000:01:00.0 on minor 0 [ 18.238820] i915 0000:01:00.0: fb0: inteldrmfb frame buffer device ... and no more flooding error from Surveillance Station at start (or package installation) But as soon as I try to create a DVA of Face recognition task, the flooding error comes back 2023-03-01T00:54:19+01:00 DVA1622 kernel: [ 755.164018] synobios get empty ttyS current 2023-03-01T00:54:21+01:00 DVA1622 coredump[19475]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [228626228] 2023-03-01T00:54:27+01:00 DVA1622 coredump[19657]: Process synodvad[19618](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [6]. Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2023-03-01T00:54:51+01:00 DVA1622 coredump[19657]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [228820988] 2023-03-01T00:54:57+01:00 DVA1622 coredump[19766]: Process synodvad[19725](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [6]. Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2023-03-01T00:55:20+01:00 DVA1622 kernel: [ 815.767070] synobios get empty ttyS current 2023-03-01T00:55:21+01:00 DVA1622 coredump[19766]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [229425961] 2023-03-01T00:55:27+01:00 DVA1622 coredump[19939]: Process synodvad[19900](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [6]. Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2023-03-01T00:55:51+01:00 DVA1622 coredump[19939]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [228392103] 2023-03-01T00:56:20+01:00 DVA1622 kernel: [ 876.368017] synobios get empty ttyS current 2023-03-01T00:57:21+01:00 DVA1622 kernel: [ 936.967093] synobios get empty ttyS current 2023-03-01T00:58:10+01:00 DVA1622 coredump[20973]: Process synodvad[20088](/volume1/@appstore/SurveillanceStation/synodva/bin/synodvad) dumped core on signal [6]. Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synodva/bin/synodvad ] 2023-03-01T00:58:21+01:00 DVA1622 kernel: [ 997.569014] synobios get empty ttyS current 2023-03-01T00:58:34+01:00 DVA1622 coredump[20973]: Core file [/volume1/@synodvad.synology_geminilake_dva1622.42962.core.gz] size [228239367] 2023-03-01T00:58:59+01:00 DVA1622 coredump[21355]: Process synofaced[15408](/volume1/@appstore/SurveillanceStation/synoface/bin/synofaced) dumped core on signal [6]. Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz]. Cmdline [/var/packages/SurveillanceStation/target/synoface/bin/synofaced ] 2023-03-01T00:59:18+01:00 DVA1622 coredump[21355]: Core file [/volume1/@synofaced.synology_geminilake_dva1622.42962.core.gz] size [87702956] The processes stop crashing/flooding when I delete matching tasks. Tried again to read the core dump : (3c30.3daf): Signal SIGABRT code SI_TKILL (Sent by tkill system call) originating from PID 3c30*** WARNING: Unable to verify timestamp for libc-2.26.so libc_2_26+0x3566f: 00007f55`e138b66f ?? ??? 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify timestamp for libpthread-2.26.so *** WARNING: Unable to verify timestamp for libtbb.so.2 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 343 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2472 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 374 Key : Analysis.Init.Elapsed.mSec Value: 41769 Key : Analysis.Memory.CommitPeak.Mb Value: 55 FILE_IN_CAB: @synofaced.synology_geminilake_dva1622.42962.core EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007f55e138b66f (libc_2_26+0x000000000003566f) ExceptionCode: e0534947 ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000006 Parameter[1]: fffffffffffffffa FAULTING_THREAD: 00003daf PROCESS_NAME: synofaced ERROR_CODE: (NTSTATUS) 0xe0534947 - <Unable to get error code text> EXCEPTION_CODE_STR: e0534947 EXCEPTION_PARAMETER1: 0000000000000006 EXCEPTION_PARAMETER2: fffffffffffffffa STACK_TEXT: 00007f54`a8bf9ce8 00007f55`e138b66f libc_2_26+0x3566f STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 17 ** ; kb SYMBOL_NAME: libc_2_26+3566f MODULE_NAME: libc_2_26 IMAGE_NAME: libc-2.26.so FAILURE_BUCKET_ID: LINUX_SIGNAL_SIGABRT_CODE_0xfffffffa_e0534947_libc-2.26.so!Unknown OSPLATFORM_TYPE: x64 OSNAME: Linux 0.0 FAILURE_ID_HASH: {c3092974-4f98-9eb0-0467-98c0f42d6a08} Followup: MachineOwner same kind of error, don't know what it means. Still no AI working, but at least if I don't use it, no more flood and core dump creation... Quite strange that loading it earlier make things better even if the SS process start lot far after module reloading in both cases. 1 Quote Link to comment Share on other sites More sharing options...
Jerryhze Posted March 9, 2023 Share #599 Posted March 9, 2023 data point: E3-1225 v3, haswell, installed baremetal with ARPL DSM boots fine Surveillance Station works fine but AI DOES NOT WORK Next: going to try some 4th gen and 6th gen desktop CPUs and see if AI works Quote Link to comment Share on other sites More sharing options...
willysoft80 Posted March 11, 2023 Share #600 Posted March 11, 2023 (edited) Hi, I have a Nuc 11 with i7-1185G7 processor. I managed to get a VM running on proxmox with DVA1622, but AI doesn't work. Help me please. Edited March 11, 2023 by willysoft80 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.