Discussion:
[UNKNOWN CARD] PVR500
(too old to reply)
Jorgen Rosink
2006-09-17 18:32:38 UTC
Permalink
After moving my 18 months old PVR-500 to a new Xen box the second unit
isn't detected anymore, because ivtv loads the PVR-150 driver by
default everything is ok though.

As far as I can remember the second unit always got detected right in
the old box ( Debian 2.6.16 kernel with ivtv0.6 source package), the
only difference is that I'm now using a 2.6.17 kernel and running
ivtv0.7 inside a Xen domU.

Are there some vendor/device IDs lost in cyberspace ?


ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.7.0 (tagged release) loading
ivtv: Linux version: 2.6.17-2-xen-686 SMP mod_unload 686 REGPARM gcc-4.1
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
st0: Block limits 1 - 16777215 bytes.
AC'97 0 analog subsections not ready
intel8x0_measure_ac97_clock: measured 47918 usecs
intel8x0: clocking to 48000
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
tveeprom 0-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 0-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has radio, has no IR remote
ivtv0: This is the second unit of a PVR500
ivtv0: Correcting tveeprom data: no radio present on second unit
Intel 810 + AC97 Audio, version 1.01, 16:10:31 Aug 31 2006
tuner 0-0060: TEA5767 detected.
tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio)
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tda9887 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 0-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv0: Initialized WinTV PVR 500 (unit #2), card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Unknown card: vendor/device: 4444/0016
ivtv1: subsystem vendor/device: 0070/a817
ivtv1: cx23416 based
ivtv1: Defaulting to Hauppauge WinTV PVR-150 card
ivtv1: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv1: card you have to the ivtv-devel mailinglist (www.ivtvdriver.org)
ivtv1: Prefix your subject line with [UNKNOWN CARD].
PCI: Enabling device 0000:00:03.0 (0000 -> 0002)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #1)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
tveeprom 1-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 1-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv1: Encoder revision: 0x02050032
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 1-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv: ==================== END INIT IVTV ====================
Hans Verkuil
2006-09-20 20:26:28 UTC
Permalink
Post by Jorgen Rosink
After moving my 18 months old PVR-500 to a new Xen box the second
unit isn't detected anymore, because ivtv loads the PVR-150 driver by
default everything is ok though.
As far as I can remember the second unit always got detected right in
the old box ( Debian 2.6.16 kernel with ivtv0.6 source package), the
only difference is that I'm now using a 2.6.17 kernel and running
ivtv0.7 inside a Xen domU.
Are there some vendor/device IDs lost in cyberspace ?
Not to my knowledge. It's the first time I see a a817 PCI ID.
Post by Jorgen Rosink
ivtv: ====================== NEXT CARD ======================
ivtv1: Unknown card: vendor/device: 4444/0016
ivtv1: subsystem vendor/device: 0070/a817
ivtv1: cx23416 based
What's the output of lspci -n? Also try it after a cold boot. These PCI
numbers are sometimes unreliable after a simple reboot (although that's
doesn't happen often with Hauppauge boards).

Hans
Jorgen Rosink
2006-09-28 18:25:05 UTC
Permalink
Post by Hans Verkuil
What's the output of lspci -n? Also try it after a cold boot. These PCI
numbers are sometimes unreliable after a simple reboot (although that's
doesn't happen often with Hauppauge boards).
dom0

03:08.0 0400: 4444:0016 (rev 01)
03:09.0 0400: 4444:0016 (rev 01)

domU

00:01.0 0400: 4444:0016 (rev 01)
00:02.0 0400: 4444:0016 (rev 01)

Because the current 2.6.17 Debian kernel doesn't like the stable Xen
package anymore I'm unable to reproduce the situation. Back to 2.6.16
(and ivtv 0.6) everything is fine again, I only noticed the reverse
detection of the tuners (second tuner first), probably something with
the order of the Xen pci redirection.

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.3 (tagged release) loading
ivtv: Linux version: 2.6.16-2-xen-686 SMP 686 gcc-4.0
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
tveeprom 0-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 0-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has radio, has no IR remote
ivtv0: This is the second unit of a PVR500
ivtv0: Correcting tveeprom data: no radio present on second unit
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tda9887 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
st0: Block limits 1 - 16777215 bytes.
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 0-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv0: Initialized WinTV PVR 500 (unit #2), card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
tuner 1-0060: TEA5767 detected.
tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #1)
tuner 1-0060: type set to 62 (Philips TEA5767HN FM Radio)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #1)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
tveeprom 1-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 1-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv1: This is the first unit of a PVR500
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv1: Encoder revision: 0x02050032
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv1: Create encoder radio stream
tuner 1-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv1: Initialized WinTV PVR 500 (unit #1), card #1
ivtv: ==================== END INIT IVTV ====================
Jorgen Rosink
2006-10-02 22:16:59 UTC
Permalink
I'm able to reproduce it again, now with a 2.6.18 kernel (Debian
2.6.18-1-xen-686_2) and the stock ivtv 0.8 drivers.


lspci -n

00:01.0 0400: 4444:0016 (rev 01)
00:02.0 0400: 4444:0016 (rev 01)


ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.0 (tagged release) loading
ivtv: Linux version: 2.6.18-1-xen-686 SMP mod_unload 686 REGPARM gcc-4.1
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Unknown card: vendor/device: 4444/0016
ivtv0: subsystem vendor/device: 0070/f7f7
ivtv0: cx23416 based
ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
ivtv0: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv0: card you have to the ivtv-devel mailinglist (www.ivtvdriver.org)
ivtv0: Prefix your subject line with [UNKNOWN CARD].
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tveeprom 0-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 0-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has radio, has no IR remote
ivtv0: This is the second unit of a PVR500
ivtv0: Correcting tveeprom data: no radio present on second unit
tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 0-0060: TEA5767 detected.
tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio)
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: Encoder revision: 0x02050032
ivtv0: Registered device video0 for encoder MPEG
ivtv0: Registered device video32 for encoder YUV
ivtv0: Registered device vbi0 for encoder VBI
ivtv0: Registered device video24 for encoder PCM audio
tuner 0-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv0: Initialized WinTV PVR 500 (unit #2), card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Unknown card: vendor/device: 4444/0016
ivtv1: subsystem vendor/device: 0070/f7f7
ivtv1: cx23416 based
ivtv1: Defaulting to Hauppauge WinTV PVR-150 card
ivtv1: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv1: card you have to the ivtv-devel mailinglist (www.ivtvdriver.org)
ivtv1: Prefix your subject line with [UNKNOWN CARD].
PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #1)
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
tveeprom 1-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 1-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: Encoder revision: 0x02050032
ivtv1: Registered device video1 for encoder MPEG
ivtv1: Registered device video33 for encoder YUV
ivtv1: Registered device vbi1 for encoder VBI
ivtv1: Registered device video25 for encoder PCM audio
tuner 1-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv: ==================== END INIT IVTV ====================
Jorgen Rosink
2006-10-02 23:21:20 UTC
Permalink
Post by Jorgen Rosink
I'm able to reproduce it again, now with a 2.6.18 kernel (Debian
2.6.18-1-xen-686_2) and the stock ivtv 0.8 drivers.
Forgot to mention that starting a MythTV recording with this
configuration, about 30 lines / second of "ivtv0 warning: Couldn't
find start of buffer within the first 256 bytes" are shown on the
console (and log). The card is actually recording, with good quality,
but my log volume is running out of space ;-).

FYI, Xen warns me in dom0 when the card gets enabled with the following message:

pciback 0000:03:08.0: Driver tried to write to a read-only
configuration space field at offset 0x48, size 2. This may be
harmless, but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtainder from lspci


Twice, also for pciback 0000:03:09.0, id's of both the PVR encoders in
Dom0, they will show up in the log below with different id's as
explained in a previous mail.

The reason why I think I should go for the "This may be harmless"
option, is that the same box runs fine with a 2.6.16 kernel and
ivtv0.6 (2.6.16 log in previous mail).

If you need more info/logs, please let me know.

dmesg:

Linux version 2.6.18-1-xen-686 (Debian 2.6.18-2) (waldi at debian.org)
(gcc version 4.1.2 20060920 (prerelease) (Debian 4.1.1-14)) #1 SMP Fri
Sep 29 20:1
6:11 UTC 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000020800000 (usable)
0MB HIGHMEM available.
520MB LOWMEM available.
On node 0 totalpages: 133120
DMA zone: 133120 pages, LIFO batch:31
ACPI in unprivileged domain disabled
Built 1 zonelists. Total pages: 133120
Kernel command line: root=/dev/sda1 ro swiotlb=force
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 3198.460 MHz processor.
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB enabled:
Aperture: 64 megabytes
Kernel range: 0x00000000c14e1000 - 0x00000000c54e1000
vmalloc area: e1000000-fb7fe000, maxmem 33ffe000
Memory: 437632k/532480k available (1546k kernel code, 86300k reserved,
562k data, 148k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 8001.18 BogoMIPS (lpj=16002361)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebc3f1 00000000 00000000 00000000
00004400 00000000 00000000
CPU: After vendor identify, caps: bfebc3f1 00000000 00000000 00000000
00004400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: bfebc3f1 00000000 00000000 00000080
00004400 00000000 00000000
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 11665k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
pcifront pci-0: Installing PCI frontend
pcifront pci-0: Creating PCI Frontend Bus 0000:00
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1159828027.726:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
blkif_init: reqs=64, pages=704, mmap_vstart=0xc0800000
netfront: Initialising virtual ethernet driver.
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
Registering block device major 8
Freeing unused kernel memory: 148k freed
SCSI subsystem initialized
PCI: Enabling device 0000:00:00.0 (0000 -> 0003)
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Vendor: PLEXTOR Model: CD-R PX-R820T Rev: 1.08
Type: CD-ROM ANSI SCSI revision: 02
target0:0:5: Beginning Domain Validation
target0:0:5: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8)
target0:0:5: Domain Validation skipping write tests
target0:0:5: Ending Domain Validation
Vendor: HP Model: Ultrium 1-SCSI Rev: E22D
Type: Sequential-Access ANSI SCSI revision: 03
target0:0:6: Beginning Domain Validation
target0:0:6: wide asynchronous
target0:0:6: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 15)
target0:0:6: Domain Validation skipping write tests
target0:0:6: Ending Domain Validation
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel at redhat.com
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input0
sr0: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:5:0: Attached scsi CD-ROM sr0
Linux video capture interface: v2.00
sr 0:0:5:0: Attached scsi generic sg0 type 5
scsi 0:0:6:0: Attached scsi generic sg1 type 1
st: Version 20050830, fixed bufsize 32768, s/g segs 256
st 0:0:6:0: Attached scsi tape st0
st0: try direct i/o: yes (alignment 512 B)
st0: Block limits 1 - 16777215 bytes.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.0 (tagged release) loading
ivtv: Linux version: 2.6.18-1-xen-686 SMP mod_unload 686 REGPARM gcc-4.1
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Unknown card: vendor/device: 4444/0016
ivtv0: subsystem vendor/device: 0070/f7f7
ivtv0: cx23416 based
ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
ivtv0: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv0: card you have to the ivtv-devel mailinglist (www.ivtvdriver.org)
ivtv0: Prefix your subject line with [UNKNOWN CARD].
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tveeprom 0-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 0-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has radio, has no IR remote
ivtv0: This is the second unit of a PVR500
ivtv0: Correcting tveeprom data: no radio present on second unit
tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 0-0060: TEA5767 detected.
tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio)
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: Encoder revision: 0x02050032
ivtv0: Registered device video0 for encoder MPEG
ivtv0: Registered device video32 for encoder YUV
ivtv0: Registered device vbi0 for encoder VBI
ivtv0: Registered device video24 for encoder PCM audio
tuner 0-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv0: Initialized WinTV PVR 500 (unit #2), card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Unknown card: vendor/device: 4444/0016
ivtv1: subsystem vendor/device: 0070/f7f7
ivtv1: cx23416 based
ivtv1: Defaulting to Hauppauge WinTV PVR-150 card
ivtv1: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv1: card you have to the ivtv-devel mailinglist (www.ivtvdriver.org)
ivtv1: Prefix your subject line with [UNKNOWN CARD].
PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #1)
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
tveeprom 1-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 1-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
(eeprom 0x74)
tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx
101, type 62)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: Encoder revision: 0x02050032
ivtv1: Registered device video1 for encoder MPEG
ivtv1: Registered device video33 for encoder YUV
ivtv1: Registered device vbi1 for encoder VBI
ivtv1: Registered device video25 for encoder PCM audio
tuner 1-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv: ==================== END INIT IVTV ====================
Adding 131064k swap on /dev/sda2. Priority:-1 extents:1 across:131064k
EXT3 FS on sda1, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
eth0: no IPv6 routers present
st0: MTSETDRVBUFFER only allowed for root.
Hans Verkuil
2006-11-10 13:26:46 UTC
Permalink
It's an reply to a rather old email, but I happen to be working on this,
so I have some more info.
Post by Jorgen Rosink
Post by Jorgen Rosink
I'm able to reproduce it again, now with a 2.6.18 kernel (Debian
2.6.18-1-xen-686_2) and the stock ivtv 0.8 drivers.
Forgot to mention that starting a MythTV recording with this
configuration, about 30 lines / second of "ivtv0 warning: Couldn't
find start of buffer within the first 256 bytes" are shown on the
console (and log). The card is actually recording, with good quality,
but my log volume is running out of space ;-).
FYI, Xen warns me in dom0 when the card gets enabled with the
pciback 0000:03:08.0: Driver tried to write to a read-only
configuration space field at offset 0x48, size 2. This may be
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details
of your device obtainder from lspci
The only candidate that I can think of is that we change a config
setting in the Hauppauge PCI config space. But that's at offset 0x40.
It may or may not be harmless: if you have DMA problems, then this might
be the cause.
Post by Jorgen Rosink
Twice, also for pciback 0000:03:09.0, id's of both the PVR encoders
in Dom0, they will show up in the log below with different id's as
explained in a previous mail.
The reason why I think I should go for the "This may be harmless"
option, is that the same box runs fine with a 2.6.16 kernel and
ivtv0.6 (2.6.16 log in previous mail).
The driver tries to detect which PCI device is the first and second unit
of the PVR500. It does so based on PCI subsystem device ID. If it
misdetects it is harmless, only radio can become a problem but you can
override it with the 'radio' module option.

