I use a wireless keyboard to control a homebuilt Mageia-KDE powered HTPC. Every so often I will find that MythTV cannot gain live TV.

Whenever this happens, mouse movements controlled by the keyboard's tracker pad will have become miniscule requiring multiple strokes across the tracker pad to gain any useful movement.

A reboot restores both mouse control and MythTV.

I can see nothing in the logs that suggests a cause.

What I need is a clue or two of what parts of the system might affect the mouse control. I suspect that will also answer mythtv's detachment from the TV tuners.

what (kind of) logs did you check?
probably you need to look for X related messages in users' home, or in /var/log or ...?
I think the behavior of you mouse is just a side-effect, not the real issue you need to catch

Hmm. I thought you might be on to something.
I examined the following log files in /var/log
boot.log
secutity.log
Xorg.0.log
Xorg.0.log.old

and the latest mythtv prior to the most reecent (following reboot). e,g. mythpreviewgen.nnnnnnnnnnnn.log
mythpreviewgen.nnnnnnnnnnnn.log
mythmetadatalookup.nnnnnnnnnnn.log
mythbackend.nnnnnnnnnnn.log

No obvious signs.

Since this thread started, I have had to reboot twice, so no luck so far.

and what about ~/.xsession-errors* and /var/log/messages (and other logs in /var/log)?

~/.xsession-errors was no help and messages wasn't available until I installed rsyslog.
It was another five days until it happened again. This time there were some clues in messages.

The first was:

[drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A*
FIFO underrun

The next was:

09:50:59 kernel: [415457.101730] irq 16: nobody cared (try booting with the*
"irqpoll" option)

The third was:

09:50:59 kernel: [415457.101788] Disabling IRQ #16

IRQ 16 is linked to the SAA716x chip on the DVB-T2 TV card.

This looks like the source of the problem but what to do about it is unclear.
I will write to TBS Technology. They may be able to add something.

I did a www search for TBS-6280 and IRQ 16.
To my surprise, I was shown a link to TBS Technology's forum and then to a link to an article describing this as a 'known' problem.

The solution is to create (if it doesn't already exist) the file:
/etc/modprobe.d/tbs.conf

then to insert into it the line:
options saa716x_tbs_dvb int_type=1 plus a further line for newer TBS cards:
options tbs_pcie-dvb tbs_int_type=1

reboot and test with cat /proc/interrupts to see that the card was now on a*
separate interrupt.

It worked. I will mark this as [SOLVED].

1 members found this post helpful.