USB-UIRT on 64 bit Windows systems? - Page 2

Fuzzy · #21 01-13-2017, 02:34 AM

Quote:

Originally Posted by Wrx4me

Here is the result from lspci

Linux 4.4.30-unRAID.
root@unraid:~# lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0)
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
00:1c.6 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 (rev d0)
00:1c.7 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 8 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
04:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43)
04:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43)
04:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04)
04:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46)
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
root@unraid:~#

Whoops... sorry, you need to run lspci -tv to get the hierarical list. This should then indicate which 'bridge' device you need to pass through to the vm.

EnterNoEscape · #22 01-13-2017, 03:45 AM

Quote:

Originally Posted by Wrx4me

Here is the result from lspci

Linux 4.4.30-unRAID.
root@unraid:~# lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0)
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
00:1c.6 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 (rev d0)
00:1c.7 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 8 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
04:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43)
04:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43)
04:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04)
04:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46)
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
root@unraid:~#

Based on that and knowing a little about the Z97 chipset, you'll want to pass through 03:00.0

Wrx4me · #23 01-13-2017, 12:09 PM

Quote:

Originally Posted by EnterNoEscape

Based on that and knowing a little about the Z97 chipset, you'll want to pass through 03:00.0

Thanks, I'll try that later.

Wrx4me · #24 01-13-2017, 12:11 PM

Quote:

Originally Posted by Fuzzy

Whoops... sorry, you need to run lspci -tv to get the hierarical list. This should then indicate which 'bridge' device you need to pass through to the vm.

Here is the result of lspci -tv

root@unraid:~# lspci -tv
-[0000:00]-+-00.0 Intel Corporation 4th Gen Core Processor DRAM Controller
+-02.0 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
+-03.0 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
+-14.0 Intel Corporation 9 Series Chipset Family USB xHCI Controller
+-16.0 Intel Corporation 9 Series Chipset Family ME Interface #1
+-1a.0 Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
+-1b.0 Intel Corporation 9 Series Chipset Family HD Audio Controller
+-1c.0-[01]--
+-1c.2-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
+-1c.3-[03-04]----00.0-[04]--+-00.0 NEC Corporation OHCI USB Controller
| +-00.1 NEC Corporation OHCI USB Controller
| +-00.2 NEC Corporation uPD72010x USB 2.0 Controller
| \-01.0 VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
+-1c.6-[05]----00.0 Intel Corporation 82574L Gigabit Network Connection
+-1c.7-[06]----00.0 ASMedia Technology Inc. ASM1062 Serial ATA Controller
+-1d.0 Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
+-1f.0 Intel Corporation 9 Series Chipset Family Z97 LPC Controller
+-1f.2 Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
\-1f.3 Intel Corporation 9 Series Chipset Family SMBus Controller
root@unraid:~#

Fuzzy · #25 01-13-2017, 04:43 PM

the forum messes up the whitespace in the output, so it's a little hard to determine (You can try again, and this tie, post the results inside [code][/code] tags to keep the spaces/indents properly positioned), but it looks like to pass through some of the USB controllers as well. (all under the 1c.3 bridge device).

EnterNoEscape · #26 01-13-2017, 06:46 PM

Quote:

Originally Posted by Fuzzy

the forum messes up the whitespace in the output, so it's a little hard to determine (You can try again, and this tie, post the results inside [code][/code] tags to keep the spaces/indents properly positioned), but it looks like to pass through some of the USB controllers as well. (all under the 1c.3 bridge device).

You do not need to pass an entire USB controller into a VM to pass a USB device through. KVM can shim almost any USB device into the VM for you; no special hardware needed.

Wrx4me · #27 01-13-2017, 10:54 PM

Quote:

Originally Posted by Fuzzy

the forum messes up the whitespace in the output, so it's a little hard to determine (You can try again, and this tie, post the results inside [code][/code] tags to keep the spaces/indents properly positioned), but it looks like to pass through some of the USB controllers as well. (all under the 1c.3 bridge device).

I see what you mean, here it is again.

Code:

