View previous topic :: View next topic |
Author |
Message |
tyrael n00b
Joined: 03 Jul 2003 Posts: 35
|
Posted: Fri Sep 05, 2003 5:10 am Post subject: Problem with a lircd-runscript |
|
|
Hi all !
I have a small problem with a runscript and lircd: I need to get 'lircd' loaded at boot, so i wrote the following script and added it to the default runlevel:
Quote: |
#! /sbin/runscript
start() {
ebegin "Starting lircd"
/usr/local/sbin/lircd
eend $? "Error: Can't start lircd."
}
stop() {
ebegin "Stopping lircd"
kill $(cat /var/run/lircd.pid)
eend $? "Error: Can't stop lircd."
}
|
Everything works fine now, my tv tuner's remote control works and I can control my tv software with it. But everytime the system boots, I get (directly after having lircd loaded succesfully):
Quote: |
modprobe: Can't locate module /dev/lircd
|
I can't imagine why it's trying to find a module '/dev/lircd' ... is anything wrong with my script above ? I can't find from where it wants to start that 'module' ... if i delete lircd from default runlevel and start it manually after boot, no modprobe error comes up.
I'm using Gentoo 1.4 release with lircd 0.6.6 (had to build it manually to configure it before compiling).
Does anyone have an idea how to get rid of that ?
Thanks |
|
Back to top |
|
|
vrih n00b
Joined: 05 Dec 2002 Posts: 69 Location: London, England
|
Posted: Fri Sep 05, 2003 9:51 am Post subject: |
|
|
you need to add have --device ${Path to your IR device}. This is what I use
Code: | #!/sbin/runscript
# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
depend()
{
need net
}
start()
{
ebegin "Starting lircd"
start-stop-daemon --start --quiet --exec /usr/sbin/lircd -- --device /dev/lirc/0
eend $?
}
stop()
{
ebegin "Stopping lircd"
start-stop-daemon --stop --quiet --exec /usr/sbin/lircd
eend $?
}
|
|
|
Back to top |
|
|
tyrael n00b
Joined: 03 Jul 2003 Posts: 35
|
Posted: Fri Sep 05, 2003 3:10 pm Post subject: |
|
|
I tested your script, and my remote control still works fine (although i had to replace the device with '/dev/lirc', i guess you're using a 2.6-kernel?). But i still get the modprobe error on boot. I don't think it's a real device problem, as it wants to load a MODULE called '/dev/lircd'. How can i find where this 'module' is requested to load ? |
|
Back to top |
|
|
tyrael n00b
Joined: 03 Jul 2003 Posts: 35
|
Posted: Sat Sep 06, 2003 1:48 am Post subject: |
|
|
errrm ... I just solved my problem, it's really weird: After emerging cups and adding it to the default runlevel, the modprobe error disappeared. I tested that again ... If I delete cups from the default level, it's coming up again!
Ok .. problem solved. But: how does cupsd influence the execution of my lircd-script ? there are no dependencies between them ...
I would be glad if someone could explain that ... |
|
Back to top |
|
|
|