[mythtv-users] mythbackend Start-up issue - possible race with dvb device firmware loading
John Pilkington
johnpilk222 at gmail.com
Fri Nov 20 13:11:05 UTC 2020
On 19/11/2020 18:22, Klaas de Waal wrote:
> Hi John, Stephen,
>
> On my system, Fedora 33 with the TBS version of the drivers, I get the
> following for the MyGIca T230 USB tuner:
> dmesg | grep si2157
> [81708.931066] si2157 14-0060: found a 'Silicon Labs Si2158-A20'
> [81708.931087] si2157 14-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [81710.127330] si2157 14-0060: firmware version: 2.1.9
> [81777.542157] si2157 14-0060: found a 'Silicon Labs Si2158-A20'
> [81777.542214] si2157 14-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [81778.737773] si2157 14-0060: firmware version: 2.1.9
> [81846.110174] si2157 14-0060: found a 'Silicon Labs Si2158-A20'
> [81846.110204] si2157 14-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [81847.300054] si2157 14-0060: firmware version: 2.1.9
> [81914.474541] si2157 14-0060: found a 'Silicon Labs Si2158-A20'
> [81914.474565] si2157 14-0060: downloading firmware from file
> 'dvb-tuner-si2158-a20-01.fw'
> [81915.647009] si2157 14-0060: firmware version: 2.1.9
>
> I have EIT running with a one minute interval, and the "Open DVB Card on
> Demand" option checked.
> So it looks like that on each "open" the firmware is loaded again.
> As said, this is outside the control of mythtv as this is something the
> driver itself decides.
> On startup the backend currently opens each virtual tuner once, so there
> are a lot of these messages at startup if you have configured multirec
> for many instances.
>
> Last time I looked into this the firmware was only loaded once but I do
> not look into this very often so I do not know when the behavior has
> changed.
>
> Klaas.
Hi Klaas. Thanks for this response. I just did 'all known' scans with,
first, the pci DVB-T tuner and then the MyGica DVB-T/T2. After closing
mythtv-setup and starting mythbackend I got a hang after the 'set
delivery system : DVB-T' line. After 'killall mythbackend' until 'no
process found' I ran 'mythbackend' again and it started as normal.
I think in kubuntu that would be 'mythtv-setup.real', 'mythbackend' and
'mythfrontend.real' in different konsole tabs.
iirc I have had this failure to start immediately after a rescan, or
perhaps after a reboot, several times recently, and it sounds as if
David, the OP here, might have been seeing much the same effect.
I'm still seeing whatever this firmware activity is on a timescale of
minutes in Fedora 32. In el7 at the same commit the tda1004x check is
much less frequent and the one below is do-and-forget.
{{{
DVB: registering new adapter (Kworld UB499-2T T09)
[Thu Nov 19 17:44:33 2020] af9033 6-0038: firmware version: LINK
12.54.14.0 - OFDM 2.47.14.0
[Thu Nov 19 17:44:33 2020] af9033 6-0038: Afatech AF9033 successfully
attached
[Thu Nov 19 17:44:33 2020] usb 1-3: DVB: registering adapter 1 frontend
0 (Afatech AF9033 (DVB-T))...
}}}
kernel there is 4.4.244-1.el7.elrepo.x86_64. That wants me to know
about CIFS VFS: key responses instead...
John P
More information about the mythtv-users
mailing list