SageTV Docker LIRC/FireWire issues

[Tomahawk51]

Originally Posted by stuckless

You'll need to install the unRAID DVB plugin and then set the kernel to LibreElec (based on your version).

I've plugged an IR cable in my HDPVR, but can't get any channel changing happening. Here's what the options are (* for my assumption):

-Select tuning option for HD PVR...

--*Use external Cable receiver to tune
--Don't Configure tuning

then...

-Select a Tuning Plugin

--DirectTV Serial Control
--Generic Tuner
*--Infrared Blaster

---ports 0-9 are shown as options next. All say "Failed setting the IR Blaster Port". So, need to cancel.

--Firewire Tuner

---"There are no firewire device IDs that can be used for Tuning" note: I really want to use this someday, and did show my FW device is listed in Unraid console. Thinking IR is simpler first - maybe not?.

Also, just to note, if I try to change tuning device after initial setup, there are no options available. So, I need to remove the source and go through all the wizard steps again - not an issue for me.

[stuckless]

Originally Posted by Tomahawk51

I've plugged an IR cable in my HDPVR, but can't get any channel changing happening. Here's what the options are (* for my assumption):

-Select tuning option for HD PVR...

--*Use external Cable receiver to tune
--Don't Configure tuning

then...

-Select a Tuning Plugin

--DirectTV Serial Control
--Generic Tuner
*--Infrared Blaster

---ports 0-9 are shown as options next. All say "Failed setting the IR Blaster Port". So, need to cancel.

--Firewire Tuner

---"There are no firewire device IDs that can be used for Tuning" note: I really want to use this someday, and did show my FW device is listed in Unraid console. Thinking IR is simpler first - maybe not?.

Also, just to note, if I try to change tuning device after initial setup, there are no options available. So, I need to remove the source and go through all the wizard steps again - not an issue for me.

My guess is that the docker container doesn't have lirc installed (and/or the lirc service is not started). Another user is doing some work on setting up USB-UIRT and there is a lirc setup part of that process. I'm not sure 100% sure if core sagetv requires the lirc service to be running or not (Narflex might be able to comment better on this).

Another thing is that the sagetv container runs with very low user permissions and it might not have access to the lirc and firewire devices. This kind of thing is hard to troubleshoot, especially remotely, since I don't have a firewire device.

I checked on my setup and both /dev/lirc0 and /dev/lirc1 are owned by 'root' and as such sagetv will not get access to the devices... I need to update the docker container to set ownership permissions on those devices so that sagetv can actually use the devices.

I don't have a firewire device so I don't know what the /dev/ file would be called or what it's default permissions would be.

Could you ssh into your unRAID server and then run the command...

# docker exec -ti stuckless-sagetv-server-java8 /bin/bash

and then run

# ls -al /dev/fire*

and see if there are any devices it finds..

It's canadian thanksgiving this weekend, so likely not much will happen on my end

[Tomahawk51]

Originally Posted by stuckless

Could you ssh into your unRAID server and then run the command...

# docker exec -ti stuckless-sagetv-server-java8 /bin/bash

and then run

# ls -al /dev/fire*

and see if there are any devices it finds.

Firstly, enjoy your holiday and don't worry about Dockers .

I'm very Novice:

root@Tower:~# docker exec -ti stuckless-sagetv-server-java8 /bin/bash
root@Tower:/# ls -al /dev/fire*
ls: cannot access '/dev/fire*': No such file or directory

so thought I'd try...

root@Tower:/# cd dev
root@Tower:/dev# ls

aer_inject mem ptyp2 tty14 tty40 ttyp0
bsg memory_bandwidth ptyp3 tty15 tty41 ttyp1
btrfs-control mqueue ptyp4 tty16 tty42 ttyp2
bus nbd0 ptyp5 tty17 tty43 ttyp3
cpu nbd1 ptyp6 tty18 tty44 ttyp4
cpu_dma_latency nbd10 ptyp7 tty19 tty45 ttyp5
fd nbd11 random tty2 tty46 ttyp6
full nbd12 rtc0 tty20 tty47 ttyp7
fuse nbd13 sda tty21 tty48 ttyS0
hpet nbd14 sda1 tty22 tty49 urandom
hwrng nbd15 sdb tty23 tty5 vcs
input nbd2 sdb1 tty24 tty50 vcs1
kcore nbd3 sdc tty25 tty51 vcs2
kmem nbd4 sdc1 tty26 tty52 vcs3
kmsg nbd5 sg0 tty27 tty53 vcs4
lirc0 nbd6 sg1 tty28 tty54 vcs5
loop0 nbd7 sg2 tty29 tty55 vcs6
loop1 nbd8 shm tty3 tty56 vcsa
loop2 nbd9 snd tty30 tty57 vcsa1
loop3 net stderr tty31 tty58 vcsa2
loop4 network_latency stdin tty32 tty59 vcsa3
loop5 network_throughput stdout tty33 tty6 vcsa4
loop6 null tty tty34 tty60 vcsa5
loop7 port tty0 tty35 tty61 vcsa6
loop-control ppp tty1 tty36 tty62 vfio
lp0 ptmx tty10 tty37 tty63 vga_arbiter
mapper pts tty11 tty38 tty7 vhost-net
mcelog ptyp0 tty12 tty39 tty8 video0
md1 ptyp1 tty13 tty4 tty9 zero

