NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support v
« Previous 1 … 5 6 7 8 9 … 43 Next »
WinTV-quadHD

 
  • 0 Vote(s) - 0 Average
WinTV-quadHD
JoBanJo
Offline

Junior Member

Australia
Posts: 20
Threads: 3
Joined: Oct 2023
#1
2023-11-04, 09:49 AM
Hello, I am trying to use a WinTV-quadHD with NextPVR on a ubuntu vm using the .deb installer but NextPVR doesn't see the device.

How do I pass the device to NextPVR when using the .deb installer?

Also when running NextPVR with docker I get this error: 2023-11-04 09:39:51.987 [ERROR][1] ERROR: Open frontend0 failed
ERROR: Open frontend0 failed
ERROR: Open frontend0 failed
ERROR: Open frontend0 failed


The WinTV-quadHD works in tvheadend but I'd much rather use NextPVR.


Attached Files
.zip   logs-20231104-0940.zip (Size: 3.71 KB / Downloads: 1)
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,865
Threads: 954
Joined: May 2006
#2
2023-11-04, 12:34 PM (This post was last modified: 2023-11-04, 12:55 PM by mvallevand.)
I don't understand the question, this log is for a Docker install but you say you are using the deb installer which is not needed for Docker.

If you are running TVHeadend in Docker you need to configure the /dev/dvb device to NextPVR Docker the same way --device /dev/dvb:/dev/dvb

Regardless of whether you want to run NextPVR on Docker or from the Ubuntu VM you do need to ensure the that the Hauppauge drivers and firmware are installed properly. If you are going from a host to a VM to Docker that would mean checking all 3 configurations. I am guessing if you look at dmesg and journalctl you will find you are missing firmware or another component. Running both a VM and a Docker seems unnecessary.

Martin
JoBanJo
Offline

Junior Member

Australia
Posts: 20
Threads: 3
Joined: Oct 2023
#3
2023-11-04, 12:56 PM (This post was last modified: 2023-11-04, 01:00 PM by JoBanJo.)
(2023-11-04, 12:34 PM)mvallevand Wrote: I don't understand the question, this log is for a Docker install but you say you are using the deb installer which is not needed for Docker.

If you are running TVHeadend in Docker you need to configure the /dev/dvb device to NextPVR Docker the same way --device /dev/dvb:/dev/dvb

Regardless of whether you want to run NextPVR on Docker or from the Ubuntu VM you do need to ensure the that the Hauppauge drivers and firmware are installed properly. If you are going from a host to a VM to Docker that would mean checking all 3 configurations.  I am guessing if you look at dmesg and journalctl you will find you are missing firmware or another component.  Running both a VM and a Docker seems unnecessary.

Martin

Hi Martin, 

It's two questions:

1. How do I pass the device to the .deb version of the install. When I run the .deb version it doesn't see the device. 

2. Why doesn't the device work with the docker version? I followed the official install guide for the device. The device works fine with tvheadend installed on the exact same vm. 

I am running a Ubuntu vm inside truenas scale because the true charts version also wasn't seeing the device....
I tried the .deb version first which didn't work then I tried the Docker version which is why I'm asking about both.

I hope that's more clear.

Thanks, 
Jo.
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,865
Threads: 954
Joined: May 2006
#4
2023-11-04, 01:40 PM (This post was last modified: 2023-11-04, 01:46 PM by mvallevand.)
Ok you are trying to thing, but they seem to be failing for the same reason. Let's see if you get it it forking in the host vm first.

First what to does running find /dev/dvb show It will be something like this is if it is installed correctly, you should have 4 devices on adapter0

Code:
/dev/dvb/
/dev/dvb/adapter3
/dev/dvb/adapter3/net0
/dev/dvb/adapter3/dvr0
/dev/dvb/adapter3/demux0
/dev/dvb/adapter3/frontend0
/dev/dvb/adapter1
/dev/dvb/adapter1/net0
/dev/dvb/adapter1/dvr0
/dev/dvb/adapter1/demux0
/dev/dvb/adapter1/frontend0

