Moderator Control Panel ]

Problem with Mumudvb - frozen broadcasting

Problem with Mumudvb - frozen broadcasting

Postby Unit » Tue Jul 24, 2012 6:36 pm

Hello. I have strange problem with TBS6984 when I catch channels from transponder. I used Mumudvb and TeVii cards before getting TBS. With TeVii broadcasting work stable for days & months (except when the electricity down :) ).
But now I install the card in system with TeVii cards (PCI 464 & PCIe 470), plug in external power, write config for mumudvb and started it. Mumu says that the card is found, signal is lock and broadcast starts.
But then, about 3-5 hours later, I found, that the broadcasting from TBS is frozen: program runs, debug shows the clients, who wants watch channels, but nothing happened. Client connected with VLC player, but the stream is not found.

Then I have MumuDVB ver. 1.6.1, but now I get a new version 1.7 from git of project, but problem is still here. I don't know what I can do to solve that. Today I restart Mumu every 4 hours, it's an only one way that I found.

p.s. Sorry for bad English. :)
Unit
 
Posts: 6
Joined: Fri Jul 06, 2012 10:18 am
Location: Russia, Tomsk

Re: Problem with Mumudvb - frozen broadcasting

Postby SergioDanielG » Tue Jul 24, 2012 7:23 pm

Hi Unit.
What about syslog when broadcasting is frozen? Is there something like errors or warnings?

Best regards.
SergioDanielG
 
Posts: 356
Joined: Tue May 31, 2011 3:53 am
Location: Tostado (SF) Argentina

Re: Problem with Mumudvb - frozen broadcasting

Postby Unit » Wed Jul 25, 2012 10:15 am

Yes, in syslog & messages writes:
Code: Select All Code
Jul 24 11:19:56 sat-capture1 kernel: [1725934.714245] TurboSight TBS 6984 Frontend:
Jul 24 11:19:56 sat-capture1 kernel: [1725934.714247]  tbs6984fe - Current Delivery System and Mode are unknown
Jul 24 11:20:03 sat-capture1 kernel: [1725941.231018] TurboSight TBS 6984 Frontend:
Jul 24 11:20:03 sat-capture1 kernel: [1725941.231019]  tbs6984fe - Current Delivery System and Mode are unknown
Jul 25 00:44:08 sat-capture1 kernel: [1774159.522484] TurboSight TBS 6984 Frontend:
Jul 25 00:44:08 sat-capture1 kernel: [1774159.522485]  tbs6984fe - software version is 1.95.2.3
Jul 25 00:44:08 sat-capture1 kernel: [1774159.522487] TurboSight TBS 6984 Frontend:
Jul 25 00:44:08 sat-capture1 kernel: [1774159.522488]  tbs6984fe - Successfully Initialized
Jul 25 03:15:19 sat-capture1 kernel: [1783225.706355] TurboSight TBS 6984 Frontend:
Jul 25 03:15:19 sat-capture1 kernel: [1783225.706357]  tbs6984fe - Current Delivery System and Mode are unknown


System: Debian Squeeze 6.0.5
Transponder: ABS-1 75E, DVB-S, 12732 V, SR 22000, FEC 7/8
Unit
 
Posts: 6
Joined: Fri Jul 06, 2012 10:18 am
Location: Russia, Tomsk

Re: Problem with Mumudvb - frozen broadcasting

Postby steven » Wed Jul 25, 2012 10:36 am

Hi Unit

Would you mind telling us that what's your mainbroad type,is it intel chip ?

Kind Regards

steven
steven
 
Posts: 2250
Joined: Fri Aug 06, 2010 3:23 pm

Re: Problem with Mumudvb - frozen broadcasting

Postby Unit » Wed Jul 25, 2012 2:39 pm

Yes, Intel P55. Motherboard Gigabyte P55-UD3L.
Here it is the dmidecode informaton:
Code: Select All Code
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: Award Software International, Inc.
        Version: FI
        Release Date: 11/01/2010
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 2048 kB
        Characteristics:
                PCI is supported
                PNP is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                EDD is supported
                5.25"/360 KB floppy services are supported (int 13h)
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 KB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                LS-120 boot is supported
                ATAPI Zip drive boot is supported
                BIOS boot specification is supported
                Targeted content distribution is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Product Name: P55-UD3L
        Version:
        Serial Number:
        UUID: 00000000-0000-0000-0000-1C6F658CDB8F
        Wake-up Type: Power Switch
        SKU Number:
        Family:

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Product Name: P55-UD3L
        Version: x.x
        Serial Number:
Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Type: Desktop
        Lock: Not Present
        Version:
        Serial Number:
        Asset Tag:
        Boot-up State: Unknown
        Power Supply State: Unknown
        Thermal State: Unknown
        Security Status: Unknown
        OEM Information: 0x00000000

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
        Socket Designation: Socket 1156
        Type: Central Processor
        Family: Other
        Manufacturer: Intel
        ID: 55 06 02 00 FF FB EB BF
        Version: Intel(R) Core(TM) i3 CPU
        Voltage: 1.0 V
        External Clock: 133 MHz
        Max Speed: 4000 MHz
        Current Speed: 3066 MHz
        Status: Populated, Enabled
        Upgrade: Socket 478
        L1 Cache Handle: 0x000A
        L2 Cache Handle: 0x000B
        L3 Cache Handle: Not Provided
        Serial Number:
        Asset Tag:
        Part Number:

