IR device at I2C address 0x7a
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi Darek,
Adding LMML to Cc.
Quoted 12 lines · Daro
I have the problem you described at the mailing list with Asus MyCinema-P7131/P/FM/AV/RC Analog TV Card:
IR remote control is not detected and "i2c-adapter i2c-3: Invalid 7-bit address0x7a" error occurs.
lspci gives the following output:
04:00.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1) dmesg output I enclose in the attachment.
I use:
Linux DOMOWY 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009x86_64GNU/Linux
Quoted 6 lines
I would be gratefull for the help on that.
(...)
subsystem: 1043:4845, board: ASUS TV-FM 7135 [card=53,autodetected] (...)
i2c-adapter i2c-3: Invalid 7-bit address0x7asaa7133[0]: P7131 analog only, using entry of ASUSTeK P7131 Analog
This error message will show on virtually every SAA713x-based board with no known IR setup. It doesn't imply your board has any I2C device at address 0x7a. So chances are that the message is harmless and you can simply ignore it.
Signature · 1 line
Jean Delvare
Hi Jean,
Thank you for your answer.
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage. Is there something that can be done to get my IR remote control working?
Thanks for your help in advance.
Best regards
Darek
W dniu 06.01.2010 15:39, Jean Delvare pisze:
Quoted 31 lines
Hi Darek,
Adding LMML to Cc.
Quoted 12 lines · Daro
I have the problem you described at the mailing list with Asus MyCinema-P7131/P/FM/AV/RC Analog TV Card:
IR remote control is not detected and "i2c-adapter i2c-3: Invalid 7-bit address0x7a" error occurs.
lspci gives the following output:
04:00.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1) dmesg output I enclose in the attachment.
I use:
Linux DOMOWY 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009x86_64GNU/LinuxQuoted 7 lines
I would be gratefull for the help on that.
(...)
subsystem: 1043:4845, board: ASUS TV-FM 7135 [card=53,autodetected] (...)
i2c-adapter i2c-3: Invalid 7-bit address0x7asaa7133[0]: P7131 analog only, using entry of ASUSTeK P7131 AnalogThis error message will show on virtually every SAA713x-based board with no known IR setup. It doesn't imply your board has any I2C device at address
0x7a. So chances are that the message is harmless and you can simply ignore it.
Quoted 5 lines · Daro
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?
Did it ever work on Linux?
Signature · 1 line
Jean Delvare
W dniu 06.01.2010 19:40, Jean Delvare pisze:
Quoted 11 lines · Daro
Quoted 7 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?Did it ever work on Linux?
I have no experience on that. I bought this card just few weeks ago and tried it only on Karmic Koala.
Quoted 9 lines · Daro
W dniu 06.01.2010 19:40, Jean Delvare pisze:
Quoted 8 lines · Daro
Quoted 7 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?
Quoted 4 lines
Quoted 1 line
Did it ever work on Linux?
I have no experience on that. I bought this card just few weeks ago and tried it only on Karmic Koala.
OK.
You could try loading the saa7134 driver with option card=146 and see if it helps.
Signature · 1 line
Jean Delvare
W dniu 06.01.2010 21:21, Jean Delvare pisze:
Quoted 16 lines · Daro
Quoted 15 lines
W dniu 06.01.2010 19:40, Jean Delvare pisze:
Quoted 12 lines · Daro
Quoted 9 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?Did it ever work on Linux?
Quoted 9 lines
Quoted 3 lines
I have no experience on that. I bought this card just few weeks ago and tried it only on Karmic Koala.
OK.
You could try loading the saa7134 driver with option card=146 and see if it helps.
It works!
[ 15.477875] input: saa7134 IR (ASUSTeK P7131 Analo as /devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input8
Thank you very much fo your help.
I have another question regarding this driver:
[ 21.340316] saa7133[0]: dsp access error [ 21.340320] saa7133[0]: dsp access error
Do those messages imply something wrong? Can they have something do do with the fact I cannot get the sound out of tvtime application directly and have to use "arecord | aplay" workaround which causes undesirable delay?
Jean Delvare
Tested-by DaroQuoted 10 lines · Daro
W dniu 06.01.2010 21:21, Jean Delvare pisze:
Quoted 8 lines · Daro
Quoted 5 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?You could try loading the saa7134 driver with option card=146 and see if it helps.
Quoted 6 lines
It works!
[ 15.477875] input: saa7134 IR (ASUSTeK P7131 Analo as/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input8
Thank you very much fo your help.
Then I would suggest the following patch:
* * * * *
From: Jean Delvare <[email protected]>
Subject: saa7134: Fix IR support of some ASUS TV-FM 7135 variants
Some variants of the ASUS TV-FM 7135 are handled as the ASUSTeK P7131 Analog (card=146). However, by the time we find out, some card-specific initialization is missed. In particular, the fact that the IR is GPIO-based. Set it when we change the card type.
--- linux/drivers/media/video/saa7134/saa7134-cards.c | 1 + 1 file changed, 1 insertion(+)
linux/drivers/media/video/saa7134/saa7134-cards.c +1 -0
@@ -7257,6 +7257,7 @@ int saa7134_board_init2(struct saa7134_dprintk (KERN_INFO "%s: P7131 analog only, using " "entry of %s\n" , dev->name, saa7134_boards[dev->board].name); + dev->has_remote =SAA7134_REMOTE_GPIO ; }break ;case SAA7134_BOARD_HAUPPAUGE_HVR1150 :
* * * * *
Quoted 8 lines
I have another question regarding this driver:
[ 21.340316] saa7133[0]: dsp access error [ 21.340320] saa7133[0]: dsp access errorDo those messages imply something wrong? Can they have something do do with the fact I cannot get the sound out of tvtime application directly and have to use "arecord | aplay" workaround which causes undesirable delay?
Yes, the message is certainly related to your sound problem. Maybe support for your card is incomplete. But I can't help with this, sorry.
Signature · 1 line
Jean Delvare
Hi,
Am Samstag, den 09.01.2010, 17:14 +0100 schrieb Jean Delvare:
Quoted 25 lines · Daro
Quoted 10 lines
W dniu 06.01.2010 21:21, Jean Delvare pisze:
Quoted 8 lines · Daro
Quoted 5 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?You could try loading the saa7134 driver with option card=146 and see if it helps.
Quoted 6 lines
It works!
[ 15.477875] input: saa7134 IR (ASUSTeK P7131 Analo as/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input8
Thank you very much fo your help.
Then I would suggest the following patch:
* * * * *
From: Jean Delvare <[email protected]>
Subject: saa7134: Fix IR support of some ASUS TV-FM 7135 variants
Quoted 7 lines
Some variants of the ASUS TV-FM 7135 are handled as the ASUSTeK P7131 Analog (card=146). However, by the time we find out, some card-specific initialization is missed. In particular, the fact that the IR is GPIO-based. Set it when we change the card type.
Signed-off-by Jean Delvare <[email protected]>Tested-by Daro <[email protected]>
just to note it, the ASUS TV-FM 7135 with USB remote is different to the Asus My Cinema P7134 Analog only, not only for the remote, but also for inputs, but they have the same PCI subsystem.
Quoted 16 lines
--- linux/drivers/media/video/saa7134/saa7134-cards.c | 1 + 1 file changed, 1 insertion(+)linux/drivers/media/video/saa7134/saa7134-cards.c +1
-0@@ -7257,6 +7257,7 @@ int saa7134_board_init2(struct saa7134_dprintk (KERN_INFO "%s: P7131 analog only, using " "entry of %s\n" , dev->name, saa7134_boards[dev->board].name); + dev->has_remote =SAA7134_REMOTE_GPIO ; }break ;case SAA7134_BOARD_HAUPPAUGE_HVR1150 :
Quoted 1 line
* * * * *
Must have been broken at that time, IIRC.
Only moving saa7134_input_init1(dev) to static int saa7134_hwinit2 in saa7134-core.c did help, AFAIK, but I might be wrong.
Quoted 11 lines
Quoted 8 lines
I have another question regarding this driver:
[ 21.340316] saa7133[0]: dsp access error [ 21.340320] saa7133[0]: dsp access errorDo those messages imply something wrong? Can they have something do do with the fact I cannot get the sound out of tvtime application directly and have to use "arecord | aplay" workaround which causes undesirable delay?
Yes, the message is certainly related to your sound problem. Maybe support for your card is incomplete. But I can't help with this, sorry.
That is nice ice to slide on, but from all others with that card previously not reported so far.
Anyway, it should have also analog audio out, the two pins in the middle of the white 4pin connector on the PCB are ground. To know that can avoid troubles using older CD-ROM audio cables and get only one of the stereo channels.
Cheers,
Hermann
Hermann
Quoted 56 lines · hermann pitton
Hi,
Am Samstag, den 09.01.2010, 17:14 +0100 schrieb Jean Delvare:
Quoted 25 lines · Daro
Quoted 10 lines
W dniu 06.01.2010 21:21, Jean Delvare pisze:
Quoted 8 lines · Daro
Quoted 5 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?You could try loading the saa7134 driver with option card=146 and see if it helps.
Quoted 6 lines
It works!
[ 15.477875] input: saa7134 IR (ASUSTeK P7131 Analo as/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input8
Thank you very much fo your help.
Then I would suggest the following patch:
* * * * *
From: Jean Delvare <[email protected]>
Subject: saa7134: Fix IR support of some ASUS TV-FM 7135 variantsQuoted 7 lines
Some variants of the ASUS TV-FM 7135 are handled as the ASUSTeK P7131 Analog (card=146). However, by the time we find out, some card-specific initialization is missed. In particular, the fact that the IR is GPIO-based. Set it when we change the card type.
Signed-off-by Jean Delvare <[email protected]>Tested-by Daro <[email protected]>just to note it, the ASUS TV-FM 7135 with USB remote is different to the Asus My Cinema P7134 Analog only, not only for the remote, but also for inputs, but they have the same PCI subsystem.
Quoted 16 lines
--- linux/drivers/media/video/saa7134/saa7134-cards.c | 1 + 1 file changed, 1 insertion(+)linux/drivers/media/video/saa7134/saa7134-cards.c +1
-0@@ -7257,6 +7257,7 @@ int saa7134_board_init2(struct saa7134_dprintk (KERN_INFO "%s: P7131 analog only, using " "entry of %s\n" , dev->name, saa7134_boards[dev->board].name); + dev->has_remote =SAA7134_REMOTE_GPIO ; }break ;case SAA7134_BOARD_HAUPPAUGE_HVR1150 :
Quoted 3 lines
Quoted 1 line
* * * * *
Must have been broken at that time, IIRC.
What must have been broken, and when? You are confusing.
Quoted 2 lines
Only moving
saa7134_input_init1(dev)to static intsaa7134_hwinit2insaa7134-core.cdid help, AFAIK, but I might be wrong.
I admit I don't quite get why dev->has_remove should be set early (in saa7134_board_init1) given that for one board (SAA7134_BOARD_FLYDVB_TRIO) it is set later (in saa7134_board_init2) and apparently it works OK. It would make more sense to do it at the same time for all boards IMHO, possibly in a separate function to make it clearer.
I am also curious if it wouldn't be even clearer and more efficient to store the default value of has_remote in struct saa7134_board. As far as I can see, only the SAA7134_BOARD_FLYDVB_TRIO needs a run-time check.
Signature · 1 line
Jean Delvare
Am Sonntag, den 10.01.2010, 09:51 +0100 schrieb Jean Delvare:
Quoted 57 lines · hermann pitton
Quoted 56 lines
Hi,
Am Samstag, den 09.01.2010, 17:14 +0100 schrieb Jean Delvare:
Quoted 25 lines · Daro
Quoted 10 lines
W dniu 06.01.2010 21:21, Jean Delvare pisze:
Quoted 8 lines · Daro
Quoted 5 lines
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working?You could try loading the saa7134 driver with option card=146 and see if it helps.
Quoted 6 lines
It works!
[ 15.477875] input: saa7134 IR (ASUSTeK P7131 Analo as/devices/pci0000:00/0000:00:1e.0/0000:05:00.0/input/input8
Thank you very much fo your help.
Then I would suggest the following patch:
* * * * *
From: Jean Delvare <[email protected]>
Subject: saa7134: Fix IR support of some ASUS TV-FM 7135 variantsQuoted 7 lines
Some variants of the ASUS TV-FM 7135 are handled as the ASUSTeK P7131 Analog (card=146). However, by the time we find out, some card-specific initialization is missed. In particular, the fact that the IR is GPIO-based. Set it when we change the card type.
Signed-off-by Jean Delvare <[email protected]>Tested-by Daro <[email protected]>just to note it, the ASUS TV-FM 7135 with USB remote is different to the Asus My Cinema P7134 Analog only, not only for the remote, but also for inputs, but they have the same PCI subsystem.
Quoted 16 lines
--- linux/drivers/media/video/saa7134/saa7134-cards.c | 1 + 1 file changed, 1 insertion(+)linux/drivers/media/video/saa7134/saa7134-cards.c +1
-0@@ -7257,6 +7257,7 @@ int saa7134_board_init2(struct saa7134_dprintk (KERN_INFO "%s: P7131 analog only, using " "entry of %s\n" , dev->name, saa7134_boards[dev->board].name); + dev->has_remote =SAA7134_REMOTE_GPIO ; }break ;case SAA7134_BOARD_HAUPPAUGE_HVR1150 :
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
* * * * *
Must have been broken at that time, IIRC.
What must have been broken, and when? You are confusing.
Sorry, I missed that thread until now.
The above patch was tried previously by Roman.
For the record, here is a link.
http://www.spinics.net/lists/vfl/msg38869.html
Quoted 2 lines
Quoted 2 lines
Only moving
saa7134_input_init1(dev)to static intsaa7134_hwinit2insaa7134-core.cdid help, AFAIK, but I might be wrong.
Maybe some regression was involved for him, at least I followed his assumption, that in case of auto detection, when first a board without remote is detected, and then that late is switched to another board with remote through eeprom detection, input_init1 would not happen again.
Quoted 10 lines
I admit I don't quite get why
dev->has_removeshould be set early (insaa7134_board_init1) given that for one board (SAA7134_BOARD_FLYDVB_TRIO) it is set later (insaa7134_board_init2) and apparently it works OK. It would make more sense to do it at the same time for all boards IMHO, possibly in a separate function to make it clearer.I am also curious if it wouldn't be even clearer and more efficient to store the default value of
has_remotein structsaa7134_board. As far as I can see, only theSAA7134_BOARD_FLYDVB_TRIOneeds a run-time check.
Patches are welcome.
Thanks,
Hermann
Hi Hermann,
Sorry for the late answer.
Quoted 42 lines · hermann pitton
Am Sonntag, den 10.01.2010, 09:51 +0100 schrieb Jean Delvare:
Quoted 41 lines · hermann pitton
Quoted 39 lines
Am Samstag, den 09.01.2010, 17:14 +0100 schrieb Jean Delvare:
Quoted 7 lines
Then I would suggest the following patch:
* * * * *
From: Jean Delvare <[email protected]>
Subject: saa7134: Fix IR support of some ASUS TV-FM 7135 variantsQuoted 7 lines
Some variants of the ASUS TV-FM 7135 are handled as the ASUSTeK P7131 Analog (card=146). However, by the time we find out, some card-specific initialization is missed. In particular, the fact that the IR is GPIO-based. Set it when we change the card type.
Signed-off-by Jean Delvare <[email protected]>Tested-by Daro <[email protected]>just to note it, the ASUS TV-FM 7135 with USB remote is different to the Asus My Cinema P7134 Analog only, not only for the remote, but also for inputs, but they have the same PCI subsystem.
Quoted 16 lines
--- linux/drivers/media/video/saa7134/saa7134-cards.c | 1 + 1 file changed, 1 insertion(+)linux/drivers/media/video/saa7134/saa7134-cards.c +1
-0@@ -7257,6 +7257,7 @@ int saa7134_board_init2(struct saa7134_dprintk (KERN_INFO "%s: P7131 analog only, using " "entry of %s\n" , dev->name, saa7134_boards[dev->board].name); + dev->has_remote =SAA7134_REMOTE_GPIO ; }break ;case SAA7134_BOARD_HAUPPAUGE_HVR1150 :Quoted 1 line
* * * * *
Must have been broken at that time, IIRC.
Quoted 7 lines
Quoted 1 line
What must have been broken, and when? You are confusing.
Sorry, I missed that thread until now.
The above patch was tried previously by Roman.For the record, here is a link.
http://www.spinics.net/lists/vfl/msg38869.html
Thanks for the pointer, this was very helpful. I had missed the fact that the call to saa7134_input_init1() was before the card number change. So indeed my patch was insufficient.
Roman's strategy to move saa7134_input_init1() to the late init section seems good to me. Honestly, I can't think of a good reason to init the remote control early. I doubt that anything else depends on that.
I'll send an updated patch shortly.
Signature · 1 line
Jean Delvare
Hi Jean,
Am Mittwoch, den 27.01.2010, 10:38 +0100 schrieb Jean Delvare:
Quoted 59 lines
Hi Hermann,
Sorry for the late answer.
Quoted 42 lines · hermann pitton
Am Sonntag, den 10.01.2010, 09:51 +0100 schrieb Jean Delvare:
Quoted 41 lines · hermann pitton
Quoted 39 lines
Am Samstag, den 09.01.2010, 17:14 +0100 schrieb Jean Delvare:
Quoted 7 lines
Then I would suggest the following patch:
* * * * *
From: Jean Delvare <[email protected]>
Subject: saa7134: Fix IR support of some ASUS TV-FM 7135 variantsQuoted 7 lines
Some variants of the ASUS TV-FM 7135 are handled as the ASUSTeK P7131 Analog (card=146). However, by the time we find out, some card-specific initialization is missed. In particular, the fact that the IR is GPIO-based. Set it when we change the card type.
Signed-off-by Jean Delvare <[email protected]>Tested-by Daro <[email protected]>just to note it, the ASUS TV-FM 7135 with USB remote is different to the Asus My Cinema P7134 Analog only, not only for the remote, but also for inputs, but they have the same PCI subsystem.
Quoted 16 lines
--- linux/drivers/media/video/saa7134/saa7134-cards.c | 1 + 1 file changed, 1 insertion(+)linux/drivers/media/video/saa7134/saa7134-cards.c +1
-0@@ -7257,6 +7257,7 @@ int saa7134_board_init2(struct saa7134_dprintk (KERN_INFO "%s: P7131 analog only, using " "entry of %s\n" , dev->name, saa7134_boards[dev->board].name); + dev->has_remote =SAA7134_REMOTE_GPIO ; }break ;case SAA7134_BOARD_HAUPPAUGE_HVR1150 :Quoted 1 line
* * * * *
Must have been broken at that time, IIRC.
Quoted 7 lines
Quoted 1 line
What must have been broken, and when? You are confusing.
Sorry, I missed that thread until now.
The above patch was tried previously by Roman.For the record, here is a link.
http://www.spinics.net/lists/vfl/msg38869.htmlThanks for the pointer, this was very helpful. I had missed the fact that the call to
saa7134_input_init1()was before the card number change. So indeed my patch was insufficient.
Quoted 5 lines
Roman's strategy to move
saa7134_input_init1()to the late init section seems good to me. Honestly, I can't think of a good reason to init the remote control early. I doubt that anything else depends on that.I'll send an updated patch shortly.
thanks for your time looking closer into it.
Unfortunately I did not have any during the last two months.
If we pass all the testing, your here announced and later following patch should be the best possible solution, as it stands now.
To give some historical notes, Gerd did try to avoid eeprom detection on the saa7134 driver, likely hoping to see better PCI subsystem use by the manufacturers, since bttv was already very complex and difficult to maintain with all the specific detection stuff and workarounds.
However, Hartmut Hackmann and me had to discover, that we still see the same disease with some saa713x OEMs, the same PCI subsystem for very different cards ...
Hence we started with some eeprom detection, known now for having caused trouble already through all the ever ongoing changing init procedures we always have and very bad for transparent maintenance.
For all, and for Asus specifically, this is still a unique case on the saa713x driver, IIRC. The rest is fine on Asus.
To print something for that card like "for IR you have to set the card=number" should be also still enough.
To remind, we run into those problems, because OEMs don't follow the rules of the chip manufacturer, excluding others by will on their m$ drivers, when initially buying greater amounts of chips.
So we always run only after the tsunamis and it is not worth it, to give those breaking rules previously, some kind of moral instance to get their devices better detected on GNU/Linux later.
Anyway, let's try.
Cheers,
Hermann
Quoted 11 lines · Daro <ghost-rider <at> aster.pl> writes:
Hi Jean,
Thank you for your answer.
It is not the error message itself that bothers me but the fact that IR remote control device is not detected and I cannot use it (I checked it on Windows and it's working). After finding this thread I thought it could have had something to do with this error mesage.
Is there something that can be done to get my IR remote control working? Thanks for your help in advance.
Quoted 3 lines
Best regards
Darek
Hi Darek,
I use a P7131 Dual with mythbuntu, and the IR remote needed special setup. While it's a slightly different model of P7131 yours, it could be worth a try. In /etc/lirc/hardware.conf I needed the lines:
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="name=saa7134*" REMOTE_LIRCD_CONF="asus/mycinema.conf"
(remove or comment out any existing REMOTE_DEVICE entries)
The device name (with wildcard) matches on input device name (rather than using numbered input which could change on reboot)
The remote config (IR codes for remote) go in:/usr/share/lirc/remotes/asus/mycinema.conf
The button mappings are in another file associated with the specific application (lircrc for mythtv).
Dave
Quoted 34 lines
W dniu 06.01.2010 15:39, Jean Delvare pisze:
Quoted 31 lines
Hi Darek,
Adding LMML to Cc.
Quoted 12 lines · Daro
I have the problem you described at the mailing list with Asus MyCinema-P7131/P/FM/AV/RC Analog TV Card:
IR remote control is not detected and "i2c-adapter i2c-3: Invalid 7-bit address0x7a" error occurs.
lspci gives the following output:
04:00.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1) dmesg output I enclose in the attachment.
I use:
Linux DOMOWY 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009x86_64GNU/LinuxQuoted 7 lines
I would be gratefull for the help on that.
(...)
subsystem: 1043:4845, board: ASUS TV-FM 7135 [card=53,autodetected] (...)
i2c-adapter i2c-3: Invalid 7-bit address0x7asaa7133[0]: P7131 analog only, using entry of ASUSTeK P7131 AnalogThis error message will show on virtually every SAA713x-based board with no known IR setup. It doesn't imply your board has any I2C device at address
0x7a. So chances are that the message is harmless and you can simply ignore it.