PoP!-OS 20.04

[shspvr]

Ok Martin what what option should I run to figer out the timing for PreStartup.sh

[sub]

Can you post the logs, so I can see the error it gets without any network available?

[shspvr]

Can you post the logs, so I can see the error it gets without any network available?

Here you ask without any network hook up bootup check same before but restart of service address tuner

[mvallevand]

Run

sudo dmesg > filename.txt

then open filename.txt in an editor

Try an determine where PCI, USB devices, and network services have loaded and compare that to the start of nextpvr.

Here are examples of what I see

[ 10.145423] usbcore: registered new interface driver iguanair
[ 10.487034] usbcore: registered new interface driver hdpvr
[ 20.218582] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
[ 23.089105] dvbdev: DVB: registering new adapter (saa7164)
[ 23.089116] saa7164 0000:01:00.0: DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[ 26.230494] dvbdev: DVB: registering new adapter (saa7164)
[ 26.230504] saa7164 0000:01:00.0: DVB: registering adapter 2 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...

So I need 27 seconds to see me devices. Then just change that in the script https://forums.nextpvr.com/showthread.ph...#pid530707

You might need to look at journalctl too with a similar process if you have slow network drives being mounted. It might be easier to read but you have to calculate the time.

If you want zip and upload the dmesg.txt and I can offer a suggestion.

Martin

[mvallevand]

Can you post the logs, so I can see the error it gets without any network available?

His issue is two fold, there is a network delay but he needs a delay for his PCE devices too.

Martin

[sub]

I was going to suggest an updated NShared.dll I posted for Windows a few minutes ago, but I can see the error is different on Linux, so I've attached an updated version which will hopefully cover both platforms.

That said, it was primarily aimed at network, so sounds like it wont entirely solve the problem...since your PCIe device is slow to load.

[shspvr]

Run

sudo dmesg > filename.txt

then open filename.txt in an editor

Try an determine where PCI, USB devices, and network services have loaded and compare that to the start of nextpvr.

Here are examples of what I see

[  10.145423] usbcore: registered new interface driver iguanair
[  10.487034] usbcore: registered new interface driver hdpvr
[  20.218582] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
[  23.089105] dvbdev: DVB: registering new adapter (saa7164)
[  23.089116] saa7164 0000:01:00.0: DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[  26.230494] dvbdev: DVB: registering new adapter (saa7164)
[  26.230504] saa7164 0000:01:00.0: DVB: registering adapter 2 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...

So I need 27 seconds to see me devices.  Then just change that in the script https://forums.nextpvr.com/showthread.ph...#pid530707

You might need to look at journalctl too with a similar process if you have slow network drives being mounted.  It might be easier to read but you have to calculate the time.

If you want zip and upload the dmesg.txt and I can offer a suggestion.

Martin

Being is my original primary server old and is AMD unlike the my gaming box which Intel that good possible but I wish make my new testing box in stead of using my dual boot steam game box as build all new Intel i3 9100 new primary media server.
Here the req output Martin

[shspvr]

I was going to suggest an updated NShared.dll I posted for Windows a few minutes ago, but I can see the error is different on Linux, so I've attached an updated version which will hopefully cover both platforms.

That said, it was primarily aimed at network, so sounds like it wont entirely solve the problem...since your PCIe device is slow to load.

Ok I give a try

[mvallevand]

Your timing seems pretty fast

[ 8.601774] input: Hauppauge WinTV-dualHD 01595 ATSC/QAM as /devices/pci0000:00/0000:00:10.1/usb8/8-1/8-1:1.0/rc/rc0/input23
[ 10.706818] r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx

So sub's network delay could work.

When you installed you did use apt and not dpkg right?

Martin

[shspvr]

Your timing seems pretty fast

[    8.601774] input: Hauppauge WinTV-dualHD 01595 ATSC/QAM as /devices/pci0000:00/0000:00:10.1/usb8/8-1/8-1:1.0/rc/rc0/input23
[  10.706818] r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx

So sub's network delay could work.

When you installed you did use apt and not dpkg right?

Martin

curl https://nextpvr.com/nextpvr-helper.deb -O then sudo apt install ./nextpvr-helper.deb --install-recommends it a brand new setup