I'm trying to find a better detection method than using PCI IDs or PCI
slots since Xen apparently can mess that up.

Hans
Post by Jorgen Rosink
If you need more info/logs, please let me know.
Linux version 2.6.18-1-xen-686 (Debian 2.6.18-2) (waldi at debian.org)
(gcc version 4.1.2 20060920 (prerelease) (Debian 4.1.1-14)) #1 SMP
Fri Sep 29 20:1
6:11 UTC 2006
Xen: 0000000000000000 - 0000000020800000 (usable)
0MB HIGHMEM available.
520MB LOWMEM available.
On node 0 totalpages: 133120
DMA zone: 133120 pages, LIFO batch:31
ACPI in unprivileged domain disabled
Built 1 zonelists. Total pages: 133120
Kernel command line: root=/dev/sda1 ro swiotlb=force
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 3198.460 MHz processor.
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Aperture: 64 megabytes
Kernel range: 0x00000000c14e1000 - 0x00000000c54e1000
vmalloc area: e1000000-fb7fe000, maxmem 33ffe000
Memory: 437632k/532480k available (1546k kernel code, 86300k
reserved, 562k data, 148k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor
mode... Ok. Calibrating delay using timer specific routine.. 8001.18
BogoMIPS (lpj=16002361) Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebc3f1 00000000 00000000
00000000 00004400 00000000 00000000
CPU: After vendor identify, caps: bfebc3f1 00000000 00000000 00000000
00004400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: bfebc3f1 00000000 00000000 00000080
00004400 00000000 00000000
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 11665k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
pcifront pci-0: Installing PCI frontend
pcifront pci-0: Creating PCI Frontend Bus 0000:00
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1159828027.726:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
blkif_init: reqs=64, pages=704, mmap_vstart=0xc0800000
netfront: Initialising virtual ethernet driver.
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
Registering block device major 8
Freeing unused kernel memory: 148k freed
SCSI subsystem initialized
PCI: Enabling device 0000:00:00.0 (0000 -> 0003)
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
Vendor: PLEXTOR Model: CD-R PX-R820T Rev: 1.08
Type: CD-ROM ANSI SCSI revision: 02
target0:0:5: Beginning Domain Validation
target0:0:5: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8)
target0:0:5: Domain Validation skipping write tests
target0:0:5: Ending Domain Validation
Vendor: HP Model: Ultrium 1-SCSI Rev: E22D
Type: Sequential-Access ANSI SCSI revision: 03
target0:0:6: Beginning Domain Validation
target0:0:6: wide asynchronous
target0:0:6: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 15)
target0:0:6: Domain Validation skipping write tests
target0:0:6: Ending Domain Validation
dm-devel at redhat.com kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input0
sr0: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:5:0: Attached scsi CD-ROM sr0
Linux video capture interface: v2.00
sr 0:0:5:0: Attached scsi generic sg0 type 5
scsi 0:0:6:0: Attached scsi generic sg1 type 1
st: Version 20050830, fixed bufsize 32768, s/g segs 256
st 0:0:6:0: Attached scsi tape st0
st0: try direct i/o: yes (alignment 512 B)
st0: Block limits 1 - 16777215 bytes.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.0 (tagged release) loading
ivtv: Linux version: 2.6.18-1-xen-686 SMP mod_unload 686 REGPARM
gcc-4.1 ivtv: In case of problems please include the debug info
between ivtv: the START INIT IVTV and END INIT IVTV lines, along
with ivtv: any module options, when mailing the ivtv-users
mailinglist. ivtv0: Unknown card: vendor/device: 4444/0016
ivtv0: subsystem vendor/device: 0070/f7f7
ivtv0: cx23416 based
ivtv0: Defaulting to Hauppauge WinTV PVR-150 card
ivtv0: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv0: card you have to the ivtv-devel mailinglist
(www.ivtvdriver.org) ivtv0: Prefix your subject line with [UNKNOWN
CARD].
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tveeprom 0-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 0-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type
56) tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
PAL(D/D1/K) (eeprom 0x74)
tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio
(idx 101, type 62)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has radio, has no IR remote
ivtv0: This is the second unit of a PVR500
ivtv0: Correcting tveeprom data: no radio present on second unit
tuner 0-0060: TEA5767 detected.
tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Registered device video0 for encoder MPEG
ivtv0: Registered device video32 for encoder YUV
ivtv0: Registered device vbi0 for encoder VBI
ivtv0: Registered device video24 for encoder PCM audio
tuner 0-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME
MK4)) ivtv0: Initialized WinTV PVR 500 (unit #2), card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Unknown card: vendor/device: 4444/0016
ivtv1: subsystem vendor/device: 0070/f7f7
ivtv1: cx23416 based
ivtv1: Defaulting to Hauppauge WinTV PVR-150 card
ivtv1: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
ivtv1: card you have to the ivtv-devel mailinglist
(www.ivtvdriver.org) ivtv1: Prefix your subject line with [UNKNOWN
CARD].
PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
tveeprom 1-0050: Hauppauge model 23559, rev D591, serial# 8228440
tveeprom 1-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type
56) tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
PAL(D/D1/K) (eeprom 0x74)
tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio
(idx 101, type 62)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: Encoder revision: 0x02050032
ivtv1: Registered device video1 for encoder MPEG
ivtv1: Registered device video33 for encoder YUV
ivtv1: Registered device vbi1 for encoder VBI
ivtv1: Registered device video25 for encoder PCM audio
tuner 1-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME
MK4)) ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv: ==================== END INIT IVTV ====================
Adding 131064k swap on /dev/sda2. Priority:-1 extents:1
across:131064k EXT3 FS on sda1, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
eth0: no IPv6 routers present
st0: MTSETDRVBUFFER only allowed for root.
_______________________________________________
ivtv-devel mailing list
ivtv-devel at ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Jorgen Rosink
2006-11-10 14:18:03 UTC
Permalink
Post by Hans Verkuil
It's an reply to a rather old email, but I happen to be working on this,
so I have some more info.
Old, but not forgotten :)
Post by Hans Verkuil
Post by Jorgen Rosink
pciback 0000:03:08.0: Driver tried to write to a read-only
configuration space field at offset 0x48, size 2. This may be
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details
of your device obtainder from lspci
The only candidate that I can think of is that we change a config
setting in the Hauppauge PCI config space. But that's at offset 0x40.
It may or may not be harmless: if you have DMA problems, then this might
be the cause.
For now I didn't see any DMA errors on my box, just detection probs
and the "ivtv0 warning: Couldn't find start of buffer within the first
256 bytes" log flood.
Post by Hans Verkuil
The driver tries to detect which PCI device is the first and second unit
of the PVR500. It does so based on PCI subsystem device ID. If it
misdetects it is harmless, only radio can become a problem but you can
override it with the 'radio' module option.
I'm trying to find a better detection method than using PCI IDs or PCI
slots since Xen apparently can mess that up.
After my first report with 2.6.18 I also tried the beta 3490 & 3508 a
couple of times, didn't see any DMA or detection errors ONLY the "log
flood" so again switch back to 2.6.16 + 0.6. I'll keep on testing when
you release new versions ;-), and I'm happy to test things out with
ivtv & Xen if you want.

