danofun Posted October 26, 2015 Share Posted October 26, 2015 @TorchRedRob I'm also experiencing very poor performance using WebGrab+Plus and schedules direct. Any chance of sharing the XMLTV docker? Quote Link to comment
PScherrer80 Posted October 29, 2015 Share Posted October 29, 2015 Hi all, I've installed tvheadend_unstable docker template. Because I need IPTV-muxes I've tried to add muxes with ffmpeg but it seems not to work. What I've to do? Is it working somewhere? Please help. I also would like to integrate following ffpipe.sh to allow X-Forward tags: name=$1 url=`echo $2 | cut -d'|' -f1` forward=`echo $2 | cut -d'|' -f2` forward=${forward/=/:} /usr/bin/ffmpeg -loglevel fatal -headers $forward$'\r\n' -i $url -vcodec copy -acodec copy -metadata service_provider=IPTV -metadata service_name=$name -f mpegts pipe:1 This can be called like tis: pipe://ffpipe.sh Das_Erste_HD your url Quote Link to comment
gerard6110 Posted October 30, 2015 Share Posted October 30, 2015 Hi, I have OSCAM and TVHeadend working in Ubuntu Server 14.04 ie. the hardware is fine, but I want to switch to UNRAID (primarily because of HDDs-usage). So, running unraid 6.1.3 (trial) and Container OSCAM-test, but getting error Reader Device Error. The live log says: (reader) SRv2 [smartreader] Libusb init error : -99 (reader) SRv2 [smartreader] Cannot open device: "ID;Serial:**" Added the extra parameters: --device=/dev/ttyUSB0:/dev/ttyUSB0, but then the container does not start; error: Error response from daemon: Cannot start container 71...d3: error gathering device information while adding custom device "/dev/ttyUSB0": lstat /dev/ttyUSB0: no such file or directory. Adding the extra parameters: --device=/dev/ttyUSB1:/dev/ttyUSB1 or --device=/dev/ttyUSB2:/dev/ttyUSB2 did not help either. # lsusb (on unraid host): Bus 006 Device 002: ID 0fca:8004 Research In Motion, Ltd. Blackberry Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Please help. Thanks. Quote Link to comment
saarg Posted October 30, 2015 Author Share Posted October 30, 2015 Can you connect to unraid and issue this command and post the result? ls -la /dev/ttyUSB* Quote Link to comment
gerard6110 Posted October 30, 2015 Share Posted October 30, 2015 # ls -la /dev/ttyUSB* Output: /bin/ls: cannot access /dev/ttyUSB*: No such file or directory Quote Link to comment
saarg Posted October 30, 2015 Author Share Posted October 30, 2015 Hmm... Which card reader do you use? Quote Link to comment
gerard6110 Posted October 30, 2015 Share Posted October 30, 2015 Argolis Smargo Smartreader V2 plus (USB smartcard reader) with smartreader protocol for the reader (in oscam.server) and newcamd protocol (in oscam.conf). http://www.argolis.com/ Under Ubuntu one has to: - Prepare it for oscam and the respective smartcard (but that's a one-time step only; so already done) Note: in there, there's a step to make the smartreader (temporary) visible through ttyUSB0 via: modprobe usbserial vendor=0x0403 product=0x6001 (should I put this in the unraid go-script?) - Compile and install libusb when using USB Readers (yes/no already in unraid?) - Actually install oscam (checkout oscam from trunk, prepare the build, compile, install oscam, make executable and run at boot), but I take it this is all done in the container. Quote Link to comment
saarg Posted October 30, 2015 Author Share Posted October 30, 2015 Argolis Smargo Smartreader V2 plus (USB smartcard reader) with smartreader protocol for the reader (in oscam.server) and newcamd protocol (in oscam.conf). http://www.argolis.com/ Under Ubuntu one has to: - Prepare it for oscam and the respective smartcard (but that's a one-time step only; so already done) Note: in there, there's a step to make the smartreader (temporary) visible through ttyUSB0 via: modprobe usbserial vendor=0x0403 product=0x6001 (should I put this in the unraid go-script?) - Compile and install libusb when using USB Readers (yes/no already in unraid?) - Actually install oscam (checkout oscam from trunk, prepare the build, compile, install oscam, make executable and run at boot), but I take it this is all done in the container. I was thinking that might be the case, but wanted to know the card reader. You can try the modprobe out first as a command to see if it works before adding it in the go script. It might be that you have to install the libusb package. I'll find the link tomorrow. How do you define the reader in oscam? By serial? Quote Link to comment
saarg Posted October 31, 2015 Author Share Posted October 31, 2015 Argolis Smargo Smartreader V2 plus (USB smartcard reader) with smartreader protocol for the reader (in oscam.server) and newcamd protocol (in oscam.conf). http://www.argolis.com/ Under Ubuntu one has to: - Prepare it for oscam and the respective smartcard (but that's a one-time step only; so already done) Note: in there, there's a step to make the smartreader (temporary) visible through ttyUSB0 via: modprobe usbserial vendor=0x0403 product=0x6001 (should I put this in the unraid go-script?) - Compile and install libusb when using USB Readers (yes/no already in unraid?) - Actually install oscam (checkout oscam from trunk, prepare the build, compile, install oscam, make executable and run at boot), but I take it this is all done in the container. A small update on libusb. I have a Infinity USB Smart that has the same USB ID as your smargo, and it get's detected without any problems by unraid and assigned as /dev/ttyUSB0. It uses the usbserial module, so no need to load it manually. It might be that there is a setting you have to do on the Smargo by running the settings tool you can download from www.argolis.com. There is no manual, so hard to say which parameter. But from the top of my head it might be that you have to set it to use the mouse protocol. If you want to try to download the newest libusb package you can go to http://packages.slackware.com/ and search for libusb and choose Slackware64 current under realease. Quote Link to comment
gerard6110 Posted October 31, 2015 Share Posted October 31, 2015 OK, tried a couple of things: - modprobe - install libusb in unraid (host) (if that was correct; don't know how to do in container) => same error. With oscam container it is impossible to check readers, because lsusb not installed. I would prefer to keep using the smartreader protocol, because of automatic card updates (I understood this is not the case with mouse protocol). FYI on the Smartreader2Tool (after installation - ubuntu instructions available). Check smartreader settings: cd smartreader ./smartreader2tool Output: ? smartreader2+ version v1.1; settings for *** Smartcard ? MODE fixed ? FREQ 6,00 Mhz ? T_MODE t = 1 ? EGT 0 ? NAME ABCDEFGH To change the device name / serial (exactly 8 characters): ./smartreader2tool -n ABCDEFGH To change other settings: ./smartreader2tool -help Output: ? Smartreader2+ settings tool v1.0 ? Usage: ./smartreader2tool -… -… -… ? -d <comport> (default comport = "/dev/ttyUSB0") ? -m <0 = autoswitch / 1 = fixed Mhz> mode ? -n <name> (max 8 characters) ? -N remove custom device name ? In fixed mode you can also apply: ? -x <frequency in khz> ? -t <val> t = val ? -e <val> egt = val Quote Link to comment
saarg Posted November 1, 2015 Author Share Posted November 1, 2015 You do not need to install libusb as it's in unraid allready. I had no problems updating my card when using the mouse protocol, so I'm not sure where you got this info from. Might be a smargo specific thing, but I never heard about it. Could you try to set the default comport to /dev/ttyUSB0 with the tool and see if it shows up in unraid? What is the output of this command: lsmod | grep serial Quote Link to comment
gerard6110 Posted November 1, 2015 Share Posted November 1, 2015 # lsmod | grep serial usbserial 19129 1 ftdi_sio When changing the comport (using Ubuntu), I suppose I must also change the protocol(s). Which one? smartreader protocol for the reader (in oscam.server file), newcamd protocol (in oscam.conf file) or both and thus which (minimal) settings changes? Sorry for the questions, but although I have OSCAM running under Ubuntu I'm actually a complete noob of what is happening in there (still to study, but on the other hand, it is running ... and where does one stop to understand). Knowing how much effort it took to get it up and running the first time (and thus the reason for my own little tutorials with all relevant steps and settings!) I would like to know all upfront before making the switch. Quote Link to comment
saarg Posted November 1, 2015 Author Share Posted November 1, 2015 I don't know this reader so I can not provide you with a guide for how it's done. You have to try it and see if you get it working or google and read up on the card reader. If you don't want to destroy a working setup I understand that In oscam you only have to change the settings in the reader section. Newcamd is the protocol tvheadend use to talk to oscam. It is possible to pass through the reader without using /dev/ttyUSB0, as I did this with a pcsc reader, but that was long time ago and I didn't take notes on how to do it Could you attach the card reader to unraid and post the output of dmesg|tail Quote Link to comment
saarg Posted November 1, 2015 Author Share Posted November 1, 2015 Hi all, I've installed tvheadend_unstable docker template. Because I need IPTV-muxes I've tried to add muxes with ffmpeg but it seems not to work. What I've to do? Is it working somewhere? Please help. I also would like to integrate following ffpipe.sh to allow X-Forward tags: name=$1 url=`echo $2 | cut -d'|' -f1` forward=`echo $2 | cut -d'|' -f2` forward=${forward/=/:} /usr/bin/ffmpeg -loglevel fatal -headers $forward$'\r\n' -i $url -vcodec copy -acodec copy -metadata service_provider=IPTV -metadata service_name=$name -f mpegts pipe:1 This can be called like tis: pipe://ffpipe.sh Das_Erste_HD your url Ffmpeg is installed, so that is not the problem. I have unfortunately no experience with the pipe command, so I suggest you head over to the tvheadend forum or irc channel to see if someone there can help. Quote Link to comment
gerard6110 Posted November 1, 2015 Share Posted November 1, 2015 @saarg: thanks for helping; no problem trying things (basically Ubuntu and unRaid are running on the same box; just during boot to decide which one I want to use). # dmesg|tail (before disconnecting or removing things) tun: © 1999-2004 Max Krasnyansky <[email protected]> kvm: Nested Virtualization enabled kvm: Nested Paging enabled Ebtables v2.0 registered device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth2f67798) entered forwarding state docker0: port 2(vethdb62bbf) entered forwarding state # dmesg|tail (2x, after disconnecting or removing things) device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth2f67798) entered forwarding state docker0: port 2(vethdb62bbf) entered forwarding state usb 6-3: USB disconnect, device number 2 usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected Notes: Line usb 6-3 came up after disconnecting my Bleckberry Lines usb 1-2 to ftdi_sio 1-2 came up after removing the card reader I have OSCAM, SABnzbd and TVHeadend4-stable running as containers. KVM enabled, but no guest OS running. # dmesg|tail (after connecting blackberry, inserting cardreader and rebooting) tun: © 1999-2004 Max Krasnyansky <[email protected]> kvm: Nested Virtualization enabled kvm: Nested Paging enabled Ebtables v2.0 registered device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(vethc2cf933) entered forwarding state docker0: port 2(veth70b087e) entered forwarding state Quote Link to comment
saarg Posted November 1, 2015 Author Share Posted November 1, 2015 I need dmesg | tail right after you connect the card reader. Quote Link to comment
spylex Posted November 3, 2015 Share Posted November 3, 2015 Thank you tobbenb for your efforts! I have a SAT>IP receiver, and sometimes TVH will just stop seeing it. I'll have to stop and start the docker for it to recover (not restart). Not sure why! Quote Link to comment
saarg Posted November 3, 2015 Author Share Posted November 3, 2015 Thank you tobbenb for your efforts! I have a SAT>IP receiver, and sometimes TVH will just stop seeing it. I'll have to stop and start the docker for it to recover (not restart). Not sure why! Do you use the stable or unstable container? Quote Link to comment
saarg Posted November 3, 2015 Author Share Posted November 3, 2015 Tvheadend Stable is updated to 4.0.7 and unstable to the latest commit as we speak. The unstable should be ready in an hour or so. Quote Link to comment
gerard6110 Posted November 4, 2015 Share Posted November 4, 2015 OK, herewith dmesg | tail again (immediately after disconnecting and connecting): # dmesg | tail virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth1f5b4f4) entered forwarding state docker0: port 2(vethe6157dc) entered forwarding state usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected usb 1-2: new full-speed USB device number 4 using xhci_hcd ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected usb 1-2: Detected FT232BM usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 Hoping making sense now ... Quote Link to comment
saarg Posted November 4, 2015 Author Share Posted November 4, 2015 OK, herewith dmesg | tail again (immediately after disconnecting and connecting): # dmesg | tail virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth1f5b4f4) entered forwarding state docker0: port 2(vethe6157dc) entered forwarding state usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected usb 1-2: new full-speed USB device number 4 using xhci_hcd ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected usb 1-2: Detected FT232BM usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 Hoping making sense now ... And this command does not return anything right after connecting the card reader? ls -la /dev/ttyUSB* Quote Link to comment
gerard6110 Posted November 5, 2015 Share Posted November 5, 2015 So after switching from ubuntu to unraid: # dmesg | tail tun: © 1999-2004 Max Krasnyansky <[email protected]> kvm: Nested Virtualization enabled kvm: Nested Paging enabled Ebtables v2.0 registered device virbr0-nic entered promiscuous mode virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered listening state virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth35e41c4) entered forwarding state docker0: port 2(veth02d5f3b) entered forwarding state # ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Nov 5 22:06 /dev/ttyUSB0 After removing and re-inserting the card reader: # dmesg | tail virbr0: port 1(virbr0-nic) entered disabled state docker0: port 1(veth35e41c4) entered forwarding state docker0: port 2(veth02d5f3b) entered forwarding state usb 1-2: USB disconnect, device number 3 ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 ftdi_sio 1-2:1.0: device disconnected usb 1-2: new full-speed USB device number 4 using xhci_hcd ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected usb 1-2: Detected FT232BM usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 # ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Nov 5 22:07 /dev/ttyUSB0 Re-starting OSCAM, still Libusb init error : -99 Cannot open device: While parameter --device=/dev/ttyUSB0:/dev/ttyUSB0 is part of the Docker. Quote Link to comment
saarg Posted November 5, 2015 Author Share Posted November 5, 2015 Now the card reader is correctly passed through How does your reader config look like in oscam? Quote Link to comment
gerard6110 Posted November 6, 2015 Share Posted November 6, 2015 I hope so. At least nothing is listed under oscam readers and log errors still the same. Reader config (from oscam.server file - working under Ubuntu) [reader] label = SRv2 description = Argolis SmartReader2 plus protocol = smartreader device = SRV2;Serial:A......4 caid = 0604 boxkey = 1122334455667788 rsakey = 3C8.........76A detect = cd mhz = 600 cardmhz = 600 ident = 0604:000000 group = 1 emmcache = 1,3,2,0 blockemm-unknown = 1 blockemm-g = 1 dropbadcws = 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.