Then look for missing firmware running sudo dmesg | less

Finally what does this show?

/opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover

It worked at one time because the devices were installed originally but it is not working now in the one log you posted, next time send all the logs. Perhaps TVHeadend is locking the device?


Martin
JoBanJo
Offline

Junior Member

Australia
Posts: 20
Threads: 3
Joined: Oct 2023
#5
2023-11-05, 12:08 AM
(2023-11-04, 01:40 PM)mvallevand Wrote: Ok you are trying to thing, but they seem to be failing for the same reason.  Let's see if you get it it forking in the host vm first.

First what to does running find /dev/dvb show  It will be something like this is if it is installed correctly, you should have 4 devices on adapter0

Code:
/dev/dvb/
/dev/dvb/adapter3
/dev/dvb/adapter3/net0
/dev/dvb/adapter3/dvr0
/dev/dvb/adapter3/demux0
/dev/dvb/adapter3/frontend0
/dev/dvb/adapter1
/dev/dvb/adapter1/net0
/dev/dvb/adapter1/dvr0
/dev/dvb/adapter1/demux0
/dev/dvb/adapter1/frontend0

Then look for missing firmware running sudo dmesg | less

Finally what does this show?

/opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover

It worked at one time because the devices were installed originally but it is not working now in the one log you posted, next time send all the logs.  Perhaps TVHeadend is locking the device?


Martin

So tvheadend was locking the device. The .deb install of npvr can now see the device but can't find any channels. 


running /dev/dvb retunred this:
jobanjo@spicyubuntu:~$ /dev/dvb
-bash: /dev/dvb: Is a directory

jobanjo@spicyubuntu:~$ cd /dev/dvb
jobanjo@spicyubuntu:/dev/dvb$ ls
adapter0  adapter1  adapter2  adapter3


running  /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover returns this:
jobanjo@spicyubuntu:/mnt/nextpvr$ opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover
-bash: opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux: No such file or directory


I have attached the logs. 

Thanks, 
Jo.


Attached Files
.zip   logs-20231105-0000.zip (Size: 43.55 KB / Downloads: 5)
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,865
Threads: 954
Joined: May 2006
#6
2023-11-05, 12:29 AM
It looks like you forgot the leading / on the command and you didn't run find but no matter you found the main issue.

Typically scans fail when the selected scanning file is bad NextPVR uses the one from Linux TVHeadend maintains theinown repo. Copy the scan fail you used for TVHeadend into /usr/share/dvb/dvb-t/ and try it.

Martin
JoBanJo
Offline

Junior Member

Australia
Posts: 20
Threads: 3
Joined: Oct 2023
#7
2023-11-05, 08:16 AM
(2023-11-05, 12:29 AM)mvallevand Wrote: It looks like you forgot the leading / on the command and you didn't run find but no matter you found the main issue.

Typically scans fail when the selected scanning file is bad NextPVR uses the one from Linux TVHeadend maintains theinown repo.  Copy the scan fail you used for TVHeadend into  /usr/share/dvb/dvb-t/ and try it.

Martin

Oops sorry I forgot to run  /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover

Heres the result: 

