[SOLVED] HVR-2250 not detected

[NinthWave]

I had this device working fine on my Windows PC.
Got a new small server and want to move NextPVR to it.

After install:

Code:

root@debianq35:/usr/share# dmesg | grep saa7164 [    3.777814] CORE saa7164[0]: subsystem: 0070:8851, board: Hauppauge WinTV-HVR2250 [card=7,autodetected] [    3.777825] saa7164[0]/0: found at 0000:01:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xc1000000 [    4.005115] saa7164_downloadfirmware() no first image [    4.005182] saa7164_downloadfirmware() Waiting for firmware upload (NXP7164-2010-03-10.1.fw) [    4.043245] saa7164 0000:01:00.0: firmware: direct-loading firmware NXP7164-2010-03-10.1.fw [    4.043253] saa7164_downloadfirmware() firmware read 4019072 bytes. [    4.043253] saa7164_downloadfirmware() firmware loaded. [    4.043258] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072 [    4.043265] saa7164_downloadfirmware() FirmwareSize = 0x1fd6 [    4.043265] saa7164_downloadfirmware() BSLSize = 0x0 [    4.043266] saa7164_downloadfirmware() Reserved = 0x0 [    4.043266] saa7164_downloadfirmware() Version = 0x1661c00 [   11.173101] saa7164_downloadimage() Image downloaded, booting... [   11.285141] saa7164_downloadimage() Image booted successfully. [   13.721143] saa7164_downloadimage() Image downloaded, booting... [   15.345137] saa7164_downloadimage() Image booted successfully. [   15.394074] saa7164[0]: Hauppauge eeprom: model=88061 [   16.060811] dvbdev: DVB: registering new adapter (saa7164) [   16.060822] saa7164 0000:01:00.0: DVB: registering adapter 0 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)... [   19.217725] dvbdev: DVB: registering new adapter (saa7164) [   19.217731] saa7164 0000:01:00.0: DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)... [   19.253711] saa7164[0]: registered device video0 [mpeg] [   19.480047] saa7164[0]: registered device video1 [mpeg] [   19.691556] saa7164[0]: registered device vbi0 [vbi] [   19.691647] saa7164[0]: registered device vbi1 [vbi] [   19.693449] saa7164 driver loaded

I have this Docker Compose (Portainer Stack):

Code:

services:   nextpvr:     image: nextpvr/nextpvr_amd64:stable     container_name: nextpvr     hostname: ricevilo     network_mode: host     ports:       - 8866:8866       - 16891:16891/udp     volumes:       - config:/config       - videos:/recorddings       - videos:/buffer           restart: unless-stopped     volumes:   config:   videos:

I can access the GUI fine but no devices are seen.

Have I missed something.

[mvallevand]

I don't see you passing the /dev/dvb device to your Docker.

Martin

[NinthWave]

I don't see you passing the /dev/dvb device to your Docker.

Martin

Damn, I saw there were no example of that on the DockerHub/nextpvr page but I forgot to put one.

Code:

root@debianq35:/dev# cd dvb root@debianq35:/dev/dvb# ls adapter0  adapter1 root@debianq35:/dev/dvb# cd adapter0 root@debianq35:/dev/dvb/adapter0# ls demux0  dvr0  frontend0  net0

I tried to include that:

Code:

    devices:       - /dev/dvb/adapter0:/dev/dvb/adapter0       - /dev/dvb/adapter1:/dev/dvb/adapter1

Without success.

Then this:

Code:

    devices:       - /dev/video0:/dev/video0       - /dev/dvb/adapter1/dvr0:/dev/dvb/adapter1/dvr0

 Nope

And finally this:

Code:

    devices:       - /dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0       - /dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0

Still no show

I am out of option

[mvallevand]

What about simply /dev/dvb. Supporting bare metal is so much easier why not just use it?

! Martin

[NinthWave]

What about simply /dev/dvb.  Supporting bare metal is so much easier why not just use it?

! Martin

/dev/sdb did not work.

What do you mean bare metal? Why using Docker instead of right on my linux OS?
I have a Windows PC and a Proxmox<Debian<Docker/Portainer server because of n containers.

This is what worked overall:

Code:

services:   nextpvr:     image: nextpvr/nextpvr_amd64:stable     environment:       TZ: America/Montreal     container_name: nextpvr #  hostname: ricevilo     network_mode: host     devices:       - /dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0       - /dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0     ports:       - 8866:8866       - 16891:16891/udp           volumes:       - config:/config       - videos:/recorddings       - videos:/buffer           restart: unless-stopped

[sub]

I'd open a bash shell into the container and have a look what is in /dev/dvb. From your description, it sounds like you're not managing to get it mapped into your container though, or NextPVR should see it.

Maybe confirm your device is fully functional on the host (like running dvbv5-scan). Might be missing firmware or something, which can cause it to show up, but not actually be usable.

[NinthWave]

It's detected now. I found the answer on Proxmox and Debian.

When the VM is rebooted, the pcie powercycle is not handled properly so the card won't be discovered at boot.
In order to make it work again, one has to reboot the host (Proxmox).
Unless one has pretty special hardware, it's the only way to properly cycle down the pcie card.