On Thu, 2008-06-05 at 16:18 -0700, Michael wrote:
> I'm not sure if the first message went through, so I apologize if this comes
> twice.
>
> > > > The "videodev:" messages bug me. Can you check to make sure you don't
> > > > have duplicate tuner, tveeprom, videodev, etc., modules lying around for
> > > > the same kernel under /lib/modules/(kernelver)/?
> > > >
> > > I'm looking around in the folder, however, I'm not sure how to tell if
> > > there
> > are multiple modules... I've never did this before. Kernel is 2.6.22.17
> >
> > In a terminal window:
> >
> > $ find /lib/modules/2.6.23.15-80.fc7 -type f -exec basename {} \; | sort |
> > uniq
> > -c
> >
> > If any module name has a number >1 in front of it, there is a second
> > version installed.
> >
> So
> I ran the command, and from what I see, everything has a 1. However,
> not the whole list fit, only part of n, and every other module starting
> with a letter below n. But all of T was covered, including everything
> that started with tv, or tuner.
>
> I did find one case which there were two things installed, and I'm not quite
> sure how this happened, or how to correct it:
>
> 2 v4l-cx23418-apu.fw
> 2 v4l-cx23418-cpu.fw
> 2 v4l-cx23418-dig.fw
>
> >From what I remember, those were the firmware drivers.
Those are firmware images. I wouldn't worry about duplicates of those.
They shouldn't be different.
> > > Someone did state awhile back that possibly re-installing the device onto
> > > of a
> > previous install could cause this.
> > > >
> > > >
> > > > Regards,
> > > > Andy
> > >
> > >
> > >
> > > > Michael,
> > > >
> > > > One more thing to try with the gpio reset patch:
> > > >
> > > > Can you change these lines in cx18-gpio.c:
> > > >
> > > > To both call "schedule_timeout_uninterruptible()" instead? And then
> > > > test again.
> > > >
> > > Starting at line 71, correct? I just want to make sure I changed the
> > > right
> > part.
> > >
> > > With that change, I cannot seem to compile:
> >
> > Sorry, I should have been more explicit. Here's what I meant in this
> > new patch. You can back out the old patch, and apply this one to avoid
> > any compile errors (or you can do the edit by hand, if that's easier).
> >
> Ok, well, I applied the patch, and EEPROM still appears to be there. Heres
> dmesg:
>
> Linux video capture interface: v2.00
> cx18: Start initialization, version 1.0.0
> cx18-0: Initializing card #0
> cx18-0: Autodetected Hauppauge card
> cx18-0: cx23418 revision 01010000 (B)
> tveeprom 0-0050: Encountered bad packet header [00]. Corrupt or not a
> Hauppauge eeprom.
> cx18-0: Invalid EEPROM
> cx18-0: VBI is not yet supported
> cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
> cx18-0: Disabled encoder IDX device
> videodev: "" has no release callback. Please fix your driver for proper sysfs
> support, see http://lwn.net/Articles/36850/
> cx18-0: Registered device video0 for encoder MPEG (2 MB)
> DVB: registering new adapter (cx18).
> MXL5005S: Attached at address 0x63
> DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
> cx18-0: DVB Frontend registered
> videodev: "" has no release callback. Please fix your driver for proper sysfs
> support, see http://lwn.net/Articles/36850/
> cx18-0: Registered device video32 for encoder YUV (2 MB)
> videodev: "" has no release callback. Please fix your driver for proper sysfs
> support, see http://lwn.net/Articles/36850/
> cx18-0: Registered device video24 for encoder PCM audio (1 MB)
> videodev: "" has no release callback. Please fix your driver for proper sysfs
> support, see http://lwn.net/Articles/36850/
> cx18-0: Registered device radio-64 for encoder radio
> cx18-0: Initialized card #0: Hauppauge HVR-1600
> cx18: End initialization
What we're really looking for is a properly recognized EEPROM. From
your May 10th post, there was one instance where your dmesg shows the
EEPROM is properly recognized:
tveeprom 0-0050: Hauppauge model 74541, rev C5B6, serial# 2977340
tveeprom 0-0050: MAC address is 00-0D-FE-2D-6E-3C
tveeprom 0-0050: tuner model is Philips FM1236 MK5 (idx 116, type 43)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is CX23418 (idx 38)
tveeprom 0-0050: decoder processor is CX23418 (idx 31)
tveeprom 0-0050: has radio, has no IR receiver, has no IR transmitter
cx18-0: Unknown model 74541, defaulting to HVR-1600
cx18-0: Autodetected Hauppauge HVR-1600
> > If this doesn't work, I only have one more idea (until I can get a copy
> > of the CX23418 datasheet). That is upping the "mdelay(10)" statements
> > to "mdelay(10)" and "mdelay(40)" in the cx18-i2c.c file.
> >
> So as follows? (With the patch):
> write_reg_sync(0x00c00000, 0xc7001c);
> mdelay(10);
> write_reg_sync(0x00c000c0, 0xc7001c);
> mdelay(10);
> write_reg_sync(0x00c00000, 0xc7001c);
>
Yes change the second one to 40:
write_reg_sync(0x00c00000, 0xc7001c);
mdelay(10);
write_reg_sync(0x00c000c0, 0xc7001c);
mdelay(40);
write_reg_sync(0x00c00000, 0xc7001c);
> If so, eeprom is still there.
>
> Thanks again for all of your help.
Hmm. I really though the problem could have been that. Here's my
rationale:
1. From my dmesg output, the cx18 driver talks to the i2c devices in
the following order at initialization:
EEPROM chip
Analog tuner chips
CS5345 audio digitizer/multiplexer chip
MXL5005S chip
S5H1490 chip
2. From your dmesg output, normally the CS5345 is the first device to
actually respond properly. That would suggest accessing the CS5345 or
the analog tuner somehow clears up the I2C bus problem.
3. A similar sequence of mdelay()'s is used in cx23885/cx23885-cards.c
for the HVR-1200, HVR-1400, HVR-1500, HVR-1700, and HVR-1800 to reset
the analog tuner.
4. You have a different analog tuner (Philips FM1236 MK5 idx 116, type
43) than I (TCL M2523_5N_E idx 112, type 50), so perhaps it needs a
longer delay to be ready after reset. Or since yours seems to have FM
radio, and mine doesn't, we might be missing a reset line for a tuner
chip.
Since we've got that one good EEPROM read from May 10th, you can use
some command line options to try and get your card working:
# modprobe -r cx18
# modprobe tveeprom debug=1
# modprobe cx18 cardtype=1 tuner=43 radio=1 ntsc=M
Hopefully, that works for you.
Regards,
Andy
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
