Compile your own exactly the way you need it.
[h=3]Tutorial: Updating Oscam to latest SVN - Ubuntu & debian with Simplebuild[/h]
Thanks I have now solved my issue
Compile your own exactly the way you need it.
[h=3]Tutorial: Updating Oscam to latest SVN - Ubuntu & debian with Simplebuild[/h]
Thanks I have now solved my issue
I click files and pcsc doesn't come under active modules which I find weird because on readers if I try to add a new one I have the option to pick pcsc as protocol. I am currently running Version: 1.20-unstable_svn Rev. 7209.
What version would you recommend to solve this issue?
My Protocol is PCSC mate however for whatever reason it keeps picking up the mouse, I feel like maybe its reading it from another folder. Could that be possible at all
EDIT: Just had a look at oscam.conf through oscam webif and I have the correct code don't get why it keeps coming up as mouse
Really hoping somebody can help me with this;
Every minute on (myi.p.):8888 I continue to get
3/08/2013 13:34:44 82E3EC0 r #mysmartcardreader [mouse] ERROR: Opening device 000:000 (errno=2 No such file or directory)
23/08/2013 13:34:44 82E3EC0 r #mysmartcardreader [mouse] Cannot open device: 000:000
I currently only have a freeview sly card till next week but I wanted to get everything running before I got it.
I've checked opensc-tool -l which detects my Omnikey 3121 & I've checked pcsc_scan which detects the s*y card
What could I be doing wrong? Any help would be much appreciated.
Hi Mate, I've checked and I have that command present.
I've just done a fresh install and I'm having the same issue, I am running Ubuntu 12.04.3 LTS (GNU/Linux 3.5.0-23-generic x86_64)
Great tutorial, I've followed it from start to finish. But for some reason I can't get oscam or cccam to start when I try Sudo CCCam.x86 and Sudo oscam .b nothing happens.
I then try Sudo killall -9 CCcam.x86 and sudo killall -9 oscam, and I get no process found. I've searched and gone through various threads a lot of people with similar solution but I haven't found a working solution for me.
I had accidentally installed the 64bit version however I have overwritten that with the 32bit Version, could that of caused a conflict?
Don't mind starting from beginning again but would be nice to potentially solve it a lot quicker