Hello all, I haven't suffered at the hands of my PVR-350 for about 2 years because it was separated from me when I left Korea. I did use it to download some transcoded shows from mythtv whilst I was travelling around the world. BTW I had to run a debian x64 system as it was more stable - can't have emerge killing anything when I'm 1000's of Ks away from the box.
Now I"m at home in Australia and I'm running Gentoo AMD64 2006.1 I'm trying to get to the bottom of the problem with my PVR. I'll post more details as they are requested. Here's the low down: I have a PVR-350 NTSC version and I'm in a PAL country. I have over-rided the standard with PAL=M, and in full debug it seems to be putting the card in PAL mode. I also use v4l2-control to do this.The MSP44xx seems to support pal audio even though it is not listed in the module options. I am running Linux hojuruku 2.6.19-rc6-mm2 #5 PREEMPT Fri Dec 22 05:12:25 EST 2006 x86_64 AMD Athlon(tm) 64 Processor 2800+ AuthenticAMD GNU/Linux with realtime-lsm loaded after the card. Asus K8V-SE MB, 1.8GHZ Socket 754 AMD64 CPU. I used kernel v4l and alsa - because hg had some unresolved symbol to do with "sleeping" with the kernel I used. Yes I know it's UNSTABLE, but I'm looking for a pata patch for a stable kernel. The 2.6.20 kernel's aren't ready for much yet, they break more than what I'm running. For the sake of peace I'll do some testing on 2.6.18 minus half my HDD storage :) I would use a more stable kernel but I need promise-pata support in order to have somewhere to store my recordings. I'll try and get a patch against 2.6.18 for this but I'm still looking..... I have tried both bleeding edge SVN and 0.9.1. I have had some success - some days. 1) Device intermittently works. Requires power off for at least 30 seconds to allow it to start. 2) PC unsable? I've got only one MCE error this week. I didn't have mcelog installed and there wasn't much I could do with the system. The PC doesn't reboot at poweroff - but it's because I've got a lame Winbond hardware watchdog - that for some reason ASUS didn't hook it up to the reset line. I'll disable it soon. I'm going to buy a GPU cooling fan to put on it - yes it does get hot and it did stay on for 2 years when it was back in Korea I changed the PCI bus latency from 32 to 64 in BIOS config (dmesg told me to). I'm thinking of under clocking my memory to 200MHZ as aftermarket ppl who use the same chips have heatsinks... I'll have the thermal issue's checked out soon but I think we are ok - its at 44'c case temp normally. 46' CPU. 3) On debug level 3 here is what I get when I try and cat /dev/video1 > test.mpg ivtv0 info: ivtv start v4l2 stream ivtv0 info: Setup VBI API header 0x0000bd03 pkts 1 buffs 4 ln 36 sz 1456 ivtv0 info: Setup VBI start 0x002fea04 frames 4 fpi 1 lines 0x000000f1 ivtv0 info: ENC: PGM Index at 0x00180150 with 0x00000190 elements ivtv0: Invalid API call: cmd = 0xb1, args = 1 ivtv0 info: ivtv_read: stream encoder MPEG ivtv0 info: ENC: 0x00000000 fill ivtv0 info: User stopped encoder MPEG ivtv0 info: close stopping capture ivtv0 info: Stop Capture The card will work the first or second time ONLY after I do a cat. I have set it to record a PAL signal from a DVD recorder's welcome screen. Tested Progressive & interlaced. 4) I think the problem may have to do with VBI. I'll try again later with VBI disabled. What's the most comprehensive way to disable all VBI processing? Also I don't think we use PRC here in Australia so they only thing useful is Teletext, I think that works with the SVN packaged version of myth that comes with gentoo. 5) What debug level is useful without flooding the IVTV list? 255 has got too much i2c stuff. The card does initialize ok, but when I did have lots of debug messages it looks like the firmware went AWOL during playback. Also when playback starts there is a 10-20 delay before the stream starts filling. This upsets mythtv but of course cat copes with it. 6) FYI An alternative fix for the firmware loading error and freeze by udev (yeah I got it earlier) is this configuration file. It will work on all systems and does not require poking through the udev conf files and disable all firmware loading. Udev falls back on modprobe to do the module loading and dependencies - lets use that to fix the firmware loading bug. my /etc/modules.d/ivtv: alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias char-major-61 lirc_i2c #add above ivtv lirc_dev lirc_i2c options ivtv cardtype=2 radio=1 ivtv_yuv_mode=2 pal=B newi2c=1 ivtv_debug=3 # #mpg_buffers=12 pcm_buffers=3 options msp3400 debug=0 #ivtv_first_minor=1 install ivtv /lib/firmware/ivtv-load.sh add below ivtv msp3400 saa7115 saa7127 tuner add above ivtv lirc_dev lirc_i2c ----- /lib/firmware/ivtv-load.sh: #!/bin/sh before=`cat /proc/sys/kernel/hotplug` echo /sbin/hotplug > /proc/sys/kernel/hotplug modprobe --ignore-install ivtv echo $before > /proc/sys/kernel/hotplug sleep 5 #v4l2-ctl -d /dev/video1 -i 1 -o 1 -s 0 ---- /etc/sysctl.conf #for making ivtv happier with memory usage: vm.min_free_kbytes = 65536 (also tried 16384 earlier when I was more successful - I've got 768 mb ram). I am using the recommended firmware as specified by the Firmware HOWTO (latest version). NB the MD5 on the troubleshooting wiki does not reflect this (update required). I tried exporting from the driver and using the gentoo pvr-firmware package. Both have the same contents. 7) I've lost my output cable in the move. Anyone got the pinout for it - I think I can get the 9 pin mini-din or whatever connector is used from an electronics wholesaler. Speaking of pinouts does the extra inputs bracket connect to a PVR-350 - I have the white socket... but I heard the pinouts could be different on some 350's??? 8) Do i2c and bttv gpio lirc interfaces only accept the remotes that were bundled with the card? Is this because they have a PIC onboard to help them control the remote - at least on BTTV's connected to the GPIO pins? I'm building my own serial one - I keep getting the "no gap error" when i try to use irrrecord with the device, that is if i stop manually pressing keys on my remote. I think this is because the timing is not as comprehensive as a serial port receiver (which I'm going to build tomorrow - already build a transmitter and it works fine). I made my own IR receiver cable, again lost in the move - using the pinout from irblaster.info. It gets "some" signals, lets hope the hauppage remote is 38Khz though. Does I2c remotes receive for any remotes or just those designed to be bundled with the card? I am using the lirc_module version not the input layer. I've had problems with that on the bttv card im working (known bug). I use lirc_i2c. 99) The big question. Will you support me? I've been honest about my setup? What are the suggested next moves to get it working to diagnose a HW / SW fault. Don't make me run X86_64/x86 windows please :P 100) Also with Mythtv when the card does feel like working will not switch to use the SVHS input - even though it's the only input tied to a media source. What's up with this? It's latest in gentoo portage unmasked from ~amd64 0.20.svn-something. Cheers, Luke Here is the startup sequence with debug=3 Dec 27 07:20:13 hojuruku ivtv: ==================== START INIT IVTV ==================== Dec 27 07:20:13 hojuruku ivtv: version 0.10.0 (development revision 3703) loading Dec 27 07:20:13 hojuruku ivtv: Linux version: 2.6.19-rc6-mm2 preempt mod_unload Dec 27 07:20:13 hojuruku ivtv: In case of problems please include the debug info between Dec 27 07:20:13 hojuruku ivtv: the START INIT IVTV and END INIT IVTV lines, along with Dec 27 07:20:13 hojuruku ivtv: any module options, when mailing the ivtv-users mailinglist. Dec 27 07:20:13 hojuruku ivtv0: User specified Hauppauge WinTV PVR-350 card (detected cx23415 based chip) Dec 27 07:20:13 hojuruku ivtv0 info: base addr: 0xdc000000 Dec 27 07:20:13 hojuruku ivtv0 info: Enabling pci device Dec 27 07:20:13 hojuruku ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ 19 Dec 27 07:20:13 hojuruku ivtv0 info: Bus Mastering Enabled. Dec 27 07:20:13 hojuruku ivtv0 info: 2051 (rev 1) at 00:0e.0, irq: 19, latency: 64, memory: 0xdc000000 Dec 27 07:20:13 hojuruku ivtv0 info: attempting ioremap at 0xdc000000 len 0x00800000 Dec 27 07:20:13 hojuruku ivtv0 info: attempting ioremap at 0xdd000000 len 0x00800000 Dec 27 07:20:13 hojuruku ivtv0 info: attempting ioremap at 0xde000000 len 0x00010000 Dec 27 07:20:13 hojuruku ivtv0 info: Preparing for firmware halt. Dec 27 07:20:13 hojuruku ivtv0 info: Stopping VDM Dec 27 07:20:13 hojuruku ivtv0 info: Stopping AO Dec 27 07:20:13 hojuruku ivtv0 info: pinging (?) APU Dec 27 07:20:13 hojuruku ivtv0 info: Stopping VPU Dec 27 07:20:13 hojuruku ivtv0 info: Resetting Hw Blocks Dec 27 07:20:13 hojuruku ivtv0 info: Stopping SPU Dec 27 07:20:13 hojuruku ivtv0 info: init Encoder SDRAM pre-charge Dec 27 07:20:13 hojuruku ivtv0 info: init Encoder SDRAM refresh to 1us Dec 27 07:20:13 hojuruku ivtv0 info: init Decoder SDRAM pre-charge Dec 27 07:20:13 hojuruku ivtv0 info: init Decoder SDRAM refresh to 1us Dec 27 07:20:13 hojuruku ivtv0 info: Sleeping for 600ms (600 recommended) Dec 27 07:20:13 hojuruku nvidia: module license 'NVIDIA' taints kernel. Dec 27 07:20:13 hojuruku ivtv0 info: Loading encoder image Dec 27 07:20:13 hojuruku ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) Dec 27 07:20:13 hojuruku ivtv0 info: Loading decoder image Dec 27 07:20:13 hojuruku ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) Dec 27 07:20:13 hojuruku ivtv0 info: Getting firmware version.. Dec 27 07:20:13 hojuruku ivtv0: Encoder revision: 0x02050032 Dec 27 07:20:13 hojuruku ivtv0: Decoder revision: 0x02020023 Dec 27 07:20:13 hojuruku ivtv0 info: activating i2c... Dec 27 07:20:13 hojuruku tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0) Dec 27 07:20:13 hojuruku tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner) Dec 27 07:20:13 hojuruku tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0) Dec 27 07:20:13 hojuruku msp3400 3-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) Dec 27 07:20:13 hojuruku msp3400 3-0040: MSP4448G-A2 supports radio, mode is autodetect and autoselect Dec 27 07:20:13 hojuruku i2c_adapter i2c-3: Client creation failed at 0x44 (-1) Dec 27 07:20:13 hojuruku saa7115 3-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0) Dec 27 07:20:13 hojuruku saa7127 3-0044: saa7127 found @ 0x88 (ivtv i2c driver #0) Dec 27 07:20:13 hojuruku ivtv0 info: Active card count: 1. Dec 27 07:20:13 hojuruku ivtv0 info: Loaded module tveeprom Dec 27 07:20:13 hojuruku tveeprom 3-0050: Hauppauge model 48132, rev K168, serial# 2844316 Dec 27 07:20:13 hojuruku tveeprom 3-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47) Dec 27 07:20:13 hojuruku tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) Dec 27 07:20:13 hojuruku tveeprom 3-0050: audio processor is MSP4448 (idx 27) Dec 27 07:20:13 hojuruku tveeprom 3-0050: decoder processor is SAA7115 (idx 19) Dec 27 07:20:13 hojuruku tveeprom 3-0050: has radio, has IR receiver, has no IR transmitter Dec 27 07:20:13 hojuruku ivtv0: Autodetected Hauppauge WinTV PVR-350 Dec 27 07:20:13 hojuruku ivtv0 info: Loaded module tuner Dec 27 07:20:13 hojuruku ivtv0 info: Loaded module saa7115 Dec 27 07:20:13 hojuruku ivtv0 info: Loaded module saa7127 Dec 27 07:20:13 hojuruku ivtv0 info: Loaded module msp3400 Dec 27 07:20:13 hojuruku ivtv0: Registered device video1 for encoder MPEG (4 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096kB total) Dec 27 07:20:13 hojuruku ivtv0: Registered device video32 for encoder YUV (2 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2037kB total) Dec 27 07:20:13 hojuruku ivtv0: Registered device vbi1 for encoder VBI (1 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate DMA encoder VBI stream: 40 x 26208 buffers (1023kB total) Dec 27 07:20:13 hojuruku ivtv0: Registered device video24 for encoder PCM audio (1 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate DMA encoder PCM audio stream: 227 x 4608 buffers (1021kB total) Dec 27 07:20:13 hojuruku ivtv0: Registered device radio1 for encoder radio Dec 27 07:20:13 hojuruku ivtv0: Registered device video16 for decoder MPEG (1 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024kB total) Dec 27 07:20:13 hojuruku ivtv0: Registered device vbi8 for decoder VBI (1 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate decoder VBI stream: 40 x 26208 buffers (1023kB total) Dec 27 07:20:13 hojuruku ivtv0: Registered device vbi16 for decoder VOUT Dec 27 07:20:13 hojuruku ivtv0: Registered device video48 for decoder YUV (1 MB) Dec 27 07:20:13 hojuruku ivtv0 info: Allocate DMA decoder YUV stream: 20 x 51840 buffers (1012kB total) Dec 27 07:20:13 hojuruku ivtv0 info: Starting Threads Dec 27 07:20:13 hojuruku ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) Dec 27 07:20:13 hojuruku st: Version 20061107, fixed bufsize 32768, s/g segs 256 Dec 27 07:20:13 hojuruku tuner 3-0061: type set to 47 (LG NTSC (TAPE series)) Dec 27 07:20:13 hojuruku ivtv0 info: Changing input from 1 to 0 Dec 27 07:20:13 hojuruku ivtv0 info: Mute Dec 27 07:20:13 hojuruku ivtv0 info: Unmute Dec 27 07:20:13 hojuruku ivtv0 info: Switching standard to 7. Dec 27 07:20:13 hojuruku ivtv0 info: Mute Dec 27 07:20:13 hojuruku ivtv0 info: v4l2 ioctl: set frequency 6400 Dec 27 07:20:13 hojuruku ivtv0 info: Unmute Dec 27 07:20:13 hojuruku ivtv0: Initialized Hauppauge WinTV PVR-350, card #0 Dec 27 07:20:13 hojuruku ivtv: ==================== END INIT IVTV ==================== -- switch to PAL and SVHS input Dec 27 07:23:28 hojuruku ivtv0 info: Switching standard to f. Dec 27 07:23:28 hojuruku ivtv0 info: Changing input from 0 to 1 Dec 27 07:23:28 hojuruku ivtv0 info: Mute Dec 27 07:23:28 hojuruku ivtv0 info: Unmute Dec 27 07:23:28 hojuruku ivtv0 info: Changing output from 0 to 1 --- first playback attempt - same feedback as cited above plus this feedback. Dec 27 07:25:11 hojuruku ivtv0 info: ENC: 0x00000fc0 fill Dec 27 07:25:11 hojuruku ivtv0 info: ENC: read 4032, 64 bytes left Dec 27 07:25:11 hojuruku ivtv0 info: ivtv_read: stream encoder MPEG Dec 27 07:25:11 hojuruku ivtv0 info: ENC: 0x00000000 fill Dec 27 07:25:11 hojuruku ivtv0 info: ivtv_read: stream encoder MPEG Dec 27 07:25:11 hojuruku ivtv0 info: ENC: 0x00000800 fill Dec 27 07:25:11 hojuruku ivtv0 info: ENC: read 2048, 2048 bytes left Dec 27 07:25:11 hojuruku ivtv0 info: ivtv_read: stream encoder MPEG Dec 27 07:25:11 hojuruku ivtv0 info: ENC: 0x00000000 fill Dec 27 07:25:11 hojuruku ivtv0 info: ivtv_read: stream encoder MPEG Dec 27 07:25:11 hojuruku ivtv0 info: ENC: 0x00000800 fill Dec 27 07:25:11 hojuruku ivtv0 info: ENC: read 2048, 2048 bytes left Dec 27 07:25:11 hojuruku ivtv0 info: ivtv_read: stream encoder MPEG Dec 27 07:25:11 hojuruku ivtv0 info: ENC: 0x00000000 fill Dec 27 07:25:11 hojuruku ivtv0 info: ivtv_read: stream encoder MPEG .......... repeated 100's times _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
