Hi. I get the same error "ERROR: Could not detect DVBAPI version", but dvbapi still works. I run oscam r9100 on a server, and it receive emms from the box and write them on the card. Above oscam r9100 I get the "ERROR: Could not detect DVBAPI version" but dvbapi don't works and I get this error "reject group-no matching reader". So if you get just the "Could not detect DVBAPI version" error, your dvbapi should works. I hope this can help you. Bye.
Posts by pattinik
-
-
Quote
Sorry m8, I was testing on SVN, do as I said earlier but enter 289 for CHOOSE menu, that will checkout Modern version 8917..
No problem man, I figured out what you meant. ;-)
Quote
Also, why are you using dvbapi? Are you compiling for a set top box or server??
If it is for a set top box, you will have to load the toolchain..I'm using dvdapi, because I run oscam on a server, and the emms of tivusat card change every f***ing week. :(
QuoteBut the last fully supported version is SVN r8638
I'm searching some very nice templates for my oscam (r9100 like I said), may you suggest me a cool one? :) -
Hi,Thank you for the very clear explanation. I followed the instruction but when I select "Choose" in simplebuil with the oscamsource.url, and I type my desidered version oscam such as "8917", the program crashs and simple go back to the terminal. So I thought to type the number revision of modern webif, like "525", then the program download the right files and I have no problem to compile it. At the end I got oscam r9100/r525, I have to use this because, like I said, with above versions I have dvbapi issues (no matching reader- group reject). Anyway I run this version and everything it's ok! :D I downloaded the picons from the other threads of the forum and they are working great and my oscam is pretty cool! ;-) By the way I want to know two other things, I hope I'm not abusing of your patience. :48_002:
First: I putted the pincons of the decoders and they are looking great, but I have to click on it to see which user it is. So I thought to make it easier creating customized picons for each ip's user that allow me to recognize the user quickly. Should it works? I thought to rename the picon like "IC_X.X.X.X.tpl".
Second: I saw others wonderful template, like those made by ***dans. To use those, should I just put the folders in my oscam's path and configure the files in webif config like this : "httptpl =/my/path, httpcss = /my/path/site.css, httpjscript = oscam.js". Am I wrong?
Thank you again for everything :D
Bye. -
Thank you ferdi for the reply. Now I deleted the entire simplebuild and recreated the folder with the modern environment following your previously post. Now I got the modern webif when I build oscam. Now the question is, how can I get the modern webif with another version of oscam? Because when I build oscam I get the the version r9542 build r782. I need to compile the version r8917 because with the r9542 I get dvbapi issues. Another question is, how can I aplly the patch with modern style and all those cool picons?
Sorry if I'm asking too noob's things. Bye
-
here there's the simplebuild log:
Quote
patch(s) applicare modern_v2.26.patch
patching file module-webif.c
Hunk #1 succeeded at 47 with fuzz 1.
Hunk #2 succeeded at 1882 (offset 44 lines).
Hunk #3 FAILED at 2226.
Hunk #4 FAILED at 2234.
Hunk #5 FAILED at 2282.
Hunk #6 succeeded at 2531 (offset 63 lines).
Hunk #7 FAILED at 2476.
Hunk #8 FAILED at 3169.
Hunk #9 succeeded at 3288 (offset 97 lines).
Hunk #10 succeeded at 3321 (offset 97 lines).
Hunk #11 succeeded at 3691 (offset 97 lines).
Hunk #12 succeeded at 4731 (offset 97 lines).
5 out of 12 hunks FAILED -- saving rejects to file module-webif.c.rej
patching file webif/cacheex/cacheex.html
patching file webif/config/menu_anticasc.html
patching file webif/config/menu_camd33.html
patching file webif/config/menu_camd35.html
patching file webif/config/menu_camd35tcp.html
patching file webif/config/menu_cccam.html
patching file webif/config/menu_dvbapi.html
patching file webif/config/menu.html
patching file webif/config/menu_lcd.html
patching file webif/config/menu_loadbalancer.html
patching file webif/config/menu_monitor.html
patching file webif/config/menu_newcamd.html
patching file webif/config/menu_radegast.html
patching file webif/config/menu_serial.html
patching file webif/config/menu_webif.html
patching file webif/emm/emm.html
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file webif/emm/emm.html.rej
patching file webif/entitlements/entitlements_bit.html
patching file webif/entitlements/entitlements.html
patching file webif/failban/failban.html
patching file webif/files/menu_anticasc.html
patching file webif/files/menu_dvbapi.html
patching file webif/files/menu.html
patching file webif/include/css.css
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file webif/include/css.css.rej
patching file webif/include/footer.html
patching file webif/include/full.html
patching file webif/include/header.html
patching file webif/include/jscript.js
patching file webif/include/menu_cacheexmenuitem.html
patching file webif/include/menu.html
patching file webif/include/refresh.html
patching file webif/readers/readers.html
patching file webif/readerstats/readerstats.html
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file webif/readerstats/readerstats.html.rej
patching file webif/services_edit/services_edit.html
patching file webif/shutdown/pre_shutdown.html
patching file webif/shutdown/shutdown.html
patching file webif/status/status_clientstatusbit.html
patching file webif/status/status.html
patching file webif/userconfig/userconfig_cwcyclethv.html
patching file webif/userconfig/userconfig_entry_cwcycletbv.html
patching file webif/userconfig/userconfig_entry.html
patching file webif/userconfig/userconfig.html
patching file webif/userconfig/userconfig_newuserform.html
patching file webif/user_edit/user_edit.html -
Hi guys, I solved the problem. It was an issue with oscam version r9504. No I'm running r8917 and it works great. Byezz
Here my configuration:Quote
oscam.conf[dvbapi]
enabled = 1
boxtype = pc
user = test
request_mode = 1
au = 1oscam.user
[account]
user = test
pwd = test
au = reader label
group = 1oscam.dvbapi
P: 183D:000000 1
P: 183D:005411 1 -
Hi all. Really nice work! :D However I was trying to use the modern webif compiling oscam with simplebuild, I putted the file.patch in "/opt/simplebuild/patches", but when I compile it and replace the old oscam binary I get the usual same old boring webif. The output file in the folder archiv has the string "-modern" but it doesn't work. Any advise?
Thank you a lot! -
Hi all guys, I need to activate a tivusat card into my server running oscam 1.20 unstable with ubuntu server. I read in some threads how to do it, but it won't work. Can some give me any tips? Or just link me a guide for oscam.dvbapi on ubuntu? Thanks, hope some help me. Byeeee
-
you can start with all.
or call *** center ,and ask them, what they recommend, my dear friend from Italy.
or call this guys - Thor II, and Deltafox , and Maseitexan- and ask them,
you are very new here, I see.....and a very good programmer. success.
My dear friend I really apprecciate your sarcasm... Programming isn't my field and neither IT. So sorry if my questions look so stupid for you, but I think that forum's purpose is to help people also if they are "stupid", at least give them a little help to understand something in a newfield where they just arrived. I'm just trying to learn, you're not constrained to help me. If you want help me, at least showing what I can do for helping (like exchange logs from cards) fine,otherwise I will not cry. There's a life over computer's stuff mate, that's a success! -
opps I read now about Sbox. But I think Sbox is harder to use with our beloved smartreaders.... I didn't found in the forum a way to configure it.... Now I'm trying to recompile oscam with simple build (I'm a noob in programming) but I don't know wich module should I disable. Any advice?
-
FALSE
you need to get the OSCAM source, and to make your own Oscam version without any EMM - G,U,B ,and NANO , support inside.
Provider SXY decided to replace the card to NDS 4 during this year, that has a new secure memory near CPU- and will protect better the written inside EEProm.
process will be ended until 2014. { always in may , June, they send this Nano EMM, to attack the cards, in sharing}
this memory - is develop for security
AT88SCxx,
AT88SC0104C、AT88SC0204C、AT88SC0404C、AT88SC0808C 、AT88SC1616C、AT88SC3216C、AT88SC6416C、AT88SC12816C、AT88SC25616C
produce in China, and very High techALL OSCAM have - a gate inside to accept NANO- soo, provider use this backdoor ,to block your cards.{ I think that is a pack between developer of soft Oscam, and TV provider- unofficial, or they make this mistake in program .....by mistake....but I belive they made this on puurpose ]
the solution is a new OSCAM version , made by you, and to eject EMM functions. please start,....do not lose time?
Italian forums, cut this info out-- only to help Italian provider- to change the NDS 3 in NDS 4 more easy- and to let the provider to have control on last version of Oscam, and to keep control on users of cards with OTA update. ( with this back door) they can block the cards, in Sharing , when they want.first are attacked the users from Sharing ( special Oscam users}, after , that they will sent the nano EMM to affect also cards in official box-- to replace the cards from normal ( correct ) user that have the card ONLY in official box. { this will be in last phase]
I hope I was helpful
bye
solution, is special OScam{homemade], or try different EMU {Sbox}God, you're been really helpfull!Thank you very much!:D So should I just recompile oscam from the source without emm's shit! And what's about others emus, they have this back door?
-
No emu can stop 9996 all of them kill the card
So there is no solution?!And what's about card 002, they have enough space for backdoor? -
Quote
soo avoid , version 1.20 and possible 1.10 rc ........... 1.20 I tested myself, you cannot control it.
Which others emu we can use instead of oscam? -
Is very convincing that right after update on original decoder can receive a backdor which once is dropped on linux and from here starts to decay card till it comes to 9995 error.
Cause almost all have closed emm and there is no way to receive them.
And they use only once this backdoor cause can not leave traces on pc.
But i`m convinced that it resides all the time in card if you use that always on its box.
When in linux it goess off the card and start its 'porcheria italiana' to make card 9995 or 6.
I belive that once updated the card if read with a phoenix this backdoor can be read and analysed and few lines in oscam are needed to erase this backdoor once initalizing card saving it from the blockDo you know if cards that start with 0001 or 0002 are less affected than latest with 0003? I read about 0001s are stonger....
-
news is this:
from 2013, on update - for data tiers, they sent EMM for each tier, according with your card contract and serial.
BUT after they finish the date update for each tiers, they sent a last EMM, that goes , in the card , in the section with free space {not used by operating system ROM}
you finish your card update- in origial rec
and you want to put the card in OSacm box
:)))
now comes the fun part....
if you are using Oscam 1.20, the remaining EMM from card, will go out from card via TDA 8024,{ and will force your processor or your operating system } and will change the Oscam server setting, disable reader and change also MHZ value from set value by you
in this way the provider can burn your card, please notice that. very simple procedure.
the good part is that the this EMM has power only one time, after is out { he left the card }you are safe. { is a one time run}depending on what is programed to do,...on card or on box.
soo avoid , version 1.20 and possible 1.10 rc ........... 1.20 I tested myself, you cannot control it.
in conclusion: they put the bomb , inside your card, in free space reaming , of card, because they have enough {4096 Bytes of EEPROM}
[is the principle of troian Horse -- very simple and efficient ]
this bomb can have different purpose, and if starts to delete or rewrite , and after this process the info is out....from the original version { from card or Oscam -depending on EMM purpose ]last year they block the cards, with this system, by modifying the Nano inside all cards- contract or prepaid because of black market for this items from Italy .... and to correct, you need to go to them to present the card.
Hi, I noticed this in my oscam configuration:
QuoteECMs OK 14254 (99.84%) ECMs NOK 23 (0.16%)
, maybe in that small part of nok ecm's there is our killer...
-
this is correct
I tried that configuration but it still don't work! :( Any other advice?
P.S.
Sei sei italiano, potremmo parlare anche normalmente. XD
-
Ok, thanks, I will try with this configuration. But I don't need to upgrade to cccam 2.2.1 on the server? Currently I'm running 2.14 on server and 2.2.1 on the client the should give me emm.
Bye -
Hi all guys!
I'm having a little issue with the weekly EMM update of the IT tivùsat. The card works perfect on a ubuntu server 12.04 x64 with oscam 1.20 unstable + CCcam 2.14, but every week emms go out of date and they don't update automatically, so I have to put the card manually on my box to update them. I'm using this configuration on oscam.server:
Quote[reader]
label = Tivusat
protocol = smargo
device = /dev/ttyUSB1
caid = 183D
rsakey = A92DA7....
detect = cd
ident = 183D:000000,005411
group = 1
emmcache = 1,2,2
blockemm-unknown = 1
blockemm-u = 1
blockemm-g = 1
blockemm-s = 0
lb_weight = 300I also added on my client's Fline a "1" on the emms rules, but entitlements won't update(I'm running CCcam 2.30 on the client). :(
Should I try with CCcam 2.21 on the server? Or maybe I should change something on the configuration? Give me some advice! :)
Thank you all guys! :D