And though I may be mixing between IR and FW (again - happy to get EITHER working), thought I'd share this:

root@Tower:~# lspci
00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HB (ICH8) 4 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GS] (rev a1)
03:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
03:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 22)
05:01.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)

[mibsy]

Try running dmesg and look for the FireWire device drivers and device mapping. You can run it in the docker container or on the unRAID shell itself.

Originally Posted by Tomahawk51

Firstly, enjoy your holiday and don't worry about Dockers .

I'm very Novice:


so thought I'd try...



And though I may be mixing between IR and FW (again - happy to get EITHER working), thought I'd share this:

[Tomahawk51]

For Firewire:

Try running dmesg and look for the FireWire device drivers and device mapping. You can run it in the docker container or on the unRAID shell itself.

Thanks. I did not find ANY references to fire, wire, 1394, texas (it's a TI pci card). I suppose this is a good indicication of why the Firewire isn't working - it's not actually enabled by the OS/Kernel/Driver?

For HDPVR IR:

I'm hoping mixing IR into this thread isn't confusing, but I did find the following. If I could get my HDPVR IR blasting going, that would be second best (and worlds better than the nothing I have now). I found this information, fwiw.

root@Tower:/# dmesg

....

[ 23.244143] lirc_dev: IR Remote Control driver registered, major 248
[ 23.244828] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[ 23.245289] Zilog/Hauppauge IR driver initializing
[ 23.248464] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[ 23.251822] probing IR Rx on Hauppage HD PVR I2C (i2c-1)
[ 23.251971] probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done. Waiting on IR Tx.
[ 23.252091] i2c i2c-1: probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done
[ 23.252208] probing IR Tx on Hauppage HD PVR I2C (i2c-1)
[ 23.252331] i2c i2c-1: Direct firmware load for haup-ir-blaster.bin failed with error -2
[ 23.252435] i2c i2c-1: firmware haup-ir-blaster.bin not available (-2)
[ 23.252641] i2c i2c-1: lirc_dev: driver lirc_zilog registered at minor = 0
[ 23.252746] i2c i2c-1: IR unit on Hauppage HD PVR I2C (i2c-1) registered as lirc0 and ready
[ 23.252849] i2c i2c-1: probe of IR Tx on Hauppage HD PVR I2C (i2c-1) done
[ 23.252984] initialization complete

It's very interesting to immerse in linux...sorry I'm so newb at it.

[mibsy]

So, I'm by no means an expert and perhaps someone has gotten the HD PVR blaster working. I've been working to get anything IR working. I have USB-UIRT and the HD PVR's and couldn't tune them for the past 4 weeks or so when I switched to the unRAiD Linux and Docker implementation. Stuckless has COMMANDIR working, but they no longer sell their wares. So, the short answer is that from what I've seen, you need something to be the intermediary between the gentuner plugin script and the IR tuner (USB-UIRT or HD PVR). I've gotten LIRC working for blasting the code out the main transmitter of my USB-UIRT(not out the zoned jack on the back). However, for it to be persistent across container updates Stuckless will need to include it on the distribution. Based on my discussion with him, he intends to do that, but I personally just got it working reasonably well on Friday and he has the holiday along with the many other great things he is working on for the Sage community, so I'm not sure when that might happen. I have DISH VIP 211k's that I controlled with USB-UIRT under windows for years. LIRC was a bit challenging to get just right, but it seems to do well and I suspect others will be able to refine it and get it working in a much more refined manner than I have and on many other devices.

As I was struggling with the USB-UIRT under LIRC, I took a detour trying to get the HD PVR IR blasters working. It is likely possible, but it didn't go well for me. I ended up locking up my HD PVR. The note in the dmesg about it not being stable and it not loading the firmware was concerning. I was able to get it to load the firmware under the docker container, but it still did not go particularly well.

I'm not familiar with the tuning your particular receiver, but I have found that the DISH VIP 211's can likely also be tuned over the network. That may be my next attempt just for fun.

Until the LIRC integration is done within the app, it isn't a trivial job to get it to work and it won't restart the LIRC daemon across docker restarts. Oh, and if the container updates, you'll have to do it all over again.

If you want to try playing around with it, I ran apt-get update and then apt-get install lirc to install the software within the sagetv container. Then the fun begins. If you can get irsend to work at the command line, then it isn't too hard to get it working with the gentuner plugin. Although I did run into permissions issues with the gentuner script and had to set them differently as well.

Getting it working this weekend may be a tall order. For me, I had HD Homeruns for all the OTA stuff, which kept my family at bay while I worked on the DISH tuning.

Originally Posted by Tomahawk51

For Firewire:



Thanks. I did not find ANY references to fire, wire, 1394, texas (it's a TI pci card). I suppose this is a good indicication of why the Firewire isn't working - it's not actually enabled by the OS/Kernel/Driver?

For HDPVR IR:

I'm hoping mixing IR into this thread isn't confusing, but I did find the following. If I could get my HDPVR IR blasting going, that would be second best (and worlds better than the nothing I have now). I found this information, fwiw.

root@Tower:/# dmesg

....

[ 23.244143] lirc_dev: IR Remote Control driver registered, major 248
[ 23.244828] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[ 23.245289] Zilog/Hauppauge IR driver initializing
[ 23.248464] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[ 23.251822] probing IR Rx on Hauppage HD PVR I2C (i2c-1)
[ 23.251971] probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done. Waiting on IR Tx.
[ 23.252091] i2c i2c-1: probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done
[ 23.252208] probing IR Tx on Hauppage HD PVR I2C (i2c-1)
[ 23.252331] i2c i2c-1: Direct firmware load for haup-ir-blaster.bin failed with error -2
[ 23.252435] i2c i2c-1: firmware haup-ir-blaster.bin not available (-2)
[ 23.252641] i2c i2c-1: lirc_dev: driver lirc_zilog registered at minor = 0
[ 23.252746] i2c i2c-1: IR unit on Hauppage HD PVR I2C (i2c-1) registered as lirc0 and ready
[ 23.252849] i2c i2c-1: probe of IR Tx on Hauppage HD PVR I2C (i2c-1) done
[ 23.252984] initialization complete

It's very interesting to immerse in linux...sorry I'm so newb at it.

[Fuzzy]

That looks like lirc is installed and detecting the HD-PVR's blaster (that's the lirc_zilog driver being loaded). lirc does take some more steps to configure though, and honestly, I never got all that far in it. Sage DOES support lirc, as far as I can tell, that's the 0-9 selection in the source config, but how to translate those into the actual lirc drivers, and how to configure the lirc to blast the right IR for your STB, I do not know.

(the number refers to the i2c port - so in your case, you would select blaster 1 (which will map to /dev/i2c-1). Looking in the code, it looks like it talks to the i2c port directly, instead of using any lirc tools, so I'm not sure how it'd be to troubleshoot it. That said, the 'blaster' driver involved here is called PVR150Tuner.c, which I actually think hasn't changed much between then and the HD-PVR.

[mibsy]

Unfortunately, the LIRC driver is only integrated into the LibreElec kernel. None of the software is installed without manual install or integration into the container. If you look at the gentuner.LIRC script, it uses irsend from the LIRC distribution. Here is what I looked at when trying to use the HD PVR transmitter:

https://www.mythtv.org/wiki/Hauppaug...mitter_Support

Perhaps there is another way that doesn't require the LIRC suite of tools. I'm just not certain.

Originally Posted by Fuzzy

That looks like lirc is installed and detecting the HD-PVR's blaster (that's the lirc_zilog driver being loaded). lirc does take some more steps to configure though, and honestly, I never got all that far in it. Sage DOES support lirc, as far as I can tell, that's the 0-9 selection in the source config, but how to translate those into the actual lirc drivers, and how to configure the lirc to blast the right IR for your STB, I do not know.

(the number refers to the i2c port - so in your case, you would select blaster 1 (which will map to /dev/i2c-1). Looking in the code, it looks like it talks to the i2c port directly, instead of using any lirc tools, so I'm not sure how it'd be to troubleshoot it. That said, the 'blaster' driver involved here is called PVR150Tuner.c, which I actually think hasn't changed much between then and the HD-PVR.

[Fuzzy]

I'm not so sure the packages are required (at least with sage's current code). Sage's PVR150Tuner.c writes/reads directly to/from the /dev/i2c-? port, not using irsend.

[Fuzzy]

Originally Posted by Fuzzy

I'm not so sure the packages are required (at least with sage's current code). Sage's PVR150Tuner.c writes/reads directly to/from the /dev/i2c-? port, not using irsend.

