Forums » General »
Some things in the log I wonder about. TVHeadend 4.2.4
Added by Anders Gustafsson about 2 years ago
First this one:
Nov 17 18:43:02 tvburk kernel: usb 2-2.4: DVB: adapter 1 frontend 1 frequency 0 out of range (42000000..1002000000)
Nov 17 18:43:02 tvburk tvheadend[6530]: linuxdvb: adapter 1 setting exclusive flag
Nov 17 18:43:02 tvburk tvheadend[6530]: linuxdvb: adapter 1 has tuner count 1 for type DVB-C (wrong config)
Nov 17 18:43:02 tvburk tvheadend[6530]: linuxdvb: adapter 1 has tuner count 2 for type DVB-T (wrong config)
Nov 17 18:43:02 tvburk kernel: usb 2-2.4: DVB: adapter 1 frontend 0 frequency 0 out of range (174000000..862000000)
Nov 17 18:43:02 tvburk tvheadend[6530]: linuxdvb: adapter added /dev/dvb/adapter1
I know that the frequency bit is cosmetic, but the config? This stick shows up as three adapters two MN88473 and one RTL2832. Of the three, only DVB-C is enabled in the TVH UI.
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) libinput: Astrometa DVB-T2: is a virtual subdevice
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Option "_source" "_driver/libinput"
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Option "Device" "/dev/input/event16"
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Astrometa DVB-T2: always reports core events
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) systemd-logind: returning pre-existing fd for /dev/input/event16 13:80
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) Using input driver 'libinput' for 'Astrometa DVB-T2'
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Astrometa DVB-T2: Applying InputClass "libinput keyboard catchall"
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Astrometa DVB-T2: Applying InputClass "evdev keyboard catchall"
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Astrometa DVB-T2: Applying InputClass "system-keyboard"
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (**) Astrometa DVB-T2: Applying InputClass "evdev keyboard catchall"
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) event16 - Astrometa DVB-T2: device is a keyboard
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) event16 - Astrometa DVB-T2: device is a pointer
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) event16 - Astrometa DVB-T2: trackpoint device set to range 20
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) event16 - Astrometa DVB-T2: trackpoint does not have a specified range, guessing... see https://wayland.freedesktop.org/libinput/doc/1.10.5/trackpoints.>
Nov 17 18:37:46 tvburk /usr/lib/gdm/gdm-x-session[13294]: (II) event16 - Astrometa DVB-T2: is tagged by udev as: Keyboard Pointingstick
What business does the server X have accessing a tuner? Why does it think it is a keyboard/mouse?
log 1
normal tuner initialisation
log 2
Remote control initialisation
OK. But the "wrong config" bugs me.
The "remote control" appears to be with the "Astrometa" stick only and I see that whenever tvh falls over 
It started happening approx a week ago when I moved around the cables to the sticks. The box in the wall where the DVB-C came in was a mess to I finally forced myself to tidy it up. After that did the issues start happening. I have removed the astrometa for now to see if it helps.
FWIW, tvh runs on a separate box and I use Xbmc to watch. It has been running fine for over a year. Could flaky cables or USB hubs cause this?
This is a problem of DVB-API
Update to latest TVH
OK. That would be 4.2.6, right? Even releases are the stable ones. Yes I have been thinking about that, just need to find the time.
Some things in the log I wonder about. TVHeadend 4.2.4
RE: Some things in the log I wonder about. TVHeadend 4.2.4
-
Added by saen acro about 2 years ago
