Восстановление видеокамер RVI-IPC43DNS

NikNo
Сообщения: 2
Зарегистрирован: 05 дек 2022, 14:38

Восстановление видеокамер RVI-IPC43DNS

Сообщение NikNo » 05 дек 2022, 15:03

Всем доброго времени суток.
Имеются 2 видеокамеры IPC43DNS с одинаковой симптоматикой. При включении уходят в бесконечный ребут.
Подключился к RS232, зашел в U-boot, вижу следующее:

Код: Выделить всё

1..2..3..boot_from:normal


U-Boot 2010.06-svn413 (Apr 26 2014 - 11:42:08)
I2C:   ready
DRAM:  254 MiB
NAND:  128 MiB
state:ff,err_count:03
Net:   Detected MACID:90:02:a9:5d:18:df
PHY:0x00221513,addr:0x00

TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0xc5000000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending through gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0xc2000000
Loading: *
Retry count exceeded; starting again
## Booting kernel from Legacy Image at c2000000 ...
   Image Name:   Linux-2.6.38.8
   Created:      2014-04-26   4:22:35 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2546876 Bytes = 2.4 MiB
   Load Address: c0208000
   Entry Point:  c0208000
   Verifying Checksum ... OK
   Loading Kernel Image ...OK
OK
crashflasg:1, logmagic:54410011.

Starting kernel ...
1..2..3..boot_from:normal


Дальше ребут и по кругу..


Включаю логирование, вижу следующее:

Код: Выделить всё

UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 64
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 1/0
UBI: image sequence number:  225629871
UBI: background thread "ubi_bgt0d" started, PID 679
PPP generic driver version 2.4.2
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
console [netcon0] enabled
netconsole: network logging started
mousedev: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
UBIFS: mounted UBI device 0, volume 0, name "romfs"
UBIFS: mounted read-only
UBIFS: file system size:   6193152 bytes (6048 KiB, 5 MiB, 48 LEBs)
UBIFS: journal size:       1419264 bytes (1386 KiB, 1 MiB, 11 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) readonly on device 0:15.
devtmpfs: mounted
Freeing init memory: 144K
UBI: attaching mtd9 to ubi1
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       2
UBI: attached mtd9 to ubi1
UBI: MTD device name:            "user"
UBI: MTD device size:            25 MiB
UBI: number of good PEBs:        204
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 204
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 1/0
UBI: image sequence number:  2053532401
UBI: background thread "ubi_bgt1d" started, PID 727
UBI device number 1, total 204 LEBs (26320896 bytes, 25.1 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
UBIFS: mounted UBI device 1, volume 0, name "user"
UBIFS: mounted read-only
UBIFS: file system size:   24256512 bytes (23688 KiB, 23 MiB, 188 LEBs)
UBIFS: journal size:       3612672 bytes (3528 KiB, 3 MiB, 28 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
UBI: attaching mtd4 to ubi2
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       2
UBI: attached mtd4 to ubi2
UBI: MTD device name:            "custom"
UBI: MTD device size:            3 MiB
UBI: number of good PEBs:        26
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 26
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 1/0
UBI: image sequence number:  1404604472
UBI: background thread "ubi_bgt2d" started, PID 734
UBI device number 2, total 26 LEBs (3354624 bytes, 3.2 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
UBIFS: mounted UBI device 2, volume 0, name "custom"
UBIFS: mounted read-only
UBIFS: file system size:   1548288 bytes (1512 KiB, 1 MiB, 12 LEBs)
UBIFS: journal size:       903169 bytes (882 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
UBI: attaching mtd5 to ubi3
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       2
UBI: attached mtd5 to ubi3
UBI: MTD device name:            "product"
UBI: MTD device size:            3 MiB
UBI: number of good PEBs:        26
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 26
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 1/0
UBI: image sequence number:  1816153035
UBI: background thread "ubi_bgt3d" started, PID 741
UBI device number 3, total 26 LEBs (3354624 bytes, 3.2 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
UBIFS: mounted UBI device 3, volume 0, name "pd"
UBIFS: mounted read-only
UBIFS: file system size:   1548288 bytes (1512 KiB, 1 MiB, 12 LEBs)
UBIFS: journal size:       903169 bytes (882 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
UBI: attaching mtd8 to ubi4
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       2
UBI: attached mtd8 to ubi4
UBI: MTD device name:            "web"
UBI: MTD device size:            8 MiB
UBI: number of good PEBs:        64
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 64
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 1/0
UBI: image sequence number:  1751322385
UBI: background thread "ubi_bgt4d" started, PID 748
UBI device number 4, total 64 LEBs (8257536 bytes, 7.9 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
UBIFS: mounted UBI device 4, volume 0, name "web"
UBIFS: mounted read-only
UBIFS: file system size:   6193152 bytes (6048 KiB, 5 MiB, 48 LEBs)
UBIFS: journal size:       1419264 bytes (1386 KiB, 1 MiB, 11 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
UBI: attaching mtd10 to ubi5
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       149464
UBI: attached mtd10 to ubi5
UBI: MTD device name:            "syslog"
UBI: MTD device size:            4 MiB
UBI: number of good PEBs:        32
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             6
UBI: total number of reserved PEBs: 26
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 5190/4667
UBI: image sequence number:  1419969641
UBI: background thread "ubi_bgt5d" started, PID 755
UBI device number 5, total 32 LEBs (4128768 bytes, 3.9 MiB), available 6 LEBs (774144 bytes, 756.0 KiB), LEB size 129024 bytes (126.0 KiB)
UBI error: ubi_create_volume: cannot create volume 1, error -17
ubimkvol: error!: cannot UBI create volume
          error 17 (File exists)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 5, volume 0, name "syslog"
UBIFS: file system size:   1548288 bytes (1512 KiB, 1 MiB, 12 LEBs)
UBIFS: journal size:       903169 bytes (882 KiB, 0 MiB, 5 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  73129 bytes (71 KiB)
UBI: attaching mtd11 to ubi6
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       201404
UBI: attached mtd11 to ubi6
UBI: MTD device name:            "config"
UBI: MTD device size:            4 MiB
UBI: number of good PEBs:        32
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             6
UBI: total number of reserved PEBs: 26
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 6975/6285
UBI: image sequence number:  1086358608
UBI: background thread "ubi_bgt6d" started, PID 764
UBI device number 6, total 32 LEBs (4128768 bytes, 3.9 MiB), available 6 LEBs (774144 bytes, 756.0 KiB), LEB size 129024 bytes (126.0 KiB)
UBI error: ubi_create_volume: cannot create volume 1, error -17
ubimkvol: error!: cannot UBI create volume
          error 17 (File exists)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 6, volume 0, name "config"
UBIFS: file system size:   1548288 bytes (1512 KiB, 1 MiB, 12 LEBs)
UBIFS: journal size:       903169 bytes (882 KiB, 0 MiB, 5 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  73129 bytes (71 KiB)
UBI: attaching mtd12 to ubi7
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       143261
UBI: attached mtd12 to ubi7
UBI: MTD device name:            "backup"
UBI: MTD device size:            4 MiB
UBI: number of good PEBs:        32
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             6
UBI: total number of reserved PEBs: 26
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 5030/4473
UBI: image sequence number:  1441091883
UBI: background thread "ubi_bgt7d" started, PID 773
UBI device number 7, total 32 LEBs (4128768 bytes, 3.9 MiB), available 6 LEBs (774144 bytes, 756.0 KiB), LEB size 129024 bytes (126.0 KiB)
UBI error: ubi_create_volume: cannot create volume 1, error -17
ubimkvol: error!: cannot UBI create volume
          error 17 (File exists)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 7, volume 0, name "backup"
UBIFS: file system size:   1548288 bytes (1512 KiB, 1 MiB, 12 LEBs)
UBIFS: journal size:       903169 bytes (882 KiB, 0 MiB, 5 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  73129 bytes (71 KiB)


[OSA-DRV] OSA Build on May  7 2014 at 20:18:00.
[OSA-DRV] SVN NUM: 2072.

[OSA-DRV] Monitor    Task   pid=799   tid=799


[LOG-DRV] LOG Build on May  7 2014 at 20:18:11.
[LOG-DRV] SVN NUM: 5882.

[LOG-DRV] ramStart:0xc8b7e000;ramSize:0x80000;select:1
[OSA-DRV] Char device create OK !
[LOG-DRV] coreId = 0, logLevel = 2
[LOG-DRV] coreId = 1, logLevel = 2
[LOG-DRV] coreId = 2, logLevel = 2
[LOG-DRV] coreId = 3, logLevel = 2
[LOG-DRV] coreId = 4, logLevel = 2
[LOG-DRV] coreId = 5, logLevel = 2
00:00:09|[Binder] Binder.ko Build on Jun 15 2013 at 11:21:13.
00:00:09|[Binder] SVN NUM: 1236.

00:00:09|[Binder] NameServer Initial OK !
00:00:09|[Binder] Binder Initial OK !
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[Binder] SR driver initial OK !
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[Binder] NS driver initial OK !
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[Binder] Binder driver initial OK !
00:00:09|[SPF] SPF Build on Nov 11 2013 at 16:39:44.
00:00:09|[SPF] SVN NUM: 4486.

00:00:09|[SPF] SIL initial OK !
00:00:09|[SPF] SPF initial ok !
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[SPF] SPF Proc Create OK!!!
00:00:09|[SPF] SPF driver initial ok !
00:00:09|[prc] PRC Driver Build on Mar 20 2014 at 16:30:15.
00:00:09|[prc] SVN NUM: 1839.

00:00:09|[prc] Start to init module!
00:00:09|[SPF] Dai 2 register OK !
00:00:09|[prc] Success to init module!
00:00:09|[pdc]

PDC Build on Apr 26 2014 at 12:47:42.
00:00:09|[pdc] SVN NUM: 4220.

00:00:09|[pdc] BASE_LINE: 210
00:00:09|[pdc] OSA_kProcCreate OK
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] PDC_PartionInit ok!!
00:00:09|[pdc] HWID : IPC-HFW4100S:01:02:02:19:0A:00:01:00:00:00:00:210:00:00:02:00:00:00:00:00:100
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] binderFlag: 0x3, funcap: 0x18538b,0x0,0x0,0x0
00:00:09|[pdc] SenCfg Match OK,pCfgParams->pCfg: bf0ec5a0
00:00:09|[pdc] Find Product: IPC-HFW4100S.
00:00:09|[pdc] Config size 2032 !
00:00:09|[pdc] SenCfgSize: 204 Bytes
00:00:09|[pdc] Init spiBus1  Successed!
00:00:09|[pdc] Init I2CBus0  Successed!
00:00:09|[pdc] PDC_MODULE_RESET_STATE
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] ircut types = [0]
00:00:09|[pdc] ircut types = [1]
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] Dev has No shutDown Cfg!
00:00:09|[pdc] PDC_pinInit As Usual!
00:00:09|[pdc] Get reset pin: 7 OK !
00:00:09|[pdc] Get comPort Cfg ok !0sa
00:00:09|[pdc] PDC_comInit OK!
00:00:09|[pdc] PDC_MODULE_SENSOR
00:00:09|[pdc] Try RtcDev:DS1338
00:00:09|[pdc] DS1338 0x07 Data: b3
00:00:09|[pdc] Choose RtcType: 1 -> DS1338
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] OSA_kProcAddFile:pdcRtc OK!
00:00:09|[pdc] Wifi init: powerGpioCfg = 54
00:00:09|[pdc]            irqGpioCfg = 75
00:00:09|[pdc]            powerGpioCfg = 65535
00:00:09|[pdc]            enGpio = 65535
00:00:09|[pdc]            intGpio = 65535
00:00:09|[pdc]            hasWps = 0
00:00:09|[pdc]            wpsGpio = 65535
00:00:09|[pdc]            resetDefaultGpio = 7
00:00:09|[pdc]            wpsKeyLevel = 1
00:00:09|[pdc] Dev has No shutDown Cfg!
00:00:09|[pdc] isWpsResetComm: 0  !
00:00:09|[pdc] PDC_MODULE_WIFI
00:00:09|[pdc] smartIr light count:1
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] SmartIR init pwmId: 0,mode: 0,activeLevel: 1
00:00:09|[pdc] OSA_kProcAddFile:pdcSmartIR OK!
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] WDT proc Add OSA_kProcAddFile ok!
00:00:09|[pdc] sclGpio = [6], sdaGpio = [5]
00:00:09|[pdc] Dev has No Key Cfg!
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] SramFile init ok !
00:00:09|[pdc] Both of Chief and Backup File CRC check OK!
 00:00:09|[OSA-DRV] Char device create OK !
00:00:09|[pdc] PDC Driver Initial OK !
00:00:09|[OSA-DRV] recordTsk  Task   pid=839   tid=839
00:00:10|[pdc]  SramFile_devRelease OK!
CATEGORY = 2
IPC Device
00:00:10|[crypt] platType = [1], DM36X = [0], A5S_CRYPT = [1], hi351x=[2].
00:00:10|[crypt] major = [232], minor = [0]
00:00:10|[crypt] CRYPT_setChipOps ......
00:00:10|[crypt] CRYPT_authenticate ......
error: write byte error
error: write_nbytes failed
error: authentication failed
error: authenticate failed
00:00:10|[crypt] ERROR  (/home/fang_qipin/test/test/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1203): CRYPT_authenticate failed!
00:00:10|[crypt] ERROR  (/home/fang_qipin/test/test/P_2013.02.22_CryptoMemory_DM8127_IPC/build/../src/crypt.c|crypt_init|1204): reboot........
<0▒1..2..3..boot_from:normal



Почитал в интернете, информации не много и все обсуждения не законченные. Результата нет.
Вкратце:
Ошибки на создание тома пишут это нормально, на рабочих камерах наблюдали тоже самое..
По ошибке на EEPROM (00:00:10|[crypt] CRYPT_authenticate ......) находится AT88SC0104CA, но ни одного успешного решения я не нашел
Кто то сталкивался с подобным? Можете что посоветовать?

iTuneDVR
Сообщения: 3139
Зарегистрирован: 24 авг 2013, 11:05

Re: Восстановление видеокамер RVI-IPC43DNS

Сообщение iTuneDVR » 05 дек 2022, 16:37

У Dahua в отличии от Hikvision данные не хранятся (не хранились в крипте), а только в переменных окружения и она была для других целей или использована, хотя там что-то определенно есть.
Для старых камер возможно есть способ обхода данного недоразумения, ведь в то время такое не увидеть быть, но поскольку данная серия уже как 10 лет без поддержки, то .... можно пробовать...
С другой стороны, тема с донором и пересадкой с другой аналогичной камерой не рабочей по другим причинам, но годной для такого...

У хика сложнее и там в криптомодуле реально данные, которые для ряда серий удалось эмулировать.

NikNo
Сообщения: 2
Зарегистрирован: 05 дек 2022, 14:38

Re: Восстановление видеокамер RVI-IPC43DNS

Сообщение NikNo » 06 дек 2022, 12:45

Поищу пока донора с живым модулем AT88SC0104CA.
Дальше попробую дамп снять, а затем перепаять на ту камеру которую хочу восстановить.
Если дамп успешно считает, закажу на али чистые модули и потестирую на второй.

iTuneDVR
Сообщения: 3139
Зарегистрирован: 24 авг 2013, 11:05

Re: Восстановление видеокамер RVI-IPC43DNS

Сообщение iTuneDVR » 06 дек 2022, 15:43

NikNo писал(а):Поищу пока донора с живым модулем AT88SC0104CA.
Дальше попробую дамп снять, а затем перепаять на ту камеру которую хочу восстановить.
Если дамп успешно считает, закажу на али чистые модули и потестирую на второй.

Дамп искать не надо, все остальное вполне живое.
Даже если какие-то проблемы, то на камеру есть прошивки и из загрузчика образом специальным update.img или распаковав прошивку на файлы архиватором, по модульно можно восстановить.
Скорее всего проблема в крипте, в которой содержаться некоторые параметры оборудования, без критичных серийника, мака и пр.


Вернуться в «IPC RVi»