Hauppauge pci card failure. Drm coming into play?

[Galaxysurfer]

I have two servers running as DVRs

Server #1 is on Debian based PC with Hauppauge pci cards

Server #2 is on Win 10 with HDHR tuner

tonights scheduled events failed to record on Server #1

All the shows sent error message
Recording missed due to capture device failure.
This was for shows on 2 different tuner instances.
All the errors happened exactly on the hour ( the beginning of scheduled recording time) so I differentiate that from antenna signal issue as root cause. OR maybe it is indeed a signal issue? I dont have option for a different antenna now to rule that out completely.

Server # 2 all scheduled shows recorded without issue.

When I did a dmesg lookup on server #1. I had many errors regarding nouveau drivers. So is this verification that drm is blocking my recording on Server #1? or do I need to get other firmware & device driver versions?
I would have to make a new computer instance with Ubuntu to gather the drivers. I dont want to go to all the trouble if it wont fix my issue.
I know my quad card had an update recently from updating software on win 10 dual boot side. I dont use the win 10 side as dvr for other complicated reasons. I only mention it for troubleshooting purposes.

What are others here experiencing?

I am in Canada on atsc 1.0 standard OTA.

[Tiki]

There is no DRM with standard OTA antenna and older ATSC. It simply wasn’t supported.

If there was a problem (either with the antenna or with the PCIe card, or with the driver), Sage would probably not know it or report it until it tried to record something and encountered a failure.

When I run into a strange tuner problem, I usually start my troubleshooting by rebooting everything to see if the problem persists. I don’t use Linux, but from time to time Windows just acts up and a reboot will cure it. If the problem persists, you will have to go through the typical troubleshooting (were there any recent software updates that may have broken something - can you roll back to an earlier version? Is there other software installed that can successfully interact with that PCIe card?, etc.).

[Galaxysurfer]

On Linux there is code for drm ( see quote below). In my case it comes from the Nvidia tuner. I am using the nouveau drivers which are the non proprietary equivalent to the Nvidia issued ones. It might not be enabled but I know it is present. Several times while attempting to engage the tuner, I got no tuner present null etc. I am not sure if my card failed or not. I ended up playing musical hardware with some extra ones I have laying around. I had to reboot it several times & after a kernel update to get everything back to "normal". Not sure why it decided to crap out yesterday specifically. I am just glad I had both servers set to run so I still was able to get a copy of desired shows when the other server failed.

nouveau 0000:03:00.0: DRM: VRAM: 512 MiB
[ 3.556890] nouveau 0000:03:00.0: DRM: GART: 1048576 MiB
[ 3.556894] nouveau 0000:03:00.0: DRM: TMDS table version 2.0
[ 3.556896] nouveau 0000:03:00.0: DRM: DCB version 4.0
[ 3.556899] nouveau 0000:03:00.0: DRM: DCB outp 00: 02000300 00000028
[ 3.556902] nouveau 0000:03:00.0: DRM: DCB outp 01: 01000302 00020030
[ 3.556904] nouveau 0000:03:00.0: DRM: DCB outp 02: 04012310 00000028
[ 3.556906] nouveau 0000:03:00.0: DRM: DCB outp 03: 02021322 00020010
[ 3.556909] nouveau 0000:03:00.0: DRM: DCB conn 00: 00001030
[ 3.556911] nouveau 0000:03:00.0: DRM: DCB conn 01: 00002161
[ 3.556912] nouveau 0000:03:00.0: DRM: DCB conn 02: 00000200
[ 3.559180] nouveau 0000:03:00.0: DRM: MM: using CRYPT for buffer copies

Puzzled at what the weirdness was about. I will chalk it up to Halloween haunting/ possession.


As to drm being present, would you say they are prepping for when atsc switches over to version 3 everywhere? In Canada I don't think there is any broadcasts in Atsc 3.0 that I know of. SiliconDust HDHR products offered for sale include both atsc 1.0 & 3.0.