Jump to content
Cesbo Community
  • Announcements

    • RadioSintetica

      News!   12/10/17

      If you have any questions related to installation and purchase, please check our documentation https://cesbo.com/en/astra/docs/ and terms of service https://cesbo.com/en/terms/
      Also, we have an official Telegram chat: https://t.me/cesbo_en  you can ask any questions or share your experience with colleagues Если у вас возникли вопросы по установке и покупке, ознакомьтесь пожалуйста с документацией по адресу https://cesbo.com/ru/astra/docs/ и условиями использования https://cesbo.com/ru/terms/
      Так же, обращаю внимание, что у нас есть официальный Телеграмм чат: https://t.me/cesbo_astra в котором можно задать вопросы - или поделиться своим опытом с коллегами

All Activity

This stream auto-updates     

  1. Past hour
  2. Cherry EPG

    hello dear i want add content_descriptor to EIT stream made by cherry i added this my $content_descriptor; $content_descriptor->{descriptor_tag} = 0x54; # content descriptor my $nibble; $nibble->{content_nibble_level_1} =0; $nibble->{content_nibble_level_2} =0; $nibble->{user_byte} =0; push( @{$content_descriptor->{list}}, $nibble); push( @descriptors, $content_descriptor); to cherryEPG.pl but there is no 0x54 descriptor in output so what is your idea?thanks
  3. Today
  4. TBS2900

    опция stream теперь исчезла из конфига
  5. TBS2900

    смотреть конфиг
  6. TBS2900

    попробовал astra # /usr/bin/astra4.4.182 /astra4/tune0 & # PANIC: unprotected error in call to Lua API ([main] /astra4/tune0:6: module 'stream' not found: no field package.preload['stream'] no file './stream.lua') чего не хватает ?
  7. USB DVB-T2

    добавление #no_sync на input и output - поток пошел, модулятор все ок, а вот vlc выдает только первый кадр из потока PS поставил дрова CrazyCat , ситуация по Т2 изменилась, но 6984 почему-то не показывает уровень сигнала
  8. Oscam timeout

    да, воткнул карту в ридер (fallback=0) а запросы как шли на fallback=1 так и остались, но вопрос пофиксил- перегрузил полностью oscam и все стало на свое место, выключение ридеров отрабатывает.
  9. Yesterday
  10. TBS 6909

    А какая материнка ? Логи можно приатачить к сообщению, а не вываливать в сообщении.
  11. Oscam timeout

    как Я понял, карту перетыкнул и к ридеру нету обращения? в ymod есть функция REFRESH ENTITLEMENT.
  12. Oscam timeout

    значение по умолчанию, указано в конфиге
  13. Oscam timeout

    ну так на карту fallback = 0
  14. Oscam timeout

    запускаю fallback для 2х карт без карты в ридере, oscam перешел на резервный ридер, поставил карту, но oscam назад не переходит, карта в ридере перегружается PS опцию убрал, но oscam ключи с карты не берет 2017/12/15 18:44:57 736C58A0 c (ecm) media (0628@000000/0000/0013/40:FE5E6FE123B1F8E710FDFD7838C864E9): found (107 ms) by sigmedia-sd1 (F/2/2/2) - NST (real 6 ms) 2017/12/15 18:45:17 736C58A0 c (ecm) media (0628@000000/0000/0003/40:B513BD8F90FCB0113C2CDC16304D9E52): found (224 ms) by sigmedia-sd1 (F/2/2/2) - Russkiy Roman (real 121 ms) 2017/12/15 18:45:17 7E9E0E72 r (reader) sig-media-sd2 [irdeto] ECM not found limit reached 10. Restarting the reader. 2017/12/15 18:45:18 736C58A0 c (ecm) media (0628@000000/0000/0004/40:F1614245099D2794EA63B5FAF0DE5726): found (885 ms) by sigmedia-sd1 (F/2/2/2) - Russkiy bestseller (real 771 ms) 2017/12/15 18:45:18 736C58A0 c (ecm) media (0628@000000/0000/0005/40:AAA18DF076DE0BE25DBE4A143E2BC5A9): found (7 ms) by sigmedia-sd1 - Sarafan oscam.server [reader] label = sig-media-sd2 protocol = mouse device = /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A6032QV7-if00-port0 key = 0102030405060708091011121314 caid = 0628 boxkey = 1122334455667788 # ecmnotfoundlimit = 10 detect = cd mhz = 600 cardmhz = 600 ident = 0628:000000 group = 1 emmcache = 1,3,12,0 fallback = 0 [reader] label = sigmedia-sd1 protocol = newcamd device = ip:port key = 0102030405060708091011121314 user = sig-media-sd2 password = fallback = 1 caid = 0628 ident = 0628:000000 group = 1 2017/12/15 18:45:17 7E9E0E72 r (reader) sig-media-sd2 [irdeto] ECM not found limit reached 10. Restarting the reader. 2017/12/15 18:45:18 736C58A0 c (ecm) media (0628@000000/0000/0004/40:F1614245099D2794EA63B5FAF0DE5726): found (885 ms) by sigmedia-sd1 (F/2/2/2) - Russkiy bestseller (real 771 ms) 2017/12/15 18:45:18 736C58A0 c (ecm) media (0628@000000/0000/0005/40:AAA18DF076DE0BE25DBE4A143E2BC5A9): found (7 ms) by sigmedia-sd1 - Sarafan
  15. N*ffmpeg = remuxme

    Там видео есть как конфиг править: "config processes and taskset " Текстовый файл, редактируем редактором. Потом перезапускаем процесс. Перед запуском не помешает "log start <process>" А можно и весь лог посмотреть - он там в папке есть.
  16. N*ffmpeg = remuxme

    как не пытался подсунуть ему свой конфиг для теста, он видит только задачи прописанные по умолчанию, может что-то пропустил?
  17. TBS 6909

    Я только ваши драйверва и использую. Использовать тбс-овские невозможно стало после введения на двбт стрим айди, который только вы и пофиксили. Так что делать с карточкой-то? Как лечить? Простыни-то тут, дмесг большой, а толку? В оси дело или в чём? Поменял уже ядро Linux TVtest 4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:13 UTC 2017 i686 i686 i686 GNU/Linux
  18. TBS 6909

    Да нет, исключительно дрова были с битбакета кота.
  19. TBS 6909

    В tbsdtv фирмварь-патч демода грузиться с dvb-fe-mxl5xx.fw, в моем с dvb-fe-mxl58x.fw (в моем media_build). В любом случае это одно и тоже по содержимому. В моем случае это исключительно чтобы разделить драйвера демода от Luis/TBSDTV и фирменный-левый от DD (хотя там фирмварь демода читается с EEPROM/флеша). Но я так понимаю "господа хорошие" привыкшие к linux-tbs-drivers не ищут "простых путей" и мутят все по-своему :) Типа тьфу на этих "китайцев" и "бешеных котов" - мы типа сами разберемся :) И валят сюда "простыни" логов :)
  20. Last week
  21. TBS 6909

    options mxl58x mode=0 Firmware не кидал, вроде несколько десяток раз инсталировал никогда не приходилось.....
  22. TBS 6909

    А что вы в /etc/modprobe.d/mxl58x.conf писали? options mxl58x mode=0 или 1,2,3? Какой ставить правильно, если подключать в схеме один провод - одна поляризация? Вы ручками .fw в lib/firmware закидывали? ./build этого не делает, у меня тоже жаловался на firmware выше, скопировал, и карта появилась. Не лочит только, но это уже другая проблема.
  23. TBS 6909

    У меня вот такая беда. Ubuntu 14.04 [ 12.356670] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 0 attach failed [ 12.356677] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.514055] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 1 attach failed [ 12.514060] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.673765] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 2 attach failed [ 12.673769] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.833678] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 3 attach failed [ 12.833682] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.990083] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 4 attach failed [ 12.990087] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 13.105841] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 5 attach failed [ 13.105853] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 13.265429] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 6 attach failed [ 13.265433] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 13.421249] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 7 attach failed [ 13.421250] TBSECP3 driver 0000:04:00.0: frontend attach failed dmesg | grep TBS [ 12.049808] TBSECP3 driver 0000:04:00.0: TurboSight TBS 6909 (Octa DVB-S/S2) [ 12.050739] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 12.171739] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:f8 [ 12.356657] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 12.356670] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 0 attach failed [ 12.356677] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.357050] TBSECP3 driver 0000:04:00.0: adapter0 attach failed [ 12.357058] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 12.475714] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:f9 [ 12.514038] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 12.514055] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 1 attach failed [ 12.514060] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.514248] TBSECP3 driver 0000:04:00.0: adapter1 attach failed [ 12.514266] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 12.635627] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:fa [ 12.673761] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 12.673765] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 2 attach failed [ 12.673769] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.674090] TBSECP3 driver 0000:04:00.0: adapter2 attach failed [ 12.674094] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 12.795625] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:fb [ 12.833674] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 12.833678] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 3 attach failed [ 12.833682] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.833843] TBSECP3 driver 0000:04:00.0: adapter3 attach failed [ 12.833847] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 12.951643] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:fc [ 12.990079] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 12.990083] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 4 attach failed [ 12.990087] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 12.990398] TBSECP3 driver 0000:04:00.0: adapter4 attach failed [ 12.990402] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 13.067628] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:fd [ 13.105838] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 13.105841] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 5 attach failed [ 13.105853] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 13.106043] TBSECP3 driver 0000:04:00.0: adapter5 attach failed [ 13.106046] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 13.227552] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:fe [ 13.265425] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 13.265429] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 6 attach failed [ 13.265433] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 13.265619] TBSECP3 driver 0000:04:00.0: adapter6 attach failed [ 13.265622] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter) [ 13.383399] TBSECP3 driver 0000:04:00.0: MAC address 00:22:ab:91:83:ff [ 13.421246] TBSECP3 driver 0000:04:00.0: Direct firmware load for dvb-fe-mxl58x.fw failed with error -2 [ 13.421249] TBSECP3 driver 0000:04:00.0: TBSECP3 frontend 7 attach failed [ 13.421250] TBSECP3 driver 0000:04:00.0: frontend attach failed [ 13.421599] TBSECP3 driver 0000:04:00.0: adapter7 attach failed [ 13.421601] TBSECP3 driver 0000:04:00.0: TurboSight TBS 6909 (Octa DVB-S/S2): PCI 0000:04:00.0, IRQ 46, MMIO 0xf7300000 Как лечить?
  24. РТРС 40 борт

    У кого то работают 3685 и 3665 L с 40е?
  25. TBS 6909

    uname -a Linux IPTV-MOI_1 4.4.76-1.el7.elrepo.x86_64 #1 SMP Wed Jul 5 12:10:20 EDT 2017 x 86_64 x86_64 x86_64 GNU/Linux [ 25.185480] tbsci: Adapter 6 CI slot enabled [ 25.185492] dvb_ca adapter 6: DVB CAM detected and initialised successfully [ 25.202494] tbsci: Adapter 7 CI slot enabled [ 25.202503] dvb_ca adapter 7: DVB CAM detected and initialised successfully [ 25.347425] tbsci: Adapter 5 CI slot enabled [ 25.347440] dvb_ca adapter 5: DVB CAM detected and initialised successfully [ 25.350638] tbsci: Adapter 3 CI slot enabled [ 25.350646] dvb_ca adapter 3: DVB CAM detected and initialised successfully [ 25.362384] tbsci: Adapter 0 CI slot enabled [ 25.362392] dvb_ca adapter 0: DVB CAM detected and initialised successfully [ 25.364474] tbsci: Adapter 4 CI slot enabled [ 25.364482] dvb_ca adapter 4: DVB CAM detected and initialised successfully [ 25.368437] tbsci: Adapter 2 CI slot enabled [ 25.368446] dvb_ca adapter 2: DVB CAM detected and initialised successfully сейчас вернул дрова tbsdtv
  26. TBS 6909

    Ручками скопировал cp media_build/v4l/firmware/dvb-fe-mxl58x.fw /lib/firmware/ Наивно полагал, что ./build это делает. теперь устройства появились, но 95.697727] intel_rng: Firmware space is locked read-only. If you can't or intel_rng: don't want to disable this in firmware setup, and if intel_rng: you are certain that your system has a functional intel_rng: RNG, try using the 'no_fwh_detect' option. [ 95.706418] media: module verification failed: signature and/or required key missing - tainting kernel [ 95.706963] media: Linux media interface: v0.10 [ 95.709402] WARNING: You are using an experimental version of the media stack. As the driver is backported to an older kernel, it doesn't offer enough quality for its usage in production. Use it with care. Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [ 95.758539] usbcore: registered new interface driver usbserial [ 95.758554] usbcore: registered new interface driver usbserial_generic [ 95.758565] usbserial: USB Serial support registered for generic [ 95.760561] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042B (\_SB_.PCI0.LPC_.TPM_.GPE0) (20150930/utaddress-254) [ 95.760570] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042B (\GPE0) (20150930/utaddress-254) [ 95.760574] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 95.760578] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000539-0x0000000000000539 (\_SB_.PCI0.LPC_.TPM_.GPLV) (20150930/utaddress-254) [ 95.760582] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000539-0x0000000000000539 (\GPLV) (20150930/utaddress-254) [ 95.760585] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 95.760586] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI_.SIOR) (20150930/utaddress-254) [ 95.697727] intel_rng: Firmware space is locked read-only. If you can't or intel_rng: don't want to disable this in firmware setup, and if intel_rng: you are certain that your system has a functional intel_rng: RNG, try using the 'no_fwh_detect' option. [ 95.706418] media: module verification failed: signature and/or required key missing - tainting kernel [ 95.706963] media: Linux media interface: v0.10 [ 95.709402] WARNING: You are using an experimental version of the media stack. As the driver is backported to an older kernel, it doesn't offer enough quality for its usage in production. Use it with care. Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [ 95.758565] usbserial: USB Serial support registered for generic [ 95.760561] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042B (\_SB_.PCI0.LPC_.TPM_.GPE0) (20150930/utaddress-254) [ 95.760570] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000428-0x000000000000042B (\GPE0) (20150930/utaddress-254) [ 95.760574] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 95.760578] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000539-0x0000000000000539 (\_SB_.PCI0.LPC_.TPM_.GPLV) (20150930/utaddress-254) [ 95.760582] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000539-0x0000000000000539 (\GPLV) (20150930/utaddress-254) [ 95.760585] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 95.760586] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000052F (\_SI_.SIOR) (20150930/utaddress-254) [ 95.760589] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 95.760591] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 95.764553] usbcore: registered new interface driver ftdi_sio [ 95.764568] usbserial: USB Serial support registered for FTDI USB Serial Device [ 95.764619] ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected [ 95.764660] usb 3-1: Detected FT232RL [ 95.767309] usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0 [ 95.802013] kvm: disabled by bios (это про феникс было) И вот еще [ 816.562623] perf interrupt took too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 [ 874.635029] {2}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0 [ 874.635039] {2}[Hardware Error]: It has been corrected by h/w and requires no further action [ 874.635042] {2}[Hardware Error]: event severity: corrected [ 874.635044] {2}[Hardware Error]: Error 0, type: corrected [ 874.635047] {2}[Hardware Error]: section_type: PCIe error [ 874.635048] [Firmware Warn]: error section length is too small [ 874.635661] demux_worker: called but nothing to do [ 979.201467] {3}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0 [ 979.201489] {3}[Hardware Error]: It has been corrected by h/w and requires no further action [ 979.201493] {3}[Hardware Error]: event severity: corrected [ 979.201496] {3}[Hardware Error]: Error 0, type: corrected [ 979.201500] {3}[Hardware Error]: section_type: PCIe error [ 979.201501] [Firmware Warn]: error section length is too small [ 979.202977] demux_worker: called but nothing to do [ 1225.705372] perf interrupt took too long (5003 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 [ 1365.317534] {4}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0 [ 1365.317546] {4}[Hardware Error]: It has been corrected by h/w and requires no further action [ 1365.317549] {4}[Hardware Error]: event severity: corrected [ 1365.317552] {4}[Hardware Error]: Error 0, type: corrected [ 1365.317555] {4}[Hardware Error]: section_type: PCIe error [ 1365.317556] [Firmware Warn]: error section length is too small [ 1365.319181] demux_worker: called but nothing to do Вроде ничего криминального, но не лочится. Почитал про vv, vh, hh, ничего толком не понял, с какой стороны vv, с какой hh подключать, поподключал во все входы, попробовал все номера карт, не лочится. ни V, ни H.
  27. TBS 6909

    Это s5000psl. Про ядро понял, до 4+ апгрейд делаю, отпишусь. Спасибо за быстрый ответ.
  28. TBS 6909

    Версия ядра, dmesg :) P.S.Я RedHat'овскими не интересуюсь лет 15 :) Это китайозы на них присели :)
  29. TBS 6909

    CrazyCat, вопрос по установки ваших дров: ./build, make install. все компилится, все вроде ставится, но в media/dvb-core пусто и соответственно /dev/dvb нет ось centos на moi amd
  1. Load more activity
×