After re-installing the card in the linux box after it worked in windows, it works in linux now......
I don't know what voodoo the hauppauge drivers did, but at least it's working now. Rob On 4/22/07, Rob Selina <[EMAIL PROTECTED]> wrote:
More info - Card works 100% in WinXP - audio works on the s-video/composite inputs and the tuner works correctly. Guess I can rule out a hardware problem now. Rob On 4/22/07, Rob Selina <[EMAIL PROTECTED]> wrote: > > Replying to myself with more information. I've now tried multiple > different kernel versions, tried building my own firmware off the supplied > CDROM (it's identical to the e-build firmware) and some other misc testing > and I've narrowed down the problem to two issues: > > 1 - audio capture off the analog inputs does not work due to this error: > > > "ivtv0: i2c hardware 0x00000020 (wm8775) not found for command > 0x4008646d!" > > I can get video off the composite & s-video inputs but I get the same > error repeated in dmesg for each input change as it tries to establish > audio. At least we know the mpeg encoder works..... > > 2 - the tuner module (or hardware) definitely is broken. I can't get any > debug output from it and it doesn't seem to do the usual handshake with the > tuner chipset. > > This is mostly a hunch at this point but I'll throw it out there in case > there's anything to it: I've begun to suspect an I2C problem since that > protocol is used for both the broken audio & tuner control. I have the > dreaded Via Apollo chipset on this MB which makes me even more suspicious of > this. I've tried building kernels with I2C built-in vs as modules with no > change in behavior...... > > I'm planning on borrowing a windows machine today and trying my luck at > installing the card in an XP environment. Maybe I can at least rule out that > the hardware is defective that way. > > Thanks, > > Rob > > On 4/21/07, Rob Selina < [EMAIL PROTECTED]> wrote: > > > > (Note: Please CC me on any replies) > > > > Hi Everybody, > > > > I can't seem to get my PVR-150 to work. All I get is static for audio > > and no video. As far as I can tell it's a tuner problem since I can modprobe > > ivtv with tuner=50 or tuner=55 or any other random tuner type and I don't > > see a single difference in behavior. > > > > When I try to tune to a channel, I do not get any signal: > > > > smokin-joe firmware # ivtv-tune -c2 > > /dev/video0: 55.250 MHz > > smokin-joe firmware # ivtv-tune -c4 > > /dev/video0: 67.250 MHz > > > > And some more indications of problems with the tuner. > > > > smokin-joe firmware # v4l2-ctl -I > > Video input : 0 (Tuner 1) > > smokin-joe firmware # v4l2-ctl -F > > Frequency: 0 (0.000000 MHz) > > smokin-joe firmware # ivtv-tune -c13 > > /dev/video0: 211.250 MHz > > smokin-joe firmware # v4l2-ctl -F > > Frequency: 0 (0.000000 MHz) > > smokin-joe firmware # > > > > The only indication I ever get of the tuner doing something useful, is > > that if I play the /dev/video0 device in mplayer, the audio static cuts out > > for 1/2 second shortly after using ivtv-tune to try to change a channel. > > > > smokin-joe firmware # v4l2-ctl --all > > Driver info: > > Driver name : ivtv > > Card type : Hauppauge WinTV PVR-150 > > Bus info : 0000:00:0d.0 > > Driver version: 2561 > > Capabilities : 0x01030051 > > Video Capture > > VBI Capture > > Sliced VBI Capture > > Tuner > > Audio > > Read/Write > > Format: > > Type : Video Capture > > Width/Height : 720/480 > > Pixel Format : MPEG > > Field : Interlaced > > Bytes per Line: 0 > > Size Image : 131072 > > Colorspace : Broadcast NTSC/PAL (SMPTE170M/ITU601) > > Format: > > Type : Sliced VBI Capture > > Service Set : > > Service Line 0: / > > Service Line 1: / > > Service Line 2: / > > Service Line 3: / > > Service Line 4: / > > Service Line 5: / > > Service Line 6: / > > Service Line 7: / > > Service Line 8: / > > Service Line 9: / > > Service Line 10: / > > Service Line 11: / > > Service Line 12: / > > Service Line 13: / > > Service Line 14: / > > Service Line 15: / > > Service Line 16: / > > Service Line 17: / > > Service Line 18: / > > Service Line 19: / > > Service Line 20: / > > Service Line 21: / > > Service Line 22: / > > Service Line 23: / > > I/O Size : 0 > > Format: > > Type : VBI Capture > > Sampling Rate : 27000000 Hz > > Offset : 248 samples (9.18519e-06 secs after leading > > edge) > > Samples per Line: 1440 > > Sample Format : GREY > > Start 1st Field : 10 > > Count 1st Field : 12 > > Start 2nd Field : 273 > > Count 2nd Field : 12 > > Video input : 0 (Tuner 1) > > Audio input : 0 (Tuner 1) > > Frequency: 0 (0.000000 MHz) > > Video standard = 0x00001000 > > NTSC-M > > Tuner: > > Capabilities : 62.5 kHz stereo lang1 lang2 > > Frequency range : 0.0 MHz - 0.0 MHz > > Signal strength : 0% > > Current audio mode : lang1 > > Available subchannels: mono lang2 > > smokin-joe firmware # > > > > Note that the tuner shows a signal strength of 0% and the frequency > > range of 0 to 0.............. > > > > Assuming it was something obvious, I tested the cable into the tuner > > and it works fine with other devices. I also tried a different cable that > > was hooked up to a working device and again no change in behavior. I'm > > 99.9% positive that I have good signal into the tuner. I'm on Comcast > > analog cable if it matters (NTSC) > > > > Here's the pertinent section of dmesg after loading the ivtv driver > > with debug=3: > > > > ivtv: ==================== START INIT IVTV ==================== > > ivtv: version 0.10.1 (tagged release) loading > > ivtv: Linux version: 2.6.19-gentoo-r5 preempt mod_unload K7 REGPARM > > 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 card (cx23416 based) > > ivtv0 info: base addr: 0x30000000 > > ivtv0 info: Enabling pci device > > ACPI: PCI Interrupt 0000:00: 0d.0[A] -> Link [LNKB] -> GSI 11 (level, > > low) -> IRQ 11 > > ivtv0 info: Attempting to enable Bus Mastering > > ivtv0 info: Bus Mastering Enabled. > > ivtv0 info: 22 (rev 1) at 00:0d.0, irq: 11, latency: 64, memory: > > 0x30000000 > > ivtv0 info: attempting ioremap at 0x30000000 len 0x00800000 > > ivtv0 info: attempting ioremap at 0x32000000 len 0x00010000 > > ivtv0 info: Preparing for firmware halt. > > ivtv0 info: Stopping VDM > > ivtv0 info: Stopping AO > > ivtv0 info: pinging (?) APU > > ivtv0 info: Stopping VPU > > ivtv0 info: Resetting Hw Blocks > > ivtv0 info: Stopping SPU > > ivtv0 info: init Encoder SDRAM pre-charge > > ivtv0 info: init Encoder SDRAM refresh to 1us > > ivtv0 info: Sleeping for 600ms (600 recommended) > > ivtv0 info: Loading encoder image > > ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > > ivtv0 info: Getting firmware version.. > > ivtv0: Encoder revision: 0x02060039 > > ivtv0 info: GPIO initial dir: 0000df00 out: 000026f3 > > ivtv0 info: activating i2c... > > PM: Adding info for No Bus:i2c-1 > > PM: Adding info for i2c:1-0050 > > cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) > > cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes) > > PM: Adding info for i2c:1-0044 > > ivtv0 info: Active card count: 1. > > ivtv0 info: Loaded module tveeprom > > tveeprom 1-0050: Hauppauge model 26582, rev E6B2, serial# 9784745 > > tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) > > tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) > > tveeprom 1-0050: audio processor is CX25843 (idx 37) > > tveeprom 1-0050: decoder processor is CX25843 (idx 30) > > tveeprom 1-0050: has no radio, has no IR remote > > ivtv0: Autodetected Hauppauge WinTV PVR-150 > > ivtv0 info: NTSC tuner detected > > ivtv0 info: Loaded module tuner > > ivtv0 info: Loaded module cx25840 > > ivtv0 info: Loaded module wm8775 > > ivtv0: Registered device video0 for encoder MPEG (4 MB) > > ivtv0 info: Allocate DMA encoder MPEG stream: 128 x 32768 buffers > > (4096kB total) > > ivtv0: Registered device video32 for encoder YUV (2 MB) > > ivtv0 info: Allocate DMA encoder YUV stream: 194 x 10800 buffers > > (2046kB total) > > ivtv0: Registered device vbi0 for encoder VBI (1 MB) > > ivtv0 info: Allocate DMA encoder VBI stream: 60 x 17472 buffers > > (1023kB total) > > ivtv0: Registered device video24 for encoder PCM audio (1 MB) > > ivtv0 info: Allocate DMA encoder PCM audio stream: 227 x 4608 buffers > > (1021kB total) > > ivtv0 info: Starting Threads > > ivtv0 info: Changing input from 1 to 0 > > ivtv0 info: Mute > > ivtv0: i2c hardware 0x00000020 (wm8775) not found for command > > 0x4008646d! > > ivtv0 info: Unmute > > ivtv0 info: Switching standard to 1000. > > ivtv0 info: Mute > > ivtv0 info: v4l2 ioctl: set frequency 1076 > > ivtv0 info: Unmute > > ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 > > ivtv: ==================== END INIT IVTV ==================== > > > > > > Not the error: "ivtv0: i2c hardware 0x00000020 (wm8775) not found for > > command 0x4008646d!" > > > > That's the only irregularity I see. > > > > In regards to the tuner, I see it detect it in eeprom and identify it > > as a type 50 and then load the tuner module down the line but I never get > > any feedback from the tuner module. If I unload the tuner module and reload > > it with debug=3, still no dmesg output. Same if I load the tuner module with > > debug=3 prior to loading ivtv. As I mentioned above, I've tried unloading > > the ivtv and tuner modules and loading ivtv with tuner=50 (or various other > > values) and I never see any difference in the output from dmesg. It's > > identified in eeprom as a type 50 and the ivtv driver loads the tuner module > > but I never see any indication that it's actually passing values to it or > > doing anything useful - I just can't get any meaningful output from the > > tuner module. > > > > I'm on gentoo and I've tried installing both the firmware & driver > > from portage and also uninstalling them and using the files from the > > ivtvdriver.org site - same behavior in both. > > > > Here are some pertinent detials on my system: > > > > smokin-joe firmware # uname -a > > Linux smokin-joe 2.6.19-gentoo-r5 #14 PREEMPT Sat Apr 21 12:06:13 MDT > > 2007 i686 AMD Athlon(tm) Processor AuthenticAMD GNU/Linux > > > > smokin-joe firmware # lsmod > > Module Size Used by > > ivtv 126928 0 > > i2c_algo_bit 6984 1 ivtv > > cx2341x 10372 1 ivtv > > tveeprom 13392 1 ivtv > > tuner 59304 0 > > wm8775 4812 0 > > cx25840 23952 0 > > eeprom 5584 0 > > snd_seq_midi 6176 0 > > snd_emu10k1_synth 6144 0 > > snd_emux_synth 32128 1 snd_emu10k1_synth > > snd_seq_virmidi 5248 1 snd_emux_synth > > snd_seq_midi_emul 5888 1 snd_emux_synth > > snd_pcm_oss 22432 0 > > snd_mixer_oss 14080 1 snd_pcm_oss > > snd_seq_oss 28736 0 > > snd_seq_midi_event 6144 3 > > snd_seq_midi,snd_seq_virmidi,snd_seq_oss > > snd_seq 45520 8 > > snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi_event > > rtc 10292 0 > > nvidia 4542228 0 > > firmware_class 7552 2 ivtv,cx25840 > > via686a 13896 0 > > i2c_isa 3648 1 via686a > > i2c_viapro 7380 0 > > i2c_core 17104 11 > > ivtv,i2c_algo_bit,tveeprom,tuner,wm8775,cx25840,eeprom,nvidia,via686a,i2c_isa,i2c_viapro > > > > rt61 239236 1 > > snd_emu10k1 111104 1 snd_emu10k1_synth > > snd_rawmidi 19360 3 > > snd_seq_midi,snd_seq_virmidi,snd_emu10k1 > > snd_ac97_codec 89696 1 snd_emu10k1 > > snd_ac97_bus 1856 1 snd_ac97_codec > > snd_pcm 63368 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec > > snd_seq_device 6348 7 > > snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi > > snd_timer 18820 3 snd_seq,snd_emu10k1,snd_pcm > > snd_page_alloc 7432 2 snd_emu10k1,snd_pcm > > snd_util_mem 3456 2 snd_emux_synth,snd_emu10k1 > > snd_hwdep 6724 2 snd_emux_synth,snd_emu10k1 > > snd 43492 13 > > snd_emux_synth,snd_seq_virmidi,snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep > > > > uhci_hcd 20680 0 > > > > Something that jumped out at me in the ivtv how-to was this: > > "For kernels <= 2.6.15 When you run a 'make install', you may have > > noticed that there are warning messages about moving some > > modules.There are duplicate modules for tveeprom, tda9887, tuner and > > msp3400. One set is provided with the kernel (originating from from the v4l > > project, and merged with the dvb project), and the other is from ivtv > > itself. Please see below how to install the modules and which one will have > > to be used." > > > > I can confirm that both the gentoo portage version and ivtv driver > > from the site did NOT over-write my tuner module. Is this only applicable to > > earlier versions of ivtv? > > > > Any help appreciated. I'm pretty stumped on this one. If I can provide > > any more information please let me know. > > > > Thanks in advance! > > > > Rob > > > > > > > -- > Rob -- Rob
-- Rob
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
