Sorry, I've been busy the past few days....  By the way, the bz link doesn't 
seem to work on your repository.

> > > > > > Quite a few HVR-1600 users have reported cx18 driver I2C related

> > > > > > problems usually with the following errors present:
> > > > > >
> > > > > >    tveeprom 1-0050: Huh, no eeprom present (err=-121)?
> > > > > >    tveeprom 1-0050: Encountered bad packet header [ff]. Corrupt or 
> > > > > > not 
> a 
> > > Hauppauge eeprom.
> > > > > >
> > > > > >    s5h1409_readreg: readreg error (ret == -121)
> > > > > >    cx18: frontend initialization failed
> > > > > >    cx18-0: DVB failed to register
> > > > > >
> > > > > > and an unusable HVR-1600/CX23418 under linux.
> > > > > >
> > > > > >
> > > > > > On the surface the problem appeared to be related to the devices on 
> the
> > > > > > I2C buses of the HVR-1600. [...] The I2C bus errors appear to be
> > > > > > just a symptom of a larger underlying problem.
> > > 
> > > 
> > > To all the users of CX23418 based cards that currently don't seem to
> > > work, showing some of the above symptoms, please test my latest changes
> > > at:
> > > 
> > > http://linuxtv.org/hg/~awalls/v4l-dvb
> > > 
> > > If your card still doesn't work with the default module options, then
> > > try upping the "mmio_ndelay" module parameter by multiples of about 30.3
> > > ns until the card does work:
> > > 
> > > For example, if the default "mmio_ndelay=31" doesn't work for you, then
> > > use:
> > > 
> > > # /sbin/modprobe cx18 mmio_ndelay=61
> > > 
> > >
> > > or 91, or 121, or 152, etc. until your card does work.
> > > 
> > > If you have multiple cx18 cards, and the default doesn't work, then you
> > > will have to specify a value for each card.  For example:
> > > 
> > > # /sbin/modprobe cx18 mmio_ndelay=61,61,61
> > > 
> > > for a three card setup.
> > > 
> > > As always feedback is appreciated.  In this case, I'd especially like to
> > > hear about digital captures, simultaneous analog & digital capture, and
> > > the (in)correctness of the cx18_memcpy_fromio() and cx18_memset_io()
> > > routines.
> > > 
> > > 
> > 
> > Hey Andy
> > 
> > I hate to be the first to report this, but I'm still obtaining the
> > eeprom error.
> 
> :( Bummer.
> 
> 
> 
> >   I'm currently away from the computer (I tested this last
> > night, but was too tired to write up the email yet...), but when I do
> > get a chance, would a dmesg be of any help, or what would you like?
> 
> I need to know if your card works under windows in that same machine.  I
> can't remember if you said it did or not.
> 
> And the dmesg output will help me see the current failure mode.

At 500:

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

> 
> 
> > Anyways, you said if it doesn't work, run "/sbin/modprobe
> > cx18 mmio_ndelay=61".  I've gotten up to 152, yet it still doesn't
> > work.  Should I keep going, to see if it'll eventually catch it?  How high?
> 
> 500 is half a microsecond and about 16.5 PCI bus cycles delay for each
> IO access.  That should be ridiculously long in PCI bus terms as a one
> word transaction can take as little as 4 PCI bus cycles.
> 
> 
> > I really appericate your help on this.
> 
> Unfortunately your case doesn't fit with the other users who were having
> problems.  I have the *exact* same motherboard as you (MSI-7184) in my
> HP machine as you have in your Compaq machine and HP owns Compaq (I
> think).  My HVR-1600's have worked in the machine from day 1, yet yours
> hasn't.
> 
> I am at a loss as to why the card doesn't work for you specifically.  I
> can only think of a few things:
> 
> 1. You have a bad card.  (Does it work in Windows?  Does it work in
> another machine?  Do you have another CX23418 based card you can try?)

Works fine in Windows, and no, this is my only CX18 card.  My only other 
computers I own are laptops, so I can't really try another machine.

> 
> 2. You have a bad slot in you motherboard.  Have you tried switching
> slots? (I can't remember if you have.)

Yes, I have tried switching slots.

>
> 3. The kernels or distributions we run are different enough that one of
> us has a kernel bug related to PCI IO that the other doesn't.

Which kernel are you on?  Could I by chance try this on a Fedora LiveCD?  Would 
that be able to rule this out?

> Michael,
> 
> One more idea.  Quite a while ago (30 June) you had partial success
> setting the  ".msecs_asserted" and " .msecs_recovery" delays in
> cx18-cards.c to 100 along with the two (now three) mdelay()'s near the
> bottom of cx18-i2c.c to 100.  
> 
> Could you try changing those again to 100, and recompiling the latest
> cx18 driver?  When you modprobe the driver, make sure you set
> "mmio_ndelay" to a number higher than 0: 31, 61, 92, or higher.
> 
> It's a shot in the dark.  But, if it's not one thing, then maybe it's
> two.

Still seems to not want to go:

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
cx18-0: unregister DVB
cx18-0: Removed Hauppauge HVR-1600, card #0
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 video-588210056 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 video-588210056 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 video-588210056 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-588210120 for encoder radio
cx18-0: Initialized card #0: Hauppauge HVR-1600
cx18:  End initialization
cx18-0: unregister DVB
cx18-0: Removed Hauppauge HVR-1600, card #0
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 video-588210056 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 video-588210056 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 video-588210056 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-588210120 for encoder radio
cx18-0: Initialized card #0: Hauppauge HVR-1600
cx18:  End initialization


      

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to