First of all thank you to the develoment team for a great product that I have had the pleasure of since version R5A22.
I have a setup with a Backend with a pvr500 (Samsung tuner) card on R5F27. As I live in Denmark the setup is PAL.
Recording works fine as long as I only record one channel at a time. Then everything is recorded on "HW Tuner: 1->1".
If I try to record on two channels at the same time the recording on HW Tuner: 2->2 becomes zero bytes long.
The same happens when I try to watch tv while a recording is going on. The connection that comes in second and gets to the HW Tuner: 2->2 gets black screen/zero filesize. After about 30 seconds the screen is returned to the menu.
I had the same zero byte files while using R5F1 but didn't find out by then.
I am certain that I could record 2 channels at the same time during R5D1.
The mythtvbackend.log shows the following.
Code:
2007-09-26 16:30:02.684 TVRec(2): Changing from None to RecordingOnly
2007-09-26 16:30:02.692 TVRec(2): HW Tuner: 2->2
2007-09-26 16:30:02.893 Started recording: Øje til øje med vildsvinet: channel $
2007-09-26 16:30:08.278 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:13.714 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:19.146 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:24.576 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:30.007 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:35.436 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:40.866 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:46.296 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
2007-09-26 16:30:51.726 MPEGRec(/dev/video1) Error: select timeout - ivtv drive$
....
.....
This goes on all through the recording time.
I have no other errors in the logs.
Dmesg extract with ivtv shows:
Code:
Linux video capture interface: v2.00
ivtv: Start initialization, version 1.1.0
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[18] MMIO=[f9001000-f90017ff] Max Packet=[2048] IR/IT contexts=[8/8]
ivtv0: Initializing card #0
ivtv0: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 22 (level, low) -> IRQ 22
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0043: type set to tda9887
TEA5767 detected.
tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tea5767 1-0060: type set to Philips TEA5767HN FM Radio
tuner 1-0060: type set to tea5767
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tveeprom 1-0050: Hauppauge model 23559, rev D496, serial# 9483174
tveeprom 1-0050: tuner model is Samsung TCPG 6121P30A (idx 96, type 73)
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 receiver, has no IR transmitter
ivtv0: Autodetected WinTV PVR 500 (unit #1)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
tuner-simple 1-0061: type set to 73 (Samsung TCPG 6121P30A)
tuner 1-0061: type set to Samsung TCPG 6121P30A
ivtv0: Registered device video0 for encoder MPG (4096 kB)
ivtv0: Registered device video32 for encoder YUV (2048 kB)
ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
ivtv0: Registered device video24 for encoder PCM (320 kB)
ivtv0: Registered device radio0 for encoder radio
ivtv0: Initialized card #0: WinTV PVR 500 (unit #1)
ivtv1: Initializing card #1
ivtv1: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 23 (level, low) -> IRQ 21
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 2-0043: type set to tda9887
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
tveeprom 2-0050: Hauppauge model 23559, rev D496, serial# 9483174
tveeprom 2-0050: tuner model is Samsung TCPG 6121P30A (idx 96, type 73)
tveeprom 2-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62)
tveeprom 2-0050: audio processor is CX25843 (idx 37)
tveeprom 2-0050: decoder processor is CX25843 (idx 30)
tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: Autodetected WinTV PVR 500 (unit #2)
tuner-simple 2-0061: type set to 73 (Samsung TCPG 6121P30A)
tuner 2-0061: type set to Samsung TCPG 6121P30A
ivtv1: Registered device video1 for encoder MPG (4096 kB)
ivtv1: Registered device video33 for encoder YUV (2048 kB)
ivtv1: Registered device vbi1 for encoder VBI (1024 kB)
ivtv1: Registered device video25 for encoder PCM (320 kB)
ivtv1: Initialized card #1: WinTV PVR 500 (unit #2)
ivtv: End initialization
Adding 1959920k swap on /dev/hda2. Priority:-1 extents:1 across:1959920k
EXT3 FS on hda1, internal journal
bttv: driver version 0.9.17 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bt878: AUDIO driver version 0.0.0 loaded
The error is not due to the recording resolution as other pvr500 card issues. I have set the recording resolution to 720x576. Also i can tell that the recordings on HW Tuner : 1->1 is very good.
The two pvr500 inputs are setup as /dev/video0 - Tuner 1 and /dev/video1 - Tuner 1.
The videosource i the same for both tuners.
I have tried to read the wiki about compiling IVTV but with ivtv version 1.1 of R5F27 it says that I shouldn't do anything as i read it. Has anybody else seems this error or know of a fix for it?
/jk
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
I was getting terrible number of TIMEOUT errors in dmesg and that resulted in recordings that stopped writing data shortly after starting, or worst 0 byte recordings through out the day until rebooted. 
(pci-usb may have been in too)
Thanks jensk