I'm thinking I might have to get a hold of the irsend code, and compare what IT does to what the PVR150Tuner code in sage is doing, and see where the differences lie. Might be able to either make improvements to PVR150, or make a while new interface for the HD-PVR's blaster.

[mibsy]

Originally Posted by Fuzzy

I'm thinking I might have to get a hold of the irsend code, and compare what IT does to what the PVR150Tuner code in sage is doing, and see where the differences lie. Might be able to either make improvements to PVR150, or make a while new interface for the HD-PVR's blaster.

It sounds like a nicer way to get the HD PVR blaster working since it wouldn't involve the complexity of LIRC. I needed to get my USB-UIRT working, which doesn't map to an i2c interface, so LIRC was my primary avenue. I did see that LIRC supports the HD PVR and many other items, so I was just offering it as a possibility.

It turns out, that while I have LIRC working for my USB-UIRT via LIRC, I've been playing around with a UPNP tuning script that should interface exceptionally well with my DISH VIP211 tuners and gentuner, but that only supports network UPNP tuning for a small subset of receivers.

LIRC is the very complex, all in one solution that can be painful to set up, but can be made to support almost anything from a transmitter and receiver standpoint. A simple point solution for HD PVR's is an outstanding idea given it is the tuner of choice for most folks.

[Fuzzy]

