On Thu, 2008-09-04 at 11:00 -0700, Michael wrote:
> > > > > 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.
> 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?)
2. You have a bad slot in you motherboard. Have you tried switching
slots? (I can't remember if you have.)
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.
Regards,
Andy
FYI here's my lspci output, it's about the same as you provide to me,
except I have a Ralink RT2500 based 802.11g card in the machine as well:
# /sbin/lspci -tv
-[0000:00]-+-00.0 ATI Technologies Inc RS480 Host Bridge
+-01.0-[0000:01]----05.0 ATI Technologies Inc RS480 [Radeon Xpress
200G Series]
+-12.0 ATI Technologies Inc 4379 Serial ATA Controller
+-13.0 ATI Technologies Inc IXP SB400 USB Host Controller
+-13.1 ATI Technologies Inc IXP SB400 USB Host Controller
+-13.2 ATI Technologies Inc IXP SB400 USB2 Host Controller
+-14.0 ATI Technologies Inc IXP SB400 SMBus Controller
+-14.1 ATI Technologies Inc Standard Dual Channel PCI IDE Controller
+-14.3 ATI Technologies Inc IXP SB400 PCI-ISA Bridge
+-14.4-[0000:02]--+-00.0 RaLink RT2500 802.11g Cardbus/mini-PCI
| +-01.0 Agere Systems Unknown device 0620
| +-02.0 Conexant Unknown device 5b7a
| +-03.0 Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+
| \-04.0 VIA Technologies, Inc. IEEE 1394 Host
Controller
+-14.5 ATI Technologies Inc IXP SB400 AC'97 Audio Controller
+-18.0 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
+-18.1 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address
Map
+-18.2 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM
Controller
\-18.3 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
/sbin/lspci -s 0:14.4 -vv
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (prog-if 01
[Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: f4000000-fbffffff
Prefetchable memory behind bridge: fdd00000-fddfffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR+
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
