Hallo, werde die Schüssel neu ausrichten und dann erneut testen. Ich melde mich sobald dies geschehen ist.
Vorerst herzlichen Dank für den Support.
Hallo, werde die Schüssel neu ausrichten und dann erneut testen. Ich melde mich sobald dies geschehen ist.
Vorerst herzlichen Dank für den Support.
Ich versuche immer noch verzweifelt meinen IR-Empfänger einzustellen.
cat /proc/bus/input/devices liefert mir:
I: Bus=0003 Vendor=9022 Product=d660 Version=0000
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:02:00.3-1/ir0
S: Sysfs=/devices/pci0000:00/0000:00:0c.0/0000:02:00.3/usb4/4-1/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=3
B: KEY=6c0904 2470c1 0 0 0 8 10000 190 40000840 1e1680 1 f8000000 ffc
I: Bus=0001 Vendor=10ec Product=0887 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:08.0/input/input7
U: Uniq=
H: Handlers=kbd event7
B: EV=40001
B: SND=6
Alles anzeigen
/root$ ls /dev/input
by-id
by-path
event0
event1
event2
event3
event4
event5
event6
event7
mice
mouse0
mouse1
wake-up
Alles anzeigen
Nur leider bleibt das Remoteplugin immer noch hier hängen:
Mar 10 11:00:09 Wohnzimmer vdr: [2241] starting plugin: remote
Mar 10 11:00:09 Wohnzimmer vdr: [2241] remote: unable to open '/dev/input/ir': Datei oder Verzeichnis nicht gefunden
Mar 10 11:00:09 Wohnzimmer vdr: [2241] ERROR: /dev/input/ir: Datei oder Verzeichnis nicht gefunden
Mar 10 11:00:11 Wohnzimmer vdr: [2241] ERROR: /dev/input/ir: Datei oder Verzeichnis nicht gefunden
Mar 10 11:00:13 Wohnzimmer vdr: [2241] remote: fatal error - unable to open input device
Mar 10 11:00:13 Wohnzimmer vdr: [2241] [xine..put] cXinelibOsdProvider: shutting down !
Kann mir das nochmal jemand helfen?
Muss ich Lirc vorher deaktivieren? Wenn ja, wie?
Edit: Leider wechselt die eventnummer ab und zu. Mal sind es 6 und 7, mal 5 und 7.
Edit2: Ich gebe es auf und habe mir ne X10 Fernbedienung mit USB Empfänger gekauft. Das klappt wunderbar mit lirc
ZitatAlles anzeigenOriginal von Garbor
In der Stable Version von "s2-liplianin" wird die Karte noch nicht unterstützt. Probier mal die Datei aus dem Link in meinem Beitrag eins über deinem
.deb Datei herunterladen und mit:
installieren.
hi,
ich weiss nicht ob ich mich zu doof anstelle...
aber wohin mit der runtergeladenen datei damit ich die auch installieren kann?
ich check nich ganz wie man da vorgeht... sorry
ist eigentlich vollkommen egal, du mußt nur Schreibrechte auf dem Ordner haben.
z.B./media/... oder /home/benutzername/Downloads
achsooo... sorry für die doofe frage!
solche selbstverständlichkeiten sind für mich noch völlig neu!
vielen dank! werde ich heute abend ausprobieren!
Update erster Beitrag:
- neue Erkenntnisse zum S3 Verhalten, der Treiber überlebt ohne weiteres die "wakeup from S3/S4" mit Anleitung für Yavdr 0.3a
Hallo,
kann mir mal jemand weiterhelfen?
Ich nutze den Treiber aus dem liplianin-dkms des vdr-teams vom 03.02.2011.
Nun wollte ich aktualisieren.
Was muss ich machen? Erst destallieren?
Ich habe folgende Anleitung gefunden:
ZitatAlles anzeigen
apt-get update
apt-get install python-software-properties
add-apt-repository ppa:the-vdr-team/vdr-ubuntu-karmic
apt-get update
apt-get install dkms
apt-get install dvb-s2api-liplianin-dkms
reboot
Aber schon beim update meckert er:
ZitatAlles anzeigen
jcc@yavdr:~$ sudo apt-get update
sudo: unable to resolve host yavdr
Ign http://ppa.launchpad.net lucid Release.gpg
Ign http://ppa.launchpad.net/the-v…vdr-ubuntu-karmic/ubuntu/ lucid/main Translation-de
Ign http://ppa.launchpad.net lucid Release.gpg
OK http://de.archive.ubuntu.com lucid Release.gpg
OK http://de.archive.ubuntu.com/ubuntu/ lucid/main Translation-de
OK http://de.archive.ubuntu.com/ubuntu/ lucid/restricted Translation-de
OK http://security.ubuntu.com lucid-security Release.gpg
Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-de
Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-de
Ign http://ppa.launchpad.net/the-v…/vdr-ubuntu-lucid/ubuntu/ lucid/main Translation-de
OK http://ppa.launchpad.net lucid Release.gpg
Ign http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu/ lucid/main Translation-de
Ign http://ppa.launchpad.net lucid Release.gpg
Ign http://ppa.launchpad.net/yavdr/vdr-ubuntu-karmic/ubuntu/ lucid/main Translation-de
OK http://ppa.launchpad.net lucid Release.gpg
Ign http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu/ lucid/main Translation-de
OK http://de.archive.ubuntu.com/ubuntu/ lucid/universe Translation-de
OK http://de.archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-de
OK http://de.archive.ubuntu.com lucid-updates Release.gpg
Ign http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-de
Ign http://de.archive.ubuntu.com/ubuntu/ lucid-updates/restricted Translation-de
Ign http://de.archive.ubuntu.com/ubuntu/ lucid-updates/universe Translation-de
Ign http://de.archive.ubuntu.com/ubuntu/ lucid-updates/multiverse Translation-de
Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-de
Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-de
OK http://ppa.launchpad.net lucid Release.gpg
Ign http://ppa.launchpad.net/yavdr/stable-xbmc/ubuntu/ lucid/main Translation-de
OK http://ppa.launchpad.net lucid Release.gpg
OK http://security.ubuntu.com lucid-security Release
OK http://de.archive.ubuntu.com lucid Release
Ign http://ppa.launchpad.net/yavdr/stable-yavdr/ubuntu/ lucid/main Translation-de
Ign http://ppa.launchpad.net lucid Release
Ign http://ppa.launchpad.net lucid Release
OK http://ppa.launchpad.net lucid Release
OK http://de.archive.ubuntu.com lucid-updates Release
Ign http://ppa.launchpad.net lucid Release
OK http://ppa.launchpad.net lucid Release
OK http://security.ubuntu.com lucid-security/main Packages
OK http://ppa.launchpad.net lucid Release
OK http://de.archive.ubuntu.com lucid/main Packages
OK http://de.archive.ubuntu.com lucid/restricted Packages
OK http://de.archive.ubuntu.com lucid/main Sources
OK http://de.archive.ubuntu.com lucid/restricted Sources
OK http://de.archive.ubuntu.com lucid/universe Packages
OK http://security.ubuntu.com lucid-security/restricted Packages
OK http://security.ubuntu.com lucid-security/main Sources
OK http://security.ubuntu.com lucid-security/restricted Sources
OK http://security.ubuntu.com lucid-security/universe Packages
OK http://security.ubuntu.com lucid-security/universe Sources
OK http://security.ubuntu.com lucid-security/multiverse Packages
OK http://ppa.launchpad.net lucid Release
Ign http://ppa.launchpad.net lucid/main Packages
Ign http://ppa.launchpad.net lucid/main Packages
OK http://de.archive.ubuntu.com lucid/universe Sources
OK http://de.archive.ubuntu.com lucid/multiverse Packages
OK http://de.archive.ubuntu.com lucid/multiverse Sources
OK http://ppa.launchpad.net lucid/main Packages
Ign http://ppa.launchpad.net lucid/main Packages
OK http://security.ubuntu.com lucid-security/multiverse Sources
OK http://de.archive.ubuntu.com lucid-updates/main Packages
OK http://de.archive.ubuntu.com lucid-updates/restricted Packages
OK http://de.archive.ubuntu.com lucid-updates/main Sources
OK http://de.archive.ubuntu.com lucid-updates/restricted Sources
OK http://de.archive.ubuntu.com lucid-updates/universe Packages
OK http://de.archive.ubuntu.com lucid-updates/universe Sources
OK http://de.archive.ubuntu.com lucid-updates/multiverse Packages
OK http://de.archive.ubuntu.com lucid-updates/multiverse Sources
OK http://ppa.launchpad.net lucid/main Packages
OK http://ppa.launchpad.net lucid/main Packages
Ign http://ppa.launchpad.net lucid/main Packages
OK http://ppa.launchpad.net lucid/main Packages
Ign http://ppa.launchpad.net lucid/main Packages
Ign http://ppa.launchpad.net lucid/main Packages
Fehl http://ppa.launchpad.net lucid/main Packages
404 Not Found
Fehl http://ppa.launchpad.net lucid/main Packages
404 Not Found
Fehl http://ppa.launchpad.net lucid/main Packages
404 Not Found
W: Fehlschlag beim Holen von http://ppa.launchpad.net/the-v…n/binary-i386/Packages.gz 404 Not Found
W: Fehlschlag beim Holen von http://ppa.launchpad.net/the-v…n/binary-i386/Packages.gz 404 Not Found
W: Fehlschlag beim Holen von http://ppa.launchpad.net/yavdr…n/binary-i386/Packages.gz 404 Not Found
E: Einige Indexdateien konnten nicht heruntergeladen werden, sie wurden ignoriert oder alte an ihrer Stelle benutzt.
Du willst sicherlich kein Karmic-Repo in Dein yaVDR, was Lucid-basiert ist einbauen. Ich würde einfach den Stand so lassen, das eine Paket deinstallieren und das neue Paket aus dem testing-repo installieren. Bei mir geht die S480 übrigens auch mit v4l. Da könntest Du Dir auch das passende Paket aus testing raussuchen.
Also kurz und knackig, für s2-liblianin, Stand heute:
sudo apt-get remove --purge dvb-s2api-liplianin-dkms
sudo wget http://ppa.launchpad.net/yavdr/testing-vdr/ubuntu/pool/main/s/s2-liplianin-dkms/s2-liplianin-dkms_0~20110319.15386_all.deb /ort/wo/du/es/hinspeichern/willst/
sudo dpkg -i /ort/wo/du/es/hingespeichert/hast/s2-liplianin-dkms_0~20110319.15386_all.deb
sudo reboot
Vielen Dank Boss666, das hat sehr gut funktioniert!
Nach dem reboot war sogar ein Bild da. Das war mit dem alten Treiber bisher nicht der Fall. Da bedurfte es noch einer 20-sekündigen PowerOff-Pause...
Alles wird gut...
Hallo.
Nachdem ein erster erfolgreicher Reboot meine Hoffnung stärkte, dass de Karte evtl. auch nach einem "Kaltstart" läuft, zeigt es sich leider, dass der Treiber mein USB-Erkennungsproblem wohl nicht beseitigt hat.
ich habe mir mal die logs angeschaut und scheinbar läuft der VDR usb-technisch Amok:
ZitatAlles anzeigen
Mar 30 09:28:28 yavdr kernel: [ 160.136108] usb 4-1: device descriptor read/8, error -110
Mar 30 09:28:30 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:28:30 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:28:33 yavdr kernel: [ 165.256103] usb 4-1: device descriptor read/8, error -110
Mar 30 09:28:33 yavdr kernel: [ 165.360034] hub 4-0:1.0: unable to enumerate USB device on port 1
Mar 30 09:28:33 yavdr kernel: [ 165.548014] usb 7-1: new full speed USB device using ohci_hcd and address 2
Mar 30 09:28:33 yavdr kernel: [ 165.760413] usb 7-1: configuration #1 chosen from 1 choice
Mar 30 09:28:33 yavdr kernel: [ 165.851571] usbcore: registered new interface driver hiddev
Mar 30 09:28:33 yavdr kernel: [ 165.856689] input: JTTEL Inc. JTTEL Composite Devices as /devices/pci0000:00/0000:00:04.0/usb7/7-1/7-1:1.0/input/input7
Mar 30 09:28:33 yavdr kernel: [ 165.856836] generic-usb 0003:20E8:5820.0001: input,hidraw0: USB HID v10.01 Keyboard [JTTEL Inc. JTTEL Composite Devices] on usb-0000:00:04.0-1/input0
Mar 30 09:28:33 yavdr kernel: [ 165.862611] input: JTTEL Inc. JTTEL Composite Devices as /devices/pci0000:00/0000:00:04.0/usb7/7-1/7-1:1.1/input/input8
Mar 30 09:28:33 yavdr kernel: [ 165.862793] generic-usb 0003:20E8:5820.0002: input,hidraw1: USB HID v10.01 Mouse [JTTEL Inc. JTTEL Composite Devices] on usb-0000:00:04.0-1/input1
Mar 30 09:28:33 yavdr kernel: [ 165.871385] input: JTTEL Inc. JTTEL Composite Devices as /devices/pci0000:00/0000:00:04.0/usb7/7-1/7-1:1.2/input/input9
Mar 30 09:28:33 yavdr kernel: [ 165.871514] generic-usb 0003:20E8:5820.0003: input,hidraw2: USB HID v10.01 Device [JTTEL Inc. JTTEL Composite Devices] on usb-0000:00:04.0-1/input2
Mar 30 09:28:33 yavdr kernel: [ 165.871551] usbcore: registered new interface driver usbhid
Mar 30 09:28:33 yavdr kernel: [ 165.871555] usbhid: v2.6:USB HID core driver
Mar 30 09:28:34 yavdr kernel: [ 166.064028] usb 7-4: new full speed USB device using ohci_hcd and address 3
Mar 30 09:28:34 yavdr kernel: [ 166.276418] usb 7-4: configuration #1 chosen from 1 choice
Mar 30 09:28:34 yavdr kernel: [ 166.279388] hub 7-4:1.0: USB hub found
Mar 30 09:28:34 yavdr kernel: [ 166.282303] hub 7-4:1.0: 3 ports detected
Mar 30 09:28:34 yavdr kernel: [ 166.600015] usb 9-1: new full speed USB device using ohci_hcd and address 2
Mar 30 09:28:36 yavdr vdr: [1685] switching to channel 1
Mar 30 09:28:36 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:28:36 yavdr vdr: [1915] Text2Skin: message display update thread started (pid=1685, tid=1915)
Mar 30 09:28:38 yavdr vdr: [1915] Text2Skin: message display update thread ended (pid=1685, tid=1915)
Mar 30 09:28:38 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:28:38 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:28:46 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:28:46 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:28:47 yavdr vdr: [1685] switching to channel 1
Mar 30 09:28:47 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:28:47 yavdr vdr: [1916] Text2Skin: message display update thread started (pid=1685, tid=1916)
Mar 30 09:28:49 yavdr vdr: [1916] Text2Skin: message display update thread ended (pid=1685, tid=1916)
Mar 30 09:28:49 yavdr kernel: [ 181.776522] usb 9-1: device descriptor read/64, error -110
Mar 30 09:28:54 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:28:54 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:28:58 yavdr vdr: [1685] switching to channel 1
Mar 30 09:28:58 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:28:58 yavdr vdr: [1917] Text2Skin: message display update thread started (pid=1685, tid=1917)
Mar 30 09:29:00 yavdr vdr: [1917] Text2Skin: message display update thread ended (pid=1685, tid=1917)
Mar 30 09:29:03 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:03 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:05 yavdr kernel: [ 197.056018] usb 9-1: device descriptor read/64, error -110
Mar 30 09:29:05 yavdr kernel: [ 197.336015] usb 9-1: new full speed USB device using ohci_hcd and address 3
Mar 30 09:29:09 yavdr vdr: [1685] switching to channel 1
Mar 30 09:29:09 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:29:09 yavdr vdr: [1918] Text2Skin: message display update thread started (pid=1685, tid=1918)
Mar 30 09:29:11 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:11 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:11 yavdr vdr: [1918] Text2Skin: message display update thread ended (pid=1685, tid=1918)
Mar 30 09:29:19 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:19 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:20 yavdr kernel: [ 212.512017] usb 9-1: device descriptor read/64, error -110
Mar 30 09:29:20 yavdr vdr: [1685] switching to channel 1
Mar 30 09:29:20 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:29:20 yavdr vdr: [1919] Text2Skin: message display update thread started (pid=1685, tid=1919)
Mar 30 09:29:22 yavdr vdr: [1919] Text2Skin: message display update thread ended (pid=1685, tid=1919)
Mar 30 09:29:27 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:27 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:31 yavdr vdr: [1685] switching to channel 1
Mar 30 09:29:31 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:29:31 yavdr vdr: [1920] Text2Skin: message display update thread started (pid=1685, tid=1920)
Mar 30 09:29:33 yavdr vdr: [1920] Text2Skin: message display update thread ended (pid=1685, tid=1920)
Mar 30 09:29:35 yavdr kernel: [ 227.792016] usb 9-1: device descriptor read/64, error -110
Mar 30 09:29:35 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:35 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:36 yavdr kernel: [ 228.072514] usb 9-1: new full speed USB device using ohci_hcd and address 4
Mar 30 09:29:41 yavdr kernel: [ 233.092152] usb 9-1: device descriptor read/8, error -110
Mar 30 09:29:42 yavdr vdr: [1685] switching to channel 1
Mar 30 09:29:42 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:29:42 yavdr vdr: [1921] Text2Skin: message display update thread started (pid=1685, tid=1921)
Mar 30 09:29:44 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:44 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:44 yavdr vdr: [1921] Text2Skin: message display update thread ended (pid=1685, tid=1921)
Mar 30 09:29:46 yavdr kernel: [ 238.212895] usb 9-1: device descriptor read/8, error -110
Mar 30 09:29:46 yavdr kernel: [ 238.492016] usb 9-1: new full speed USB device using ohci_hcd and address 5
Mar 30 09:29:51 yavdr kernel: [ 243.512620] usb 9-1: device descriptor read/8, error -110
Mar 30 09:29:52 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:29:52 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:29:53 yavdr vdr: [1685] switching to channel 1
Mar 30 09:29:53 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:29:53 yavdr vdr: [1922] Text2Skin: message display update thread started (pid=1685, tid=1922)
Mar 30 09:29:55 yavdr vdr: [1922] Text2Skin: message display update thread ended (pid=1685, tid=1922)
Mar 30 09:29:56 yavdr kernel: [ 248.632359] usb 9-1: device descriptor read/8, error -110
Mar 30 09:29:56 yavdr kernel: [ 248.736026] hub 9-0:1.0: unable to enumerate USB device on port 1
Mar 30 09:29:57 yavdr kernel: [ 249.040015] usb 10-1: new full speed USB device using ohci_hcd and address 2
Mar 30 09:30:00 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:00 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:04 yavdr vdr: [1685] switching to channel 1
Mar 30 09:30:04 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:30:04 yavdr vdr: [1923] Text2Skin: message display update thread started (pid=1685, tid=1923)
Mar 30 09:30:06 yavdr vdr: [1923] Text2Skin: message display update thread ended (pid=1685, tid=1923)
Mar 30 09:30:08 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:08 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:12 yavdr kernel: [ 264.216017] usb 10-1: device descriptor read/64, error -110
Mar 30 09:30:16 yavdr vdr: [1685] switching to channel 1
Mar 30 09:30:16 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:30:16 yavdr vdr: [1924] Text2Skin: message display update thread started (pid=1685, tid=1924)
Mar 30 09:30:16 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:16 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:18 yavdr vdr: [1924] Text2Skin: message display update thread ended (pid=1685, tid=1924)
Mar 30 09:30:25 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:25 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:26 yavdr vdr: [1685] switching to channel 1
Mar 30 09:30:26 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:30:26 yavdr vdr: [1925] Text2Skin: message display update thread started (pid=1685, tid=1925)
Mar 30 09:30:27 yavdr kernel: [ 279.496017] usb 10-1: device descriptor read/64, error -110
Mar 30 09:30:27 yavdr kernel: [ 279.776020] usb 10-1: new full speed USB device using ohci_hcd and address 3
Mar 30 09:30:28 yavdr vdr: [1925] Text2Skin: message display update thread ended (pid=1685, tid=1925)
Mar 30 09:30:33 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:33 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:37 yavdr vdr: [1685] switching to channel 1
Mar 30 09:30:37 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:30:37 yavdr vdr: [1926] Text2Skin: message display update thread started (pid=1685, tid=1926)
Mar 30 09:30:39 yavdr vdr: [1926] Text2Skin: message display update thread ended (pid=1685, tid=1926)
Mar 30 09:30:41 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:41 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:42 yavdr kernel: [ 294.952016] usb 10-1: device descriptor read/64, error -110
Mar 30 09:30:48 yavdr vdr: [1685] switching to channel 1
Mar 30 09:30:48 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:30:48 yavdr vdr: [1927] Text2Skin: message display update thread started (pid=1685, tid=1927)
Mar 30 09:30:49 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:49 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:50 yavdr vdr: [1927] Text2Skin: message display update thread ended (pid=1685, tid=1927)
Mar 30 09:30:57 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:30:57 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:30:58 yavdr kernel: [ 310.232012] usb 10-1: device descriptor read/64, error -110
Mar 30 09:30:58 yavdr kernel: [ 310.512516] usb 10-1: new full speed USB device using ohci_hcd and address 4
Mar 30 09:30:59 yavdr vdr: [1685] switching to channel 1
Mar 30 09:30:59 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:30:59 yavdr vdr: [1928] Text2Skin: message display update thread started (pid=1685, tid=1928)
Mar 30 09:31:01 yavdr vdr: [1928] Text2Skin: message display update thread ended (pid=1685, tid=1928)
Mar 30 09:31:03 yavdr kernel: [ 315.532953] usb 10-1: device descriptor read/8, error -110
Mar 30 09:31:06 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:31:06 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:31:08 yavdr kernel: [ 320.652691] usb 10-1: device descriptor read/8, error -110
Mar 30 09:31:08 yavdr kernel: [ 320.932015] usb 10-1: new full speed USB device using ohci_hcd and address 5
Mar 30 09:31:10 yavdr vdr: [1685] switching to channel 1
Mar 30 09:31:10 yavdr vdr: [1685] info: Kanal nicht verfügbar!
Mar 30 09:31:10 yavdr vdr: [1929] Text2Skin: message display update thread started (pid=1685, tid=1929)
Mar 30 09:31:12 yavdr vdr: [1929] Text2Skin: message display update thread ended (pid=1685, tid=1929)
Mar 30 09:31:13 yavdr kernel: [ 325.952420] usb 10-1: device descriptor read/8, error -110
Mar 30 09:31:14 yavdr vdr-sxfe[1784]: [1805] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 09:31:14 yavdr vdr-sxfe[1784]: [1805] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 09:31:19 yavdr kernel: [ 331.072160] usb 10-1: device descriptor read/8, error -110
Mar 30 09:31:19 yavdr kernel: [ 331.176023] hub 10-0:1.0: unable to enumerate USB device on port 1
Mar 30 09:31:19 yavdr kernel: [ 331.509559] usb 7-4.3: new full speed USB device using ohci_hcd and address 4
Mar 30 09:31:19 yavdr kernel: [ 331.620711] usb 7-4.3: configuration #1 chosen from 1 choice
Mar 30 09:31:19 yavdr kernel: [ 331.630130] input: RAPTOR-GAMING RAPTOR-USB-Keyboard as /devices/pci0000:00/0000:00:04.0/usb7/7-4/7-4.3/7-4.3:1.0/input/input10
Mar 30 09:31:19 yavdr kernel: [ 331.630767] generic-usb 0003:046A:003C.0004: input,hidraw3: USB HID v1.10 Keyboard [RAPTOR-GAMING RAPTOR-USB-Keyboard] on usb-0000:00:04.0-4.3/input0
Wie bereits in diesem thread beschrieben, wenn man den VDR für ca. 30 Sekunden vom Stromnetz trennt, klappt die Erkennung, aber nach einem reboot oder wakeup sieht es aus wie in den logs oben.
Kann ich evtl. etwas am BIOS ändern, dass die USB-Erkennung tangiert?
Es handelt sich um VDR1.
Grüße
EDIT:
Ich habe mal alle USB-devices (inkl. der imon-Einheit) abgeklemmt:
ZitatAlles anzeigen
Mar 30 10:13:09 yavdr dvbmon: Saving number of devices (0) after boot
Mar 30 10:13:09 yavdr dvbmon: vdr started by udev allready
Mar 30 10:13:09 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:09 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:13:16 yavdr kernel: [ 46.720531] usb 3-1: device descriptor read/64, error -110
Mar 30 10:13:17 yavdr vdr: [1889] Text2Skin: message display update thread ended (pid=1755, tid=1889)
Mar 30 10:13:17 yavdr vdr: [1857] EPGSearch: timer conflict check finished
Mar 30 10:13:17 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:17 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:13:18 yavdr vdr: [1755] switching to channel 1
Mar 30 10:13:18 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:13:18 yavdr vdr: [1903] Text2Skin: message display update thread started (pid=1755, tid=1903)
Mar 30 10:13:20 yavdr vdr: [1903] Text2Skin: message display update thread ended (pid=1755, tid=1903)
Mar 30 10:13:20 yavdr vdr: [1755] max. latency time 11 seconds
Mar 30 10:13:26 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:26 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:13:29 yavdr vdr: [1755] switching to channel 1
Mar 30 10:13:29 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:13:29 yavdr vdr: [1904] Text2Skin: message display update thread started (pid=1755, tid=1904)
Mar 30 10:13:31 yavdr vdr: [1904] Text2Skin: message display update thread ended (pid=1755, tid=1904)
Mar 30 10:13:31 yavdr kernel: [ 61.936036] usb 3-1: device descriptor read/64, error -110
Mar 30 10:13:31 yavdr kernel: [ 62.152024] usb 3-1: new high speed USB device using ehci_hcd and address 4
Mar 30 10:13:34 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:34 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:13:36 yavdr kernel: [ 67.172133] usb 3-1: device descriptor read/8, error -110
Mar 30 10:13:40 yavdr vdr: [1755] switching to channel 1
Mar 30 10:13:40 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:13:40 yavdr vdr: [1905] Text2Skin: message display update thread started (pid=1755, tid=1905)
Mar 30 10:13:41 yavdr kernel: [ 72.292112] usb 3-1: device descriptor read/8, error -110
Mar 30 10:13:42 yavdr kernel: [ 72.508029] usb 3-1: new high speed USB device using ehci_hcd and address 5
Mar 30 10:13:42 yavdr vdr: [1905] Text2Skin: message display update thread ended (pid=1755, tid=1905)
Mar 30 10:13:42 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:42 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:13:47 yavdr kernel: [ 77.528144] usb 3-1: device descriptor read/8, error -110
Mar 30 10:13:50 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:50 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:13:51 yavdr vdr: [1755] switching to channel 1
Mar 30 10:13:51 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:13:51 yavdr vdr: [1906] Text2Skin: message display update thread started (pid=1755, tid=1906)
Mar 30 10:13:52 yavdr kernel: [ 82.648124] usb 3-1: device descriptor read/8, error -110
Mar 30 10:13:52 yavdr kernel: [ 82.752036] hub 3-0:1.0: unable to enumerate USB device on port 1
Mar 30 10:13:52 yavdr kernel: [ 83.004542] usb 4-1: new high speed USB device using ehci_hcd and address 2
Mar 30 10:13:53 yavdr vdr: [1906] Text2Skin: message display update thread ended (pid=1755, tid=1906)
Mar 30 10:13:58 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:13:58 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:14:02 yavdr vdr: [1755] switching to channel 1
Mar 30 10:14:02 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:14:02 yavdr vdr: [1907] Text2Skin: message display update thread started (pid=1755, tid=1907)
Mar 30 10:14:04 yavdr vdr: [1907] Text2Skin: message display update thread ended (pid=1755, tid=1907)
Mar 30 10:14:07 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:14:07 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:14:07 yavdr kernel: [ 98.116532] usb 4-1: device descriptor read/64, error -110
Mar 30 10:14:13 yavdr vdr: [1755] switching to channel 1
Mar 30 10:14:13 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:14:13 yavdr vdr: [1908] Text2Skin: message display update thread started (pid=1755, tid=1908)
Mar 30 10:14:15 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:14:15 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:14:15 yavdr vdr: [1908] Text2Skin: message display update thread ended (pid=1755, tid=1908)
Mar 30 10:14:22 yavdr kernel: [ 113.332033] usb 4-1: device descriptor read/64, error -110
Mar 30 10:14:23 yavdr kernel: [ 113.548029] usb 4-1: new high speed USB device using ehci_hcd and address 3
Mar 30 10:14:23 yavdr vdr-sxfe[1855]: [1876] [input_vdr] No data in 8 seconds, queuing no signal image
Mar 30 10:14:23 yavdr vdr-sxfe[1855]: [1876] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Mar 30 10:14:24 yavdr vdr: [1755] switching to channel 1
Mar 30 10:14:24 yavdr vdr: [1755] info: Kanal nicht verfügbar!
Mar 30 10:14:24 yavdr vdr: [1909] Text2Skin: message display update thread started (pid=1755, tid=1909)
Daran lag es wohl nicht.
@champain
also das Syslog zum Start und erkennen der S480 sieht ganz anders aus, als Deins. Ist das überhaupt syslog oder nur das user.log? Bzw ein Ausschnitt aus einem viel späteren Teil. Bei Dir ist der VDR ja bereits gestartet.
Syslog:
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.505888] sr 1:0:0:0: Attached scsi generic sg1 type 5
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.524722] sda5 >
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.525496] sd 0:0:0:0: [sda] Attached SCSI disk
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.634853] usb 3-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.636541] usb 3-1: configuration #1 chosen from 1 choice
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.842391] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.842400] EXT4-fs (sda1): write access will be enabled during recovery
Mar 30 08:56:10 vdr-sylvia kernel: [ 1.873526] usb 10-2: new full speed USB device using uhci_hcd and address 2
Mar 30 08:56:10 vdr-sylvia kernel: [ 2.045337] usb 10-2: configuration #1 chosen from 1 choice
Mar 30 08:56:10 vdr-sylvia kernel: [ 2.814756] EXT4-fs (sda1): recovery complete
Mar 30 08:56:10 vdr-sylvia kernel: [ 2.816490] EXT4-fs (sda1): mounted filesystem with ordered data mode
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.153054] udev: starting version 151
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.167778] Adding 6037496k swap on /dev/sda5. Priority:-1 extents:1 across:6037496k
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.327577] Linux agpgart interface v0.103
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.361185] lp: driver loaded but no devices found
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.617726] nvidia: module license 'NVIDIA' taints kernel.
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.617735] Disabling lock debugging due to kernel taint
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.870457] r8169: eth0: link up
Mar 30 08:56:10 vdr-sylvia kernel: [ 12.870472] r8169: eth0: link up
Mar 30 08:56:10 vdr-sylvia statd-pre-start: local-filesystems started
Mar 30 08:56:10 vdr-sylvia rpc.statd[852]: Version 1.1.6 Starting
Mar 30 08:56:10 vdr-sylvia rpc.statd[852]: Flags:
Mar 30 08:56:10 vdr-sylvia init: Failed to open system console: Input/output error
Mar 30 08:56:10 vdr-sylvia cron[877]: (CRON) INFO (pidfile fd = 3)
Mar 30 08:56:10 vdr-sylvia acpid: starting up with proc fs
Mar 30 08:56:10 vdr-sylvia anacron[886]: Anacron 2.3 started on 2011-03-30
Mar 30 08:56:10 vdr-sylvia acpid: 36 rules loaded
Mar 30 08:56:10 vdr-sylvia acpid: waiting for events: event logging is off
Mar 30 08:56:10 vdr-sylvia cron[887]: (CRON) STARTUP (fork ok)
Mar 30 08:56:10 vdr-sylvia cron[887]: (CRON) INFO (Running @reboot jobs)
Mar 30 08:56:11 vdr-sylvia anacron[886]: Normal exit (0 jobs run)
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.034295] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.034309] usb 2-1: firmware: requesting dvb-usb-s660.fw
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.045449] lirc_dev: IR Remote Control driver registered, major 61
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.085736] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.085744] dw2102: start downloading DW210X firmware
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.124086] RPC: Registered udp transport module.
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.124092] RPC: Registered tcp transport module.
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.124097] RPC: Registered tcp NFSv4.1 backchannel transport module.
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.172839] lirc_mceusb: Windows Media Center Edition USB IR Transceiver driver for LIRC 1.90
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.172850] lirc_mceusb: Daniel Melander <lirc@rajidae.se>, Martin Blatter <martin_a_blatter@yahoo.com>, Dan Conti <dconti@acm.wwu.edu>
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.244141] nvidia 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.244161] nvidia 0000:02:00.0: setting latency timer to 64
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.244172] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.244840] NVRM: loading NVIDIA UNIX x86 Kernel Module 270.26 Mon Feb 14 01:29:17 PST 2011
Mar 30 08:56:13 vdr-sylvia dhclient: Listening on LPF/eth0/20:cf:30:90:ae:4b
Mar 30 08:56:13 vdr-sylvia dhclient: Sending on LPF/eth0/20:cf:30:90:ae:4b
Mar 30 08:56:13 vdr-sylvia dhclient: Sending on Socket/fallback
Mar 30 08:56:13 vdr-sylvia dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Mar 30 08:56:13 vdr-sylvia dhclient: DHCPOFFER of 192.168.0.41 from 192.168.0.10
Mar 30 08:56:13 vdr-sylvia dhclient: DHCPREQUEST of 192.168.0.41 on eth0 to 255.255.255.255 port 67
Mar 30 08:56:13 vdr-sylvia dhclient: DHCPACK of 192.168.0.41 from 192.168.0.10
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.276338] HDA Intel 0000:02:00.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.276350] hda_intel: codec_mask forced to 0xf2
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.281559] usb 10-2: reset full speed USB device using uhci_hcd and address 2
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.289551] dvb-usb: found a 'TeVii S660 USB' in warm state.
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.289687] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.290158] DVB: registering new adapter (TeVii S660 USB)
Mar 30 08:56:13 vdr-sylvia kernel: [ 16.298818] HDA Intel 0000:02:00.1: setting latency timer to 64
Alles anzeigen
was meldet denn lspci und dmesg | grep dvb oder dmesg | grep firmware ? Wenn der Fehler beim Kaltstart auftritt? Ich vermute hier wirklich eher ein Hardware Problem/Inkompatibilität. Kannst Du die Karte in einem anderen System probieren? Ansonsten könnte ich Dir nur anbieten die Karte mal für dich zu testen, ob sie bei mir funktioniert.
Hallo Torsten,
der Auszug war schon aus den syslogs, aber nach einem Warmstart.
Ansonsten (nach einem Kaltstart) sieht es aus wie bei Dir, daher nehme ich an, dass die Karte schon funktioniert. Demnächst kann und werde ich das mal in einem anderen System testen um sicher zu gehen.
Danke für das Angebot.
Ich denke auch das Problem liegt irgendwo am Zusammenspiel mit dem Zotac-Board.
Scheint mehr oder weniger ein USB-Problem zu sein. Vielleicht kann man das ja auch BIOS-einstellungstechnisch beeinflussen, aber ich wüsste nicht wie.
Ich habe die Karte jetzt erst mal rausgeschmissen und meine beiden Tevii-S660-Boxen wieder angeschlossen.
Läuft somit schon mal deutlich besser.
Das nächste Ziel ist das Aktivieren von S3 (suspend to ram). Vielleicht merkt sich der VDR dann die USB-Zuordnung der S480.
Komischerweise ist das bei mir im yavdr-frontend gegraut ("nicht verfügbar").
Wie kommt das?
Habe heute erstmals ein yavdr-update gemacht, aber S3 bleibt gegraut.
Hallo Champain,
das ist ganz einfach, Du verwendest nicht den Orginal Kernel und/oder hast zuviel rumgebastelt . Nimm den Orginal Kernel und Du kannst S3 aktivieren, so ist das normalerweise. Die USB Zuordnung kannst Du eigentlich nicht beeinflussen, dass macht der Treiber selbstständig und die Karte wird ja im Grunde nicht als USB Device angesprochen.
Wenn es Dir möglich ist, würde ich Dir eher raten nochmal sauber von vorne zu beginnen. Die Karte läuft ootb mit dem dkms einwandfrei. Es gibt zwar mittlerweile neue Erkenntnisse bezüglich S3 (siehe ersten Topic) wo ich die templates für vdr-exit-1.conf verlinkt habe und es gibt auch einen Speedup Patch für S3 von Pauli8585 (steht auch im ersten Topic). Der ist allerdings nicht im dkms enthalten (zur Zeit).
Bei Pauli behebt der Patch auch das Problem, dass nach dem Wakeup bzw Warmstart die S660 nicht erkannt wird. Da er aber die S660 verwendet denke ich, das das eine andere Baustelle ist, obwohl die S660 technisch die Grundlage der S480 ist. Also wer weiß .
Und wenn das Dein Syslog ist, dann poste bitte das Syslog nicht vom webif sondern von /var/log/syslog ab der gleichen Stelle wie bei mir. Ob kalt oder warmstart ist dabei egal, kannst ja beide posten, oder Du hängst das syslog als datei an, bzw auf pastebin ablegen und hier verlinken. Im Webif bekommst Du die älteren Inhalte nicht angezeigt, den der eigentlich interessante Teil ist schon längst vorbei.
Gruß
Torsten
Edit:
habe gerade nochmal nachgelesen, dass Du den orginal Kernel verwendest. Wenn dann S3 nicht gewählt werden kann fehlt hier irgendwas wodurch acpi nicht funktioniert. Ich vermute auch ein blank installiertes yavdr ohne liplianin macht bei Dir auch kein S3. Also wäre auch wichtig herauszufinden, ob der S3 überhaupt bei deinem Board funktioniert. Dazu gibt es eine ganze Palette an Lösungswegen, die aber hier zu weit führen. Also bleibt eigentlich die "Hausaufgabe" Dein Board erstmal zum S3 ohne irgendwelche Zusatzinstallationen und DVB Modulen zu bewegen. Bei mir z.B. macht auch der Realtek Kernel-Netzwerktreiber ärger, der r8168-dkms hat da Abhilfe gebracht.
Es hilft nicht wenn Du an mehreren Baustellen gleichzeitig beginnst, denn erstmal muß das System ohne S3 laufen, danach mit S3 und dann mit DVB Modulen.
PPS: ACPI Wakeup in acpiwakeup.conf ist eingerichtet?
Hallo,
bzgl ein paar wakeup spezifischen Sachen bei yavdr habe ich einen neuen Thread (yavdr Voreinstellungsfragen / Gedanken) aufgemacht.
Mal schauen ob da Interesse besteht...
@Thorsten73:
Kann sein, dass dich "Igor" bzgl dem Patch nicht richtig interpretiert hat?!
lG Paul
Hallo an alle,
habe seit gestern Problem mit zweitem Tuner.Es wurde die Aufzeichnung abgebrochen und seitdem kein Signal.
Habe mit einem Sat-Kabel beide Tuner getestet.
1 Tuner hat Signal:
Apr 10 11:48:53 ssamy kernel: [ 15.792029] dvb-usb: found a 'TeVii S660 USB' in warm state.
Apr 10 11:48:53 ssamy kernel: [ 15.792100] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Apr 10 11:48:53 ssamy kernel: [ 15.792508] DVB: registering new adapter (TeVii S660 USB)
Apr 10 11:48:53 ssamy kernel: [ 16.037986] dvb-usb: MAC address: 00:18:bd:5c:60:c8
Apr 10 11:48:53 ssamy kernel: [ 16.041607] DS3000 chip version: 0.192 attached.
Apr 10 11:48:53 ssamy kernel: [ 16.041980] dw2102: Attached ds3000+ds2020!
Apr 10 11:48:53 ssamy kernel: [ 16.041982]
Apr 10 11:48:53 ssamy kernel: [ 16.041988] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
Apr 10 11:48:53 ssamy kernel: [ 16.042962] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0c.0/0000:02:00.1/usb3/3-1/input/input8
Apr 10 11:48:53 ssamy kernel: [ 16.043033] dvb-usb: schedule remote query interval to 150 msecs.
Apr 10 11:48:53 ssamy kernel: [ 16.043040] dvb-usb: TeVii S660 USB successfully initialized and connected.
Apr 10 11:48:53 ssamy kernel: [ 16.280042] usb 4-1: new high speed USB device using ehci_hcd and address 3
Apr 10 11:48:53 ssamy kernel: [ 16.413983] usb 4-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
Apr 10 11:48:53 ssamy kernel: [ 16.415514] usb 4-1: configuration #1 chosen from 1 choice
Apr 10 11:48:53 ssamy kernel: [ 16.416172] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Apr 10 11:48:53 ssamy kernel: [ 16.416179] usb 4-1: firmware: requesting dvb-usb-s660.fw
Apr 10 11:48:53 ssamy kernel: [ 16.433789] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Apr 10 11:48:53 ssamy kernel: [ 16.433794] dw2102: start downloading DW210X firmware
Apr 10 11:48:54 ssamy kernel: [ 16.588536] dvb-usb: found a 'TeVii S660 USB' in warm state.
Apr 10 11:48:54 ssamy kernel: [ 16.588605] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Apr 10 11:48:54 ssamy kernel: [ 16.589020] DVB: registering new adapter (TeVii S660 USB)
Apr 10 11:48:54 ssamy kernel: [ 16.839739] dvb-usb: MAC address: 00:18:bd:5c:60:c8
Apr 10 11:48:54 ssamy kernel: [ 16.845176] DS3000 chip version: 0.192 attached.
Apr 10 11:48:54 ssamy kernel: [ 16.847579] dw2102: Attached ds3000+ds2020!
Apr 10 11:48:54 ssamy kernel: [ 16.847583]
Apr 10 11:48:54 ssamy kernel: [ 16.847591] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
Apr 10 11:48:54 ssamy kernel: [ 16.848957] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0c.0/0000:02:00.3/usb4/4-1/input/input9
Apr 10 11:48:54 ssamy kernel: [ 16.849051] dvb-usb: schedule remote query interval to 150 msecs.
Apr 10 11:48:54 ssamy kernel: [ 16.849058] dvb-usb: TeVii S660 USB successfully initialized and connected.
Apr 10 11:48:54 ssamy kernel: [ 17.256124] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
Apr 10 11:48:54 ssamy kernel: [ 17.256140] usb 3-1: firmware: requesting dvb-fe-ds3000.fw
Apr 10 11:48:54 ssamy kernel: [ 17.266893] ds3000_firmware_ondemand: Waiting for firmware upload(2)...
Apr 10 11:48:55 ssamy kernel: [ 17.868002] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
Apr 10 11:48:55 ssamy kernel: [ 17.868029] usb 4-1: firmware: requesting dvb-fe-ds3000.fw
Apr 10 11:48:55 ssamy kernel: [ 17.872446] ds3000_firmware_ondemand: Waiting for firmware upload(2)...
Apr 10 11:48:55 ssamy vdr: [1646] [xine..put] Listening on port 37890
Apr 10 11:48:55 ssamy vdr: [1646] [xine..put] Listening for UDP broadcasts on port 37890
Apr 10 11:48:55 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57141
Apr 10 11:48:55 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:55 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1648]: [1648] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57144
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1658]: [1658] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57148
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1665]: [1665] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57152
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1686]: [1686] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57156
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1693]: [1693] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57159
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1700]: [1700] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57162
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1707]: [1707] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57166
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1714]: [1714] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57169
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1721]: [1721] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:56 ssamy vdr: [1676] [xine..put] Detected video size 1280x720
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57172
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:56 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:56 ssamy vdr-sxfe[1728]: [1728] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:48:57 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57175
Apr 10 11:48:57 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:48:57 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:48:57 ssamy vdr-sxfe[1735]: [1735] [vdr-sxfe] If X server is running, try running "xhost +" in xterm window
Apr 10 11:49:08 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57183
Apr 10 11:49:08 ssamy vdr: [1646] [xine..put] Client connection 0 closed
Apr 10 11:49:08 ssamy vdr: [1646] [xine..put] Closing connection 0
Apr 10 11:49:08 ssamy vdr-sxfe[1771]: [1771] [scrnsaver] Failed to open connection to bus: /bin/dbus-launch terminated abnormally without any error message
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [vdr-fe] Detected 2 CPUs
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [vdr-fe] Enabling FFmpeg multithreaded video decoding
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [input_vdr] Connecting (control) to tcp://127.0.0.1:37890 ...
Apr 10 11:49:09 ssamy vdr: [1646] [xine..put] Client 0 connected: 127.0.0.1:57184
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [input_vdr] Server greeting: VDR-1.7.16 xineliboutput-1.0.90-cvs READY
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [input_vdr] Connected (control) to tcp://127.0.0.1:37890
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [input_vdr] Connecting (data) to pipe:///var/lib/vdr/plugins/xineliboutput/pipes.1258/pipe.0
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [input_vdr] Data stream connected (PIPE)
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [demux_vdr] Using decoder "libmpeg2" for mpeg2 video
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1771] [demux_vdr] Using decoder "FFmpeg" for H.264 video
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1785] [input_vdr] WARNING: xine-engine setting "engine.buffers.video_num_frames":22 is too small for some HD channels
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1787] [console] Keyboard thread terminated
Apr 10 11:49:09 ssamy vdr-sxfe[1771]: [1786] [demux_vdr] PMT changed, resetting demuxer
Alles anzeigen
2 Tuner hat kein Signal:
Apr 10 11:57:21 ssamy kernel: [ 10.293945] Linux agpgart interface v0.103
Apr 10 11:57:21 ssamy kernel: [ 10.739310] nvidia: module license 'NVIDIA' taints kernel.
Apr 10 11:57:21 ssamy kernel: [ 10.739315] Disabling lock debugging due to kernel taint
Apr 10 11:57:21 ssamy kernel: [ 11.296862] EXT4-fs (sda5): mounted filesystem with ordered data mode
Apr 10 11:57:21 ssamy statd-pre-start: local-filesystems started
Apr 10 11:57:22 ssamy kernel: [ 12.618746] i2c i2c-0: nForce2 SMBus adapter at 0x4d00
Apr 10 11:57:22 ssamy kernel: [ 12.618755] ACPI: resource nForce2_smbus [0x4e00-0x4e3f] conflicts with ACPI region SM00 [0x4e00-0x4e3f]
Apr 10 11:57:22 ssamy kernel: [ 12.618759] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Apr 10 11:57:22 ssamy kernel: [ 12.632273] lp: driver loaded but no devices found
Apr 10 11:57:22 ssamy kernel: [ 12.845119] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Apr 10 11:57:22 ssamy kernel: [ 12.855716] cfg80211: Calling CRDA to update world regulatory domain
Apr 10 11:57:23 ssamy kernel: [ 12.946248] RPC: Registered udp transport module.
Apr 10 11:57:23 ssamy kernel: [ 12.946253] RPC: Registered tcp transport module.
Apr 10 11:57:23 ssamy kernel: [ 12.946257] RPC: Registered tcp NFSv4.1 backchannel transport module.
Apr 10 11:57:23 ssamy kernel: [ 12.974663] ACPI: PCI Interrupt Link [LPMU] enabled at IRQ 20
Apr 10 11:57:23 ssamy kernel: [ 12.974675] nvidia 0000:00:03.5: PCI INT B -> Link[LPMU] -> GSI 20 (level, low) -> IRQ 20
Apr 10 11:57:23 ssamy kernel: [ 12.975426] ACPI: PCI Interrupt Link [SGRU] enabled at IRQ 23
Apr 10 11:57:23 ssamy kernel: [ 12.975438] nvidia 0000:03:00.0: PCI INT A -> Link[SGRU] -> GSI 23 (level, low) -> IRQ 23
Apr 10 11:57:23 ssamy kernel: [ 12.975462] vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Apr 10 11:57:23 ssamy kernel: [ 12.976653] NVRM: loading NVIDIA UNIX x86 Kernel Module 270.26 Mon Feb 14 01:29:17 PST 2011
Apr 10 11:57:23 ssamy kernel: [ 13.002813] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Apr 10 11:57:23 ssamy kernel: [ 13.002821] usb 3-1: firmware: requesting dvb-usb-s660.fw
Apr 10 11:57:23 ssamy kernel: [ 13.024613] ACPI: PCI Interrupt Link [LN3A] enabled at IRQ 19
Apr 10 11:57:23 ssamy kernel: [ 13.024623] ath9k 0000:04:00.0: PCI INT A -> Link[LN3A] -> GSI 19 (level, low) -> IRQ 19
Apr 10 11:57:23 ssamy kernel: [ 13.056869] HDA Intel 0000:00:08.0: power state changed by ACPI to D0
Apr 10 11:57:23 ssamy kernel: [ 13.056945] HDA Intel 0000:00:08.0: power state changed by ACPI to D0
Apr 10 11:57:23 ssamy kernel: [ 13.057592] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 22
Apr 10 11:57:23 ssamy kernel: [ 13.057601] HDA Intel 0000:00:08.0: PCI INT A -> Link[LAZA] -> GSI 22 (level, low) -> IRQ 22
Apr 10 11:57:23 ssamy kernel: [ 13.057606] hda_intel: Disable MSI for Nvidia chipset
Apr 10 11:57:23 ssamy kernel: [ 13.074565] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Apr 10 11:57:23 ssamy kernel: [ 13.074570] dw2102: start downloading DW210X firmware
Apr 10 11:57:23 ssamy kernel: [ 13.122729] Registered led device: ath9k-phy0::radio
Apr 10 11:57:23 ssamy kernel: [ 13.122758] Registered led device: ath9k-phy0::assoc
Apr 10 11:57:23 ssamy kernel: [ 13.122785] Registered led device: ath9k-phy0::tx
Apr 10 11:57:23 ssamy kernel: [ 13.122812] Registered led device: ath9k-phy0::rx
Apr 10 11:57:23 ssamy kernel: [ 13.122831] phy0: Atheros AR9285 MAC/BB Rev:2 AR5133 RF Rev:e0: mem=0xf86e0000, irq=19
Apr 10 11:57:23 ssamy kernel: [ 13.163284] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Apr 10 11:57:23 ssamy kernel: [ 13.248023] dvb-usb: found a 'TeVii S660 USB' in warm state.
Apr 10 11:57:23 ssamy kernel: [ 13.248098] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Apr 10 11:57:23 ssamy kernel: [ 13.248522] DVB: registering new adapter (TeVii S660 USB)
Apr 10 11:57:23 ssamy kernel: [ 13.326948] svc: failed to register lockdv1 RPC service (errno 97).
Apr 10 11:57:23 ssamy kernel: [ 13.328331] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Apr 10 11:57:23 ssamy kernel: [ 13.328525] NFSD: starting 90-second grace period
Apr 10 11:57:23 ssamy kernel: [ 13.527409] dvb-usb: MAC address: 00:18:bd:5c:60:c8
Apr 10 11:57:23 ssamy kernel: [ 13.576909] DS3000 chip version: 0.192 attached.
Apr 10 11:57:23 ssamy kernel: [ 13.577282] dw2102: Attached ds3000+ds2020!
Apr 10 11:57:23 ssamy kernel: [ 13.577283]
Apr 10 11:57:23 ssamy kernel: [ 13.577288] DVB: registering adapter 0 frontend 0 (Montage Technology DS3000/TS2020)...
Apr 10 11:57:23 ssamy kernel: [ 13.581645] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0c.0/0000:02:00.1/usb3/3-1/input/input5
Apr 10 11:57:23 ssamy kernel: [ 13.581718] dvb-usb: schedule remote query interval to 150 msecs.
Apr 10 11:57:23 ssamy kernel: [ 13.581723] dvb-usb: TeVii S660 USB successfully initialized and connected.
Apr 10 11:57:23 ssamy kernel: [ 13.581751] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
Apr 10 11:57:23 ssamy kernel: [ 13.581756] usb 4-1: firmware: requesting dvb-usb-s660.fw
Apr 10 11:57:23 ssamy kernel: [ 13.594571] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
Apr 10 11:57:23 ssamy kernel: [ 13.594575] dw2102: start downloading DW210X firmware
Apr 10 11:57:23 ssamy kernel: [ 13.753844] dvb-usb: found a 'TeVii S660 USB' in warm state.
Apr 10 11:57:23 ssamy kernel: [ 13.753918] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Apr 10 11:57:23 ssamy kernel: [ 13.754569] DVB: registering new adapter (TeVii S660 USB)
Apr 10 11:57:24 ssamy kernel: [ 13.969999] hda_codec: ALC662 rev1: BIOS auto-probing.
Apr 10 11:57:24 ssamy kernel: [ 14.085132] dvb-usb: MAC address: 00:18:bd:5c:60:c8
Apr 10 11:57:24 ssamy kernel: [ 14.089178] DS3000 chip version: 0.192 attached.
Apr 10 11:57:24 ssamy kernel: [ 14.089558] dw2102: Attached ds3000+ds2020!
Apr 10 11:57:24 ssamy kernel: [ 14.089561]
Apr 10 11:57:24 ssamy kernel: [ 14.089567] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
Apr 10 11:57:24 ssamy kernel: [ 14.091504] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0c.0/0000:02:00.3/usb4/4-1/input/input6
Apr 10 11:57:24 ssamy kernel: [ 14.091581] dvb-usb: schedule remote query interval to 150 msecs.
Apr 10 11:57:24 ssamy kernel: [ 14.091586] dvb-usb: TeVii S660 USB successfully initialized and connected.
Apr 10 11:57:24 ssamy kernel: [ 14.091617] usbcore: registered new interface driver dw2102
Apr 10 11:57:24 ssamy kernel: [ 14.260140] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:08.0/input/input7
Apr 10 11:57:24 ssamy kernel: [ 14.414718] lirc_dev: IR Remote Control driver registered, major 61
Apr 10 11:57:25 ssamy kernel: [ 15.380030] lirc_serial: auto-detected active low receiver
Apr 10 11:57:25 ssamy kernel: [ 15.380036] lirc_dev: lirc_register_driver: sample_rate: 0
Apr 10 11:57:25 ssamy kernel: [ 15.380137] lirc_serial $Revision: 5.104 $ registered
Apr 10 11:57:25 ssamy vdr: [1491] [xine..put] Listening on address '127.0.0.1' port 37890
Apr 10 11:57:27 ssamy vdr: [1594] [xine..put] Listening on port 37890
Apr 10 11:57:27 ssamy vdr: [1594] [xine..put] Listening for UDP broadcasts on port 37890
Apr 10 11:57:27 ssamy vdr: [1594] [xine..put] Client 0 connected: 127.0.0.1:45999
Apr 10 11:57:27 ssamy vdr: [1594] [xine..put] Client connection 0 closed
Apr 10 11:57:27 ssamy vdr: [1594] [xine..put] Closing connection 0
Apr 10 11:57:27 ssamy vdr-sxfe[1596]: [1596] [scrnsaver] Failed to open connection to bus: /bin/dbus-launch terminated abnormally without any error message
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [vdr-fe] Detected 2 CPUs
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [vdr-fe] Enabling FFmpeg multithreaded video decoding
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [input_vdr] Connecting (control) to tcp://127.0.0.1:37890 ...
Apr 10 11:57:28 ssamy vdr: [1594] [xine..put] Client 0 connected: 127.0.0.1:46003
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [input_vdr] Server greeting: VDR-1.7.16 xineliboutput-1.0.90-cvs READY
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [input_vdr] Connected (control) to tcp://127.0.0.1:37890
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [input_vdr] Connecting (data) to pipe:///var/lib/vdr/plugins/xineliboutput/pipes.1491/pipe.0
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [input_vdr] Data stream connected (PIPE)
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [demux_vdr] Using decoder "libmpeg2" for mpeg2 video
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1596] [demux_vdr] Using decoder "FFmpeg" for H.264 video
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1631] [console] Keyboard thread terminated
Apr 10 11:57:28 ssamy vdr-sxfe[1596]: [1630] [demux_vdr] PMT changed, resetting demuxer
Apr 10 11:57:29 ssamy vdr: [1617] [xine..put] OSD bandwidth: 188692 bytes/s (1474 kbit/s)
Apr 10 11:57:31 ssamy vdr: [1617] [xine..put] OSD bandwidth: 186288 bytes/s (1455 kbit/s)
Apr 10 11:57:32 ssamy vdr: [1617] [xine..put] OSD bandwidth: 186278 bytes/s (1455 kbit/s)
Apr 10 11:57:37 ssamy vdr-sxfe[1596]: [1630] [input_vdr] No data in 8 seconds, queuing no signal image
Apr 10 11:57:37 ssamy vdr-sxfe[1596]: [1630] [input_vdr] using custom "no signal" image /usr/share/libxine1-xvdr/nosignal.mpg
Apr 10 11:57:54 ssamy dvbmon: Saving number of devices (2) after boot
Apr 10 11:57:54 ssamy dvbmon: vdr started by udev allready
Alles anzeigen
Was ist mti dem zweitem Tuner passiert??
gruss
ssamy
Jetzt habe ich unter W 7 die Karte getestet: beide Tuner sind in Ordnung.Beide Signale gleich stark.
Unter yavdr zeigt zweiter Tuner sehr schwaches Signal.
Hat jemand eine Idee?
ssamy
Hallo.
Zitathabe gerade nochmal nachgelesen, dass Du den orginal Kernel verwendest. Wenn dann S3 nicht gewählt werden kann fehlt hier irgendwas wodurch acpi nicht funktioniert. Ich vermute auch ein blank installiertes yavdr ohne liplianin macht bei Dir auch kein S3. Also wäre auch wichtig herauszufinden, ob der S3 überhaupt bei deinem Board funktioniert. Dazu gibt es eine ganze Palette an Lösungswegen, die aber hier zu weit führen. Also bleibt eigentlich die "Hausaufgabe" Dein Board erstmal zum S3 ohne irgendwelche Zusatzinstallationen und DVB Modulen zu bewegen. Bei mir z.B. macht auch der Realtek Kernel-Netzwerktreiber ärger, der r8168-dkms hat da Abhilfe gebracht.
Es hilft nicht wenn Du an mehreren Baustellen gleichzeitig beginnst, denn erstmal muß das System ohne S3 laufen, danach mit S3 und dann mit DVB Modulen.
Das sehe ich ganz genauso. Mit den Tevii S660-Boxen läuft der VDR fast perfekt. Nur kleinere Pröblemchen, aber die gehören (trotz der verwandschaft zur S480) nicht in diesen thread.
ZitatPPS: ACPI Wakeup in acpiwakeup.conf ist eingerichtet?
Ist eingerichtet und das wakeup funktioniert auch. Trotzdem ist der S3 im yavdr-webfrontend gegraut.
[Blockierte Grafik: http://www.jcc-ing.de/no_S3.png]
Wie gesagt alles original yavdr + der dkms-Treiber, aber das gegraute war auch schon vorher.
Ich mache dazu mal nen einen neuen thread auf.
ssamy:
Kann da leider auch nicht weiterhelfen.
Grüße
Hallo.
S3 läuft mittlerweise, aber nicht mit der Tevii S480.
Ich poste jetzt mal die
- syslog nach kaltstart: http://pastebin.com/zK6g7Y0N
und
- lsusb & lspci
jcc@yavdr:~$ lsusb
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 002: ID 15c2:0035 SoundGraph Inc.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 20e8:5820
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 9022:d660
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 9022:d660
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jcc@yavdr:~$ lspci
00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b2)
00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.4 RAM memory: nVidia Corporation Device 0a98 (rev b1)
00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)
00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1)
00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
00:0b.0 IDE interface: nVidia Corporation MCP79 SATA Controller (rev b1)
00:0c.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:10.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:16.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:17.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:18.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
02:00.0 USB Controller: NetMos Technology Device 9990
02:00.1 USB Controller: NetMos Technology Device 9990
02:00.2 USB Controller: NetMos Technology Device 9990
02:00.3 USB Controller: NetMos Technology Device 9990
02:00.4 USB Controller: NetMos Technology Device 9990
02:00.5 USB Controller: NetMos Technology Device 9990
02:00.6 USB Controller: NetMos Technology Device 9990
02:00.7 USB Controller: NetMos Technology Device 9990
03:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9300 / nForce 730i] (rev b1)
Alles anzeigen
Wo ist die Tevii?
- dmesg | grep dvb
jcc@yavdr:~$ dmesg | grep dvb
[ 12.162377] dvb-usb: found a 'TeVii S480.1 USB' in cold state, will try to load a firmware
[ 12.162382] usb 3-1: firmware: requesting dvb-usb-s660.fw
[ 12.201441] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 12.364015] dvb-usb: found a 'TeVii S480.1 USB' in warm state.
[ 12.364062] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.364220] dvb-usb: MAC address: cc:cc:cc:cc:cc:cc
[ 12.378368] dvb-usb: no frontend was attached by 'TeVii S480.1 USB'
[ 12.378494] dvb-usb: schedule remote query interval to 150 msecs.
[ 12.378498] dvb-usb: TeVii S480.1 USB successfully initialized and connected.
[ 12.378516] dvb-usb: found a 'TeVii S480.2 USB' in cold state, will try to load a firmware
[ 12.378519] usb 4-1: firmware: requesting dvb-usb-s660.fw
[ 12.381472] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 12.396812] dvb-usb: TeVii S480.1 USB successfully deinitialized and disconnected.
[ 12.536017] dvb-usb: found a 'TeVii S480.2 USB' in warm state.
[ 12.536063] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.536221] dvb-usb: MAC address: e9:e9:e9:e9:e9:e9
[ 12.536605] dvb-usb: no frontend was attached by 'TeVii S480.2 USB'
[ 12.536695] dvb-usb: schedule remote query interval to 150 msecs.
[ 12.536698] dvb-usb: TeVii S480.2 USB successfully initialized and connected.
[ 12.556880] dvb-usb: TeVii S480.2 USB successfully deinitialized and disconnected.
[ 14.155916] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 14.155921] usb 3-1: firmware: requesting dvb-usb-s660.fw
[ 14.158977] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 14.312521] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 14.312574] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 14.568350] dvb-usb: MAC address: 00:18:bd:5c:60:c8
[ 14.573094] dvb-usb: schedule remote query interval to 150 msecs.
[ 14.573098] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 14.947168] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 14.947172] usb 4-1: firmware: requesting dvb-usb-s660.fw
[ 14.950185] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 15.104018] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 15.104068] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 15.342819] dvb-usb: MAC address: 00:18:bd:5c:60:c8
[ 15.347555] dvb-usb: schedule remote query interval to 150 msecs.
[ 15.347559] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 44.877250] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 44.897319] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 44.946466] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 44.946472] usb 3-1: firmware: requesting dvb-usb-s660.fw
[ 44.953239] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 45.104518] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 45.104564] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 45.362487] dvb-usb: MAC address: 00:18:bd:5c:60:c8
[ 45.367349] dvb-usb: schedule remote query interval to 150 msecs.
[ 45.367352] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 45.367369] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 45.367373] usb 4-1: firmware: requesting dvb-usb-s660.fw
[ 45.375017] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 45.528026] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 45.528075] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 45.769335] dvb-usb: MAC address: 00:18:bd:5c:60:c8
[ 45.774450] dvb-usb: schedule remote query interval to 150 msecs.
[ 45.774454] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 75.784456] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 75.784462] usb 3-1: firmware: requesting dvb-fe-ds3000.fw
[ 76.403999] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 76.404010] usb 4-1: firmware: requesting dvb-fe-ds3000.fw
jcc@yavdr:~$
Alles anzeigen
- dmesg | grep firmware
jcc@yavdr:~$ dmesg | grep firmware
[ 12.162377] dvb-usb: found a 'TeVii S480.1 USB' in cold state, will try to load a firmware
[ 12.162382] usb 3-1: firmware: requesting dvb-usb-s660.fw
[ 12.201441] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 12.201445] dw2102: start downloading DW210X firmware
[ 12.378516] dvb-usb: found a 'TeVii S480.2 USB' in cold state, will try to load a firmware
[ 12.378519] usb 4-1: firmware: requesting dvb-usb-s660.fw
[ 12.381472] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 12.381475] dw2102: start downloading DW210X firmware
[ 14.155916] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 14.155921] usb 3-1: firmware: requesting dvb-usb-s660.fw
[ 14.158977] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 14.158980] dw2102: start downloading DW210X firmware
[ 14.947168] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 14.947172] usb 4-1: firmware: requesting dvb-usb-s660.fw
[ 14.950185] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 14.950188] dw2102: start downloading DW210X firmware
[ 44.946466] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 44.946472] usb 3-1: firmware: requesting dvb-usb-s660.fw
[ 44.953239] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 44.953242] dw2102: start downloading DW210X firmware
[ 45.367369] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 45.367373] usb 4-1: firmware: requesting dvb-usb-s660.fw
[ 45.375017] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw'
[ 45.375020] dw2102: start downloading DW210X firmware
[ 75.784456] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 75.784462] usb 3-1: firmware: requesting dvb-fe-ds3000.fw
[ 75.786881] ds3000_firmware_ondemand: Waiting for firmware upload(2)...
[ 76.403999] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)...
[ 76.404010] usb 4-1: firmware: requesting dvb-fe-ds3000.fw
[ 76.406329] ds3000_firmware_ondemand: Waiting for firmware upload(2)...
jcc@yavdr:~$
Alles anzeigen
Komisch, weil dvb-fe-ds3000.fw in /lib/firmware liegt und weil es ja läuft.
Wie gesagt, das sind die logs des FUNKTIONIERENDEN Systems (nach Kaltstart).
Könnt ihr mal vergleichen, wie das bei euch aussieht?
Grüße
@champpain:
Hast du bzgl. S3 den (teilweise von mir geschriebenen) Patch ausprobiert, welcher "mittlerweile" im ersten Beitrag dieses Threads erwähnt wird?!
P.S.: Keine Gewährleistung
lG
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!