[mythtv-users] pcHDTV HD3000 stops receiving

[H P Ladds]

On 10/29/07, Kevin Bailey <ke-myth at retriever.dyndns.org> wrote:

> [45759.444000] or51132: unknown status 0x00
> [45759.596000] or51132: unknown status 0x00
> [46063.140000] or51132: unknown status 0x00
> [46063.292000] or51132: unknown status 0x00

This message (above) is very familiar to me.

> Well, they may be different versions of the same problem.
> The HD3000 forum mentions some bugs and fixes related to
> I2C, which could very well be used for downloading firmware.
> (We use it for small EEPROMs here at work.) While I2C is a
> very simple protocol, the devices on it can be pretty
> picky about timing, and one bit missed kills the chip.

The error message from dmesg (below) implicates IC2. It seems probable
that the HD3000 loads the needed firmware to eeprom(s). Now that I
know what the heck IC2 is, I'm beginning to believe that our troubles
are similar. Perhaps it's our particular mobo Nvidia chipset w/
HD3000? This problem is pretty severe and strikes at the very core of
what Myth does; we'd know if several other had this trouble.

or51132: Waiting for firmware upload(dvb-fe-or51132-vsb.fw)...
or51132: I2C write (addr 0x15 len 1771) error: -121
or51132: load_firmware error 1
or51132: Writing firmware to device failed!
or51132: I2C error reading register 0: -121
or51132: read_status: error reading receiver status: -121
or51132: I2C error reading register 0: -121
or51132: read_status: error reading receiver status: -121........

> I guess I'll just hope that the fixes they talk about make
> it into the mainstream build someday.

Google was not helpful to me in regards to IC2.  I never tried the
HD3000 forum for IC2. Will take a look at it.