Jump to content


Photo

Libusb support added to oscam-experimental


  • Please log in to reply
77 replies to this topic

Re: Libusb support added to oscam-experimental #41 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 13:06

is your machine vuduo or vuultimo ??


ultimo!

Re: Libusb support added to oscam-experimental #42 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 13:08

when You replaced the oscam bin in vu by that from dm500hd.

It's best that You also do a full box restart. On the other hand if list_smargo is not working it will never work. Then there is something wrong elsewhere or a driver conflict in vu duo build

Re: Libusb support added to oscam-experimental #43 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 13:10

when You replaced the oscam bin in vu by that from dm500hd.

It's best that You also do a full box restart. On the other hand if list_smargo is not working it will never work. Then there is something wrong elsewhere or a driver conflict in vu duo build


Yes, I did restart to make sure the new binary was loaded. I think the feed for oscam is the same on both VU/Ultimo and dm500hd, since the binaries was same size.

Must be something wrong in the vu+ image.

Edited by spock, 25 June 2012 - 13:10.


Re: Libusb support added to oscam-experimental #44 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 13:16

Then a question to a core member.

Which machine do have to select in openpli 3.0 to build vu image ? As in make file from 3.0 it seems not to be present yet ?

Re: Libusb support added to oscam-experimental #45 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 13:20

It's the build downloaded from main page: http://openpli.org/download/vuultimo/

Re: Libusb support added to oscam-experimental #46 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 13:24

No no I gonna build an vuultimo image and see what it does with the build of oscam . need to build a full image self in order to investigate. It's vuultimo that I need to select. and as far i could see the makefile isn't adapted, but you can build anyway I 'll give it I try. It will well take some time.

Re: Libusb support added to oscam-experimental #47 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 25 June 2012 - 13:28

for vuultimo you use

MACHINE=vuultimo make init