root@unviper:~# lspci -tv
-[0000:00]-+-00.0  Intel Corporation 4th Gen Core Processor DRAM Controller
           +-02.0  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           +-03.0  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           +-14.0  Intel Corporation 9 Series Chipset Family USB xHCI Controller
           +-16.0  Intel Corporation 9 Series Chipset Family ME Interface #1
           +-1a.0  Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
           +-1b.0  Intel Corporation 9 Series Chipset Family HD Audio Controller
           +-1c.0-[01]--
           +-1c.2-[02]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Control
           +-1c.3-[03-04]----00.0-[04]--+-00.0  NEC Corporation OHCI USB Controller
           |                            +-00.1  NEC Corporation OHCI USB Controller
           |                            +-00.2  NEC Corporation uPD72010x USB 2.0 Controller
           |                            \-01.0  VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controll
           +-1c.6-[05]----00.0  Intel Corporation 82574L Gigabit Network Connection
           +-1c.7-[06]----00.0  ASMedia Technology Inc. ASM1062 Serial ATA Controller
           +-1d.0  Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
           +-1f.0  Intel Corporation 9 Series Chipset Family Z97 LPC Controller
           +-1f.2  Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
           \-1f.3  Intel Corporation 9 Series Chipset Family SMBus Controller

Wrx4me · #28 01-13-2017, 10:55 PM

Quote:

Originally Posted by EnterNoEscape

You do not need to pass an entire USB controller into a VM to pass a USB device through. KVM can shim almost any USB device into the VM for you; no special hardware needed.

Good to know, thanks.

Fuzzy · #29 01-13-2017, 11:08 PM

Quote:

Originally Posted by Wrx4me

I see what you mean, here it is again.

Code:

root@unviper:~# lspci -tv
-[0000:00]-+-00.0  Intel Corporation 4th Gen Core Processor DRAM Controller
           +-02.0  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           +-03.0  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           +-14.0  Intel Corporation 9 Series Chipset Family USB xHCI Controller
           +-16.0  Intel Corporation 9 Series Chipset Family ME Interface #1
           +-1a.0  Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
           +-1b.0  Intel Corporation 9 Series Chipset Family HD Audio Controller
           +-1c.0-[01]--
           +-1c.2-[02]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Control
           +-1c.3-[03-04]----00.0-[04]--+-00.0  NEC Corporation OHCI USB Controller
           |                            +-00.1  NEC Corporation OHCI USB Controller
           |                            +-00.2  NEC Corporation uPD72010x USB 2.0 Controller
           |                            \-01.0  VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controll
           +-1c.6-[05]----00.0  Intel Corporation 82574L Gigabit Network Connection
           +-1c.7-[06]----00.0  ASMedia Technology Inc. ASM1062 Serial ATA Controller
           +-1d.0  Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
           +-1f.0  Intel Corporation 9 Series Chipset Family Z97 LPC Controller
           +-1f.2  Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
           \-1f.3  Intel Corporation 9 Series Chipset Family SMBus Controller

