<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 2025-05-21 15:29, Curtis Walker
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPzMZFET5JhXHV427w5yGy9QhNHB5GsW9eqPLgDeoxLyhJNzKg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div><br>
<br>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Wed, 21 May 2025, 14:54
Paul, <<a href="mailto:paulgir@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">paulgir@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><br>
</p>
<div>On 2025-05-21 14:34, Curtis Walker wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif">I had an
issue with the saa7164 firmware in 2011....maybe
some of what worked for me back then will work for
you now?</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><a
href="https://bbs.archlinux.org/viewtopic.php?id=126229" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">https://bbs.archlinux.org/viewtopic.php?id=126229</a></div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif">I run Arch
linux, latest updates & kernel (6.14.6), with
no such issues, thankfully.</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif">Good luck!</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 21 May
2025 at 14:28, Paul <<a
href="mailto:paulgir@gmail.com" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">paulgir@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
On 2025-05-21 13:55, Stephen Worthington wrote:<br>
> On Wed, 21 May 2025 10:54:09 +1200, you
wrote:<br>
><br>
>> On 2025-05-21 10:41, Curtis Walker wrote:<br>
>>> On Wed, 21 May 2025 at 10:19, Paul
<<a href="mailto:paulgir@gmail.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">paulgir@gmail.com</a>>
wrote:<br>
>>><br>
>>> Hi<br>
>>><br>
>>> I have been seeing minor
artifacts (pixellation) , mainly after<br>
>>> skipping forward during
playback.<br>
>>><br>
>>> Hauppauge_WinTV-HVR-2200Back in
my installation of MythTV on<br>
>>> Xubuntu 16.04 I saw a similar
effect because one piece of firmware<br>
>>> (nxp7164-2010-03-10.1.fw) for<br>
>>><br>
>>> my Hauppauge_WinTV-HVR-2200 was
not in /lib/firmware/'current<br>
>>> kernal' , so I was checking the
locations of the relevant<br>
>>> firmware and I see
/lib/firmware/'current kernal' no longer<br>
>>><br>
>>> exists.<br>
>>><br>
>>> The HVR-2200 drivers:
v4l-saa7164-1.0.2.fw ;<br>
>>> v4l-saa7164-1.0.3.fw ;
cp dvb-fe-tda10048-1.0.fw and<br>
>>> nxp7164-2010-03-10.1.fw are
currently all in<br>
>>><br>
>>> /lib/firmware.<br>
>>><br>
>>> The other thing I noticed is
that all the firmware is Zstandard<br>
>>> compressed and the 4 HVR-2200
files with .fw extensions are<br>
>>> described in the Thunar file
manager as "unknown".<br>
>>><br>
>>> Do I need to compress these
files and convert them to .fw.zst<br>
>>> extensions like all the others
or are these ok as is?<br>
>>><br>
>>> Regards<br>
>>><br>
>>><br>
>>> I may have missed it, but what distro
are you currently using?<br>
>> Hi , in recent weeks I went from 20.04
to 24.04 via 22.04 and to MythTV<br>
>> version 35<br>
> I had a look at my /lib/firmware directory
and it looks like the new<br>
> standard in Ubuntu 24.04 is to compress all
the .fw files. I have a<br>
> lot of .fw.zst files - it looks like most of
the .fw files that are<br>
> coming from current 24.04 packages are zst
compressed. But in the<br>
> dmesg output, I can still see .fw files being
loaded, so it is not<br>
> necessary to go around compressing your other
.fw files.<br>
><br>
> Not all drivers report loading their firmware
files, but it always<br>
> pays to check occasionally to see what is
happening at boot time. Take<br>
> a look at the output of:<br>
><br>
> dmesg | grep "\.fw"<br>
><br>
> If it is a long time since the last boot,
there may no longer be any<br>
> boot messages in the dmesg output, so if
possible check soon after a<br>
> boot.<br>
><br>
> I have never actually heard of there being a
/lib/firmware/'current<br>
> kernel' directory. I have always put the
firmware in /lib/firmware or<br>
> an appropriate subdirectory of /lib/firmware.<br>
><br>
><br>
>
_______________________________________________<br>
> mythtvnz mailing list<br>
> <a href="mailto:mythtvnz@lists.ourshack.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">mythtvnz@lists.ourshack.com</a><br>
> <a
href="https://lists.ourshack.com/mailman/listinfo/mythtvnz"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.ourshack.com/mailman/listinfo/mythtvnz</a><br>
> Archives <a
href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a><br>
<br>
<br>
/lib/firmware/'current kernel' Probably dated
back to 12.04 or 16.04 . I used to have to copy
NXP7164_2010-03-10.1.fw to /lib/firmware/'current
kernel' after kernel updates , or I would get
intermittent pixellation in recordings.<br>
After 20.04 I no longer need to do that. That's
probably when /lib/firmware/'current kernel'
ceased to exist.<br>
<br>
The output of dmesg | grep "\.fw" :<br>
<br>
[ 6.047781] saa7164_downloadfirmware() Waiting
for firmware upload (NXP7164-2010-03-10.1.fw)<br>
[ 22.767075] tda10048_firmware_upload: waiting
for firmware upload (dvb-fe-tda10048-1.0.fw)...<br>
[ 28.488814] tda10048_firmware_upload: waiting
for firmware upload (dvb-fe-tda10048-1.0.fw)...<br>
<br>
My system boots for recordings and then shuts down<br>
<br>
I compressed the four firmware files to see if it
makes any difference.<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
mythtvnz mailing list<br>
<a href="mailto:mythtvnz@lists.ourshack.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">mythtvnz@lists.ourshack.com</a><br>
<a
href="https://lists.ourshack.com/mailman/listinfo/mythtvnz"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.ourshack.com/mailman/listinfo/mythtvnz</a><br>
Archives <a
href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a><br>
</blockquote>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
mythtvnz mailing list
<a href="mailto:mythtvnz@lists.ourshack.com" target="_blank"
rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">mythtvnz@lists.ourshack.com</a>
<a href="https://lists.ourshack.com/mailman/listinfo/mythtvnz"
target="_blank" rel="noreferrer"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.ourshack.com/mailman/listinfo/mythtvnz</a>
Archives <a
href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/"
target="_blank" rel="noreferrer"
moz-do-not-send="true" class="moz-txt-link-freetext">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a></pre>
</blockquote>
<p>Thanks </p>
<p>That is the same procedure I used in 12.04 </p>
<p>Apart from the brief pixellation after skipping
forward during replay there are no other problems and
both HVR tuners work and come on-line fast.</p>
<p>There may be an entirely different cause for the
pixellation. I just looked at the HVR firmware because
that was a similar effect over a decade ago.</p>
<blockquote type="cite"> </blockquote>
</div>
_______________________________________________<br>
mythtvnz mailing list<br>
<a href="mailto:mythtvnz@lists.ourshack.com"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">mythtvnz@lists.ourshack.com</a><br>
<a
href="https://lists.ourshack.com/mailman/listinfo/mythtvnz"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.ourshack.com/mailman/listinfo/mythtvnz</a><br>
Archives <a
href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a></blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Heh. I remember upgrading my cabling and
installing a new, stronger roof antenna before finding it out
was a driver/firmware issue causing pixellation for the good
old saa7164.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I
think I had a HDHomerun by then , so I quickly eliminated
the possibility that it was a signal problem.</blockquote>
</div>
</div>
</div>
</blockquote>
<p>Your symptoms looked exactly the same as mine back then - after
20~30 mins of playback I would get pixellation:</p>
<p>"The additional firmware is for the RF modulator in the card -
specifically, the tda10048. Without this, it SEEMS to work fine,
until you get otherwise inexplicable pixellation. I hope this info
saves someone else a week's work and several dollars in trialling
new/different aerial connectors and attenuators!"</p>
<p>Pretty much what I saw.</p>
</body>
</html>