[vdr] how to set up the "OSD device handle"?

To: vdr@linuxtv.org
Subject: [vdr] how to set up the "OSD device handle"?
From: Michael Nausch <michael@nausch.org>
Date: Sun, 12 Jan 2003 23:01:00 +0100
Content-transfer-encoding: quoted-printable
Content-type: text/plain; charset="us-ascii"
Organization: nausch.org
Reply-to: vdr@linuxtv.org
Sender: vdr-bounce@linuxtv.org
User-agent: KMail/1.4.3

HI,

I've tried to set up VDR plugin-version 1.1.21 with the recommended 
dvb-drivers, how it is explaind on Hubertus's page:

 http://home.t-online.de/home/hubertus.sandmann/vdr_installation.htm#dvb

But something went wrong. I think my VDR can't find the TT-DVB-S card (with 
the mpeg2 decoder).

After starting runvdr, in /var/log/messages appears:

Jan 12 22:39:41 vdr kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan 12 22:39:41 vdr kernel: Inspecting /boot/System.map-2.4.19-4GB
Jan 12 22:39:41 vdr kernel: Loaded 14220 symbols from 
/boot/System.map-2.4.19-4GB.
Jan 12 22:39:41 vdr kernel: Symbols match kernel version 2.4.19.
Jan 12 22:39:41 vdr kernel: Loaded 665 symbols from 13 modules.
Jan 12 22:39:41 vdr kernel: usb.c: registered new driver usbdevfs
Jan 12 22:39:41 vdr kernel: usb.c: registered new driver hub
Jan 12 22:39:41 vdr kernel: PCI: Found IRQ 6 for device 00:11.5
Jan 12 22:39:41 vdr kernel: IRQ routing conflict for 00:11.5, have irq 5, want 
irq 6
Jan 12 22:39:41 vdr kernel: PCI: Setting latency timer of device 00:11.5 to 64
Jan 12 22:39:41 vdr kernel: Broadcom 4401 Ethernet Driver bcm4400 ver. 1.0.1 
(08/26/02)
Jan 12 22:39:41 vdr kernel: PCI: Found IRQ 10 for device 00:09.0
Jan 12 22:39:41 vdr kernel: PCI: Sharing IRQ 10 with 00:0f.0
Jan 12 22:39:41 vdr kernel: eth0: Broadcom BCM4401 100Base-T found at mem 
ed800000, IRQ 10, node addr 00e018b05171
Jan 12 22:39:41 vdr kernel: IPv6 v0.8 for NET4.0
Jan 12 22:39:41 vdr kernel: IPv6 over IPv4 tunneling driver
Jan 12 22:39:41 vdr kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan 12 22:39:41 vdr kernel: bcm4400: eth0 NIC Link is Up, 100 Mbps full duplex
Jan 12 22:39:48 vdr kernel: eth0: no IPv6 routers present
Jan 12 22:40:07 vdr kernel: Linux video capture interface: v1.00
Jan 12 22:40:07 vdr kernel: DVB: registering new adapter 
(TT-Budget/WinTV-NOVA-S  PCI).
Jan 12 22:40:07 vdr kernel: PCI: Found IRQ 12 for device 00:0a.0
Jan 12 22:40:07 vdr kernel: PCI: Sharing IRQ 12 with 01:00.0
Jan 12 22:40:07 vdr kernel: DVB: registering frontend 0:0 (stv0299 based (e.g. 
Alps BSRU6 or LG TDQB-S00x))...
Jan 12 22:40:09 vdr kernel: DVB: registering new adapter 
(Siemens/Technotrend/Hauppauge PCI rev1.3).
Jan 12 22:40:09 vdr kernel: PCI: Found IRQ 3 for device 00:0c.0
Jan 12 22:40:09 vdr kernel: DVB: registering frontend 1:0 (Grundig 29504-491, 
(TDA8083 based))...
Jan 12 22:40:10 vdr kernel: DVB: registering new adapter 
(TT-Budget/WinTV-NOVA-S  PCI).
Jan 12 22:40:10 vdr kernel: PCI: Found IRQ 9 for device 00:0e.0
Jan 12 22:40:10 vdr kernel: DVB: registering frontend 2:0 (stv0299 based (e.g. 
Alps BSRU6 or LG TDQB-S00x))...
Jan 12 22:40:11 vdr kernel: DVB: registering new adapter 
(TT-Budget/WinTV-NOVA-S  PCI).
Jan 12 22:40:11 vdr kernel: PCI: Found IRQ 10 for device 00:0f.0
Jan 12 22:40:11 vdr kernel: PCI: Sharing IRQ 10 with 00:09.0
Jan 12 22:40:11 vdr kernel: DVB: registering frontend 3:0 (stv0299 based (e.g. 
Alps BSRU6 or LG TDQB-S00x))...
Jan 12 22:40:14 vdr kernel: DVB: AV7111(1) - firm f0240009, rtsl b0250018, vid 
71010068, app c0012110
Jan 12 22:40:14 vdr kernel: av7110: Warning: you are using the experimental LL 
firmware!
Jan 12 22:40:14 vdr kernel:         Please report problems and success stories 
to kls@cadsoft.de.
Jan 12 22:40:14 vdr kernel:         Don't use this firmware for production, 
don't redistribute it.
Jan 12 22:40:14 vdr kernel:         Get updates from the VDR homepage until 
this firmware is part of
Jan 12 22:40:14 vdr kernel:         the public LinuxDVB CVS!
Jan 12 22:40:14 vdr su: (to vdr) root on /dev/tty1
Jan 12 22:40:14 vdr su: pam_unix2: session started for user vdr, service su 
Jan 12 22:40:15 vdr vdr[883]: VDR version 1.1.21 started
Jan 12 22:40:15 vdr vdr[883]: loading plugin: 
/usr/local/src/VDR/PLUGINS/lib/libvdr-dvd.so.1.1.21
Jan 12 22:40:15 vdr vdr[883]: loading plugin: 
/usr/local/src/VDR/PLUGINS/lib/libvdr-lcdproc.so.1.1.21
Jan 12 22:40:15 vdr vdr[883]: loading plugin: 
/usr/local/src/VDR/PLUGINS/lib/libvdr-prefermenu.so.1.1.21
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/setup.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/sources.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/diseqc.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/channels.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/commands.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/reccmds.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/svdrphosts.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/ca.conf
Jan 12 22:40:15 vdr vdr[883]: loading /usr/local/src/VDRtmp/keymacros.conf
Jan 12 22:40:15 vdr vdr[883]: probing /dev/dvb/adapter0/frontend0
Jan 12 22:40:15 vdr vdr[886]: EIT processing thread started (pid=886) - master
Jan 12 22:40:15 vdr vdr[887]: tuner thread started on device 1 (pid=887)
Jan 12 22:40:16 vdr vdr[883]: probing /dev/dvb/adapter1/frontend0
Jan 12 22:40:16 vdr vdr[889]: EIT processing thread started (pid=889)
Jan 12 22:40:16 vdr vdr[883]: CAM: found 2 CAM slots
Jan 12 22:40:23 vdr vdr[883]: CAM: no CAM detected
Jan 12 22:40:23 vdr vdr[890]: tuner thread started on device 2 (pid=890)
Jan 12 22:40:23 vdr vdr[883]: probing /dev/dvb/adapter2/frontend0
Jan 12 22:40:23 vdr vdr[892]: EIT processing thread started (pid=892)
Jan 12 22:40:23 vdr vdr[893]: tuner thread started on device 3 (pid=893)
Jan 12 22:40:23 vdr vdr[883]: probing /dev/dvb/adapter3/frontend0
Jan 12 22:40:23 vdr vdr[895]: EIT processing thread started (pid=895)
Jan 12 22:40:24 vdr vdr[896]: tuner thread started on device 4 (pid=896)
Jan 12 22:40:24 vdr vdr[883]: found 4 video devices
Jan 12 22:40:24 vdr vdr[883]: reading EPG data from /video/epg.data
Jan 12 22:40:24 vdr vdr[883]: starting plugin: dvd (0.2.0): turn VDR into an 
(almost) full featured DVD player
Jan 12 22:40:24 vdr vdr[883]: starting plugin: lcdproc (0.0.8): LCDproc output
Jan 12 22:40:24 vdr vdr[897]: LCD output thread started (pid=897), display 
size: 4x40
Jan 12 22:40:24 vdr vdr[883]: connection to LCDd at localhost:13666 
established.
Jan 12 22:40:24 vdr vdr[883]: starting plugin: prefermenu (0.4.0): Prefer 
Channel menu
Jan 12 22:40:24 vdr vdr[883]: setting primary device to 1
Jan 12 22:40:24 vdr vdr[883]: SVDRP listening on port 2001
Jan 12 22:40:24 vdr vdr[883]: setting watchdog timer to 30 seconds
Jan 12 22:40:24 vdr vdr[883]: ERROR: illegal OSD device handle (-1)!
Jan 12 22:40:30 vdr vdr[883]: assuming manual start of VDR
Jan 12 22:40:30 vdr vdr[883]: max. latency time 1 seconds

I think something went wrong to access the TT-DVB-S card, but what? Maybe VDR 
doesn't know where to send the OSD-menue.

After starting runvdr the (c) Convergence Media messages appears short on TV 
but then I've a black screen. 

VDR is running, 'cause VDR writes data into /video/epg.data.

Every hint is welcome! 

ttyl,
     BC
-- 
Michael Nausch                Anzinger Str. 20                 85586 Poing
+49-8121-971940 (voice)                              +49-8121-971941 (fax)
http://omni128.de                                       michael@nausch.org


--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.

Follow-Ups:
- [vdr] Re: how to set up the "OSD device handle"?
  - From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>

Prev by Date: [vdr] Re: Announcement:NEWSTRUCT driver snapshot archive
Next by Date: [vdr] Re: two little feature suggestions for VDR
Previous by thread: [vdr] Re: Announcement:NEWSTRUCT driver snapshot archive
Next by thread: [vdr] Re: how to set up the "OSD device handle"?
Index(es):
- Date
- Thread

Home | Main Index | Thread Index