Bug#653136: vdradmin-am: Record commands (RecCMD) broken using vdr 1.7.22
Package: vdradmin-am
Version: 3.6.9-1
Severity: normal
Tags: patch
Hello maintainer and developer
Execution of the record commands especially 'vdrconvert' is broken using vdr
1.7.22 and above. I localized the problem in the 'recRunCmd' sub. The
additional length information was not processed correctly. Please find below
the patch to solve the problem. The code was adapted from other subs within the
script where the length info was already handled correctly.
Patch to solve the problem:
diff /usr/bin/vdradmind /tmp/vdradmin-am-3.6.9/vdradmind.pl
6441,6445c6441
if ($FEATURES{VDRVERSION} 10721) {
($rec_id, $date, $time, $title) = split(/ +/, $_, 4);
} else {
($rec_id, $date, $time, undef, $title) = split(/ +/, $_, 5);
}
---
($rec_id, $date, $time, $title) = split(/ +/, $_, 4);
-- System Information:
Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-2-686-pae (SMP w/3 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages vdradmin-am depends on:
ii adduser3.112+nmu2add and remove users and groups
ii libio-socket-inet6-per 2.65-1.1 Object interface for AF_INET6 doma
ii liblocale-gettext-perl 1.05-6Using libc functions for internati
ii libsocket6-perl0.23-1Perl extensions for IPv6
ii libtemplate-perl 2.22-0.1 template processing system written
ii libtemplate-plugin-jav 0.01-1Perl module to sanitize text for J
ii liburi-perl1.54-2module to manipulate and access UR
ii libwww-perl5.836-1 Perl HTTP/WWW client/server librar
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii perl [libio-compress-p 5.10.1-17squeeze2 Larry Wall's Practical Extraction
vdradmin-am recommends no packages.
Versions of packages vdradmin-am suggests:
pn libauthen-sasl-perl none (no description available)
ii vdr 1.7.22-1~ctvdr2 Video Disk Recorder for DVB cards
ii vdr-plugin-epgsearch 1.0.0-3 VDR plugin that provides extensive
-- Configuration Files:
/etc/default/vdradmin-am changed [not included]
-- no debconf information
Bug#646765: vdr_1.7.21-1~ctvdr2_i386.deb crashed/restarting with dummydevice
Package: vdr Version: 1.7.21-1~ctvdr2 Severity: grave Justification: renders package unusable Hello After upgrading from vdr 1.7.21-1~ctvdr1 to vdr 1.7.21-1~ctvdr2 the program seems crashing when dummydevice plugin is loaded. As a consequence vdr restarts endlessly. dummydevice plugin information: Package: vdr-plugin-dummydevice Version: 1.0.2-16 Maintainer: Debian VDR Team pkg-vdr-dvb-de...@lists.alioth.debian.org /var/log/user.log Oct 26 23:24:48 iris vdr: [31564] initializing plugin: osdteletext (0.9.1): Displays teletext on the OSD Oct 26 23:24:48 iris vdr: [31564] initializing plugin: dummydevice (1.0.2): Output device that does nothing Oct 26 23:24:48 iris runvdr: restarting VDR Oct 26 23:25:06 iris vdr: [31715] VDR version 1.7.21 started Oct 26 23:25:06 iris vdr: [31715] switched to user 'vdr' Oct 26 23:25:06 iris vdr: [31715] codeset is 'ISO-8859-1' - known Oct 26 23:25:06 iris vdr: [31715] found 28 locales in /usr/share/locale Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-vdrrip.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-control.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-osdteletext.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-dummydevice.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-quickepgsearch.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearchonly.so.1.7.21 Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/setup.conf Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: CutTimePatchEnabled = 0 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: HardLinkCutter = 0 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: MaxRecordingSize = 100 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: MenuCmdPosition = 0 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: ShowProgressBar = 0 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: ShowRecDate = 1 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: ShowRecLength = 0 Oct 26 23:25:06 iris vdr: [31715] ERROR: unknown config parameter: ShowRecTime = 1 Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/sources.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/diseqc.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/channels.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/timers.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/commands.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/reccmds.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/svdrphosts.conf Oct 26 23:25:06 iris vdr: [31715] loading /var/lib/vdr/keymacros.conf Oct 26 23:25:06 iris vdr: [31715] reading EPG data from /var/cache/vdr/epg.data Oct 26 23:25:06 iris vdr: [31717] video directory scanner thread started (pid=31715, tid=31717) Oct 26 23:25:06 iris vdr: [31717] video directory scanner thread ended (pid=31715, tid=31717) Oct 26 23:25:06 iris vdr: [31716] video directory scanner thread started (pid=31715, tid=31716) Oct 26 23:25:06 iris vdr: [31716] video directory scanner thread ended (pid=31715, tid=31716) Oct 26 23:25:06 iris vdr: [31715] registered source parameters for 'A - ATSC' Oct 26 23:25:06 iris vdr: [31715] registered source parameters for 'C - DVB-C' Oct 26 23:25:06 iris vdr: [31715] registered source parameters for 'S - DVB-S' Oct 26 23:25:06 iris vdr: [31715] registered source parameters for 'T - DVB-T' Oct 26 23:25:06 iris vdr: [31715] probing /dev/dvb/adapter0/frontend0 Oct 26 23:25:06 iris vdr: [31715] creating cDvbDevice Oct 26 23:25:06 iris vdr: [31715] new device number 1 Oct 26 23:25:06 iris vdr: [31715] frontend 0/0 provides DVB-S2 with QPSK (STB0899 Multistandard) Oct 26 23:25:06 iris vdr: [31715] probing /dev/dvb/adapter1/frontend0 Oct 26 23:25:06 iris vdr: [31715] creating cDvbDevice Oct 26 23:25:06 iris vdr: [31715] new device number 2 Oct 26 23:25:06 iris vdr: [31715] cTimeMs: using monotonic clock (resolution is 1 ns) Oct 26 23:25:06 iris vdr: [31721] section handler thread started (pid=31715, tid=31721) Oct 26 23:25:06 iris vdr: [31723] CI adapter on device 1 thread started (pid=31715, tid=31723) Oct 26 23:25:06 iris vdr: [31720] tuner on frontend 0/0 thread started (pid=31715, tid=31720) Oct 26 23:25:06 iris vdr: [31715] frontend 1/0 provides DVB-S with QPSK (ST STV0299 DVB-S) Oct 26 23:25:06 iris vdr: [31715] found 2 DVB devices Oct 26 23:25:06 iris vdr: [31715] initializing
Bug#616720: linux-image-2.6-xen-amd64: Feature request -- Serial driver serial8250 as module
Hello Ian
I tried without unload the 8250 driver and starting the domU resuted
in an IRQ 4 error.
So what you really need is to inhibit the 8250 driver from claiming the
ports/irqs associated with the serial points. I don't think you need to
inhibit the driver loading to do this.
I see /sys/bus/platform/drivers/serial8250/{un,}bind on my systems, so
it's perhaps possible that you can also control this stuff even more
dynamically on a per-port basis too.
Thanks a lot-lot for the hint!
I was indeed able to unbind the driver from the port with the following command:
echo -n serial8250 /sys/bus/platform/drivers/serial8250/unbind
And domU could be started with serial access!
The subject can also be closed.
Cheers
David
Ian.
Bug#616720: linux-image-2.6-xen-amd64: Feature request -- Serial driver serial8250 as module
Hello Bastian Please compile serial driver serial8250 as module instead into the kernel. Please explain why. I would like to provide a DomU serial port access according to the xen-wiki. To have access to the serial port in DomU, we need to prevent Dom0 from taken hold of this piece of hardware add to /etc/hotplug/blacklist the following modules to exclude from being loaded 8250 8250_pnp serial_core domU config: irq = [ 4 ] ioports = [ 3f8-3ff ] to load the modules in domU. I tried without unload the 8250 driver and starting the domU resuted in an IRQ 4 error. Kind regards David
Bug#616720: linux-image-2.6-xen-amd64: Feature request -- Serial driver serial8250 as module
Hello Ben Thank you for your quick reply! Please compile serial driver serial8250 as module instead into the kernel. Serial console support requires the serial driver to be built-in. OK. Has this been changed in Xen 4.0 and kernel 2.6.32? Before squeeze was released, I have been using c't server with xen 3 and kernel 2.6.18 and the driver serial8250 was compiled as module. I would like to provide a DomU serial port access according to the xen-wiki http://wiki.xensource.com/xenwiki/InstallationNotes. Before it worked stable. Do you have an idea what I could try? As far as I am informed, pvusb is currently not working in squeeze. David