well, the hd-pvr still uses the lirc_zilog driver, as that's what essentially simulates the i2c port, but it appears that it is being loaded in the unraid (with the DVB kernal at least). I think for a single device, it would not be difficult to have the docker preconfigured to deal with HD-PVR's, even if we were to use irsend, so that is also an option - again, I have to see how far sage is from working with it right now before trying to figure out which route to go.

[stuckless]

I'm adding some "lirc" support to the container (ie, installing lirc), and setting the permissions on /dev/lirc0 and /dev/lirc1 so that sagetv can access those.

Also, setting the permissions on irsend so that if gentuner is used to call irsend, it has permissions to access the ports, etc.

There will be a new variable, OPT_LIRC, and if it is set to Y then a couple things will happen.
1. it will copy SAGE_HOME/lirc.d/hardware.conf and SAGE_HOME/lirc.d/lircd.conf to /etc/lirc/ (ie, this gives you a place to configure your hardware and lirc settings)
2. it will start the lirc daemon

[Fuzzy]

Originally Posted by stuckless

I'm adding some "lirc" support to the container (ie, installing lirc), and setting the permissions on /dev/lirc0 and /dev/lirc1 so that sagetv can access those.

Also, setting the permissions on irsend so that if gentuner is used to call irsend, it has permissions to access the ports, etc.

There will be a new variable, OPT_LIRC, and if it is set to Y then a couple things will happen.
1. it will copy SAGE_HOME/lirc.d/hardware.conf and SAGE_HOME/lirc.d/lircd.conf to /etc/lirc/ (ie, this gives you a place to configure your hardware and lirc settings)
2. it will start the lirc daemon

Excellent. I was just getting ready to post an issue asking about how hard this would be.

[Tomahawk51]

I was asking about Firewire before, but now have the HD PVR blaster working fine in an Unraid VM. I neglected to realize my old Firewire card was PCI and not compatible with PCIe.

So, when the updates are available, I'll also fire up the docker and see if HD PVR IR blasting is working. For now, it's a relief to have the VM working - but I miss the cleanliness of the docker approach .

[Wrx4me]

Originally Posted by Tomahawk51

I was asking about Firewire before, but now have the HD PVR blaster working fine in an Unraid VM. I neglected to realize my old Firewire card was PCI and not compatible with PCIe.

So, when the updates are available, I'll also fire up the docker and see if HD PVR IR blasting is working. For now, it's a relief to have the VM working - but I miss the cleanliness of the docker approach .

Hey Tomahawk51, would you be able to tell me how you got your port 0 - 9 recognized? I seem to be stuck at the same place you were initially where each port I select gives me the "Failed setting the Infrared Blaster Port!" message. Any help would be appreciated.

[Tomahawk51]

Originally Posted by Wrx4me

Hey Tomahawk51, would you be able to tell me how you got your port 0 - 9 recognized? I seem to be stuck at the same place you were initially where each port I select gives me the "Failed setting the Infrared Blaster Port!" message. Any help would be appreciated.

Hi (presumed Subaru fan - and count me with you on that),

My Docker ambitions are on hold, I couldn't get my HDPVR IR Blaster working with my limited skillset.

Fuzzy has been working towards enabling the UIRT product, and sharing info on that over time. It may be extended or translatable to the HDPVR perhaps. I'm waiting to learn of developments like this.

What I did do was move to Unraid and simply setup a Windows 10 VM that controls the HDPVR IR blaster just fine. It's working very well (though I'd like to migrate to Docker when I can). I can share more on that if desired.

[Wrx4me]

Originally Posted by Tomahawk51

Hi (presumed Subaru fan - and count me with you on that),

My Docker ambitions are on hold, I couldn't get my HDPVR IR Blaster working with my limited skillset.

Fuzzy has been working towards enabling the UIRT product, and sharing info on that over time. It may be extended or translatable to the HDPVR perhaps. I'm waiting to learn of developments like this.

What I did do was move to Unraid and simply setup a Windows 10 VM that controls the HDPVR IR blaster just fine. It's working very well (though I'd like to migrate to Docker when I can). I can share more on that if desired.

Haha I do like the Subaru WRX but I used that acronym to say that Sage 'works for me' because when I joined the forum a lot of posts were mainly complaints.

I am actually going to be doing something similar to what you did only because Opendct is not playing nice with my Docker so I am also on hold with the Docker implementation.

I am going to migrate to Unraid and run Sage on a Linux VM. I have Sage 9 running on both Ubuntu 14.04 and 16.04 so I am trying to iron out things like the HDPVR before making the move. I gave up on the HDPVR blaster and have a USBUIRT on order so if you have some setup suggestions I'd be glad to hear it. I regret that Unraid does not support Firewire as that is what I currently use on my Windows 7 Sage Server HDPVR channel changing.

[Tomahawk51]

FWIW: I've been running SageTV in a Windows 10 VM in Unraid, using my HDPVR for IR Blasting, and it's rock solid all around. HD PVR blasting is unexpectedly flawless. I used to use firewire, but my cards weren't PCIe, so I ditched them and am OK having done so.

Under my prior PC the HDPVR would disconnect often (Sage lost the tuner). I rarely see that now as well. I thought I had a weak power supply...but seems it may have been usb controllers instead or just windows.

[wayner]

Anyone know what the current state of either FW or the USB-UIRT are under unRAID? I had no problems having my HD-PVR recognized but I don't see firewire.

Here is the bottom of the the dmesg command that has all I can find relating to IR. Does it look like the Hauppauge IR would work?

[252651.636101] media: Linux media interface: v0.10
[252651.638978] Linux video capture interface: v2.00
[252651.657254] hdpvr 2-1.4:1.0: firmware version 0x17 dated Jul 27 2011 05:11:32
[252651.657256] hdpvr 2-1.4:1.0: untested firmware, the driver might not work.
[252652.048964] lirc_dev: IR Remote Control driver registered, major 247 
[252652.049436] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[252652.049634] Zilog/Hauppauge IR driver initializing
[252652.049636] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
[252652.051206] probing IR Rx on Hauppage HD PVR I2C (i2c-1)
[252652.051318] probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done. Waiting on IR Tx.
[252652.051323] i2c i2c-1: probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done
[252652.051336] probing IR Tx on Hauppage HD PVR I2C (i2c-1)
[252652.051362] i2c i2c-1: Direct firmware load for haup-ir-blaster.bin failed with error -2
[252652.051365] i2c i2c-1: firmware haup-ir-blaster.bin not available (-2)
[252652.051467] i2c i2c-1: lirc_dev: driver lirc_zilog registered at minor = 0
[252652.051470] i2c i2c-1: IR unit on Hauppage HD PVR I2C (i2c-1) registered as lirc0 and ready
[252652.051473] i2c i2c-1: probe of IR Tx on Hauppage HD PVR I2C (i2c-1) done
[252652.051504] initialization complete
[252652.167811] hdpvr 2-1.4:1.0: device now attached to video0
[252652.167859] usbcore: registered new interface driver hdpvr