From: Christopher F. <chr...@ho...> - 2006-05-31 11:10:12
|
Hi, I'm having problems getting lirc + the lirc_mceusb2 module to work from boot on suse (10.0 + 10.1). Firstly, I've already set up a previous remote (hauppauge one) with lirc_i2c before and it works fine from boot. I forget what steps i took but I know that it took me about 2 weeks to get it all working so i'm trying to cut the time on this one down a little... I've followed the guide at http://www.mythtv.org/wiki/index.php/MCE_Remote (it's a slightly different remote but still mce) and running modprobe lirc_mceusb2 then starting lircd works fine, but I can't seem to get it working from boot, always have to kill lircd (if it's started from boot), modprobe then start lircd to get it to work (using irw to test). I've tried various things to get it to work, inc. only starting lirc in run level 5 (no change), starting lirc from a kde autoload script (won't load, think it needs root permisions), changing stuff in /etc/modprobe.conf (originally had alias char-major-61 lirc_i2c under # char dev aliases, and include /etc/modprobe.d include /etc/modprobe.conf.local install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c at the end. i tried changing the i2c bits to mceusb2, using both, using bits of each... ) and I guess between not knowing what i'm doing and not knowing what to do with what i do know, I haven't managed to figure it out over the past few days. So if anyone knows how to get it working properly then I'd love to know... Christopher ================= The Crimea / The Crocketts http://www.inaudible.co.uk ================= |
From: Eli C. <zy...@ve...> - 2006-06-01 23:53:49
|
"Christopher Friend" <chr...@ho...> | Wed, 31 May 2006 12:09:57 +0100 > Firstly, I've already set up a previous remote (hauppauge one) with > lirc_i2c before and it works fine from boot. I forget what steps i > took but I know that it took me about 2 weeks to get it all working > so i'm trying to cut the time on this one down a little... > > I've followed the guide at > http://www.mythtv.org/wiki/index.php/MCE_Remote (it's a slightly > different remote but still mce) and running modprobe lirc_mceusb2 > then starting lircd works fine, but I can't seem to get it working > from boot, always have to kill lircd (if it's started from boot), > modprobe then start lircd to get it to work (using irw to test). > > I've tried various things to get it to work, inc. only starting lirc > in run level 5 (no change), starting lirc from a kde autoload script > (won't load, think it needs root permisions), changing stuff > in /etc/modprobe.conf (originally had > > alias char-major-61 lirc_i2c > > under # char dev aliases, and > > include /etc/modprobe.d > include /etc/modprobe.conf.local > install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install > lirc_i2c > > at the end. i tried changing the i2c bits to mceusb2, using both, > using bits of each... ) > > and I guess between not knowing what i'm doing and not knowing what > to do with what i do know, I haven't managed to figure it out over > the past few days. > > So if anyone knows how to get it working properly then I'd love to > know... I have lirc_mceusb2 working fine without any i2c modules - I am not sure why you would need them. I have nothing about lirc in /etc/modules.conf either (debian sid). I just built the correct module against current kernel source and set lircd to start at boot. Udev, which runs before lircd, detects connected hardware and loads all necessary modules. If you have any further problems, the output of your /var/log/lircd.log or syslog if that's where you configured lirc to log to, would be useful -- Eli C. 2006:06:01 |