Skip to content

vtunerc vs. Enigma2 OE2.0 #28

@GoogleCodeExporter

Description

@GoogleCodeExporter
What steps will reproduce the problem?
1. DVB-T USB Stick on PC. latest vtunerd running
   Current OE2.0 (20121108) image on dreambox (7020HD here)
   latest vtunerc.mipsel running
2. start channel scan on USB-Stick only
3. enigma2 hangs after some time displaying the spinner

What is the expected output? What do you see instead?
working channelscan and switch/view

What version of the product are you using? On what operating system?
all the latest from Downloads and OE2.0 from dreamboxupdates.com
vtuned runs on Fedora 17 i686. USB Stick is a af9015 or it9135. Makes no 
difference so far.

Please provide any additional information below.
debug output ends with:
vtunerc: [858 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [858 ../../vtuner-network.c:168] debug:  v2/5f 3 3
vtunerc: [858 ../../vtuner-network.c:205] debug:  541064970
vtunerc: [858 ../../vtuner-network.c:259] debug:  300 3000000
vtunerc: [858 ../../vtuner-network.c:269] debug:  v2/5f 768 0
vtunerc: [858 ../../vtuner-network.c:275] debug:  3 0
vtunerc: [858 ../../vtuner-network.c:312] debug:  0
vtunerc: [858 ../../vtuner-network.c:360] debug: 
vtunerc: [858 ../../vtunerc.c:790] error: VTUNER_SET_RESPONSE - Invalid argument

Before I often see:
vtunerc: [858 ../../vtunerc.c:694] debug: vtuner message!
vtunerc: [858 ../../vtuner-network.c:168] debug:  v2/5f 18 18
vtunerc: [858 ../../vtuner-network.c:251]  warn: unkown message type 18
vtunerc: [858 ../../vtuner-network.c:259] debug:  1200 12000000
vtunerc: [858 ../../vtuner-network.c:269] debug:  v2/5f 4608 0
vtunerc: [858 ../../vtuner-network.c:275] debug:  18 0
vtunerc: [858 ../../vtuner-network.c:357]  warn: unknown message type 18
vtunerc: [858 ../../vtuner-network.c:360] debug: 
vtunerc: [858 ../../vtunerc.c:794] debug: msg: 18 completed

At this point 
  858 pts/1    Zl+    0:00 [vtunerc.mipsel] <defunct>
vtunerc is a zombie and
  895 ?        Rl    11:37 /usr/bin/enigma2
enigma ends up in a busyloop.

Original issue reported on code.google.com by mas...@gmail.com on 4 Dec 2012 at 11:42

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions