<!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 13:55, Stephen
Worthington wrote:<br>
</div>
<blockquote type="cite"
cite="mid:uubq2kp8fs266ua4s4qi6eg4k3gg13lmco@4ax.com">
<pre wrap="" class="moz-quote-pre">On Wed, 21 May 2025 10:54:09 +1200, you wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">
On 2025-05-21 10:41, Curtis Walker wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">On Wed, 21 May 2025 at 10:19, Paul <a class="moz-txt-link-rfc2396E" href="mailto:paulgir@gmail.com"><paulgir@gmail.com></a> wrote:
Hi
I have been seeing minor artifacts (pixellation) , mainly after
skipping forward during playback.
Hauppauge_WinTV-HVR-2200Back in my installation of MythTV on
Xubuntu 16.04 I saw a similar effect because one piece of firmware
(nxp7164-2010-03-10.1.fw) for
my Hauppauge_WinTV-HVR-2200 was not in /lib/firmware/'current
kernal' , so I was checking the locations of the relevant
firmware and I see /lib/firmware/'current kernal' no longer
exists.
The HVR-2200 drivers: v4l-saa7164-1.0.2.fw ;
v4l-saa7164-1.0.3.fw ; cp dvb-fe-tda10048-1.0.fw and
nxp7164-2010-03-10.1.fw are currently all in
/lib/firmware.
The other thing I noticed is that all the firmware is Zstandard
compressed and the 4 HVR-2200 files with .fw extensions are
described in the Thunar file manager as "unknown".
Do I need to compress these files and convert them to .fw.zst
extensions like all the others or are these ok as is?
Regards
I may have missed it, but what distro are you currently using?
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Hi , in recent weeks I went from 20.04 to 24.04 via 22.04 and to MythTV
version 35
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
I had a look at my /lib/firmware directory and it looks like the new
standard in Ubuntu 24.04 is to compress all the .fw files. I have a
lot of .fw.zst files - it looks like most of the .fw files that are
coming from current 24.04 packages are zst compressed. But in the
dmesg output, I can still see .fw files being loaded, so it is not
necessary to go around compressing your other .fw files.
Not all drivers report loading their firmware files, but it always
pays to check occasionally to see what is happening at boot time. Take
a look at the output of:
dmesg | grep "\.fw"
If it is a long time since the last boot, there may no longer be any
boot messages in the dmesg output, so if possible check soon after a
boot.
I have never actually heard of there being a /lib/firmware/'current
kernel' directory. I have always put the firmware in /lib/firmware or
an appropriate subdirectory of /lib/firmware.
_______________________________________________
mythtvnz mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtvnz@lists.ourshack.com">mythtvnz@lists.ourshack.com</a>
<a class="moz-txt-link-freetext" href="https://lists.ourshack.com/mailman/listinfo/mythtvnz">https://lists.ourshack.com/mailman/listinfo/mythtvnz</a>
Archives <a class="moz-txt-link-freetext" href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a></pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
</pre>
<p>Btw: <span style="white-space: pre-wrap">/lib/firmware/'current </span><span
style="white-space: pre-wrap">kernel' e.g. /lib/firmware/4.4.0-31-generic</span></p>
<p><span style="white-space: pre-wrap">/lib/firmware had a sub-directory for every new kernel.</span></p>
<blockquote type="cite"
cite="mid:uubq2kp8fs266ua4s4qi6eg4k3gg13lmco@4ax.com">
<pre wrap="" class="moz-quote-pre">
</pre>
</blockquote>
</body>
</html>