PDA

View Full Version : Oscam Runing On Triple Dragon (Almost Ok ?)



passete
09-04-2011, 01:34 PM
I'm runing oscam on Triple Dragon, but it seems that the problem is the dvb_api.
I tryed several dvbapi combinations, without success, also i found how to initialize the card readers, but not working.
maybe someone can give us the good clues :


2011/04/09 11:47:47 4000 s 82 tier-id's loaded
2011/04/09 11:47:47 4000 s 1000 provid's loaded
2011/04/09 11:47:47 4000 s 22 lengths for caid guessing loaded
2011/04/09 11:47:47 4000 s monitor: disabled
2011/04/09 11:47:47 4000 s camd33: disabled
2011/04/09 11:47:47 4000 s camd35: disabled
2011/04/09 11:47:47 4000 s cs378x: disabled
2011/04/09 11:47:47 4000 s newcamd: disabled
2011/04/09 11:47:47 4000 s cccam: disabled
2011/04/09 11:47:47 4000 s radegast: disabled
2011/04/09 11:47:47 4000 s http thread started
2011/04/09 11:47:47 4000 s creating thread for device /dev/stb/tdsc0
2011/04/09 11:47:47 4000 s creating thread for device /dev/stb/tdsc1
2011/04/09 11:47:47 4000 s creating thread for device 192.168.1.12
2011/04/09 11:47:47 4000 s loadbalancer: can't read from file /tmp/.oscam/stat
2011/04/09 11:47:47 4000 s waiting for local card init
2011/04/09 11:47:47 8003 h HTTP Server listening on port 8888
2011/04/09 11:47:47 C004 r reader thread started (thread= C004, label=lower_slot, device=/dev/stb/tdsc0, detect=cd, mhz=500, cardmhz=357)
2011/04/09 11:47:47 10005 r reader thread started (thread= 10005, label=upper_slot, device=/dev/stb/tdsc1, detect=cd, mhz=500, cardmhz=357)
2011/04/09 11:47:47 14006 p proxy thread started (thread= 14006, label=dm_800se, server=192.168.1.12)
2011/04/09 11:47:47 14006 p connecting to 192.168.1.12
2011/04/09 11:47:47 14006 p 192.168.1.12: resolved ip=192.168.1.12
2011/04/09 11:47:48 4000 s init for all local cards done
2011/04/09 11:47:48 4000 s anti cascading disabled
2011/04/09 11:47:48 18007 c plain dvbapi-client granted (anonymous, au=off)
2011/04/09 11:47:48 18007 c dvbapi: 361 entries read from oscam.dvbapi
2011/04/09 11:47:48 18007 c dvbapi: could not detect api version

passete
10-04-2011, 01:40 PM
i think that i found why, oscam is runing but is not requesting ecm's !
The trick is, all binaries (emus) on tripledragon, are not in var/bin, but in stb/bin.
I tryed to copy oscam to this folder stb/bin, but nothing is writed.

Now, i would like to know, how to overwrite or delete a read only file ?
tryed with telnet, but refused.

ian
10-04-2011, 02:42 PM
if a file is in use it cannot be deleted or overwritten.

ensure that all instances of oscam are killed using the killall -9 oscam command from telnet
then FTP into the box and delete the existing file,then FTP the new file over and chmod to 755.

Ian.

passete
10-04-2011, 04:25 PM
Thanks ian
oscam is not runing, neither evocamd (file that i would like to overwrite or simply delete), then place oscam (or renamed evocamd, that is actualy oscam) in this folder stb/bin, but it is a read only folder, i'm stuck.
solution is to open the original image (with pc linux) and replace this file with oscam.
I'm installing ubunto on a pc to see if i can open this bin image.

snakie
11-04-2011, 11:03 AM
Actually the problem seems to be incompatible api.
When we say dvb-api , usually mean the way the OS communicates with a program to pass the PAT,PMT ( ecm and emm filter pids ).
On dreambox receivers its the dvb-api v3 as far as i remember, which means under the /dev/dvb/ will have the correct structure of devices talking the language based on dvb-api standards.
I guess in TD that is not supported , so the TD is creating some other dvb devices (like many other receivers in the market) which oscam dont know how to handle.
A list of the /dev/ or /dev/dvb/ or /dev/adapter(s)/ would show what is created.
Then must check in oscam code to see if they are included for support.

Its possible also some image makers to create symbolic links for some of the dvb adapters to look compatible with dvb-api, but still the communication be incorrect.

passete
11-04-2011, 11:29 AM
Thanks snakie
i'm also prety 100% sure that is the dvbapi.
Spended a few hours yesterday (testing diferents dvbapi combinations, no joy)

Here what i have on the /dev
/dev/stb/taudio
/dev/stb/tdsystem
/dev/stb/tdsc0
/dev/stb/tdsc1
/dev/stb/tdtuner1
/dev/stb/tddemux0
/dev/stb/tddemux1
/dev/stb/tddemux2
/dev/stb/tdlcd
/dev/stb/tdci
/dev/fb/0
/dev/stb/tdpvr
/dev/stb/tdremote
/dev/stb/tuner0
/dev/stb/tuner2
/dev/stb/tdvideo

Now on /dev/stb i have this :
tdaudio
tdauio_mixer
tdci
tddemux0
tddemux1
tddemux2
tdfx
tdlcd
tdpvr
tdremote
tdsc0
tdsc1
tdsystem
tdtuner0
tdtuner1
tdtuner2
tdvideo

EDIT: also can't get smargo working with oscam

snakie
11-04-2011, 08:03 PM
No reference in the oscam trunk for such api, i checked dvbapi.c , but no use of such adapters.
So i guess no go .

passete
11-04-2011, 08:45 PM
This is really a big joke, why people are compiling 3/4 times a day, oscam for Triple Dragon ?
Also, Smargo States "Triple Dragon" working, but no info about "how" ! LOL

Thanks m8