jobanjo@spicyubuntu:/usr/share/dvb/dvb-t$ /opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux -discover
<devices>
  <device>
    <name>adapter3/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-T</type>
    <filter>adapter3/frontend0</filter>
    <instance>1</instance>
    <resource>adapter3</resource>
  </device>
  <device>
    <name>adapter3/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-C</type>
    <filter>adapter3/frontend0</filter>
    <instance>1</instance>
    <resource>adapter3</resource>
  </device>
  <device>
    <name>adapter2/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-T</type>
    <filter>adapter2/frontend0</filter>
    <instance>1</instance>
    <resource>adapter2</resource>
  </device>
  <device>
    <name>adapter2/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-C</type>
    <filter>adapter2/frontend0</filter>
    <instance>1</instance>
    <resource>adapter2</resource>
  </device>
  <device>
    <name>adapter1/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-T</type>
    <filter>adapter1/frontend0</filter>
    <instance>1</instance>
    <resource>adapter1</resource>
  </device>
  <device>
    <name>adapter1/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-C</type>
    <filter>adapter1/frontend0</filter>
    <instance>1</instance>
    <resource>adapter1</resource>
  </device>
  <device>
    <name>adapter0/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-T</type>
    <filter>adapter0/frontend0</filter>
    <instance>1</instance>
    <resource>adapter0</resource>
  </device>
  <device>
    <name>adapter0/frontend0 (Silicon Labs Si2168)</name>
    <type>DVB-C</type>
    <filter>adapter0/frontend0</filter>
    <instance>1</instance>
    <resource>adapter0</resource>
  </device>
</devices>

I tried manually creating a DVB scan table using the frequency my local tower uses but it still didnt work. I have attached the scan table I made. 

Thanks, 
Jo.


Attached Files
.zip   au-Test.zip (Size: 432 bytes / Downloads: 1)
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,865
Threads: 954
Joined: May 2006
#8
2023-11-05, 11:16 AM
Let's test your file outside NextPVR using just Linux

sudo service nextpvr-server restart
dvbv5-scan /usr/share/dvb/dvb-t/au-Test
JoBanJo
Offline

Junior Member

Australia
Posts: 20
Threads: 3
Joined: Oct 2023
#9
2023-11-06, 01:41 AM
(2023-11-05, 11:16 AM)mvallevand Wrote: Let's test your  file outside NextPVR using just Linux
sudo service nextpvr-server restart
dvbv5-scan /usr/share/dvb/dvb-t/au-Test


jobanjo@spicyubuntu:~$ sudo service nextpvr-server restart
jobanjo@spicyubuntu:~$ sudo dvbv5-scan /usr/share/dvb/dvb-t/au-Test
Scanning frequency #1 620500000
Lock  (0x1f) Signal= -30.00dBm C/N= 26.00dB UCB= 0 postBER= 545x10^-3
ERROR    dvb_read_sections: no data read on section filter
ERROR    error while waiting for PAT table
Scanning frequency #2 648500000
Lock  (0x1f) Signal= -29.00dBm C/N= 26.75dB UCB= 0 postBER= 1.00
ERROR    dvb_read_sections: no data read on section filter
ERROR    error while waiting for PAT table
Scanning frequency #3 627500000
Lock  (0x1f) Signal= -28.00dBm C/N= 22.75dB UCB= 0 postBER= 1.00
ERROR    dvb_read_sections: no data read on section filter
ERROR    error while waiting for PAT table
Scanning frequency #4 634500000
Lock  (0x1f) Signal= -28.00dBm C/N= 28.75dB UCB= 0 postBER= 1.00
ERROR    dvb_read_sections: no data read on section filter
ERROR    error while waiting for PAT table
Scanning frequency #5 641500000
Lock  (0x1f) Signal= -29.00dBm C/N= 27.75dB UCB= 0 postBER= 1.00
ERROR    dvb_read_sections: no data read on section filter
ERROR    error while waiting for PAT table
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,865
Threads: 954
Joined: May 2006
#10
2023-11-06, 01:53 AM
Until you have that working on Linux NextPVR won't work. Not sure what to say since it is locking. Which Ubuntu version are you running?

Martin
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)

Pages (2): 1 2 Next »


Possibly Related Threads…
Thread Author Replies Views Last Post
  Hauppauge WinTV-HVR-955Q Supported - US? cybrsage 2 937 2021-12-03, 01:15 AM
Last Post: cybrsage
  WinTV-DualHD Supported on RaspberryPi? zed 6 3,542 2021-03-17, 03:31 PM
Last Post: shspvr

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode