Jump to content


Photo

Vtunerd Dm500 <> vtunerc Ubuntu 10.04 question...


  • Please log in to reply
4 replies to this topic

#1 patx

  • Senior Member
  • 55 posts

0
Neutral

Posted 2 December 2011 - 20:58

Hello,

I want to use dm500 vtunerd.ppc to vtunerc.i686... i compiled kernel and installed vtuner.ko + vtunerc.i686 to my ubuntu laptop. I think i have to stop all emu + enigma on the dm500 for it to work... but i am not sure about this...

What this error mean ? :

vtunerd: [20987 ../../vtunerd.c:103] debug: session status:0 session type:0 tuner_type:8 match:0
vtunerd: [20987 ../../vtunerd.c:113] info: No idle device found


Is there a way to stop enigma on dm500 ie: "killall enigma" "kill -9 pidof enigma" without automatic restart ??

Thank you

on dm500

root@dm500 ~ # vtunerd
vtunerd: [20987 ../../vtuner-dmm-2.c:48] info: FE_GET_INFO dvb-type:0 vtuner-type:1
vtunerd: [20987 ../../vtuner-dmm-2.c:59] error: failed to open /dev/dvb/card0/demux0[25] - Too many open files
vtunerd: [20987 ../../vtunerd.c:88] warn: Failed to init adapter:0, frontend:0, demux,0, dvr:0
vtunerd: [20987 ../../vtunerd-service.c:35] debug: autodiscover socket bound
vtunerd: [20987 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...
vtunerd: [20987 ../../vtunerd-service.c:265] debug: request received
vtunerd: [20987 ../../vtunerd.c:99] info: received discover request, vtuner_type:8
vtunerd: [20987 ../../vtunerd.c:103] debug: session status:0 session type:0 tuner_type:8 match:0
vtunerd: [20987 ../../vtunerd.c:113] info: No idle device found
vtunerd: [20987 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...
vtunerd: [20987 ../../vtunerd-service.c:265] debug: request received
vtunerd: [20987 ../../vtunerd.c:99] info: received discover request, vtuner_type:8
vtunerd: [20987 ../../vtunerd.c:103] debug: session status:0 session type:0 tuner_type:8 match:0
vtunerd: [20987 ../../vtunerd.c:113] info: No idle device found
vtunerd: [20987 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...
vtunerd: [20987 ../../vtunerd-service.c:265] debug: request received
vtunerd: [20987 ../../vtunerd.c:99] info: received discover request, vtuner_type:8
vtunerd: [20987 ../../vtunerd.c:103] debug: session status:0 session type:0 tuner_type:8 match:0
vtunerd: [20987 ../../vtunerd.c:113] info: No idle device found
vtunerd: [20987 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...
vtunerd: [20987 ../../vtunerd-service.c:265] debug: request received
vtunerd: [20987 ../../vtunerd.c:99] info: received discover request, vtuner_type:8
vtunerd: [20987 ../../vtunerd.c:103] debug: session status:0 session type:0 tuner_type:8 match:0
vtunerd: [20987 ../../vtunerd.c:113] info: No idle device found
vtunerd: [20987 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...
vtunerd: [20987 ../../vtunerd-service.c:265] debug: request received
vtunerd: [20987 ../../vtunerd.c:99] info: received discover request, vtuner_type:8
vtunerd: [20987 ../../vtunerd.c:103] debug: session status:0 session type:0 tuner_type:8 match:0
vtunerd: [20987 ../../vtunerd.c:113] info: No idle device found
vtunerd: [20987 ../../vtunerd-service.c:261] info: waiting for autodiscover packet ...

root@dm500 ~ #

on ubuntu 10.04

patx@Patx:/usr/sbin$ sudo vtunerc -f S2 -n 192.168.14.119
[sudo] password for patx:
vtunerc: vtuner client (vtunerc), part of vtuner project
Visit http://code.google.com/p/vtuner/ for more information
Copyright © 2009-11 Roland Mieslinger
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.
vtunerc: Revision:63f73de8b63c/tip DVB:5.1 allow:5.x NetProto:2 MsgSize:96, Debug:3
vtunerc: [2112 ../../vtunerc.c:452] info: added frontend mode DVB-S2 as mode 0, searching for tuner types 8
vtunerc: [2112 ../../vtunerc.c:477] info: direct connection: host='192.168.14.119' port=39305
vtunerc: [2112 ../../vtunerc.c:533] info: Created pidfile /var/run/vtunerc0.pid
vtunerc: [2112 ../../vtunerc.c:586] info: no server connected. discover thread is 0 (DWS_IDLE:0, DWS_RUNNING:1)
vtunerc: [2112 ../../vtunerc.c:588] info: changing frontend mode to DVB-S2
vtunerc: [2112 ../../vtunerc.c:617] info: Start discover worker for device type 8 groups ffff
vtunerc: [2112 ../../vtunerc.c:214] info: starting discover thread
vtunerc: [2112 ../../vtunerc.c:258] info: Sending direct discover message for device types 8
vtunerc: [2112 ../../vtunerc.c:258] info: Sending direct discover message for device types 8
vtunerc: [2112 ../../vtunerc.c:258] info: Sending direct discover message for device types 8
vtunerc: [2112 ../../vtunerc.c:258] info: Sending direct discover message for device types 8
vtunerc: [2112 ../../vtunerc.c:258] info: Sending direct discover message for device types 8
^C
patx@Patx:/usr/sbin$



Re: Vtunerd Dm500 <> vtunerc Ubuntu 10.04 question... #2 patx

  • Senior Member
  • 55 posts

0
Neutral

Posted 2 December 2011 - 21:56

Ok i got it to work but as i suspected all emu and enigma needs to be down for it to work...

Fixed the dvb-type mismatch error using -f S insteand of -f S2... How Do i stop enigma completely on Dm500 ??

patx@Patx:/usr/sbin$ sudo vtunerc -f S -n 192.168.14.119
vtunerc: vtuner client (vtunerc), part of vtuner project
Visit http://code.google.com/p/vtuner/ for more information
Copyright © 2009-11 Roland Mieslinger
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.
vtunerc: Revision:63f73de8b63c/tip DVB:5.1 allow:5.x NetProto:2 MsgSize:96, Debug:3
vtunerc: [2258 ../../vtunerc.c:452] info: added frontend mode DVB-S as mode 0, searching for tuner types 1
vtunerc: [2258 ../../vtunerc.c:477] info: direct connection: host='192.168.14.119' port=39305
vtunerc: [2258 ../../vtunerc.c:533] info: Created pidfile /var/run/vtunerc0.pid
vtunerc: [2258 ../../vtunerc.c:586] info: no server connected. discover thread is 0 (DWS_IDLE:0, DWS_RUNNING:1)
vtunerc: [2258 ../../vtunerc.c:588] info: changing frontend mode to DVB-S
vtunerc: [2258 ../../vtunerc.c:617] info: Start discover worker for device type 1 groups ffff
vtunerc: [2258 ../../vtunerc.c:214] info: starting discover thread
vtunerc: [2258 ../../vtunerc.c:258] info: Sending direct discover message for device types 1
vtunerc: [2258 ../../vtunerc.c:272] info: Received discover message from 192.168.14.119 proto2 control 4949 data 4950
vtunerc: [2258 ../../vtunerc.c:637] info: connect control socket to 192.168.14.119:4949
vtunerc: [2258 ../../vtunerc.c:654] info: connected data socket to 192.168.14.119:4950



Re: Vtunerd Dm500 <> vtunerc Ubuntu 10.04 question... #3 hemispherical1

  • Senior Member
  • 1,596 posts

+49
Good

Posted 2 December 2011 - 21:56

It's been a long time, but iirc there's a /tmp/.enigma file. If you delete that enigma will not automatically restart when you kill it.

--
hemi

Re: Vtunerd Dm500 <> vtunerc Ubuntu 10.04 question... #4 WanWizard

  • Forum Moderator
    PLi® Core member
  • 48,469 posts

+824
Excellent

Posted 3 December 2011 - 01:16

You can also kill start_enigma first, which contains the loop that restarts it...

Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: Vtunerd Dm500 <> vtunerc Ubuntu 10.04 question... #5 atari

  • Senior Member
  • 27 posts

0
Neutral

Posted 10 September 2019 - 19:40

did anyone success to use vtuner<>minisatip on dm500






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users