Tuner troubles with unRAID

[kenP]

--- begin update of update ----

I just realized I failed to update my description, I upgraded my hdpvrs to
HD-PVR 2s via hauppauge's upgrade program.

----end of update update. -------

=== begin update ==============
Here's an update since this was first posted

I figured out I need to use placeshifter/HD200 to configure sage - duh
My 2 HDHRs are working fine for OTA
I was able to copy over 2+ TB of old recordings (along with the old wiz.bin) and they play fine
stuckless' docker is a breeze to use
unRAID DVB Edition not so much (easy enough but doesn't seem to work for me)
-- I have tried the LibreELEC 6.3.5, TBS (crazycat) and TBS(open source) both 6.3.5 with out success

I've two problems
1) my 3 HD-PVRs (HDPVR2) are not recognized by Sage (they are the 157320 models known as gaming plus)
-- see below for what unRAID DVB Edition reports
-- /dev/dvb/ and adapter* are not created
-- I tried copying 00-haupauge...rules from their linux driver package to /etc/.../rules.d/ and still not created. udev shows to be running
-- reformatted everything and rebuilt from scratch no luck
-- they work fine under Win10 including having loaded the latest drivers and firmware (the win10 install that came on this pc so all hardware is same just booted to win vs unRAID)
-- I'm out of ideas

2) Favorites didn't come over from my old system but I haven't researched this problem yet

thanks in advance

=== end update ===========================

After my old XP server crashed I replaced it with a bargain priced Lenovo refurb with more decent specs.

After getting Sage up and running in Win10Pro x64 that came with the Lenovo I ran into the STB firewire tuning problem. I'll spare the details but it seems Sage would almost run in the 'Store' version of Ubuntu along with Ubuntu running in a VM but I could never quite figure out how to pass-through the network so I switched gears, as recommended by others, to unRAID.

Here I am with a clean install of unRAID 6.3.5; Plug-ins: CA, Unassigned Devices, unRAID DVB Edition(LibreELEC driver 1.2.1); and Stuckless' docker sagetv-server-java8.

unRAID DVB shows
unRAID Version: 6.3.5
DVB Version: LibreELEC
Driver Version: 1.2.1
DVB Kernel: Detected
DVB Adapter Drivers: Not Detected
DVB Adapter 0: Not Detected
DVB Adapter 1: Not Detected
etc...



System Devices shows (detects my 3 HD-PVRs)
PCI Devices and IOMMU Groups
IOMMU group 0
[8086:0150] 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
IOMMU group 1
[8086:0152] 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
IOMMU group 2
[8086:1e31] 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
IOMMU group 3
[8086:1e3a] 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
[8086:1e3d] 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04)
IOMMU group 4
[8086:1502] 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
IOMMU group 5
[8086:1e2d] 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
IOMMU group 6
[8086:1e20] 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
IOMMU group 7
[8086:1e26] 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
IOMMU group 8
[8086:244e] 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
[104c:8019] 01:0a.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller
IOMMU group 9
[8086:1e47] 00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 04)
[8086:1e02] 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
[8086:1e22] 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
CPU Thread Pairings
cpu 0
cpu 1
cpu 2
cpu 3
USB Devices
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 13fe:5500 Kingston Technology Company Inc.
Bus 001 Device 004: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 2040:e505 Hauppauge
Bus 002 Device 004: ID 2040:e505 Hauppauge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 2040:e505 Hauppauge
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 152d:1562 JMicron Technology Corp. / JMicron USA Technology Corp.
SCSI Devices
[0:0:0:0] disk Patriot Memory PMAP /dev/sdb 15.8GB
[1:0:0:0] disk ST315005 41AS 0103 /dev/sda 1.50TB
[1:0:0:1] disk WDC WD10 EACS-00D6B0 0103 /dev/sdc 1.00TB
[2:0:0:0] disk ATA Hitachi HUA72202 A3NH /dev/sdd 2.00TB
[3:0:0:0] disk ATA ST4000DM005-2DP1 0001 /dev/sde 4.00TB
[4:0:0:0] cd/dvd TSSTcorp DVD-RW SH-216BB LW02 /dev/sr0 -

looking in /dev I don't see /dev/dvb/
root@Tower:/dev# ls d*
dvd@ dvd0@ dvdr@ dvdr0@ dvdrw@ dvdrw0@ dvdwriter@ dvdwriter0@

I've tried with and without adding the extra parameter of --device=/dev/dvb/ to the sage docker container.