So yeah, you can see there that the firewire controller is connected to the 1.c3 PCI bridge device. The IOMMU in the motherboard is only really mapped to passthrough the root devices on the motherboard, so that bridge is what will be passed. In doing so, the devices below it should no longer be accessible by the hypervisor, but will show up in the vm, where drivers will be able to talk to them directly. So some of the USB ports on the motherboard (the ones on those usb controllers on the same PCI bus as your firewire card, will also be directly tied to the VM, and not the host.

Wrx4me · #30 01-14-2017, 05:09 PM

Quote:

Originally Posted by Fuzzy

So yeah, you can see there that the firewire controller is connected to the 1.c3 PCI bridge device. The IOMMU in the motherboard is only really mapped to passthrough the root devices on the motherboard, so that bridge is what will be passed. In doing so, the devices below it should no longer be accessible by the hypervisor, but will show up in the vm, where drivers will be able to talk to them directly. So some of the USB ports on the motherboard (the ones on those usb controllers on the same PCI bus as your firewire card, will also be directly tied to the VM, and not the host.

Ok, so I can safely pass that through as my only worry was accidentally passing through my unRAID USB device.

wayner · #31 02-04-2017, 10:51 AM

I really want to get firewire working as I have to control multiple STBs and the USB-UIRT isn't going to work for more than on box.

My motherboard is an Asus P8H67-M EVO. with an i5-2500k Unfortunately this CPU does not support Vt-d - does that mean this is futile?

I would like to eventually get firewire working in the unRAID sagetv docker container, but to play around for now I thought it might make sense to try to get things working in the Ubuntu 16.04 VM that I have running under unRAID.

When I do an lspci -tv command from an unRAID bash prompt here is what I get:

Code:

-[0000:00]-+-00.0  Intel Corporation 2nd Generation Core Processor Family DRAM Controller
           +-01.0-[01]--
           +-02.0  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller
           +-16.0  Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1
           +-1a.0  Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2
           +-1b.0  Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller
           +-1c.0-[02]--
           +-1c.3-[03]----00.0  VIA Technologies, Inc. VT6315 Series Firewire Controller
           +-1c.4-[04]----00.0  ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
           +-1c.5-[05]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           +-1c.6-[06-07]----00.0-[07]--
           +-1c.7-[08]----00.0  Marvell Technology Group Ltd. 88SE6121 SATA II / PATA Controller
           +-1d.0  Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1
           +-1f.0  Intel Corporation H67 Express Chipset Family LPC Controller
           +-1f.2  Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller
           \-1f.3  Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller

So it looks like the Firewire is on bus 1c.3[03]. Note that when I do an lspci -tv from a bash prompt within the sagetv docker container it says that the lspci command is not found.

And when I do an lspci -tv from within the Ubuntu VM you can see that some of the devices are not getting through:

Code:

-[0000:00]-+-00.0  Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
           +-01.0  Red Hat, Inc. QXL paravirtual graphic card
           +-07.0  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1
           +-07.1  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2
           +-07.2  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3
           +-07.7  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1
           +-1e.0-[01-02]----01.0-[02]--+-01.0  Red Hat, Inc Virtio network device
           |                            +-02.0  Red Hat, Inc Virtio console
           |                            +-03.0  Red Hat, Inc Virtio block device
           |                            \-04.0  Red Hat, Inc Virtio memory balloon
           +-1f.0  Intel Corporation 82801IB (ICH9) LPC Interface Controller
           +-1f.2  Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode]
           \-1f.3  Intel Corporation 82801I (ICH9 Family) SMBus Controller

Any advice on passing through the firewire device to either the SageTV docker or the Ubunut VM?

mgpaulus · #32 02-04-2017, 01:31 PM

Quote:

Originally Posted by wayner

I really want to get firewire working as I have to control multiple STBs and the USB-UIRT isn't going to work for more than on box.

Just out of curiousity, why won't the USB-UIRT work for more than one box?

I am running a USB-UIRT on win7 64-bit controlling 2 STB. I am using a L-R Mono Splitter and 2 of these DTA to Tivo cables (http://www.ebay.com/itm/TiVo-to-DTA-...QAAOSw7aBVJGPl)

I also had to get and install the USB-UIRT driver that supports Zones (or was it multiple/named devices), and I had to modify my Channel definition files to support Zones.

And, it's possible to support multiple USB-UIRT on the same system, by "renaming" each USB-UIRT with a unique number in the firmware, and updating your channel definition files to utilize that device number, so with that, you can easily have 4 direct connected devices, or 6 devices (4 direct, 2 using onboard IR).

BobPhoenix · #33 02-04-2017, 01:36 PM

Quote:

Originally Posted by mgpaulus

Just out of curiousity, why won't the USB-UIRT work for more than one box?

I am running a USB-UIRT on win7 64-bit controlling 2 STB. I am using a L-R Mono Splitter and 2 of these DTA to Tivo cables (http://www.ebay.com/itm/TiVo-to-DTA-...QAAOSw7aBVJGPl)

I also had to get and install the USB-UIRT driver that supports Zones (or was it multiple/named devices), and I had to modify my Channel definition files to support Zones.

And, it's possible to support multiple USB-UIRT on the same system, by "renaming" each USB-UIRT with a unique number in the firmware, and updating your channel definition files to utilize that device number, so with that, you can easily have 4 direct connected devices, or 6 devices (4 direct, 2 using onboard IR).

One word: Linux.

wayner · #34 02-04-2017, 03:59 PM

Quote:

Originally Posted by mgpaulus

Just out of curiousity, why won't the USB-UIRT work for more than one box?.

Apparently the Linux drivers don't support it. I have also been using the multi-zone feature for years.

IMHO this is a real problem. I have been slapped down for saying this in the past, but I believe that the momentum for the future direction of the server component of SageTV is docker/unRAID on Linux. And not being able to easily drive multiple STBs is a real issue.

wayner · #35 02-04-2017, 04:01 PM

Quote:

Originally Posted by BobPhoenix

One word: Linux.

I am trying that word but there are issues for channel tuning as it is not nearly as easy as Windows where the USB-UIRT is directly supported by SageTV and the second problem is that Linux doesn't support the multi-zone feature of the USB-UIRT.

BobPhoenix · #36 02-04-2017, 05:43 PM

Quote:

Originally Posted by wayner

I am trying that word but there are issues for channel tuning as it is not nearly as easy as Windows where the USB-UIRT is directly supported by SageTV and the second problem is that Linux doesn't support the multi-zone feature of the USB-UIRT.

Yep. I know. If I had to resort to using a USB-UIRT I would be in the same boat. I would however setup an encoding server VM and use that for unRAID. I thought about doing that for my AVerMedia Duet tuners as they are not supported in linux either. However I currently have it as a separate server VM rather than an encoding server.

Fuzzy · #37 02-04-2017, 06:34 PM

You can likely use multiple USB-UIRT devices... that said, the creator of the USB-UIRT has been on this forum, and has expressed some interest in improving the situation with sage and the USB-UIRT on linux, but I don't know the amount of time and/or motivation he might have in that direction.

wayner · #38 02-04-2017, 06:47 PM

He posted this on Nov 8 of last year:

Quote:

What is the current status of USB-UIRT support? I'm thinking about building a new Linux based Sage server to replace my aging Windows server.
I would like to update direct support for the USB-UIRT in Linux. I only recently found out that SageTV was open-sourced and am now starting to look at the repo.

It's been a while since I wrote the original USB-UIRT plugin (13+ years!) so bear with me...

I emailed Jon about this and he said:

Quote:

...Perhaps the best stop-gap solution is to see if SageTV on Linux can be set up to launch a command-line script for IR tuning. If so we could provide a command-line utility to send IR via multiple zone.

I just emailed back saying that Sage does call a command line program called gentuner that is a command line script.

Hopefully he has a solution.

Oatz · #39 07-17-2017, 08:41 PM

Which USB-UIRT should one buy for 3+ tuners?

This is the only decent unit I could find
http://www.irblaster.info/distribution.html

For Windows 10 64bit Sage 9 BTW

Fuzzy · #40 07-18-2017, 01:53 AM

Quote:

Originally Posted by Oatz

Which USB-UIRT should one buy for 3+ tuners?

This is the only decent unit I could find
http://www.irblaster.info/distribution.html

For Windows 10 64bit Sage 9 BTW

The USB-UIRT, as discussed in this thread, is a specific product, sold here: http://www.usbuirt.com/. It is directly supported by SageTV, and does support up to 3 zones. 2 via external emitter's, one via the blaster included in the device.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Windows 7 - will not wake with USB-UIRT	timg11	Hardware Support	5	08-16-2010 11:59 AM
USB-UIRT setup on Windows 7	aclarke	Hardware Support	1	03-27-2010 09:16 AM
What RAID systems are you using	SafetyBob	Hardware Support	38	03-17-2007 09:16 AM
usb-uirt in windows 2003	mattdcknsn	Hardware Support	2	07-01-2005 09:59 AM
Help decide between 2 systems	Lonc_25	Hardware Support	13	12-19-2004 03:35 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)