From: Andreas A. <li...@a-...> - 2006-01-09 20:57:56
|
Hello everybody, i have compiled the latest cvs checkout (lirc-0_8_pre3) on my fedora core 2 system. Make and make install works pretty well, but my Actysis will not receive any signal when i try irrecord. I've tried several io and irq settings, no change. Here is my modprobe.conf: --- snip --- options lirc_sir irq=3 install lirc_sir /bin/setserial /dev/ttyS0 uart none ;\ /sbin/modprobe --ignore-install lirc_sir alias eth0 sis900 alias usb-controller ehci-hcd install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/a lsactl restore >/dev/null 2>&1 || : remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/mo dprobe -r --ignore-remove snd-intel8x0 alias snd-card-0 snd-intel8x0 # nvidia kernel module alias char-major-195 nvidia-1_0-7174 alias nvidia nvidia-1_0-7174 alias char-major-81 bttv --- snap --- When i load lirc_sir in debug mode i get these dmesg message: --- snip --- lirc_dev: IR Remote Control driver registered, at major 61 lirc_dev: lirc_register_plugin: sample_rate: 0 lirc_dev: plugin lirc_sir registered at minor number = 0 lirc_sir: I/O port 0x02e8, IRQ 3. lirc_sir: Installed. --- snap --- When starting irrecord these messages appear in dmesg: --- snip --- lirc_dev (lirc_sir[0]): ioctl called (0x80046900) lirc_dev (lirc_sir[0]): ioctl called (0x40046911) lirc_dev (lirc_sir[0]): ioctl called (0x40046912) lirc_dev (lirc_sir[0]): ioctl called (0x80046907) lirc_dev (lirc_sir[0]): poll called lirc_dev (lirc_sir[0]): poll called lirc_dev (lirc_sir[0]): poll called lirc_dev (lirc_sir[0]): close called --- snap --- but irrecord tells me that no signals where received for about 10 seconds and closes then. I want my 2nd Hauppauge Remote to work without a tv card in this pc. Is this possible whith the actisys irda device or am i completely on the wrong path? Any hints? Thank You Regards Andreas |
From: <ma...@sp...> - 2006-01-10 15:50:28
|
On Mon, Jan 09, 2006 at 09:57:51PM +0100, Andreas Angerer wrote: > Hello everybody, > > i have compiled the latest cvs checkout (lirc-0_8_pre3) on my fedora > core 2 system. Make and make install works pretty well, but my Actysis > will not receive any signal when i try irrecord. I've tried several io > and irq settings, no change. > Here is my modprobe.conf: > --- snip --- > options lirc_sir irq=3 > install lirc_sir /bin/setserial /dev/ttyS0 uart none ;\ > /sbin/modprobe --ignore-install lirc_sir > alias eth0 sis900 > alias usb-controller ehci-hcd > install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && > /usr/sbin/a > lsactl restore >/dev/null 2>&1 || : > remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; > /sbin/mo > dprobe -r --ignore-remove snd-intel8x0 > alias snd-card-0 snd-intel8x0 > # nvidia kernel module > alias char-major-195 nvidia-1_0-7174 > alias nvidia nvidia-1_0-7174 > alias char-major-81 bttv > --- snap --- > > When i load lirc_sir in debug mode i get these dmesg message: > --- snip --- > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_dev: lirc_register_plugin: sample_rate: 0 > lirc_dev: plugin lirc_sir registered at minor number = 0 > lirc_sir: I/O port 0x02e8, IRQ 3. > lirc_sir: Installed. > --- snap --- > > When starting irrecord these messages appear in dmesg: > --- snip --- > lirc_dev (lirc_sir[0]): ioctl called (0x80046900) > lirc_dev (lirc_sir[0]): ioctl called (0x40046911) > lirc_dev (lirc_sir[0]): ioctl called (0x40046912) > lirc_dev (lirc_sir[0]): ioctl called (0x80046907) > lirc_dev (lirc_sir[0]): poll called > lirc_dev (lirc_sir[0]): poll called > lirc_dev (lirc_sir[0]): poll called > lirc_dev (lirc_sir[0]): close called > --- snap --- > > but irrecord tells me that no signals where received for about 10 > seconds and closes then. > > I want my 2nd Hauppauge Remote to work without a tv card in this pc. Is > this possible whith the actisys irda device or am i completely on the > wrong path? > > Any hints? > Thank You > > Regards > Andreas Hi, at first please ensure that you've compiled lirc with explicit support for this driver by using 'configure --with-drivers=act220l' or 'setup.sh'. Second please re-verify your serial port settings. Isn't the first serial port almost anywhere port 0x3f8 int 4? The 220L(+) is a so very simple device that you should notice when it receives anything, even with the wrong LIRC driver. If there's absolutely no go it might be a totally different device or somethings wrong with your serial port. Btw: all other Actisys dongles _are_ totally different. Have fun Jan |
From: Andreas A. <li...@a-...> - 2006-01-10 20:19:14
|
Hi Jan, > > Hi, > > at first please ensure that you've compiled lirc with explicit support for > this driver by using 'configure --with-drivers=act220l' or 'setup.sh'. modinfo lirc_sir: description: LIRC driver for Actisys Act220L(+) > Second please re-verify your serial port settings. Isn't the first > serial port almost anywhere port 0x3f8 int 4? The 220L(+) is a so very > simple device that you should notice when it receives anything, even > with the wrong LIRC driver. If there's absolutely no go it might be a > totally different device or somethings wrong with your serial port. Btw: all > other Actisys dongles _are_ totally different. checked it now on 2 different machines (one is a debian sarge, the other like i've written a fedora core 2), controlled bios settings for serial ports, no change. On the back of the receiver is printed: ACT-IR220Lplus looks like it is this device: http://www.actisys.com/ac200-220.html > > Have fun > Jan fun is not the problem :) Sitting in front of tv with a keyboard is ... Regards Andreas |
From: <ma...@sp...> - 2006-01-11 19:31:11
|
On Tue, Jan 10, 2006 at 09:18:53PM +0100, Andreas Angerer wrote: > Hi Jan, > > > > > Hi, > > > > at first please ensure that you've compiled lirc with explicit support for > > this driver by using 'configure --with-drivers=act220l' or 'setup.sh'. > > modinfo lirc_sir: > description: LIRC driver for Actisys Act220L(+) > > > Second please re-verify your serial port settings. Isn't the first > > serial port almost anywhere port 0x3f8 int 4? The 220L(+) is a so very > > simple device that you should notice when it receives anything, even > > with the wrong LIRC driver. If there's absolutely no go it might be a > > totally different device or somethings wrong with your serial port. Btw: all > > other Actisys dongles _are_ totally different. > > checked it now on 2 different machines (one is a debian sarge, the other > like i've written a fedora core 2), controlled bios settings for serial > ports, no change. On the back of the receiver is printed: > ACT-IR220Lplus > > looks like it is this device: > http://www.actisys.com/ac200-220.html > > > > > Have fun > > Jan > > > fun is not the problem :) > Sitting in front of tv with a keyboard is ... Hehe, if it's a wireless keyboard ;-) Well, i don't know how to investigate this further, did you test standart IRDA operation btw? My experience with this adapter was, that it receives even with the wrongest settings, although it's just crap but works for 90% chance of recognission. You could try compiling lirc with debug messages, so you should see anything it received in dmesg. If the data received is 0x5B something more high-level might be broken but there is a chance getting it to work. So there might be 2 options now: First - my device is not what it says. Second - your's isn't. If the first is the case we'd have to rename the driver in the lirc distribution - but to what? ;-) So, good luck, there must be some way... Jan PS: I'm going to test my driver with the actual release, i'm still using some older version with my own patch. Maybe there's a new bug somewhere. |
From: Andreas A. <li...@a-...> - 2006-01-11 22:42:05
|
>> > Hi, >> > >> > at first please ensure that you've compiled lirc with explicit support for >> > this driver by using 'configure --with-drivers=act220l' or 'setup.sh'. >> >> modinfo lirc_sir: >> description: LIRC driver for Actisys Act220L(+) >> >> > Second please re-verify your serial port settings. Isn't the first >> > serial port almost anywhere port 0x3f8 int 4? The 220L(+) is a so very >> > simple device that you should notice when it receives anything, even >> > with the wrong LIRC driver. If there's absolutely no go it might be a >> > totally different device or somethings wrong with your serial port. Btw: all >> > other Actisys dongles _are_ totally different. >> >> checked it now on 2 different machines (one is a debian sarge, the other >> like i've written a fedora core 2), controlled bios settings for serial >> ports, no change. On the back of the receiver is printed: >> ACT-IR220Lplus >> >> looks like it is this device: >> http://www.actisys.com/ac200-220.html >> >> > >> > Have fun >> > Jan >> >> >> fun is not the problem :) >> Sitting in front of tv with a keyboard is ... > Hehe, if it's a wireless keyboard ;-) > Well, i don't know how to investigate this further, did you test > standart IRDA operation btw? My experience with this adapter was, that > it receives even with the wrongest settings, although it's just crap > but works for 90% chance of recognission. You could try compiling lirc > with debug messages, so you should see anything it received in dmesg. If > the data received is 0x5B something more high-level might be broken but > there is a chance getting it to work. > > So there might be 2 options now: First - my device is not what it says. > Second - your's isn't. If the first is the case we'd have to rename the > driver in the lirc distribution - but to what? ;-) > > So, good luck, there must be some way... > Jan in a word, nothing. No irda, no messages when compiled with debug enabled. As i have mailed to christoph, with my xp box the dongle is fully functional. When it is ok for you i can make a picture from that thing and send it to you. I bought it last week from Conrad (this is a big german electronic shop) think about to bring it back and buy a pinnacle tv card with a supported remote (you know the tv thing is my aim) > > PS: I'm going to test my driver with the actual release, i'm still using > some older version with my own patch. Maybe there's a new bug somewhere. > should i try other versions of lirc ? Andreas |
From: <ma...@sp...> - 2006-01-12 00:42:40
Attachments:
lirc-act220l.patch
|
On Wed, Jan 11, 2006 at 11:41:53PM +0100, Andreas Angerer wrote: > in a word, nothing. No irda, no messages when compiled with debug > enabled. As i have mailed to christoph, with my xp box the dongle is > fully functional. When it is ok for you i can make a picture from that > thing and send it to you. I bought it last week from Conrad (this is a > big german electronic shop) think about to bring it back and buy a > pinnacle tv card with a supported remote (you know the tv thing is my aim) No thanks, a photo won't be neccessary because i got the same, also from conrad ;-) Mine just isn't labeled at the bottom. > should i try other versions of lirc ? I'd say yes after a quick test of pre3 CVS release. I wasn't able to send anything. Testing receiving is a bit difficult if not at home - there's noone hitting the buttons on a remote ;-) If you like a quick hack, get lirc-0.7.2 (the current stable one), apply the attached patch and copy the 'autogen.sh'-script from the CVS version to this release (and, of course, use it). Now configure lirc as you like, build and install. I didn't investigate the current release further, but i think it'll get fixed soon. Hope this lights up the situation Jan |
From: Andreas A. <li...@a-...> - 2006-01-12 21:02:50
|
Hi Jan, > On Wed, Jan 11, 2006 at 11:41:53PM +0100, Andreas Angerer wrote: >> in a word, nothing. No irda, no messages when compiled with debug >> enabled. As i have mailed to christoph, with my xp box the dongle is >> fully functional. When it is ok for you i can make a picture from that >> thing and send it to you. I bought it last week from Conrad (this is a >> big german electronic shop) think about to bring it back and buy a >> pinnacle tv card with a supported remote (you know the tv thing is my aim) > > No thanks, a photo won't be neccessary because i got the same, also from > conrad ;-) Mine just isn't labeled at the bottom. > >> should i try other versions of lirc ? > > I'd say yes after a quick test of pre3 CVS release. I wasn't able to > send anything. Testing receiving is a bit difficult if not at home - > there's noone hitting the buttons on a remote ;-) > If you like a quick hack, get lirc-0.7.2 (the current stable one), apply > the attached patch and copy the 'autogen.sh'-script from the CVS version > to this release (and, of course, use it). Now configure lirc as you > like, build and install. I didn't investigate the current release > further, but i think it'll get fixed soon. did as you told, no signal. Maybe it is a complete other dongle under the same name. I'll bring it back tomorrow and change it against a Pinnacle PCTV Stereo (is only 5 EUR more than the Actisys) Sorry that i can't test any further, but i have limited time to get this to work. Thank you for all your help Andreas |
From: <li...@ba...> - 2006-01-11 20:23:25
|
Hi! Andreas Angerer "li...@a-..." wrote: [...] > install lirc_sir /bin/setserial /dev/ttyS0 uart none ;\ This indicates you are using COM1 for your adapter. [...] > -+- snip --- > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_dev: lirc_register_plugin: sample_rate: 0 > lirc_dev: plugin lirc_sir registered at minor number = 0 > lirc_sir: I/O port 0x02e8, IRQ 3. This indicates that you configured lirc to use COM4. One of the settings is probably wrong. Btw.; I have verified that the driver works with an Act-IR220Lplus. Christoph |
From: Andreas A. <li...@a-...> - 2006-01-11 22:39:08
|
Hi, > [...] >> install lirc_sir /bin/setserial /dev/ttyS0 uart none ;\ no change here, it is com1 > > This indicates you are using COM1 for your adapter. > > [...] >> -+- snip --- >> lirc_dev: IR Remote Control driver registered, at major 61 >> lirc_dev: lirc_register_plugin: sample_rate: 0 >> lirc_dev: plugin lirc_sir registered at minor number = 0 >> lirc_sir: I/O port 0x02e8, IRQ 3. ok, loaded module with following options: modprobe lirc_sir irq=4 io=0x3f8 debug > > This indicates that you configured lirc to use COM4. > One of the settings is probably wrong. dmesg shows me for ttyS0: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > Btw.; I have verified that the driver works with an Act-IR220Lplus. still no luck :( I tried it with my Win XP Machine, the dongle is ok, it works with xp. Andreas |
From: Andreas A. <a-...@a-...> - 2006-01-11 22:31:44
|
Hi, > [...] >> install lirc_sir /bin/setserial /dev/ttyS0 uart none ;\ no change here, it is com1 > > This indicates you are using COM1 for your adapter. > > [...] >> -+- snip --- >> lirc_dev: IR Remote Control driver registered, at major 61 >> lirc_dev: lirc_register_plugin: sample_rate: 0 >> lirc_dev: plugin lirc_sir registered at minor number = 0 >> lirc_sir: I/O port 0x02e8, IRQ 3. ok, loaded module with following options: modprobe lirc_sir irq=4 io=0x3f8 debug > > This indicates that you configured lirc to use COM4. > One of the settings is probably wrong. dmesg shows me for ttyS0: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > Btw.; I have verified that the driver works with an Act-IR220Lplus. still no luck :( I tried it with my Win XP Machine, the dongle is ok, it works with xp. Andreas |
From: Darth P. (s. by Nabble.com) <li...@na...> - 2006-02-01 21:47:52
|
Hi Andreas, I have spent endless nights trying to get my Actisys 220L(+) IR Blaster to work. I think my problems were slightly different from yours (I eventually managed to get mine to receive but could not transmit). I was following Jarod Wilson's excelent guide, and got to http://iwamble.net/6901.html for help with compiling a second LIRC module to use an IR Blaster along side the PVR 350. Anyway, the iwamble site recommends lirc-0.8.0pre1, which seems to contain drivers for the Acisys 200 but not the 220L(+). After much digging around (and looking at LIRC source code), I found that lirc-0.8.0 (i.e. not the pre* versions) does include a 220L(+) driver. I edited the lirc2remote.sh script from the iwamble site to use the "non pre" version. However, I didn't realise (being a bit of a module compiling newbie) that you have to configure the remote0.8.0 module with the "--with-transmitter" flag to enable transmitting on the blaster as well as receiving. Anyway, I don't know if that is any help to you, but maybe will be of help to somebody. Good Luck, Pablo. Andreas Angerer wrote: > > Hello everybody, > > i have compiled the latest cvs checkout (lirc-0_8_pre3) on my fedora > core 2 system. Make and make install works pretty well, but my Actysis > will not receive any signal when i try irrecord. I've tried several io > and irq settings, no change. > Here is my modprobe.conf: > --- snip --- > options lirc_sir irq=3 > install lirc_sir /bin/setserial /dev/ttyS0 uart none ;\ > /sbin/modprobe --ignore-install lirc_sir > alias eth0 sis900 > alias usb-controller ehci-hcd > install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && > /usr/sbin/a > lsactl restore >/dev/null 2>&1 || : > remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; > /sbin/mo > dprobe -r --ignore-remove snd-intel8x0 > alias snd-card-0 snd-intel8x0 > # nvidia kernel module > alias char-major-195 nvidia-1_0-7174 > alias nvidia nvidia-1_0-7174 > alias char-major-81 bttv > --- snap --- > > When i load lirc_sir in debug mode i get these dmesg message: > --- snip --- > lirc_dev: IR Remote Control driver registered, at major 61 > lirc_dev: lirc_register_plugin: sample_rate: 0 > lirc_dev: plugin lirc_sir registered at minor number = 0 > lirc_sir: I/O port 0x02e8, IRQ 3. > lirc_sir: Installed. > --- snap --- > > When starting irrecord these messages appear in dmesg: > --- snip --- > lirc_dev (lirc_sir[0]): ioctl called (0x80046900) > lirc_dev (lirc_sir[0]): ioctl called (0x40046911) > lirc_dev (lirc_sir[0]): ioctl called (0x40046912) > lirc_dev (lirc_sir[0]): ioctl called (0x80046907) > lirc_dev (lirc_sir[0]): poll called > lirc_dev (lirc_sir[0]): poll called > lirc_dev (lirc_sir[0]): poll called > lirc_dev (lirc_sir[0]): close called > --- snap --- > > but irrecord tells me that no signals where received for about 10 > seconds and closes then. > > I want my 2nd Hauppauge Remote to work without a tv card in this pc. Is > this possible whith the actisys irda device or am i completely on the > wrong path? > > Any hints? > Thank You > > Regards > Andreas > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > > -- View this message in context: http://www.nabble.com/Actisys-Act220L%28%2B%29-latest-cvs-checkout-t883040.html#a2709350 Sent from the LIRC forum at Nabble.com. |