--------

My issue are:
1) none of the 3 HD-PVRs appear in Sage as available sources.
a) They continue to fast flash the led

2) 2 HDHRs I have do appear as 4 available tuners and I can configure and channel scan.
a) BUT if I preview a channel then the win10 client I'm running on a pc suddenly shuts down, same if I play live TV
b) BUT then again using an HD200, I can record with no issue and I can play the recording back on the PC client.

I have clearly been whacked with the stupid stick multiple times since I last setup a Sage server! I've read myself in circles to no avail.

Would one of you kind lads or lasses please put me out of my misery? A pointer to the right docs or a clue for the clueless would be greatly appreciated!
Best and Merry Holidays to all,
Ken

[rickgillyon]

Do you have the extra parameters for the SageTV docker set as described?
--device=/dev/dvb/

In any case, I don't think the HDPVRs are supported in Linux properly, just in Ubuntu. I couldn't get it working in unRAID and just gave up and replaced it with a satIP device. Expensive solution though.

[kenP]

Yes, I have tried with and without the --devices= parameter. One problem is that /dev/dvb/adapter* is not created in /dev/. I extracted the 99--hauppauge...Rules file from their linux driver package and placed it in the /etc/.../rules.d/ folder but that didn't help. I assume the firmware isn't available to load but I couldn't figure out what the firmware file was from their diver package.
(please excuse my ballpark references, I'm a noob and working from memory, hope those in the know know what I mean)

[rickgillyon]

Do you know you would need to look in the Docker environment to see if /dev/dvb exists in Sage? e.g.

docker exec -it stuckless-sagetv-server-java8 bash

This gives you a shell in the Docker itself.

Don't think it'll help with HDPVR though, they just don't work in unRAID as far as I can tell. I spent days trying.

[kenP]

I had no idea!! Thanks. It makes sense it could/would be in the docket. Unfortunately I'm still in the guess and check mode.

I'll give your command a try and see what i get.

Sorry to learn the the hdpvrs don't work. I thought I'd read otherwise but like i said I'm still learning left from right

[rickgillyon]

Let us know if you get the hdpvrs working, would be interested to hear.

[kenP]

Originally Posted by rickgillyon

Do you know you would need to look in the Docker environment to see if /dev/dvb exists in Sage? e.g.

docker exec -it stuckless-sagetv-server-java8 bash

This gives you a shell in the Docker itself.

Don't think it'll help with HDPVR though, they just don't work in unRAID as far as I can tell. I spent days trying.

I checked the docker, --device=/dev/dvb option is present but the folder does not exist per you command to get to the docker shell

I'll definitely post more especially if this gets sorted out,

[dstanley]

I have been running Unraid with four HD-PVRs without any problems at all for quite some time now.
I had to get the add-on APP called Unraid DVB Edition and install the 6.35 Digital Devices (Github) version to make them work.
Not sure if your HDHRs work with this edition though - I am ONLY running HD-PVRs with my setup of SageTV.

Dwight

[kenP]

Hi Dwight,

Thanks for your response, I'm glad to know this configuration is working for someone!

I just tried the Digital Services version without success. Did you have to edit the config file settings as described in the unRAID DVB Edition forum? there are two params msi and fmode that can take different settings. I didn't change anything.

I suspect my problem is related to this section of the unRAID DVB Edition description section:

unRAID Version: 6.3.5
DVB Version: Digital Devices (Github)
Driver Version: 0.9.29
DVB Kernel: Detected
DVB Adapter Drivers: Not Detected
DVB Adapter 0: Not Detected

My setup never creates/populates /etc/dvb/adapter*
either from a root console or from within the sage docker

I've also tried the LibreELEC version.

Is there a simple step I could be overlooking?

1) install unRAID
2) install community applications, unassigned devices and unRAID dvb edition
3) set LibraELEC (or Digital Devices) as the kernel
4) install stuckless-sagetv-server-java8
5) edit the docker to include the parameter: --device=/dev/dvb

since /dev/dvb wasn't created I looked around various forums and found some info at linuxtv.org that made me think I needed to have the right firmware (*.fw) file and a rule file to be used by udev to create /dev/dvb. I d/led Hauppauge's linux driver package for the 157320 hdpvr and extracted the contents. I couldn't find a .fw file but did find a rule file I copied to rule.d directory.
Still no joy

I did update via windows drivers and they work there. Don't know if unRAID has to have the fw available to upload before creating /dev/dvb or not.