Keep up the good work !!!
Hans Verkuil
2006-11-10 14:32:44 UTC
Permalink
Post by Jorgen Rosink
Post by Hans Verkuil
It's an reply to a rather old email, but I happen to be working on
this, so I have some more info.
Old, but not forgotten :)
Post by Hans Verkuil
Post by Jorgen Rosink
pciback 0000:03:08.0: Driver tried to write to a read-only
configuration space field at offset 0x48, size 2. This may be
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with
details of your device obtainder from lspci
The only candidate that I can think of is that we change a config
setting in the Hauppauge PCI config space. But that's at offset
0x40. It may or may not be harmless: if you have DMA problems, then
this might be the cause.
For now I didn't see any DMA errors on my box, just detection probs
and the "ivtv0 warning: Couldn't find start of buffer within the
first 256 bytes" log flood.
Post by Hans Verkuil
The driver tries to detect which PCI device is the first and second
unit of the PVR500. It does so based on PCI subsystem device ID. If
it misdetects it is harmless, only radio can become a problem but
you can override it with the 'radio' module option.
I'm trying to find a better detection method than using PCI IDs or
PCI slots since Xen apparently can mess that up.
After my first report with 2.6.18 I also tried the beta 3490 & 3508 a
couple of times, didn't see any DMA or detection errors ONLY the "log
flood" so again switch back to 2.6.16 + 0.6. I'll keep on testing
when you release new versions ;-), and I'm happy to test things out
with ivtv & Xen if you want.
Well, it would be nice if you could check out the trunk version of ivtv
with 2.6.18 and do a test with that and mail me the results. I am in
particular interested whether you still get the buffer messages (and
please mail me a short sample of them in that case) and the INIT IVTV
messages.

Please note, I advise that you use the trunk only for this test, not for
production. It is still under heavy development.

Thanks,

Hans
Post by Jorgen Rosink
Keep up the good work !!!
_______________________________________________
ivtv-devel mailing list
ivtv-devel at ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Jorgen Rosink
2006-11-10 17:42:19 UTC
Permalink
Post by Hans Verkuil
Well, it would be nice if you could check out the trunk version of ivtv
with 2.6.18 and do a test with that and mail me the results. I am in
particular interested whether you still get the buffer messages (and
please mail me a short sample of them in that case) and the INIT IVTV
messages.
I tried the trunk version this afternoon, the messages are still there
when recording from MythTV, but now with some extra lines I didn't see
before:

--------------------------------------------------------------------------------------------------------------------
Nov 10 16:41:52 hoofddoos kernel: ivtv0 warning: encoder VBI: Couldn't
find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0 warning: encoder VBI: Couldn't
find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0 warning: encoder VBI: Couldn't
find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
Nov 10 16:41:52 hoofddoos kernel: ivtv0: Cause: the application is not
reading fast enough.
Nov 10 16:41:52 hoofddoos kernel: ivtv0 warning: encoder VBI: Couldn't
find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
Nov 10 16:41:52 hoofddoos kernel: ivtv0: Cause: the application is not
reading fast enough.
Nov 10 16:41:52 hoofddoos kernel: ivtv0 warning: encoder VBI: Couldn't
find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
--------------------------------------------------------------------------------------------------------------------

The "All encoder VBI stream buffers are full" are there for about 5
seconds, then the
"Couldn't find start of buffer within the first 256 bytes" is flooding
again till I stop the recording.

You can view the full syslog and resulting mpg (45MB) here:

http://docs.rosink.net/syslog.txt
http://docs.rosink.net/1011_20061110164200.mpg

Perhaps bogus, but I noticed that loading this version of ivtv took
quite some time, normally both encoders are initialized in about 5
secs, now it took more than 15.
It looks like it doesn't detect a PVR500 with two (PVR150) tuners, but
two single PVR150 units not part of a PVR500 as I'm used to see in
previous versions. Part of the new detection methods you talked about
earlier ?

