On 18/11/2020 09:46, David Watkins wrote:
> A bit more googling suggests it may be the backend testing the card
> which is triggering the firmware load, in which case I'm back to
> square one with trying to identify the problem.
>
> I'll try increasing the timeouts on the card to see if that helps.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums:https://forum.mythtv.org
Whats changed recently :- is it a new host machine or have you just
added a new DVB card.
When I went from a dual core Haswell box to a quad core NUC, udev rules
just went unreliable.
I would fit a single WinTV-dualHD which gives you the same recording
capability without needing udev.
Or for that matter just use two identical cards, I've got a spare PCTV
nanoStick T2 290e which is just gathering dust if you want it send me
your address.
> A bit more googling suggests it may be the backend testing the card
> which is triggering the firmware load, in which case I'm back to
> square one with trying to identify the problem.
>
> I'll try increasing the timeouts on the card to see if that helps.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums:https://forum.mythtv.org
Whats changed recently :- is it a new host machine or have you just
added a new DVB card.
When I went from a dual core Haswell box to a quad core NUC, udev rules
just went unreliable.
I would fit a single WinTV-dualHD which gives you the same recording
capability without needing udev.
Or for that matter just use two identical cards, I've got a spare PCTV
nanoStick T2 290e which is just gathering dust if you want it send me
your address.