[dstanley]

Your description is the same as mine - that is really weird. I do not remember having to do ANYTHING to get SageTV to recognize by HD-PVRs.
As far as I remember I did exactly as you did but did not have to do anything to the docker image - at the time I had no idea how to bash in or anything like that.
It was out-of-the-box operational after the steps you mentioned.
Are you sure your power supplies for the HD-PVRs are ok?
I am concerned when you say the led is flashing - It should flash once while powering on I believe.
Not sure what else to tell you - they certainly do work in unraid.
Somehow this thread needs to get the attention of Wayner or Stuckless to see if they have any ideas of why this won't work for you.

Dwight

Edit - Added some lines from my system log on the initialization of three of my HD-PVRs for your reference - there are other lines in between but just want to show you the entires I though were relevant. Does you system log register the HD-PVRs like this!?

[stuckless]

In linux the only HDPVRs that worked out of box are the first gen ones. I have two of those, and using unRAID/LibreElec they show up as /dev/video0 and /dev/video1, and sagetv can see them. They've been running fine since my early days of SageTV.

Apparently HDPVR2 might work in linux, but the process to do so, appears complicated

http://www.hauppauge.com/site/support/linux.html#tabs-3

Where you need to manually build the driver based on the model # of the HDPVR2 unit that you have.

I'm not even sure how you could have the docker container do this for you, since, you'd need to know the exact model # of the hdpvr, so I'd need to create a separate docker image per hdpvr2 which is never going to happen.

The problem of course is that even if you connected to the docker image and do those instructions to build the driver, it would all be undone when you restart the container or upgrade.

[rickgillyon]

Mine is a HDPVR2 so that's probably why it never worked. satIP is simpler anyway...

[kenP]

Originally Posted by stuckless

Apparently HDPVR2 might work in linux, but the process to do so, appears complicated

http://www.hauppauge.com/site/support/linux.html#tabs-3

Where you need to manually build the driver based on the model # of the HDPVR2 unit that you have.

I'm not even sure how you could have the docker container do this for you, since, you'd need to know the exact model # of the hdpvr, so I'd need to create a separate docker image per hdpvr2 which is never going to happen.

I came across a post elsewhere (which of course I can't find now) that said the only difference between all the versions on their page was the usb ID in the rules file. Since I have no idea how this stuff works, is it possible the driver could be common and a parameter passed to the docker where udev (whatever that is) could make the correct mapping?

I wish I could actively contribute; something more than just shots in the dark and wish-it-woulds.

If I have to go back to windows 10 pro x64, what tuning method is recommended? I was using firewire under XP.

[stuckless]

Originally Posted by kenP

I came across a post elsewhere (which of course I can't find now) that said the only difference between all the versions on their page was the usb ID in the rules file. Since I have no idea how this stuff works, is it possible the driver could be common and a parameter passed to the docker where udev (whatever that is) could make the correct mapping?

I wish I could actively contribute; something more than just shots in the dark and wish-it-woulds.

If I have to go back to windows 10 pro x64, what tuning method is recommended? I was using firewire under XP.

If that were true, then would be good... since, all the rules can simply be added to the same rule file.. ie, there is no harm in defining 100s of rules even though only a 1 will be used. I have to think there is more than just a rule file, since, they would know this.

Either way, driver support would have to be added to the LibreElec kernel, not the SageTV container.

[kenP]

Originally Posted by stuckless

If that were true, then would be good... since, all the rules can simply be added to the same rule file.. ie, there is no harm in defining 100s of rules even though only a 1 will be used. I have to think there is more than just a rule file, since, they would know this.

Either way, driver support would have to be added to the LibreElec kernel, not the SageTV container.

Rats. I wish that didn't make so much sense.

Looks like I'm back to windows. I was using firewire tuning but that's won't work in the x64 system I have now. What is the preferred method of tuning Motorola DCT6200s? Three of them.

[stuckless]

Originally Posted by kenP

Rats. I wish that didn't make so much sense.

Looks like I'm back to windows. I was using firewire tuning but that's won't work in the x64 system I have now. What is the preferred method of tuning Motorola DCT6200s? Three of them.

I did post a comment/suggestion to the owner of the LibreElect unRAID kernel project (on the unRAID forums), and he doesn't have time to figure this out, and Haupppuage isn't great to work with, but he's OK if someone else wants to take this on. He did look at the drivers and they are mess, apparently. So, not muck luck getting HDPVR2 drivers working in unRAID, unfortunately.