Handle 0x0005, DMI type 5, 24 bytes
Memory Controller Information
        Error Detecting Method: 8-bit Parity
        Error Correcting Capabilities:
                None
        Supported Interleave: One-way Interleave
        Current Interleave: One-way Interleave
        Maximum Memory Module Size: 1024 MB
        Maximum Total Memory Size: 4096 MB
        Supported Speeds:
                Other
        Supported Memory Types:
                Other
        Memory Module Voltage: 5.0 V
        Associated Memory Slots: 4
Handle 0x0006, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: A0
        Bank Connections: 1
        Current Speed: Unknown
        Type: Other
        Installed Size: 2048 MB (Single-bank Connection)
        Enabled Size: 2048 MB (Single-bank Connection)
        Error Status: OK

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: A1
        Bank Connections: 2
        Current Speed: Unknown
        Type: Unknown
        Installed Size: Not Installed
        Enabled Size: Not Installed
        Error Status: OK

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: A2
        Bank Connections: 3
        Current Speed: Unknown
        Type: Other
        Installed Size: 2048 MB (Single-bank Connection)
        Enabled Size: 2048 MB (Single-bank Connection)
        Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
        Socket Designation: A3
        Bank Connections: 4
        Current Speed: Unknown
        Type: Unknown
        Installed Size: Not Installed
        Enabled Size: Not Installed
        Error Status: OK

Handle 0x000A, DMI type 7, 19 bytes
Cache Information
        Socket Designation: Internal Cache
        Configuration: Enabled, Not Socketed, Level 1
        Operational Mode: Write Back
        Location: Internal
        Installed Size: 64 KB
        Maximum Size: 64 KB
        Supported SRAM Types:
                Synchronous
        Installed SRAM Type: Synchronous
        Speed: Unknown
        Error Correction Type: Unknown
        System Type: Unknown
        Associativity: Unknown

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
        Socket Designation: External Cache
        Configuration: Enabled, Not Socketed, Level 2
        Operational Mode: Write Back
        Location: Internal
        Installed Size: 4096 KB
        Maximum Size: 2048 KB
        Supported SRAM Types:
                Synchronous
        Installed SRAM Type: Synchronous
        Speed: Unknown
        Error Correction Type: Unknown
        System Type: Unknown
        Associativity: Unknown
Unit
 
Posts: 6
Joined: Fri Jul 06, 2012 10:18 am
Location: Russia, Tomsk

Re: Problem with Mumudvb - frozen broadcasting

Postby steven » Thu Jul 26, 2012 9:39 am

Hi Unit

From the Gigabyte P55-UD3L's information?What PCI-E type you are using with TBS6984? X1 or X16,
if you are using PCI-E x1 slot ,would you mind changing it to PCI-E X16 slot,
and have a test again.

Kind Regards

steven
steven
 
Posts: 2250
Joined: Fri Aug 06, 2010 3:23 pm

Re: Problem with Mumudvb - frozen broadcasting

Postby Unit » Thu Jul 26, 2012 12:38 pm

TBS Card was installed in PCIe x16 slot from the beginning.
Unit
 
Posts: 6
Joined: Fri Jul 06, 2012 10:18 am
Location: Russia, Tomsk

Re: Problem with Mumudvb - frozen broadcasting

Postby Unit » Mon Jul 30, 2012 6:03 pm

Now I try TBS with Getstream and things getting worse. Broadcast continued about 1-3 minutes and then the stream frozen. In logs I can't found anything new that I wrote earlier.
Maybe, I should trying TBS standalone without any other cards? Can other firmwares & drivers can prefer normal work mode of TBS?
Unit
 
Posts: 6
Joined: Fri Jul 06, 2012 10:18 am
Location: Russia, Tomsk

Re: Problem with Mumudvb - frozen broadcasting

Postby Unit » Mon Aug 20, 2012 10:15 am

Hello, guys.

My colleague told me that in the source driver is an option
linux-tbs-drivers/linux/drivers/media/dvb/dvb-core/dvb_frontend.c

static int dvb_powerdown_on_sleep = 0;
~~~
module_param(dvb_powerdown_on_sleep, int, 0644);
MODULE_PARM_DESC(dvb_powerdown_on_sleep, "0: do not power down, 1: turn LNB voltage off on sleep (default)");
that is enabled by default. His map also fell asleep, after some time. He rebuilt the driver without this option, and broadcasting has become stable. Why is it included by default?
However, I disable this option, only the extended broadcasting time from 2-3 hours to 9-10. After that, all the channels goes down. What else can I try to change the driver? Or is it to move the map on another machine and try it there?

Best regards.
Unit
 
Posts: 6
Joined: Fri Jul 06, 2012 10:18 am
Location: Russia, Tomsk


Return to Linux

Who is online

Users browsing this forum: No registered users and 2 guests