Nov 10 16:36:30 hoofddoos kernel: ivtv: ==================== START
INIT IVTV ====================
Nov 10 16:36:30 hoofddoos kernel: ivtv: version 0.9.0 (development
revision 3541) loading
Nov 10 16:36:30 hoofddoos kernel: ivtv: Linux version:
2.6.18-2-xen-686 SMP mod_unload 686 REGPARM gcc-4.1
Nov 10 16:36:30 hoofddoos kernel: ivtv: In case of problems please
include the debug info between
Nov 10 16:36:30 hoofddoos kernel: ivtv: the START INIT IVTV and END
INIT IVTV lines, along with
Nov 10 16:36:30 hoofddoos kernel: ivtv: any module options, when
mailing the ivtv-users mailinglist.
Nov 10 16:36:30 hoofddoos kernel: ivtv0: Autodetected Hauppauge card
Nov 10 16:36:30 hoofddoos kernel: PCI: Enabling device 0000:00:01.0
(0000 -> 0002)
Nov 10 16:36:30 hoofddoos kernel: ivtv0: loaded v4l-cx2341x-enc.fw
firmware (262144 bytes)
Nov 10 16:36:31 hoofddoos kernel: ivtv0: Encoder revision: 0x02050032
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: Hauppauge model
23559, rev D591, serial# 8228440
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: tuner model is
Philips FQ1216AME MK4 (idx 91, type 56)
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: TV standards
PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: second tuner model
is Philips TEA5768HL FM Radio (idx 101, type 62)
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: audio processor is
CX25843 (idx 37)
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: decoder processor
is CX25843 (idx 30)
Nov 10 16:36:31 hoofddoos kernel: tveeprom 0-0050: has radio, has no IR remote
Nov 10 16:36:31 hoofddoos kernel: ivtv0: Autodetected Hauppauge WinTV PVR-150
Nov 10 16:36:31 hoofddoos kernel: tuner 0-0043: chip found @ 0x86
(ivtv i2c driver #0)
Nov 10 16:36:31 hoofddoos kernel: tda9887 0-0043: tda988[5/6/7] found
@ 0x43 (tuner)
Nov 10 16:36:31 hoofddoos kernel: tuner 0-0060: TEA5767 detected.
Nov 10 16:36:31 hoofddoos kernel: tuner 0-0060: chip found @ 0xc0
(ivtv i2c driver #0)
Nov 10 16:36:31 hoofddoos kernel: tuner 0-0060: type set to 62
(Philips TEA5767HN FM Radio)
Nov 10 16:36:31 hoofddoos kernel: tuner 0-0061: chip found @ 0xc2
(ivtv i2c driver #0)
Nov 10 16:36:31 hoofddoos kernel: cx25840 0-0044: cx25843-23 found @
0x88 (ivtv i2c driver #0)
Nov 10 16:36:41 hoofddoos kernel: cx25840 0-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
Nov 10 16:36:41 hoofddoos kernel: wm8775 0-001b: chip found @ 0x36
(ivtv i2c driver #0)
Nov 10 16:36:42 hoofddoos kernel: ivtv0: Registered device video0 for
encoder MPEG (4 MB)
Nov 10 16:36:42 hoofddoos kernel: ivtv0: Registered device video32 for
encoder YUV (2 MB)
Nov 10 16:36:42 hoofddoos kernel: ivtv0: Registered device vbi0 for
encoder VBI (1 MB)
Nov 10 16:36:42 hoofddoos kernel: ivtv0: Registered device video24 for
encoder PCM audio (1 MB)
Nov 10 16:36:42 hoofddoos kernel: ivtv0: Registered device radio0 for
encoder radio
Nov 10 16:36:42 hoofddoos kernel: tuner 0-0061: type set to 56
(Philips PAL/SECAM multi (FQ1216AME MK4))
Nov 10 16:36:42 hoofddoos kernel: ivtv0: Initialized Hauppauge WinTV
PVR-150, card #0
Nov 10 16:36:42 hoofddoos kernel: ivtv: ====================== NEXT
CARD ======================
Nov 10 16:36:42 hoofddoos kernel: ivtv1: Autodetected Hauppauge card
Nov 10 16:36:42 hoofddoos kernel: PCI: Enabling device 0000:00:02.0
(0000 -> 0002)
Nov 10 16:36:43 hoofddoos kernel: ivtv1: loaded v4l-cx2341x-enc.fw
firmware (262144 bytes)
Nov 10 16:36:43 hoofddoos kernel: ivtv1: Encoder revision: 0x02050032
Nov 10 16:36:43 hoofddoos kernel: tuner 1-0043: chip found @ 0x86
(ivtv i2c driver #1)
Nov 10 16:36:43 hoofddoos kernel: tda9887 1-0043: tda988[5/6/7] found
@ 0x43 (tuner)
Nov 10 16:36:43 hoofddoos kernel: tuner 1-0061: chip found @ 0xc2
(ivtv i2c driver #1)
Nov 10 16:36:43 hoofddoos kernel: cx25840 1-0044: cx25843-23 found @
0x88 (ivtv i2c driver #1)
Nov 10 16:36:53 hoofddoos kernel: cx25840 1-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
Nov 10 16:36:53 hoofddoos kernel: wm8775 1-001b: chip found @ 0x36
(ivtv i2c driver #1)
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: Hauppauge model
23559, rev D591, serial# 8228440
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: tuner model is
Philips FQ1216AME MK4 (idx 91, type 56)
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: TV standards
PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: second tuner model
is Philips TEA5768HL FM Radio (idx 101, type 62)
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: audio processor is
CX25843 (idx 37)
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: decoder processor
is CX25843 (idx 30)
Nov 10 16:36:53 hoofddoos kernel: tveeprom 1-0050: has radio, has no IR remote
Nov 10 16:36:53 hoofddoos kernel: ivtv1: Autodetected Hauppauge WinTV PVR-150
Nov 10 16:36:53 hoofddoos kernel: ivtv1: Registered device video1 for
encoder MPEG (4 MB)
Nov 10 16:36:53 hoofddoos kernel: ivtv1: Registered device video33 for
encoder YUV (2 MB)
Nov 10 16:36:53 hoofddoos kernel: ivtv1: Registered device vbi1 for
encoder VBI (1 MB)
Nov 10 16:36:53 hoofddoos kernel: ivtv1: Registered device video25 for
encoder PCM audio (1 MB)
Nov 10 16:36:53 hoofddoos kernel: ivtv1: Registered device radio1 for
encoder radio
Nov 10 16:36:53 hoofddoos kernel: tuner 1-0061: type set to 56
(Philips PAL/SECAM multi (FQ1216AME MK4))
Nov 10 16:36:54 hoofddoos kernel: ivtv1: Initialized Hauppauge WinTV
PVR-150, card #1
Nov 10 16:36:54 hoofddoos kernel: ivtv: ==================== END
INIT IVTV ====================
Hans Verkuil
2006-11-11 11:13:52 UTC
Permalink
Post by Jorgen Rosink
Post by Hans Verkuil
Well, it would be nice if you could check out the trunk version of
ivtv with 2.6.18 and do a test with that and mail me the results. I
am in particular interested whether you still get the buffer
messages (and please mail me a short sample of them in that case)
and the INIT IVTV messages.
I tried the trunk version this afternoon, the messages are still
there when recording from MythTV, but now with some extra lines I
---------------------------------------------------------------------
----------------------------------------------- Nov 10 16:41:52
hoofddoos kernel: ivtv0 warning: encoder VBI: Couldn't find start of
buffer within the first 256 bytes
Couldn't find start of buffer within the first 256 bytes
Couldn't find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
Nov 10 16:41:52 hoofddoos kernel: ivtv0: Cause: the application is
not reading fast enough.
Couldn't find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
Nov 10 16:41:52 hoofddoos kernel: ivtv0: Cause: the application is
not reading fast enough.
Couldn't find start of buffer within the first 256 bytes
Nov 10 16:41:52 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
---------------------------------------------------------------------
-----------------------------------------------
The "All encoder VBI stream buffers are full" are there for about 5
seconds, then the
"Couldn't find start of buffer within the first 256 bytes" is
flooding again till I stop the recording.
Does this happen only under Xen, or also 'native'? (These 'first 256
bytes' messages, I mean).
Post by Jorgen Rosink
http://docs.rosink.net/syslog.txt
http://docs.rosink.net/1011_20061110164200.mpg
Perhaps bogus, but I noticed that loading this version of ivtv took
quite some time, normally both encoders are initialized in about 5
secs, now it took more than 15.
Not aware of any changes here. Is it under Xen only, or also native?
Looking at the log I see that it takes 10 (!) seconds to load the
cx2584x firmware. It should take about 5 seconds. I wish I could reduce
that, it is by far the slowest part of the driver load.
Post by Jorgen Rosink
It looks like it doesn't detect a PVR500 with two (PVR150) tuners,
but two single PVR150 units not part of a PVR500 as I'm used to see
in previous versions. Part of the new detection methods you talked
about earlier ?
Yes. Although I've improved it a bit so that it shows the card as a
PVR500 at least, even though it cannot detect whether it is the first
or second unit.

Thanks,

Hans
Jorgen Rosink
2006-11-11 20:52:02 UTC
Permalink
Post by Hans Verkuil
Post by Jorgen Rosink
The "All encoder VBI stream buffers are full" are there for about 5
seconds, then the
"Couldn't find start of buffer within the first 256 bytes" is
flooding again till I stop the recording.
Does this happen only under Xen, or also 'native'? (These 'first 256
bytes' messages, I mean).
For now I'm running ivtv inside a Xen virtual machine (aka domU),
that's where these messages appear. The PVR500 is hidden for the Xen
host (dom0) and redirected to the domU where I run MythTV.
FYI, to load the ivtv modules inside a Xen domU I've to give an extra
kernel boot option "swiotlb=force". This eats 64MB of the allocated
memory inside the domU, but memory is cheap these days ;-). Attempts
with lower values, 32 and 16 never succeeded in the past.

Software IO TLB enabled:
Aperture: 64 megabytes
Kernel range: 0x00000000b1526000 - 0x00000000b5526000
vmalloc area: d1000000-fb7fe000, maxmem 43ffe000
Memory: 437504k/532480k available (1511k kernel code, 86388k reserved,
526k data, 148k init, 0k highmem)

I also noticed that after playing with 2.6.18 and 0.8 (plus beta's) I
had to power cycle my computer to load my MythTV domU again. With a
"warm-reboot" the MythTV domU kernel (with the swiotlb option) crashes
hard early in the boot process when enabling swiotlb, power down and
restart solves this.

Again, with 2.6.16 and ivtv0.6 this Xen setup is running great.
Post by Hans Verkuil
Post by Jorgen Rosink
Perhaps bogus, but I noticed that loading this version of ivtv took
quite some time, normally both encoders are initialized in about 5
secs, now it took more than 15.
Not aware of any changes here. Is it under Xen only, or also native?
Looking at the log I see that it takes 10 (!) seconds to load the
cx2584x firmware. It should take about 5 seconds. I wish I could reduce
that, it is by far the slowest part of the driver load.
Well, they're just seconds, I have many of them...
Jorgen Rosink
2006-11-13 02:48:35 UTC
Permalink
Post by Hans Verkuil
Post by Jorgen Rosink
The "All encoder VBI stream buffers are full" are there for about 5
seconds, then the
"Couldn't find start of buffer within the first 256 bytes" is
flooding again till I stop the recording.
Does this happen only under Xen, or also 'native'? (These 'first 256
bytes' messages, I mean).
I've tested 3573 on the same box, _without_ any Xen stuff. The 'first
256 bytes' messages are gone, so that should be a Xen thing. I did
watch some LiveTV for ten minutes, no errors in syslog but picture was
crappy, about 6 frames/sec many artefacts and green stripes. After
exiting LiveTV and go back watching LiveTV MythTV crashed, the syslog
only showed some:

Nov 13 03:45:00 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
Nov 13 03:45:00 hoofddoos kernel: ivtv0: Cause: the application is not
reading fast enough.



Nov 13 01:49:01 hoofddoos kernel: ivtv: ==================== START
INIT IVTV ====================
Nov 13 01:49:01 hoofddoos kernel: ivtv: version 0.9.0 (development
revision 3573) loading
Nov 13 01:49:01 hoofddoos kernel: ivtv: Linux version: 2.6.18-2-686
SMP mod_unload 686 REGPARM gcc-4.1
Nov 13 01:49:01 hoofddoos kernel: ivtv: In case of problems please
include the debug info between
Nov 13 01:49:01 hoofddoos kernel: ivtv: the START INIT IVTV and END
INIT IVTV lines, along with
Nov 13 01:49:01 hoofddoos kernel: ivtv: any module options, when
mailing the ivtv-users mailinglist.
Nov 13 01:49:01 hoofddoos kernel: ivtv0: Autodetected Hauppauge card
(cx23416 based)
Nov 13 01:49:01 hoofddoos kernel: ACPI: PCI Interrupt 0000:03:08.0[A]
-> GSI 21 (level, low) -> IRQ 217
Nov 13 01:49:01 hoofddoos kernel: ivtv0: loaded v4l-cx2341x-enc.fw
firmware (262144 bytes)
Nov 13 01:49:01 hoofddoos kernel: ivtv0: Encoder revision: 0x02050032
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: Hauppauge model
23559, rev D591, serial# 8228440
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: tuner model is
Philips FQ1216AME MK4 (idx 91, type 56)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: TV standards
PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: second tuner model
is Philips TEA5768HL FM Radio (idx 101, type 62)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: audio processor is
CX25843 (idx 37)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: decoder processor
is CX25843 (idx 30)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: has radio, has no IR remote
Nov 13 01:49:01 hoofddoos kernel: ivtv0: Autodetected WinTV PVR 500 (unit #1)
Nov 13 01:49:01 hoofddoos kernel: ivtv0: reopen i2c bus for IR-blaster support
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0043: chip found @ 0x86
(ivtv i2c driver #0)
Nov 13 01:49:02 hoofddoos kernel: tda9887 0-0043: tda988[5/6/7] found
@ 0x43 (tuner)
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0060: TEA5767 detected.
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0060: chip found @ 0xc0
(ivtv i2c driver #0)
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0060: type set to 62
(Philips TEA5767HN FM Radio)
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0061: chip found @ 0xc2
(ivtv i2c driver #0)
Nov 13 01:49:02 hoofddoos kernel: cx25840 0-0044: cx25843-23 found @
0x88 (ivtv i2c driver #0)
Nov 13 01:49:07 hoofddoos kernel: cx25840 0-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
Nov 13 01:49:07 hoofddoos kernel: wm8775 0-001b: chip found @ 0x36
(ivtv i2c driver #0)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device video0 for
encoder MPEG (4 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device video32 for
encoder YUV (2 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device vbi0 for
encoder VBI (1 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device video24 for
encoder PCM audio (1 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device radio0 for
encoder radio
Nov 13 01:49:07 hoofddoos kernel: tuner 0-0061: type set to 56
(Philips PAL/SECAM multi (FQ1216AME MK4))
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Initialized WinTV PVR 500
(unit #1), card #0
Nov 13 01:49:07 hoofddoos kernel: ivtv: ====================== NEXT
CARD ======================
Nov 13 01:49:07 hoofddoos kernel: ivtv1: Autodetected Hauppauge card
(cx23416 based)
Nov 13 01:49:07 hoofddoos kernel: ACPI: PCI Interrupt 0000:03:09.0[A]
-> GSI 22 (level, low) -> IRQ 177
Nov 13 01:49:08 hoofddoos kernel: ivtv1: loaded v4l-cx2341x-enc.fw
firmware (262144 bytes)
Nov 13 01:49:08 hoofddoos kernel: ivtv1: Encoder revision: 0x02050032
Nov 13 01:49:08 hoofddoos kernel: tuner 1-0043: chip found @ 0x86
(ivtv i2c driver #1)
Nov 13 01:49:08 hoofddoos kernel: tda9887 1-0043: tda988[5/6/7] found
@ 0x43 (tuner)
Nov 13 01:49:08 hoofddoos kernel: tuner 1-0061: chip found @ 0xc2
(ivtv i2c driver #1)
Nov 13 01:49:08 hoofddoos kernel: cx25840 1-0044: cx25843-23 found @
0x88 (ivtv i2c driver #1)
Nov 13 01:49:13 hoofddoos kernel: cx25840 1-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
Nov 13 01:49:13 hoofddoos kernel: wm8775 1-001b: chip found @ 0x36
(ivtv i2c driver #1)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: Hauppauge model
23559, rev D591, serial# 8228440
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: tuner model is
Philips FQ1216AME MK4 (idx 91, type 56)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: TV standards
PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: second tuner model
is Philips TEA5768HL FM Radio (idx 101, type 62)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: audio processor is
CX25843 (idx 37)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: decoder processor
is CX25843 (idx 30)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: has radio, has no IR remote
Nov 13 01:49:13 hoofddoos kernel: ivtv1: Correcting tveeprom data: no
radio present on second unit
Nov 13 01:49:13 hoofddoos kernel: ivtv1: Autodetected WinTV PVR 500 (unit #2)
Nov 13 01:49:13 hoofddoos kernel: ivtv1: reopen i2c bus for IR-blaster support
Nov 13 01:49:13 hoofddoos kernel: tuner 1-0043: chip found @ 0x86
(ivtv i2c driver #1)
Nov 13 01:49:13 hoofddoos kernel: tda9887 1-0043: tda988[5/6/7] found
@ 0x43 (tuner)
Nov 13 01:49:13 hoofddoos kernel: tuner 1-0061: chip found @ 0xc2
(ivtv i2c driver #1)
Nov 13 01:49:13 hoofddoos kernel: cx25840 1-0044: cx25843-23 found @
0x88 (ivtv i2c driver #1)
Nov 13 01:49:18 hoofddoos kernel: cx25840 1-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
Nov 13 01:49:19 hoofddoos kernel: wm8775 1-001b: chip found @ 0x36
(ivtv i2c driver #1)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device video1 for
encoder MPEG (4 MB)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device video33 for
encoder YUV (2 MB)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device vbi1 for
encoder VBI (1 MB)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device video25 for
encoder PCM audio (1 MB)
Nov 13 01:49:19 hoofddoos kernel: tuner 1-0061: type set to 56
(Philips PAL/SECAM multi (FQ1216AME MK4))
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Initialized WinTV PVR 500
(unit #2), card #1
Nov 13 01:49:19 hoofddoos kernel: ivtv: ==================== END
INIT IVTV ====================
Hans Verkuil
2006-11-13 07:07:48 UTC
Permalink
Can you also test with the head of the ivtv-0.8 branch? Especially check
if there are no artifacts with this ivtv version. I want to make a ivtv
release at the end of the week, so I want to be sure that this version
at least is working correctly.

Very strange BTW that under Xen the 'first 256 bytes' messages appear.

Hans
Post by Jorgen Rosink
Post by Hans Verkuil
Post by Jorgen Rosink
The "All encoder VBI stream buffers are full" are there for about
5 seconds, then the
"Couldn't find start of buffer within the first 256 bytes" is
flooding again till I stop the recording.
Does this happen only under Xen, or also 'native'? (These 'first
256 bytes' messages, I mean).
I've tested 3573 on the same box, _without_ any Xen stuff. The 'first
256 bytes' messages are gone, so that should be a Xen thing. I did
watch some LiveTV for ten minutes, no errors in syslog but picture
was crappy, about 6 frames/sec many artefacts and green stripes.
After exiting LiveTV and go back watching LiveTV MythTV crashed, the
Nov 13 03:45:00 hoofddoos kernel: ivtv0: All encoder VBI stream
buffers are full. Dropping data.
Nov 13 03:45:00 hoofddoos kernel: ivtv0: Cause: the application is
not reading fast enough.
Nov 13 01:49:01 hoofddoos kernel: ivtv: ==================== START
INIT IVTV ====================
Nov 13 01:49:01 hoofddoos kernel: ivtv: version 0.9.0 (development
revision 3573) loading
Nov 13 01:49:01 hoofddoos kernel: ivtv: Linux version: 2.6.18-2-686
SMP mod_unload 686 REGPARM gcc-4.1
Nov 13 01:49:01 hoofddoos kernel: ivtv: In case of problems please
include the debug info between
Nov 13 01:49:01 hoofddoos kernel: ivtv: the START INIT IVTV and END
INIT IVTV lines, along with
Nov 13 01:49:01 hoofddoos kernel: ivtv: any module options, when
mailing the ivtv-users mailinglist.
Nov 13 01:49:01 hoofddoos kernel: ivtv0: Autodetected Hauppauge card
(cx23416 based)
Nov 13 01:49:01 hoofddoos kernel: ACPI: PCI Interrupt 0000:03:08.0[A]
-> GSI 21 (level, low) -> IRQ 217
Nov 13 01:49:01 hoofddoos kernel: ivtv0: loaded v4l-cx2341x-enc.fw
firmware (262144 bytes)
Nov 13 01:49:01 hoofddoos kernel: ivtv0: Encoder revision: 0x02050032
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: Hauppauge model
23559, rev D591, serial# 8228440
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: tuner model is
Philips FQ1216AME MK4 (idx 91, type 56)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: TV standards
PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: second tuner model
is Philips TEA5768HL FM Radio (idx 101, type 62)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: audio processor is
CX25843 (idx 37)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: decoder processor
is CX25843 (idx 30)
Nov 13 01:49:01 hoofddoos kernel: tveeprom 0-0050: has radio, has no
IR remote Nov 13 01:49:01 hoofddoos kernel: ivtv0: Autodetected WinTV
PVR 500 (unit #1) Nov 13 01:49:01 hoofddoos kernel: ivtv0: reopen i2c
bus for IR-blaster support Nov 13 01:49:02 hoofddoos kernel: tuner
Nov 13 01:49:02 hoofddoos kernel: tda9887 0-0043: tda988[5/6/7] found
@ 0x43 (tuner)
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0060: TEA5767 detected.
(ivtv i2c driver #0)
Nov 13 01:49:02 hoofddoos kernel: tuner 0-0060: type set to 62
(Philips TEA5767HN FM Radio)
(ivtv i2c driver #0)
0x88 (ivtv i2c driver #0)
Nov 13 01:49:07 hoofddoos kernel: cx25840 0-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
(ivtv i2c driver #0)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device video0 for
encoder MPEG (4 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device video32
for encoder YUV (2 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device vbi0 for
encoder VBI (1 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device video24
for encoder PCM audio (1 MB)
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Registered device radio0 for
encoder radio
Nov 13 01:49:07 hoofddoos kernel: tuner 0-0061: type set to 56
(Philips PAL/SECAM multi (FQ1216AME MK4))
Nov 13 01:49:07 hoofddoos kernel: ivtv0: Initialized WinTV PVR 500
(unit #1), card #0
Nov 13 01:49:07 hoofddoos kernel: ivtv: ====================== NEXT
CARD ======================
Nov 13 01:49:07 hoofddoos kernel: ivtv1: Autodetected Hauppauge card
(cx23416 based)
Nov 13 01:49:07 hoofddoos kernel: ACPI: PCI Interrupt 0000:03:09.0[A]
-> GSI 22 (level, low) -> IRQ 177
Nov 13 01:49:08 hoofddoos kernel: ivtv1: loaded v4l-cx2341x-enc.fw
firmware (262144 bytes)
Nov 13 01:49:08 hoofddoos kernel: ivtv1: Encoder revision: 0x02050032
(ivtv i2c driver #1)
Nov 13 01:49:08 hoofddoos kernel: tda9887 1-0043: tda988[5/6/7] found
@ 0x43 (tuner)
(ivtv i2c driver #1)
0x88 (ivtv i2c driver #1)
Nov 13 01:49:13 hoofddoos kernel: cx25840 1-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
(ivtv i2c driver #1)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: Hauppauge model
23559, rev D591, serial# 8228440
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: tuner model is
Philips FQ1216AME MK4 (idx 91, type 56)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: TV standards
PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: second tuner model
is Philips TEA5768HL FM Radio (idx 101, type 62)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: audio processor is
CX25843 (idx 37)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: decoder processor
is CX25843 (idx 30)
Nov 13 01:49:13 hoofddoos kernel: tveeprom 1-0050: has radio, has no
IR remote Nov 13 01:49:13 hoofddoos kernel: ivtv1: Correcting
tveeprom data: no radio present on second unit
Nov 13 01:49:13 hoofddoos kernel: ivtv1: Autodetected WinTV PVR 500
(unit #2) Nov 13 01:49:13 hoofddoos kernel: ivtv1: reopen i2c bus for
Nov 13 01:49:13 hoofddoos kernel: tda9887 1-0043: tda988[5/6/7] found
@ 0x43 (tuner)
(ivtv i2c driver #1)
0x88 (ivtv i2c driver #1)
Nov 13 01:49:18 hoofddoos kernel: cx25840 1-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
(ivtv i2c driver #1)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device video1 for
encoder MPEG (4 MB)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device video33
for encoder YUV (2 MB)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device vbi1 for
encoder VBI (1 MB)
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Registered device video25
for encoder PCM audio (1 MB)
Nov 13 01:49:19 hoofddoos kernel: tuner 1-0061: type set to 56
(Philips PAL/SECAM multi (FQ1216AME MK4))
Nov 13 01:49:19 hoofddoos kernel: ivtv1: Initialized WinTV PVR 500
(unit #2), card #1
Nov 13 01:49:19 hoofddoos kernel: ivtv: ==================== END
INIT IVTV ====================
_______________________________________________
ivtv-devel mailing list
ivtv-devel at ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Jorgen Rosink
2006-11-13 23:51:18 UTC
Permalink
Post by Hans Verkuil
Can you also test with the head of the ivtv-0.8 branch? Especially check
if there are no artifacts with this ivtv version.
My wife already got pissed because she couldn't record "Het Blok" last
sunday while I was playing with ivtv ;-) So I found a bit of extra
time to do some testing.

With _no_ Xen stuff enabled (kernel 2.6.18-686 / debian 2.6.18-5) I'm
experiencing the following picture quality (artifacts and other mpg
noise):

0.8 release -> very bad

branch 0.8.1 (3575) -> best of bads

trunk 0.9 (3573) -> bad

All tested 0.8 versions, including the stable, are unusable here

To be sure my hardware is OK (P4 3,2GHz + Intel 865) I did setup a new
Xen domU with MythTV (2.6.16 and 0.6), my last known working setup,
again this is working perfect (even inside a Xen virtual machine). I'm
able to start mythfrontend on it and watch LiveTV over VNC (insane,
but possible ;-)). Well VNC isn't refreshing fast enough to give a
good picture and is also fighting together with mythfrontend for 100%
CPU utilization.... but ivtv keeps on going and the picture is smooth
and sharp.
Post by Hans Verkuil
I want to make a ivtv release at the end of the week, so I want to be sure that this version
at least is working correctly.
0.6 is the only version that's working for me...
Post by Hans Verkuil
Very strange BTW that under Xen the 'first 256 bytes' messages appear.
I'll try to keep up testing new ivtv versions with Xen.
Hans Verkuil
2006-11-14 19:22:21 UTC
Permalink
Post by Jorgen Rosink
Post by Hans Verkuil
Can you also test with the head of the ivtv-0.8 branch? Especially
check if there are no artifacts with this ivtv version.
My wife already got pissed because she couldn't record "Het Blok"
last sunday while I was playing with ivtv ;-) So I found a bit of
extra time to do some testing.
With _no_ Xen stuff enabled (kernel 2.6.18-686 / debian 2.6.18-5) I'm
experiencing the following picture quality (artifacts and other mpg
0.8 release -> very bad
branch 0.8.1 (3575) -> best of bads
You mean to say that ivtv native is lousy quality, but under Xen on the
same box it is working? I find that hard to believe. Or is ivtv-0.8 bad
in either case?

Can you do the following (native!) test under an 2.6.18.x kernel:

Make sure there are no ivtv, cx25804 or tuner options set
in /etc/modprobe.conf. Use the latest from the 0.8 branch (rev 3577).
Then tune to a channel using ivtv-tune or v4l2-ctl -f <freq>. Capture a
bit using 'cat /dev/videoX >foo.mpg'. Test if the video quality is
still bad. Assuming it is, then I would like to have the full INIT IVTV
messages and a short mpeg that demonstrates what the video looks like.

Thanks,

Hans
Post by Jorgen Rosink
trunk 0.9 (3573) -> bad
All tested 0.8 versions, including the stable, are unusable here
To be sure my hardware is OK (P4 3,2GHz + Intel 865) I did setup a
new Xen domU with MythTV (2.6.16 and 0.6), my last known working
setup, again this is working perfect (even inside a Xen virtual
machine). I'm able to start mythfrontend on it and watch LiveTV over
VNC (insane, but possible ;-)). Well VNC isn't refreshing fast enough
to give a good picture and is also fighting together with
mythfrontend for 100% CPU utilization.... but ivtv keeps on going and
the picture is smooth and sharp.
Post by Hans Verkuil
I want to make a ivtv release at the end of the week, so I want to
be sure that this version at least is working correctly.
0.6 is the only version that's working for me...
Post by Hans Verkuil
Very strange BTW that under Xen the 'first 256 bytes' messages appear.
I'll try to keep up testing new ivtv versions with Xen.
_______________________________________________
ivtv-devel mailing list
ivtv-devel at ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Jorgen Rosink
2006-11-15 02:12:12 UTC
Permalink
Post by Hans Verkuil
Post by Jorgen Rosink
With _no_ Xen stuff enabled (kernel 2.6.18-686 / debian 2.6.18-5) I'm
experiencing the following picture quality (artifacts and other mpg
0.8 release -> very bad
branch 0.8.1 (3575) -> best of bads
You mean to say that ivtv native is lousy quality, but under Xen on the
same box it is working? I find that hard to believe. Or is ivtv-0.8 bad
in either case?
No, the Xen thing is running 0.6 with 2.6.16.

I meant all 0.8 versions are not working for me, but that's not true anymore:

I never tried to output /dev/video directly like you instructed below
, the results from these tests are looking much better than I reported
before from MythTV (always used LiveTV picture as reference).
Post by Hans Verkuil
Make sure there are no ivtv, cx25804 or tuner options set
in /etc/modprobe.conf. Use the latest from the 0.8 branch (rev 3577).
Then tune to a channel using ivtv-tune or v4l2-ctl -f <freq>. Capture a
bit using 'cat /dev/videoX >foo.mpg'. Test if the video quality is
still bad. Assuming it is, then I would like to have the full INIT IVTV
messages and a short mpeg that demonstrates what the video looks like.
* 0.8-tagged
- same picture as viewing LiveTV = both crappy
- http://docs.rosink.net/0.8-tagged.txt
- http://docs.rosink.net/0.8-tagged.mpg (9MB)

* 0.8.1-3577
- with LiveTV still crappy, with cat & MythTV Recordings _good_
picture (just a funny blue dot lower right corner)
- http://docs.rosink.net/0.8.1-3577.txt
- http://docs.rosink.net/0.8.1-3577.mpg (9MB)

So even with cat the 0.8-tagged release gives crappy video, 0.8.1-3577
is producing a good picture. When watching LiveTV running mythfrontend
on the same box with 0.8.1-3577, I still get a crappy picture as seen
in the screenshot below, but 0.8.1-3577 recordings from MythTV are as
clear as the cat output.

Loading Image...

I see a lot of messages from mythfrontend

"NVP prebuffering pause"

"NVP AddAudioData():p1: Audio buffer overflow, audio data lost!

"NVP: Prebuffer wait timed out 10 times"

After 5-10 minutes it dies with

"2006-11-15 02:50:03.398 MPEGRec(/dev/video0) Error: select timeout -
ivtv driver has stopped responding"

No errors from ivtv seen anywhere, perhaps something with my sound
setup, I tried both ALSA and OSS with mythfrontend.
Hans Verkuil
2006-11-15 07:02:46 UTC
Permalink
Post by Jorgen Rosink
Post by Hans Verkuil
Post by Jorgen Rosink
With _no_ Xen stuff enabled (kernel 2.6.18-686 / debian 2.6.18-5)
I'm experiencing the following picture quality (artifacts and
0.8 release -> very bad
branch 0.8.1 (3575) -> best of bads
You mean to say that ivtv native is lousy quality, but under Xen on
the same box it is working? I find that hard to believe. Or is
ivtv-0.8 bad in either case?
No, the Xen thing is running 0.6 with 2.6.16.
I never tried to output /dev/video directly like you instructed below
, the results from these tests are looking much better than I
reported before from MythTV (always used LiveTV picture as
reference).
Post by Hans Verkuil
Make sure there are no ivtv, cx25804 or tuner options set
in /etc/modprobe.conf. Use the latest from the 0.8 branch (rev
3577). Then tune to a channel using ivtv-tune or v4l2-ctl -f
<freq>. Capture a bit using 'cat /dev/videoX >foo.mpg'. Test if the
video quality is still bad. Assuming it is, then I would like to
have the full INIT IVTV messages and a short mpeg that demonstrates
what the video looks like.
* 0.8-tagged
- same picture as viewing LiveTV = both crappy
- http://docs.rosink.net/0.8-tagged.txt
- http://docs.rosink.net/0.8-tagged.mpg (9MB)
Wow, that's really bad. Never seen something like this before.
Post by Jorgen Rosink
* 0.8.1-3577
- with LiveTV still crappy, with cat & MythTV Recordings _good_
picture (just a funny blue dot lower right corner)
- http://docs.rosink.net/0.8.1-3577.txt
- http://docs.rosink.net/0.8.1-3577.mpg (9MB)
So even with cat the 0.8-tagged release gives crappy video,
0.8.1-3577 is producing a good picture. When watching LiveTV running
mythfrontend on the same box with 0.8.1-3577, I still get a crappy
picture as seen in the screenshot below, but 0.8.1-3577 recordings
from MythTV are as clear as the cat output.
http://docs.rosink.net/crappy-livetv-0.8.1-3577.png
I see a lot of messages from mythfrontend
"NVP prebuffering pause"
"NVP AddAudioData():p1: Audio buffer overflow, audio data lost!
"NVP: Prebuffer wait timed out 10 times"
After 5-10 minutes it dies with
"2006-11-15 02:50:03.398 MPEGRec(/dev/video0) Error: select timeout -
ivtv driver has stopped responding"
No errors from ivtv seen anywhere, perhaps something with my sound
setup, I tried both ALSA and OSS with mythfrontend.
Just to be sure: you are using MythTV-0.20 with ivtv-0.8, right?

Assuming it is, then I have two more tests for you:

1) Turn off VBI support in MythTV and test again. (This assumes it is
turned on of course).
2) Test also with the ivtv trunk version (0.9 development version).

Thanks,

Hans
Jorgen Rosink
2006-11-15 21:42:21 UTC
Permalink
Post by Hans Verkuil
Just to be sure: you are using MythTV-0.20 with ivtv-0.8, right?
Yup, I'm using the MythTV packages from Christian Marillat
(www.debian-multimedia.org), version 0.20-0.4.
Post by Hans Verkuil
1) Turn off VBI support in MythTV and test again. (This assumes it is
turned on of course).
Sorry, I can't find the setting. I removed and recreated both devices
from mythtv-setup but still lost...
Post by Hans Verkuil
2) Test also with the ivtv trunk version (0.9 development version).
Will do if I can find that damn VBI setting ;-)

But I have some new news about my previous post...

When watching back the two raw mpg files from my previous post I
noticed that the 0.8-tagged.mpg is in 480x480 (the default MythTV
LiveTV settings). The "good" mpg file, 0.8.1-3577.mpg is in 720x576,
the default state of the device after loading ivtv in PAL mode.
I probably first watched LiveTV when testing 0.8-tagged and after
closing MytvTV I did a cat from the raw device only after setting the
frequency with v4l2-ctl -f. The device must have had the 480x480
settings still loaded from it's previous MythTV task.

To test 0.8.1-3577 I had to restart my computer and directly captured
the 0.8.1-3577.mpg test file from the raw device (in default PAL
720x576 mode), so without starting MythTV first.
If I change the default MythTV LiveTV recording profile from 480x480
to 720x576 I'm able to watch LiveTV from mythfrontend on the same box
with 0.8.1-3577, something I couldn't do in my previous 0.8-anything
reports. Also the prebuffering and audio errors are gone, so it looks
like ivtv and MythTV don't like each other in 480x480 and perhaps
other non-default resolutions. I'm able to reproduce the choppy video
by switching LiveTV recording profile from 480x480 to 720x576 and back
with 0.8.1-3577. I didn't test 0.8-tagged in 720x576 mode yet, but I
believe it will also function OK when running in 720x576.

I'm happy to do some more testing if you want.
Hans Verkuil
2006-11-15 22:05:47 UTC
Permalink
Post by Jorgen Rosink
Post by Hans Verkuil
Just to be sure: you are using MythTV-0.20 with ivtv-0.8, right?
Yup, I'm using the MythTV packages from Christian Marillat
(www.debian-multimedia.org), version 0.20-0.4.
Post by Hans Verkuil
1) Turn off VBI support in MythTV and test again. (This assumes it
is turned on of course).
Sorry, I can't find the setting. I removed and recreated both devices
from mythtv-setup but still lost...
Post by Hans Verkuil
2) Test also with the ivtv trunk version (0.9 development version).
Will do if I can find that damn VBI setting ;-)
But I have some new news about my previous post...
When watching back the two raw mpg files from my previous post I
noticed that the 0.8-tagged.mpg is in 480x480 (the default MythTV
LiveTV settings). The "good" mpg file, 0.8.1-3577.mpg is in 720x576,
the default state of the device after loading ivtv in PAL mode.
I probably first watched LiveTV when testing 0.8-tagged and after
closing MytvTV I did a cat from the raw device only after setting the
frequency with v4l2-ctl -f. The device must have had the 480x480
settings still loaded from it's previous MythTV task.
To test 0.8.1-3577 I had to restart my computer and directly captured
the 0.8.1-3577.mpg test file from the raw device (in default PAL
720x576 mode), so without starting MythTV first.
If I change the default MythTV LiveTV recording profile from 480x480
to 720x576 I'm able to watch LiveTV from mythfrontend on the same box
with 0.8.1-3577, something I couldn't do in my previous 0.8-anything
reports. Also the prebuffering and audio errors are gone, so it looks
like ivtv and MythTV don't like each other in 480x480 and perhaps
other non-default resolutions. I'm able to reproduce the choppy video
by switching LiveTV recording profile from 480x480 to 720x576 and
back with 0.8.1-3577. I didn't test 0.8-tagged in 720x576 mode yet,
but I believe it will also function OK when running in 720x576.
I'm happy to do some more testing if you want.
Can you run v4l2-ctl -v width=480,height=480 to force the picture size
and do another simple capture using 'cat'? Do you see the same
artefacts there as well? Of course, needless to say it works fine for
me.

A question for the MythTV experts: why on earth does MythTV use 480x480?
There is no doubt some good reason for that. I hope.

Regards,

Hans
Post by Jorgen Rosink
_______________________________________________
ivtv-devel mailing list
ivtv-devel at ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Jorgen Rosink
2006-11-15 22:43:38 UTC
Permalink
Post by Hans Verkuil
Can you run v4l2-ctl -v width=480,height=480 to force the picture size
and do another simple capture using 'cat'? Do you see the same
artefacts there as well? Of course, needless to say it works fine for
me.
http://docs.rosink.net/cat480x480.mpg

http://docs.rosink.net/cat720x576.mpg
Hans Verkuil
2006-11-15 23:00:41 UTC
Permalink
Post by Jorgen Rosink
Post by Hans Verkuil
Can you run v4l2-ctl -v width=480,height=480 to force the picture
size and do another simple capture using 'cat'? Do you see the same
artefacts there as well? Of course, needless to say it works fine
for me.
http://docs.rosink.net/cat480x480.mpg
http://docs.rosink.net/cat720x576.mpg
OK, final test: capture at 480x480 using cat. While capturing
run: 'v4l2-ctl --log-status' and 'ivtvctl -R chip=cx2584x'. In order to
do the latter command you need to have the advanced debugging option
set in the video4linux configuration of the kernel.

If I don't see anything strange here, then I don't know either. All I
can say is that it works for me, capturing at 480x480.

Thanks,

Hans
Jorgen Rosink
2006-11-15 23:01:07 UTC
Permalink
Well, shoot me, with 0.9.0-3582 it's perfect again

http://docs.rosink.net/ivtv-0.9-3582.txt

http://docs.rosink.net/cat480x480-0.9-3582.mpg

http://docs.rosink.net/cat720x576-0.9-3582.mpg
Hans Verkuil
2006-11-16 06:54:23 UTC
Permalink
Post by Jorgen Rosink
Well, shoot me, with 0.9.0-3582 it's perfect again
http://docs.rosink.net/ivtv-0.9-3582.txt
http://docs.rosink.net/cat480x480-0.9-3582.mpg
http://docs.rosink.net/cat720x576-0.9-3582.mpg
_______________________________________________
ivtv-devel mailing list
ivtv-devel at ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
You know what? I'm going to ignore all this :-) The reorganized ivtv in
the trunk will be the future anyway. I hope to do some more
fixing/improvements on that this weekend.

Thanks for testing,

Hans
Jorgen Rosink
2006-11-16 10:16:45 UTC
Permalink
Post by Hans Verkuil
You know what? I'm going to ignore all this :-)
hehe
Post by Hans Verkuil
The reorganized ivtv in the trunk will be the future anyway. I hope to do some more
fixing/improvements on that this weekend.
Yeah, that should be more usefull... Thanks for your help

Loading...