Den gibt es nicht mehr, er heißt jetzt ATD.
Das macht nichts. Ich nehme jede Hilfe
Nein, nur ein Paar Anregungen:
- Wird der Empfänger erkannt? (cat /proc/bus/input/devices)
- Wird das Modul geladen? (dkms status)
- Steht etwas im Syslog, wenn es abfliegt?
- Ist der Receiver an USB 3.0/2.0 oder an USB 2.0/1.1 header angeschlossen? Letzteres favorisiert.
Albert
Alles anzeigen
- klar, wie gesagt, nach USB ziehen und wieder Verbinden läuft alles einwandfrei
$ dkms status
hid-rcking, 0.0.1, 3.8.0-26-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-27-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-29-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-31-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-33-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-35-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-39-generic, x86_64: installed
hid-rcking, 0.0.1, 3.8.0-44-generic, x86_64: installed
nvidia-304, 304.125, 3.8.0-44-generic, x86_64: installed
nvidia-304-updates, 304.125, 3.8.0-44-generic, x86_64: installed
$ uname -a
Linux yavdr 3.8.0-44-generic #66~precise1-Ubuntu SMP Tue Jul 15 04:01:04 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Alles anzeigen
May 30 22:00:22 yavdr vdr: video: 11:45:15.729 +27 371 0/\ms 62+2 v-buf
May 30 22:01:22 yavdr vdr: video: 11:46:15.729 +27 306 0/\ms 58+2 v-buf
May 30 22:02:22 yavdr vdr: video: 11:47:15.729 +27 434 0/\ms 63+2 v-buf
May 30 22:03:18 yavdr vdr: [1128] connect from 127.0.0.1, port 57108 - accepted
May 30 22:03:18 yavdr vdr: [1128] closing SVDRP connection
May 30 22:03:22 yavdr vdr: video: 11:48:15.729 +27 370 0/\ms 67+2 v-buf
May 30 22:04:22 yavdr vdr: video: 11:49:15.729 +27 242 0/\ms 58+2 v-buf
May 30 22:05:22 yavdr vdr: video: 11:50:15.729 +27 370 0/\ms 61+2 v-buf
May 30 22:05:48 yavdr kernel: [ 1664.498461] input: Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3:1.0/input/input12
May 30 22:05:48 yavdr kernel: [ 1664.498639] rcking 0003:1D57:AC01.0001: input,hidraw0: USB HID v1.10 Keyboard [Mouse] on usb-0000:00:12.0-3/input0
May 30 22:05:48 yavdr kernel: [ 1664.499013] rcking 0003:1D57:AC01.0002: unknown main item tag 0x0
May 30 22:05:48 yavdr kernel: [ 1664.499045] rcking 0003:1D57:AC01.0002: unknown main item tag 0x0
May 30 22:05:48 yavdr kernel: [ 1664.499096] rcking 0003:1D57:AC01.0002: collection stack underflow
May 30 22:05:48 yavdr kernel: [ 1664.499124] rcking 0003:1D57:AC01.0002: item 0 0 0 12 parsing failed
May 30 22:05:48 yavdr kernel: [ 1664.499160] rcking: probe of 0003:1D57:AC01.0002 failed with error -22
May 30 22:05:48 yavdr vdr-frontend[2262]: added /dev/input/event2
May 30 22:06:22 yavdr vdr: video: 11:51:15.729 +27 402 0/\ms 61+2 v-buf
May 30 22:06:56 yavdr vdr: [1128] connect from 192.168.120.107, port 38709 - accepted
May 30 22:07:19 yavdr vdr: [1128] closing SVDRP connection
May 30 22:07:22 yavdr vdr: video: 11:52:15.729 +27 434 0/\ms 65+2 v-buf
May 30 22:07:44 yavdr vdr: [1128] connect from 192.168.120.107, port 41265 - accepted
May 30 22:07:50 yavdr vdr: [1128] switching to channel 19
May 30 22:07:50 yavdr vdr: [1128] [softhddev]SetPlayMode: 0
May 30 22:07:50 yavdr vdr: [1128] [softhddev]SetVideoDisplayFormat: 1
May 30 22:07:50 yavdr vdr: [1128] [softhddev]GetSpuDecoder:
May 30 22:07:50 yavdr vdr: [2337] osdteletext-receiver thread ended (pid=1128, tid=2337)
May 30 22:07:50 yavdr vdr: [1128] buffer stats: 0 (0%) used
May 30 22:07:50 yavdr vdr: [2338] ERROR (device.c,1862): Ungültiger Dateideskriptor
May 30 22:07:50 yavdr vdr: [2338] TS buffer on device 10 thread ended (pid=1128, tid=2338)
May 30 22:07:50 yavdr vdr: [2335] buffer stats: 299296 (14%) used
May 30 22:07:50 yavdr vdr: [2335] receiver on device 10 thread ended (pid=1128, tid=2335)
May 30 22:07:50 yavdr vdr: [1128] dynamite: no devices within 60 seconds for receiving startup channel 7, giving up
May 30 22:07:50 yavdr vdr: [3155] receiver on device 10 thread started (pid=1128, tid=3155, prio=high)
May 30 22:07:50 yavdr vdr: [2336] ttxtsubs player thread ended (pid=1128, tid=2336)
May 30 22:07:50 yavdr vdr: [1128] buffer stats: 0 (0%) used
May 30 22:07:50 yavdr vdr: [1128] ttxtsubs: teletext subtitles replayer started with initial page 000
May 30 22:07:50 yavdr vdr: [3156] TS buffer on device 10 thread started (pid=1128, tid=3156, prio=high)
May 30 22:07:50 yavdr vdr: [3157] ttxtsubs player thread started (pid=1128, tid=3157, prio=high)
May 30 22:07:50 yavdr vdr: [1128] creating directory /var/run/vdr/vtx/S19.2E-133-5-772
May 30 22:07:50 yavdr vdr: [3158] osdteletext-receiver thread started (pid=1128, tid=3158, prio=high)
May 30 22:07:50 yavdr vdr: [1128] [softhddev]SetPlayMode: 1
May 30 22:07:50 yavdr vdr: audio/alsa: using pass-through device 'default'
May 30 22:07:50 yavdr vdr: audio/alsa: start delay 1000ms
May 30 22:07:50 yavdr vdr: [softhddev] invalid PES video packet
May 30 22:07:50 yavdr vdr: [softhddev] 2 invalid PES video packet(s)
May 30 22:07:51 yavdr vdr: codec: buggy libav, use ffmpeg
May 30 22:07:51 yavdr vdr: audio/alsa: using device 'default'
May 30 22:07:51 yavdr vdr: audio/alsa: start delay 1000ms
May 30 22:07:53 yavdr vdr: video/vdpau: synced after 94 frames
May 30 22:08:00 yavdr vdr: [1205] EPGSearch: timer conflict check started
May 30 22:08:00 yavdr vdr: [1205] EPGSearch: timer conflict check finished
Alles anzeigen
- um 22:03 war es wieder soweit, danach habe ich das Modul entladen und neu geladen um 22:05, das hat nicht geholfen und ich zog wieder den USB Stecker. Erst dann war alles wieder OK. Soweit ich sehe, steht nur dazu was, dass ich das Modul geladen habe.
- hängt am USB 2.0 OnBoard. Ein Gigabyte Board F2A85X-D3H http://www.gigabyte.com/fileup…oduct/2/4384/6849_big.jpg unter den PCI Leisten. Hatte vorher ein ASUS Board installiert M4A785TD-V EVO, gleiches Problem