[mythtv-users] Best tuner? - now driver question
jimmorton01 at gmail.com
Wed Jan 13 12:14:52 UTC 2021
On Tue, Jan 12, 2021 at 11:54 AM DaveD <mythtv at guiplot.com> wrote:
> On 12/6/20 11:34 AM, DaveD wrote:
> After a couple of days, I stopped checking the data and let it run for a
> week before looking again. Unfortunately, after about 3 days the logged
> card started to always be "unknown". That's the default. When the
> program starts, it checks for adapters by listing /dev/dvb. It then
> finds the chip for each adapter using "dmesg | grep 'DVB: registering
> adapter '" which lets me build a unique name for each card. The problem
> occurred when dmesg got overloaded with messages and the old ones were
> dropped. No more output from the dmesg | grep command.
> Whenever I've used dmesg in the past, it showed history all the way back
> to the boot. I never even realized there was a limit, but now the
> driver for the Hauppauge spams dmesg every time it changes channels with
> "xc5000: Firmware dvb-fe-xc5000-1.6.114.fw loaded and running"
> (ridiculous!). With my app changing channels 12 times every hour (plus
> normal use), it takes about 4 days to fill the dmesg ring buffer. The
> Dvico does a similar output to dmesg, but only once per app invocation.
> Dave D.
How about something such as
dmesg | grep 'DVB: registering adapter >> adapters.txt # append any
sort adapters.txt > temp_file # sort
uniq temp_file > adapters.txt # get rid of dups and write to orig file
rm temp_file # cleanup
And change your script to look at adapters.txt which will obviously
accumulate the messages regardless of what ages out of dmesg.
This could probably be made into a one liner and skip the temp working file
but this illustrates the process clearly.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users