On 28/06/06, Mark Weaver <[EMAIL PROTECTED]> wrote: > > modprobe lirc_dev debug=1 > > modprobe lirc_i2c debug=1 > > lircd > > > > lirc_dev: IR Remote Control driver registered, at major 61 > > lirc_i2c: probe 0x1a @ ivtv i2c driver #0: no > > lirc_i2c: probe 0x18 @ ivtv i2c driver #0: no > > lirc_i2c: probe 0x71 @ ivtv i2c driver #0: no > > lirc_i2c: probe 0x4b @ ivtv i2c driver #0: no > > lirc_i2c: probe 0x64 @ ivtv i2c driver #0: no > > lirc_i2c: probe 0x30 @ ivtv i2c driver #0: no > > lirc_i2c: probe 0x6b @ ivtv i2c driver #0: no > > > Does this card work under Windows/in another machine? If the IR > hardware isn't on the i2c bus, either it's broken or you have issues > with the bit banging algorithm. >
I saw simmular messages last night when I briefly booted into 2.6.17. The Remote works fine with 2.6.16 + ivtv 0.6 svn. I'll post them as soon as I have some time. Also I did not get any video or audio from the PVR350 (did not test the PVR500 yet). Greets _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
