[TinyCore RedPill Loader (TCRP)]

7 minutes ago, Peter Suh said:

 

 

I mentioned this in the post below today.
The GA-H87N-WIFI has been my main XPE for a long time. It's a DS918+ that hasn't been updated to DSM7 yet, but one of the SHR disks installed in the HBA gets corrupted in the system partition very occasionally.
I do not know the exact cause, but it seems that this phenomenon mainly occurs in low-cost ripper disks.
Of course it's bare metal and there were no serious errors as you mentioned.

 

Thanks for this clarification. Perhaps it's in my case related to the DSM7 loader. I didn't tests with DSM6

 

 

[TinyCore RedPill Loader (TCRP)]

6 minutes ago, Peter Suh said:

 

I searched all the way through that topic.
The model mentioned in this topic is the GA-H87M-HD3.
It is different from the model we have.
Just because the models are similar, it cannot be concluded that the same phenomenon will occur.

Hello Peter,

interesting, this bios reset was the only explanation I could think of. I tried a lot with this Gigabyte board. Reflash bios, replacement of the battery, different usb key. A different loader. Still at every reboot the system halted because of corruption. It's in Proxmox now and no problems at all. Do you have the same board running baremetal without this corruption issue at reboot?

[TinyCore RedPill Loader (TCRP)]

11 minutes ago, Peter Suh said:

 

https://dlcdnets.asus.com/pub/ASUS/mb/LGA1155/P8H61-I_LX_R2.0/E7989_P8H61-I_LX_R2.pdf
If you look at page 31 of this manual, it says that hot plug and ahci are possible.
Be sure to enable both options.
This will help with disk not being found related to sataportmap.

Thanks Peter. Did a test after enabling hot plug but no luck yet. Will do some more tests with different mapping settings.

Regards, Paul

[TinyCore RedPill Loader (TCRP)]

3 minutes ago, pocopico said:

 

Added additional info into my previous post.

Very learnful for me, thanks again for the information. Btw this board was a replacement for a Gigabyte GA-H87N-WIFI. This Gigabyte works well with DSM 7 but the bios get's corrupted every reboot. See below. It's on Proxmox now, working well but I preferred baremetal.

 

 

[TinyCore RedPill Loader (TCRP)]

6 minutes ago, pocopico said:

 

Well i was afraid of that : ata_piix 

 

ata_piix is not supported in DSM7. Modules will not compile. I've tried a lot of times.

 

check your BIOS settings for AHCI or IDE mode. ONLY AHCI will work

 

Thanks for the help Pocopico. AHCI is active in the BIOS, checked it again. Proxmox is maybe the way forward with this board.

Kind regards,

Paul

[TinyCore RedPill Loader (TCRP)]

13 minutes ago, pocopico said:

 

From within tinycore can you sent the following ?

 

lspci -nnq 

lspci -k 

lsblk -t

fdisk -l 

 

 

Results are in the attached txt file.

Regards

lspci-fidsk.txt

[TinyCore RedPill Loader (TCRP)]

11 minutes ago, pocopico said:

 

First, make sure your SATA disks are set to AHCI in bios.

 

While at GRUB select your boot option and press "e" then edit the sataportmap and diskidxmap to :

 

sataportmap=888 and diskidxmap=00080F 

 

and press F10. Then login and execute fdisk -l again 

 

 

 Thank you but unfortunately the same result. Only the USB stick is seen.

[TinyCore RedPill Loader (TCRP)]

Hello Pocopico,

 

Thanks for your answer and thanks a lot for your your amazing work!

The fdisk -l command only show the USB stick. DSM is not installed yet because of the missing disk(s). What can I do to find the right mapping?

 

Regards, Paul

[TinyCore RedPill Loader (TCRP)]

Hello all,

 

Hope someone can help me with  the right DiskIdxMap and SataPortMap. I made a loader for a 3615xs and 3622xs+ and both show that no disks are found. TC suggests DiskIdxMap = 2 and SataPortMap = 22. The motherboard is an Asus P8H61-I-LX-R2 with an i5-2500. The codes for the drive controllers are 00:1f.2 (8086:1c00) and 00:1f.5 (8086:1c08). Tried a lot of combinations for the mapping, changed BIOS settings for sata like AHCI and IDE, but no luck. What can I do, any ideas ?

 

Regards, Paul

[DVA3221 loader development thread]

@Carl10 strange behaviour of your GTX1650 card. I am using an Asus GTX1650 in this build, working well in 7.01 and 7.1. Are you sure your GTX1650 card is working well? For instance you could test it on a Windows machine.

[DVA3221 loader development thread]

Hello all,

 

Here we go with the steps voor having DVA (AI) in a DVA3221 with a lower performance video card like a GTX1050

 

1) I assume you have a well functioning SS in DVA3221 7.0.1
2? Download SurveillanceStation-x86_64-8.2.9-6459_DVA_3219.spk   (the 2019 version of DVA, this file is unencrypted)
3) Extract package.tgz from it
4) Extract all the files from the package file which you got in step 3
5) Find the folder and files in it \package\dvacore\etc\model
6) Stop the SS service on your DVA3221
7) Connect with your DVA3221 with WinSCP and go to /volume1/@appstore/SurveillanceStation/dvacore/etc/model

8.) Rename the directory /model to something else
9) Copy the folder and subs which you found in step 5 to it
10) Change ownership and group (recursive) to the 'model' folder and it's contents to 'SurveillanceStation'
11) Start the SS service
12) Create a task in SS in Deep Video Analytics
13) Do some experiments with it and enjoy your tests with AI and the amazing work in all the 'loader' activities

 

Regards, Paul

 

ps you will see a difference in the amount of models in the model directory if you have SS9 beta. More tests are necessary so the model can be identified which is responsible for the incompatibilities before this patch. So for instance the 'PlateDetection' can be used as well with a GTX1050. Will test that in short.

[DVA3221 loader development thread]

As mentioned in my previous post in this thread the deep video analysis (dva) with a GTX1050 card is not working. One of the dva binaries is restarting in the system and crashes again and so on. After a lot of experiments with a GTX1050 card I have it working in a DVA3221 (7.01 42218 update 3 SS8 and/or SS9 beta in Proxmox) 😅

 

If somenone is interested in how it's done than let me know. Perhaps other GTX10xx series will work as well.

 

Regards

[DVA3221 loader development thread]

Hello Orphée,

 

Indeed the right type is DVA3221 and I corrected it. And your conclusions are correct. Thanks for al your information like the passthrough for the GPU in Proxmox. That helped me a lot in getting it operational!

[DVA3221 loader development thread]

Hello all,

 

Thanks a lot to all who contributed to the work on a loader for the DVA3221, magnificient. I think I can answer some of the questions which where mentioned by Orphée.

In a Proxmox 7 environment I have a DVA3221 running for 2 days. Motherboard is an Asrock H370 with a i3 8th gen. The loader was build in Tinycore (and before that in TOSSP toolchain). The serial/mac was generated there as well.

My first test was with a GTX1050 card which was recognised in DSM7.0.1 u3. In the log file however was a continous fault message:  segvault Synodvad, error 4 in libdvacore.dll. No AI functionality.

Replacing it with a GTX1650 works flawless. No fault messages anymore and AI (video deep learning) is working. It recognises peoples, cars, license plates. It has 8 camera licenses, and I have 2 camera's active at this moment. Both with AI. Hope this gives some answers.

 

Regards, Paul