On Mon, 30 Dec 2019 15:29:41 -0800 (PST)
Paul Heinlein <[email protected]> dijo:
>> I could use some suggestions for what to poke at next. Any ideas?
>My first thought is that a new Intel video driver was recently
>installed and that it's buggy with desktop hardware, which I assume to
>be somewhat different (and older) and your laptop.
>
>My second thought, not unlike the first, is that a new kernel
>subsystem isn't working and playing well with the desktop hardware.
>
>Can you reboot into an older kernel on the desktop?
I had 4.15.0-72-generic, and Grub listed a couple older ones, so I
rebooted into 4.13..0-36-generic. No difference. I had upgraded the
laptop to 5.3 in order to get the wifi working, so I installed 5.3 on
the desktop as well. But after rebooting to 5.3.0-24-generic it still
won't work correctly. I keep getting a popup that says 'Communication
error.' The tuner is hung until I click on OK in the popup, then the
tuner lets me reconnect. This happens every three or four minutes.
It was a good idea, but it didn't work. :(
Edit: Maybe it did work, at least partially. I had a terminal window
open so it dawned on me to launch the tuner from the command line to
see what might happen. Omigod, the error messages - pages and pages,
all the same:
ts demux error:libvbpsi error (PSI decoder): TS duplicate
(received 0, expected 1) for PID 0
And after about six minutes of playing I got the dreaded 'Communication
error' popup again, whereupon the terminal announced:
main input error: ES_OUT_SET_(GROUP_)PCR is called too late
(pts_delay increased to 1000ms)
Now, I don't know whether those error messages were from the tuner or
from VLC. And regardless, they mean nothing to me. All I can tell is
that the last one is apparently what caused the 'Communication error'
popup.
At least now I have a bit more data to go on. Maybe those error
messages will mean something to someone here.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug