Hi
I have budget card (Hauppauge WinTv NOVA-S Plus) digital satellite
receiver.
Kernel 2.6.16.18
Vdr-1.3.43
I am not getting osd after running vdr.
----I get the follwing messages regarding Hauppauge card during boot:-
Jun 14 19:23:31 localhost kernel: CORE cx88[0]: subsystem: 0070:9202,
board: Hauppauge Nova-S-Plus DVB-S
[card=37,autodetected]
Jun 14 19:23:31 localhost kernel: tveeprom 1-0050: Hauppauge model
92001, rev B1B1, serial# 415502
Jun 14 19:23:32 localhost …
[View More]kernel: cx88[0]: hauppauge eeprom: model=92001
Jun 14 19:23:32 localhost kernel: input: cx88 IR (Hauppauge Nova-S-Plus
as /class/input/input0
Jun 14 19:23:32 localhost kernel: cx88[0]/2: cx2388x based dvb card
Jun 14 19:23:32 localhost kernel: DVB: registering new adapter
(cx88[0]).
Jun 14 19:23:32 localhost kernel: DVB: registering frontend 0 (Conexant
CX24123/CX24109)...
If I run "# vdr -Pxine" I get the fiollwing messages in
/var/log/messages but still there is no OSD (Almost same message for
mplayer)
Jun 14 19:31:47 localhost vdr: [3666] VDR version 1.3.43 started
Jun 14 19:31:47 localhost vdr: [3666] switched to user 'vdr'
Jun 14 19:31:47 localhost vdr: [3666] loading
plugin:/usr/lib/vdr/libvdr-xine.so.1.3.43
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/setup.conf
Jun 14 19:31:47 localhost vdr: [3666] ERROR: unknown config parameter:
InitialChannel = 8
Jun 14 19:31:47 localhost vdr: [3666] ERROR: unknown config parameter:
InitialVolume = 1
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/sources.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/diseqc.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/channels.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/timers.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/commands.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/reccmds.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/svdrphosts.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/remote.conf
Jun 14 19:31:47 localhost vdr: [3666] loading /etc/vdr/keymacros.conf
Jun 14 19:31:47 localhost vdr: [3666] found 1 video device
Jun 14 19:31:47 localhost vdr: [3666] initializing plugin: xine (0.7.6):
Software based playback using xine
Jun 14 19:31:47 localhost vdr: [3666] setting primary device to 2
Jun 14 19:31:47 localhost vdr: [3666] SVDRP listening on port 2001
Jun 14 19:31:47 localhost vdr: [3666] loading
/etc/vdr/themes/sttng-default.theme
Jun 14 19:31:47 localhost vdr: [3666] starting plugin: xine
Jun 14 19:31:47 localhost vdr: [3666] loading
/etc/vdr/themes/sttng-default.theme
Jun 14 19:31:47 localhost vdr: [3666] ERROR: remote control XineRemote
not ready!
Jun 14 19:31:57 localhost vdr: [3666] switching to channel 1
I get follwing messages also regarding dvb during boot up
Jun 14 19:23:29 localhost kernel: Linux video capture interface: v1.00
Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget
dvb'.
Jun 14 19:23:29 localhost kernel: saa7146: register extension
'budget_av'.
Jun 14 19:23:29 localhost kernel: saa7146: register extension 'budget_ci
dvb'.
Jun 14 19:23:29 localhost kernel: saa7146: register extension
'budget_patch dvb'.
Jun 14 19:23:29 localhost kernel: saa7146: register extension 'dvb'
Can any body suggest me what should I do to get VDR OSD.
--Regards
Gulab Chandra Yadava
______________________________________________________________
DISCLAIMER:
This electronic message, and any attachments to this electronic message are
intended for the exclusive use of the addressee(s)named herein and may contain
legally privileged and confidential information. It is the property of Celstream
Technologies Pvt. Ltd. If you are not the intended recipient, you are hereby
strictly notified not to copy, forward, distribute or use this message or any
attachments thereto. If you have received this message in error, please delete
it and all copies thereof from your system and notify the sender at Celstream
Technologies or administrator(a)celstream.com immediately
_______________________________________________________________
[View Less]
Maybe not thr right place to ask for but I do not get the GRAB command
working with latest mercurial drivers.
I have a Nexus-S FF-card. GRAB works with drivers from kernel 2.6.16.
Latest drivers from mercurial repository do not work. To update the
repository I did the following
root@fontina:/usr/src/v4l-dvb# hg pull
root@fontina:/usr/src/v4l-dvb# hg update
root@fontina:/usr/src/v4l-dvb# make
root@fontina:/usr/src/v4l-dvb# make install
modules under /lib/modules/2.6.16 are updated and …
[View More]after rebooting GRAB
does not work anymore ;)
Best regards
Peter
[View Less]
Hi,
I'm in the way of set different vdr clients based on softdevice and
streamdev-client.
Depending on each I have to decide witch softdevice output use.
For example, one client is a debian gnome desktop machine with a pci
express radeon X700.
The output of :
xdpyinfo |grep Video
Returns only XVideo. What is the best way to set that I want? I have
tried to set the xv option but when I start VDR with:
-P"softdevice -vo xv:"
It says me that softdevice is not compiled with xv support.
I …
[View More]have been checked the softdevice Makefile and XV_SUPPORT is set to 1
But I have noticed that when I execute in the softdevice dir the
./configure command with an option related to xv then the config.h and
config.mak don't change. For example if I execute ./config --disable-fb
I see config.h and config.mak updated.
But if I execute ./configure --disable-xv don't update anything. If
after that I execute again only ./configure anything changed again and
it must update to enable all the outputs again.
The other type of client I want set is a non x-window system based. I
have tried it with directfb without luck. The hardware is geoforce mx
4400 or 5500.
I know there is a lot of docs and I have readed a lot of them but I'm
confused about how to set the best output. I know that the fb output is
bad because cpu have a lot of work. At the moment the fb output is the
only way softdevice worked to me.
I understand that xvmc or directfb is the best way but I don't know
exactly how to set up these.
Thanks.
[View Less]
hi
I am new to linux as well as VDR.
I have DVB Hauppauge DVB card. I have installed vdr-1.3.43. and I am
using 2.6.16 kernel
when I run vdr through console I get message
vdr: no primary device found - using first device!
on the same console.
I am not getting any OSD for VDR. and I have also installed xine and
Mplayer as a plugin to VDR.
I give the following command to run the VDR
$ vdr
and I get the following message in /var/log/messages
Jun 5 15:28:40 localhost vdr: [3361] VDR …
[View More]version 1.3.43 started
Jun 5 15:28:40 localhost vdr: [3361] switched to user 'vdr'
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/setup.conf
Jun 5 15:28:40 localhost vdr: [3361] ERROR: unknown config parameter:
InitialChannel = 8
Jun 5 15:28:40 localhost vdr: [3361] ERROR: unknown config parameter:
InitialVolume = 1
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/sources.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/diseqc.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/channels.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/timers.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/commands.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/reccmds.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/svdrphosts.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/remote.conf
Jun 5 15:28:40 localhost vdr: [3361] loading /etc/vdr/keymacros.conf
Jun 5 15:28:40 localhost vdr: [3361] found 1 video device
Jun 5 15:28:40 localhost vdr: [3361] ERROR: invalid primary device
number: 2
Jun 5 15:28:40 localhost vdr: [3361] ERROR: no primary device found -
using first device!
Jun 5 15:28:40 localhost vdr: [3361] setting primary device to 1
Jun 5 15:28:40 localhost vdr: [3361] SVDRP listening on port 2001
Jun 5 15:28:40 localhost vdr: [3361] loading
/etc/vdr/themes/sttng-default.theme
Jun 5 15:28:40 localhost vdr: [3361] loading
/etc/vdr/themes/sttng-default.theme
Jun 5 15:28:40 localhost vdr: [3361] ERROR: no OSD provider available -
using dummy OSD!
Jun 5 15:28:50 localhost vdr: [3361] switching to channel 1
Jun 5 15:28:50 localhost vdr: [3361] ERROR: no OSD provider available -
using dummy OSD!
Jun 5 15:28:52 localhost vdr: [3366] channel 11 (306) event 21:30 'M
-23/06/98 Chan 5454 Program #17' status 4
Jun 5 15:28:52 localhost vdr: [3366] channel 12 (407) event 21:50 'W
-23/06/98 Chan 5455 Program #26' status 4
Jun 5 15:28:53 localhost vdr: [3366] channel 8 (Sky Sports 2) event
22:02 'H -23/06/98 Chan 5451 Program #54' status 4
Jun 5 15:28:53 localhost vdr: [3366] channel 9 (229) event 22:10 'C
-23/06/98 Chan 5452 Program #9' status 4
Jun 5 15:28:53 localhost vdr: [3366] channel 10 (302) event 22:10 'K
-23/06/98 Chan 5453 Program
Can any body help me please
--Thanks and Regards
Gulab Chandra Yadava
______________________________________________________________
DISCLAIMER:
This electronic message, and any attachments to this electronic message are
intended for the exclusive use of the addressee(s)named herein and may contain
legally privileged and confidential information. It is the property of Celstream
Technologies Pvt. Ltd. If you are not the intended recipient, you are hereby
strictly notified not to copy, forward, distribute or use this message or any
attachments thereto. If you have received this message in error, please delete
it and all copies thereof from your system and notify the sender at Celstream
Technologies or administrator(a)celstream.com immediately
_______________________________________________________________
[View Less]
Hi folks,
i'm pleased to announce a new version of my
Ext(ended)Rec(ordings)Menu-plugin. With this version it is possible to
protect recordings in co-work with the PIN-Plugin. The layout was
revised and: it is now possible to select the type of sorting (by name
or by date) for each directory inidividually.
Screenshots and download:
http://martins-kabuff.de/extrecmenu_en.html
Have fun with it!
Greets,
Martin
Hi,
here's the next release of epgsearch that already includes some fixes
for problems
found at vdrportal:
2006-06-05: Version 0.9.17
- dropped support for vdr < 1.3.46 :-(
- changed logic in jumping through menus with user-defined times: you
can now
also access times on next day, if they are less then 20 hours in the
future. Thanks to egal@vdrportal and CKone@vdrportal.
- epgsearch has now its own timer conflict check which can be customized by
setup regarding relevant priorities, …
[View More]the time span to check or the
relevant
conflict duration. There is also a conflict manager in Search/Actions that
can be used to resolve conflicts. Many thanks to Mike Constabel for heavy
testing ;-)
- if there is a timer conflicts notification via OSD, you can now press
'Ok' to
go directly to the timer conflicts overview.
- if you like to have a separate main menu entry for the timer conflict
check
use '-P conflictcheckonly' which comes as 'mini'-plugin with epgsearch
and
simply calls epgsearch's conflict menu. conflictcheckonly has a setup
option
to display an info about the last conflict check directly in its main menu
entry.
- setup is now completely restructured and has now something like an
'online'
help.
- menu 'switch timers' now also displays the channel number
- input logic for extended EPG categories changed to allow multiple values.
- added script 'timercmds-auxinfo.sh' that displays the aux info (e.g. the
search timer responsible for the timer) in VDR's timer menu (requires the
timercmd patch), thanks to the author Mike Constabel
- user-defined EPG times with empty description get now their associated
time
as description, suggested by Bafan@vdrportal
- new service interface "Epgsearch-conflictmenu-v1.0" to call epgsearch's
conflict menu from other plugins.
- new service interface "Epgsearch-lastconflictinfo-v1.0" to get an info
about
the last conflict check result.
- epgsearchmenu.conf is not more reloaded with every plugin call, since
this is
only useful when testing the conf file. To activate the permanent
reload again, pass the new start parameter '-r' or '--reloadmenuconf' in
your runvdr
- thanks to Rolf Ahrenberg for finnish translation update
- added HISTORY.DE (german HISTORY)
fixes:
- loading epgsearchmenu.conf now falls back to menu defaults, if the
conf file
contains any errors.
- fixed handling of '%' in LSTS in SVDRP for vdr > 1.3.44, thanks to Mike
Constabel
- fixed loading epgsearchmenu.conf for epgsearchonly and service interface
"Epgsearch-searchmenu-v1.0", thanks to Daniel Dorau for reporting.
- fixed display update in menu 'Search templates', thanks to Mike Constabel
- fixed a bug when deleting associated timers of a search timer when there
are no timers present, thanks to Patrick Koppen for reporting.
- hopefully fixed a bug when adding a search entry to templates, thanks to
Patrick Koppen for reporting.
2006-06-06: Version 0.9.17a
fixes:
- menu 'timer conflicts' automatically returned if there where periodic
timers, thanks to lostinspc@vdrportal
- fixed some compiling problems with gcc-2.95 and gcc-4.1.0, thanks to
ferdi03@vdrportal, smudo81@vdrportal, toxic-tonic@vdrportal
2006-06-10: Version 0.9.17b
fixes:
- fixed some problems with repeating timers in timer conflict check,
thanks to
Peter Juenger for reporting
- fixed a crash in timer conflict check when there was an active
recording on
a device provided by a plugin (e.g. pvr, streamdev), thanks to Gerhard
Steiner for reporting.
http://people.freenet.de/cwieninger/html/vdr-epg-search__english_.html
wget: http://people.freenet.de/cwieninger/vdr-epgsearch-0.9.17b.tgz
BR,
Christian
[View Less]
Hi all,
a new release (0.4.0) of the Mailbox-plugin is available at
<http://sites.inka.de/~seca/vdr/>
Changes since version 0.3.0:
2006-05-20: Version 0.4.0-pre1
- Developed and tested with vdr-1.4.0 with Gentoo-Linux/gcc-3.4.6
- Adopted changes to the Makefile as required since vdr-1.3.47
- Added a service-call "MailBox-HasNewMail-1.0" to allow other plugins
to query if there is at least one new mail present.
This call doesn't query the mail accounts at the mail server, …
[View More]instead
it simply returns the currently known status for those accounts which
have enabled the periodic check.
There will be a patch for the Elchi-skin to use this call to
(optionally) display a mail icon in the replay and channel info.
- Added a new configuration option to the common settings to setup the
connection timeout. A value of 0 uses the system default. A reasonable
value would be somewhat smaller than the watchdog timeout of vdr
(option -w when starting vdr). The default setting is 0.
- Added new configuration option for every mail account to display an
OSD message when unread mail is present. Pressing OK while the message
is visible opens the mail account.
It isn't necessary any more to use the external mailcmd.sh to simply
display the "new mail in ..." message on the OSD. The feature of the
external mailcmd.sh is still available and may be used for other ways
to signal the arrival of new mail, e.g. switching on some LEDs.
- Added new configuration option for every mail account to display the
number of unseen mails in the main-menu entry of the plugin.
- If necessary the plugin converts the mail (subject & body) using
iconv from the charset used in the mail to the charset used by vdr.
- Mail parts encoded in Base64 are decoded and displayed.
- The Plugin now queries the width and font of the text area to make a
nice word-wrapping (especially when wrapping quoted text). To use this
feature, the skin has to implement the methods
cSkin::GetTextAreaWidth() and cSkin::GetTextAreaFont() as the
standard-skins Classic & ST:TNG and the Elchi-skin currently do.
- The mail account passwords are now stored in an obscured way in the
file accounts.conf.
Note: There is is no real encryption; it is just to make the passwords
difficult to read for humans.
The warning from the README is still valid:
ATTENTION: The account settings are stored in a plain text file in a
directory 'plugins/mailbox' below the directory where vdr stores its
setup files. The file will be created with umask 0x600, therefore
only the user which executes vdr is able to read this file.
If you consider this insecure, don't use this plugin.
- Added a key in the Mailbox-View to refresh a single mailbox.
- Added a new OSD-menu to display the communication log for accounts
which have debugging enabled. The log is reachable in the following
views:
- Mailbox-View
- Configuration of a mail account
- IMAP folder selection view
- Corrected a bug which caused that sometimes the last lines of mails
were missing.
- The background check for new mail is now stopped in the
cPlugin::Stop() method of the plugin (according to the HISTORY of
vdr-1.3.20)
- Added a help-screen to all OSD-menus which displays a generated list
of valid keys/actions. The help-screen is (currently) reachable with
key 0 (if no element is active, which consumes the key 0).
- Actions that aren't supported for the current account type aren't
visible (e.g. setting the flag "/FLAGGED" or "/SEEN" for POP3
accounts)
- Key-handling in the configuration menus is now similar to editing
channels in vdr
- Changed the configuration menus for mail accounts
- several separate options instead of the long mailbox-string
- accounts can now be duplicated
- accounts can be tested directly within the configuration dialog
- reordering of mail accounts is now possible
- Completely restructured the OSD- and key-handling in all OSD menus.
- Corrected a bug when fetching multipart mails.
- More characters are usable for user name, password and account name.
(Thanks to Peter Herold for reporting this one.)
- Use proportial font to display the mail text instead of monospaced
(DisplayMenu()->SetText(..., false))
- When started the Mailbox-View calls Display() before all mail accounts
are checked - otherwise the status-message ("Checking mailbox xxx")
is displayed below the main menu of vdr.
(Thanks to Olaf Henkel for reporting this one.)
2006-06-05: Version 0.4.0-pre2
- Update the color buttons when selecting another mail according
to the status flags.
- Avoid some warnings about missing translations for the keys 0..9
in the help screen.
- The setting of vdr 'OSDMessageTime' is now used as the time to display
the osd message "new mail in ..., open?".
(Suggested by Ronny Kornexl)
- Fixed some issues with gcc 3.2
(Thanks to Stephan Sachse for providing the patch)
2006-06-10: Version 0.4.0-pre3
- Added a remark about the required version of the c-client-library to
the INSTALL file:
Version 2004 of the c-client library is required. The plugin was
developed with version 2004a of the library (contained in
imap-2004a.tar.Z). The current version 2004g may work too, but was not
tested by the author.
- Added option to mail account settings to specify if new mails in the
mail account should influence the state delivered by the internal
service call which could be used e.g. to display a mail icon in replay
and channel info.
- Allow ':' in the hostname of mail accounts.
- Added '-fPIC' to CXXFLAGS in Makefile
(Suggested by Thomas Günther)
- Fixed a bug which was introduced in pre2 which caused the background
thread to display the message "New mail in XXX, open?" after every
check.
(Reported by Thomas Günther)
2006-06-11: Version 0.4.0
- no changes since pre3
Have fun,
Alex
[View Less]