(just like you did with the other machines you're building for)

Edited by pieterg, 25 June 2012 - 13:28.


Re: Libusb support added to oscam-experimental #48 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 13:41

Thanks' so i'm shure i selected the good machine

Build in process now It was a good occasion to test my script it does work

Re: Libusb support added to oscam-experimental #49 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 13:47

Many thanks for helping!

Meanwhile I've tried a couple of things;
- running the smargo in a powered usb-hub
- trying binaries for mips-tuxbox-oe2.0 from http://oscam.to (http://download.osca...ps-tuxbox-oe2.0)
- opening up smargo unit to verify it's an original (not mup), it is original
- unloading all other usb related modules (wifi etc.)

but nothing helps. list_smargo has no output and oscam keeps telling me error -99 (which apparently means LIBUSB_OTHER_ERROR, in other words an unspecified error according to libusb docs/mailing lists).

If there is more things to test I'm happy to try anything to help debug this. Just point me in the right direction :)

Edited by spock, 25 June 2012 - 13:52.


Re: Libusb support added to oscam-experimental #50 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 14:19

Wen build is done , I go just check what's up with the list_smargo. If the oscam version of list_smargo does not issue any output on a vuultimo ,then we are running into troubles. First a go look on the build reports when they are done. Oscam self and it's list_smargo util does use static libusb link. seems that possibly it does conflict on the vu. For a pc the same is done. But no conflicts in use.

Perhaps we will need to build other static libusb-1.00 version in vu image which then will be used when compiling oscam. changes to oscam source itself for this matter, are a lot. And will require to much maintenance in openpli self later on.

Since I do not have an vu box Yes i will ask You to test further. If I can find some possible errors. I will build temporrarely mannually patched versions . If they work then we can adapt the openpli image for that specific box.

Re: Libusb support added to oscam-experimental #51 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 14:56

Sounds good.

Is it possible to build list_smargo with debug? Then I could run it through gdb to get more information, if that's possible (I'm no expert in this area, but I've done it before to help debugging).

Re: Libusb support added to oscam-experimental #52 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 15:57

Just for test here the very latest oscam-experimental and list smargo. compiled in vuultimo image for openpli 3.0

Can You just try. As it did compile very good no errors. They do work on dreambox.

Just unpack use ftp to box . first remove the present list_oscam and oscam_experimental , Then copy the two files From this package to /usr/bin

restart box (full reboot not enigma2 only) and test.

Attached Files



Re: Libusb support added to oscam-experimental #53 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 16:25

No luck. :(

root@vuultimo:/media/hdd/oscamexpListsmargvu/usr/bin# pwd
/hdd/oscamexpListsmargvu/usr/bin
root@vuultimo:/media/hdd/oscamexpListsmargvu/usr/bin# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 003 Device 002: ID 0403:6001
root@vuultimo:/media/hdd/oscamexpListsmargvu/usr/bin# ./list_smargo
root@vuultimo:/media/hdd/oscamexpListsmargvu/usr/bin# ./oscam-experimental -c /etc/tuxbox/config/oscam-experimental/ -r 2 -b
root@vuultimo:/media/hdd/oscamexpListsmargvu/usr/bin#

2012/06/25 18:22:33 0 s starting thread log_list_thread
2012/06/25 18:22:33 0 s log_list_thread thread started
2012/06/25 18:22:33 0 s >> OSCam << cardserver started, version 1.20-unstable_svn, build #7079 (mipsel-oe-linux)
2012/06/25 18:22:33 0 s version=1.20-unstable_svn, build #7079, system=mipsel-oe-linux, nice=-1
2012/06/25 18:22:33 0 s client max. idle=0 sec, debug level=0
2012/06/25 18:22:33 0 s max. logsize=5000 Kb, loghistorysize=9096 bytes
2012/06/25 18:22:33 0 s client timeout=5000 ms, fallback timeout=4500 ms, cache delay=0 ms
2012/06/25 18:22:33 0 s services reloaded: 0 services freed, 0 services loaded, rejected 0
2012/06/25 18:22:33 0 s userdb reloaded: 2 accounts loaded, 0 expired, 0 disabled
2012/06/25 18:22:33 0 s signal handling initialized (type=sysv)
2012/06/25 18:22:33 0 s oscam.srvid loading failed, old format
2012/06/25 18:22:33 0 s oscam.tiers loading failed
2012/06/25 18:22:33 0 s oscam.provid loading failed, wrong format?
2012/06/25 18:22:33 0 s 0 lengths for caid guessing loaded
2012/06/25 18:22:33 0 s can't open whitelist file /etc/tuxbox/config/oscam-experimental//oscam.whitelist
2012/06/25 18:22:33 0 s can't open cacheex-matcher file /etc/tuxbox/config/oscam-experimental//oscam.cacheex
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s monitor: initialized (fd=5, port=16500)
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s camd35: disabled
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s cs378x: disabled
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s newcamd: disabled
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s cccam: initialized (fd=6, port=55500, crypted)
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s pandora: disabled
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s csp: disabled
2012/06/25 18:22:33 0 s Starting listener 0
2012/06/25 18:22:33 0 s radegast: disabled
2012/06/25 18:22:33 0 s starting thread http
2012/06/25 18:22:33 0 s http thread started
2012/06/25 18:22:33 0 s starting thread reader check
2012/06/25 18:22:33 0 s reader check thread started
2012/06/25 18:22:33 77900468 h HTTP Server listening on port 16200
2012/06/25 18:22:33 0 s starting thread check
2012/06/25 18:22:33 0 s check thread started
2012/06/25 18:22:33 0 s creating thread for device 003:002
2012/06/25 18:22:33 0 s loadbalancer: can't read from file /tmp/.oscam/stat
2012/06/25 18:22:33 0 s anti cascading disabled
2012/06/25 18:22:33 5AE2E8 r Libusb init error : -99
2012/06/25 18:22:33 5AE2E8 r smargo [smartreader] Cannot open device: 003:002
2012/06/25 18:22:33 77901CB8 c plain dvbapi-client granted (dvbapi, au=auto (5 reader))
2012/06/25 18:22:33 77901CB8 c dvbapi: 0 entries read from oscam.dvbapi
2012/06/25 18:22:34 77901CB8 c dvbapi: [ADD PID 0] CAID: 0960 ECM_PID: 0501 PROVID: 000000
2012/06/25 18:22:34 77901CB8 c dvbapi: [ADD PID 1] CAID: 0961 ECM_PID: 0501 PROVID: 000000
2012/06/25 18:22:34 77901CB8 c dvbapi: [ADD PID 2] CAID: 0963 ECM_PID: 0501 PROVID: 000000
2012/06/25 18:22:34 77901CB8 c dvbapi: new program number: 0F10 (0960:0F10 unknown) [pmt_list_management 3]
2012/06/25 18:22:34 77901CB8 c dvbapi: try pids again #1
2012/06/25 18:22:34 77901CB8 c dvbapi: try pids again #2
2012/06/25 18:22:34 77901CB8 c dvbapi: try pids again #3
2012/06/25 18:22:34 77901CB8 c dvbapi: can't decode channel
2012/06/25 18:22:48 779040D0 c encrypted cccam-client 192.168.199.8 granted (dm500hd, au=auto (5 reader))

Also tried replacing binaries in /usr/bin but result is the same as before.

Edited by spock, 25 June 2012 - 16:27.


Re: Libusb support added to oscam-experimental #54 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 16:50

this command will not work

./oscam-experimental -c /etc/tuxbox/config/oscam-experimental/ -r 2 -b

the correct one is

./oscam-experimental -c /etc/tuxbox/config/oscam-experimental -r 2 -b


Two to check the good working You really need to put all on the correct place first as it may influence.

the oscam-experimental should be in /usr/bin not from an other device like /meddia/hdd
the list smargo should be in /usr/bin ass well

list_smargo is an util . Its just made to check the location od your smartreader and eventually serial info. You do not need to start it before oscam.

At first use all default settings off openpli.

there may absolutely be no other running instance of oscam.

Re: Libusb support added to oscam-experimental #55 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 June 2012 - 16:58

Just remove the list_oscam from /usr/bin
remove oscam-experimental from /usr/bin

copy the files given to /usr/bin not somewhere else

start oscam trough softcam on box. What You can do as well is

telnet to box

cd to /etc/init.d

sh softcam.oscam-experimental stop

sh softcam.oscam-experimental start

Re: Libusb support added to oscam-experimental #56 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 17:42

Tried that too. I'm no newbie to linux :-)

/etc/rc0.d/K50softcam stop
rm /usr/bin/oscam-experimental
rm /usr/bin/list_smargo
cp ./oscam-experimental /usr/bin
cp ./list_smargo /usr/bin
reboot

As you can see from the log too it starts your build #7079 (current build in openpli feed is #7069), and loads the configuration files properly (disabled all readers except the smargo).
But the problem remains.

Edited by spock, 25 June 2012 - 17:44.


Re: Libusb support added to oscam-experimental #57 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 25 June 2012 - 17:52

I know it's hard to trust users that they're running the correct version and loading the correct files, even though I might tell you I know what I'm doing. If you want you could tag your oscam build with something like "christest" so you can see in the log that the correct build is starting.

Anyway isn't it possible to build list_smargo with debugging symbols so it can be run through gdb and maybe we can find out something more about what's going wrong? (This is not something I'm so experienced with, maybe it's not even possible in this scenario, but as I said earlier I've done it before to hunt down bugs in other programs).

Since not even list_smargo will work, we could maybe focus on that one instead of all of what is oscam. If we manage to get list_smargo working (i.e linking correct libs, be it static or dynamic ones), maybe we will figure out why oscam also has these issues. I noticed on oscam.to ULC builds they provide the libusb separately.

Again I'm not really a programmer so maybe what I'm saying is not even possible, but I do have experience with compiling/building and debugging software on linux.

Edited by spock, 25 June 2012 - 17:55.


Re: Libusb support added to oscam-experimental #58 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 27 June 2012 - 11:06

@pieterg @Wanwizard

Since in openpli 3.0 vuultimo image list_smargo utility and oscam does compile perfectly whitout any error, The binary's are issued correctly and do work also on dm8000. That is normal as vu is also mip32 linux tuxbox.
It then results in exact same binary.

I just thought about something. The smartreader support and detect utility is based on the loaded usb device inode.
And does read and interact based on the inode self.
By dm boxes or pc's (ubuntu debian),The inodes are located into /dev/bus/usb/busid/devid with the devid being the inode and busid is map.

I do not have a vuultimo box. That's why i can not check this out.

The question is does the vuultimo uses other dev node location then that mentionned above ?

Re: Libusb support added to oscam-experimental #59 spock

  • Senior Member
  • 214 posts

+1
Neutral

Posted 27 June 2012 - 11:29

I can reply to this;

On my DM500HD, it's working fine:
root@dm500hd:~# cd /dev/bus/usb
root@dm500hd:/dev/bus/usb# ls
001  002  003  004
root@dm500hd:/dev/bus/usb# pwd
/dev/bus/usb
root@dm500hd:/dev/bus/usb#

On the VU+ Ultimo on the other hand, the directory does not exist:
root@vuultimo:~# cd /dev/bus
-sh: cd: can't cd to /dev/bus
root@vuultimo:~# cd /dev/bus/usb
-sh: cd: can't cd to /dev/bus/usb
root@vuultimo:~# cd /dev
root@vuultimo:/dev# ls
3-2				 dvb0.ca4		    dvb0.video0		 hda19			   log				 mtd1ro			  mtdblock3		   sda				 tty20			   tty38			   tty55			   ubi0_0
apm_bios		    dvb0.demux0		 dvb0.video1		 hda2			    loop-control	    mtd2			    mtdblock4		   sda1			    tty21			   tty39			   tty56			   ubi_ctrl
audio			   dvb0.demux1		 fb				  hda3			    loop0			   mtd2ro			  mtdblock5		   seq				 tty22			   tty4			    tty57			   urandom
autofs			  dvb0.demux2		 fb0				 hda4			    loop1			   mtd3			    mtdblock6		   sg0				 tty23			   tty40			   tty58			   usbdev1.1
bcm_mu			  dvb0.demux3		 fp0				 hda5			    loop2			   mtd3ro			  mtdblock7		   snd				 tty24			   tty41			   tty59			   usbdev2.1
ci0				 dvb0.demux4		 fpga_dp			 hda6			    loop3			   mtd4			    mtdblock8		   tty				 tty25			   tty42			   tty6			    usbdev3.1
ci1				 dvb0.dvr0		   full			    hda7			    loop4			   mtd4ro			  network_latency	 tty0			    tty26			   tty43			   tty60			   usbdev3.2
console			 dvb0.dvr1		   fuse			    hda8			    loop5			   mtd5			    network_throughput  tty1			    tty27			   tty44			   tty61			   usbdev4.1
cpu_dma_latency	 dvb0.dvr2		   hda				 hda9			    loop6			   mtd5ro			  null			    tty10			   tty28			   tty45			   tty62			   vcs
dbox			    dvb0.dvr3		   hda1			    hdmi_cec		    loop7			   mtd6			    port			    tty11			   tty29			   tty46			   tty63			   vcs1
device			  dvb0.dvr4		   hda10			   i2c				 mdev.seq		    mtd6ro			  ptmx			    tty12			   tty3			    tty47			   tty7			    vcsa
dp				  dvb0.frontend0	  hda11			   i2c-0			   mem				 mtd7			    pts				 tty13			   tty30			   tty48			   tty8			    vcsa1
dsp				 dvb0.frontend1	  hda12			   i2c-1			   misc			    mtd7ro			  ram0			    tty14			   tty31			   tty49			   tty9			    zero
dvb				 dvb0.frontend2	  hda13			   i2c-2			   mixer			   mtd8			    ram1			    tty15			   tty32			   tty5			    ttyS0
dvb0.audio0		 dvb0.net0		   hda14			   i2c-3			   mtab			    mtd8ro			  ram2			    tty16			   tty33			   tty50			   ttyS1
dvb0.ca0		    dvb0.net1		   hda15			   initctl			 mtd				 mtdblock		    ram3			    tty17			   tty34			   tty51			   ttyS2
dvb0.ca1		    dvb0.net2		   hda16			   input			   mtd0			    mtdblock0		   random			  tty18			   tty35			   tty52			   ttyS3
dvb0.ca2		    dvb0.net3		   hda17			   kmem			    mtd0ro			  mtdblock1		   sci0			    tty19			   tty36			   tty53			   ttySA0
dvb0.ca3		    dvb0.net4		   hda18			   kmsg			    mtd1			    mtdblock2		   sci1			    tty2			    tty37			   tty54			   ubi0
root@vuultimo:/dev#

I think you're on to something!

Re: Libusb support added to oscam-experimental #60 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 27 June 2012 - 11:31

DEVTMPFS was missing in vuplus kernels.
That would probably fix coldplugging.
I'm wondering about hotplugging though (for your dm8000 as well), we might need to add a custom mdev rule to create /dev/bus/usb nodes for hotplug events.


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users