http://bugzilla.novell.com/show_bug.cgi?id=515040 Summary: How to start lircmd properly? Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: revealed@freakmail.de QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-5.2 Firefox/3.0.11 Hello there! First: I got a Haupauge PVR150; (No MCE); Remote is: A415 (Hauppauge); I am able to use the TV-Card very well, together with: - ivtv <- SuSE rpm's - tv-viewer <- (Program for watching TV, etc. ) [Not available as SuSE (rpm)] http://sourceforge.net/projects/tv-viewer I wanted to use all features of LIRC, too. There is a problem with IVTV of SuSE rpm's. - There seems to be no firmware for PVR 150 remote included. - Firmware for card itselves is definitively included and working fine. So i had to get it from another resource. So here is the first question: Can the Firmware for the PVR 150 remote be included into IVTV SuSE packing? This would be very Helpful in any case!! :) So i wanted to: Change channels and use all the buttons. With SuSE RPM of LIRC there was no chance in doing this. But i am very lucky, that there is a speciel CVS version of LIRC which makes it possible. Here you can find the CVS Version: http://www.blushingpenguin.com/mark/blog/?p=24 But... This version doesnt offer a convinient way to start LIRC. So i got me the SuSE RPM and used the contained rclirc to start LIRC. This works pretty well itselves. I also put symlinks to fit the binarys that it complies the same way with SuSE rpm. Also i added missing files like the sysconfig script manually. So i can start the CVS version of LIRC. :) And i can use the remote together with TV-Viewer to change volume and channels. Question one: I am wondering if it was possible to have the new PVR150 compatibility layer of the CVS packet from the link provided above implementend into SuSE's LIRC package. As i know that this is working ???? Next step for me was to try lircmd: LIRCMD is a daemon which makes it possible to control the desktop like using a mouse via a remote control. I had to add a new mouse section to xorg.conf. This was relatively easy. It simulates a mouse with IntelliMouse protocol in my case. Here is the problem.. or am i wrong? Is it an implementation issue? Dont blame me if it relies on the CVS version. I am using the SuSE RPM rclirc to start the LIRC functions. But there is no way offered to start LIRCMD properly. It has to be started prior to detection of mouse devices as there has to be an: /dev/lircm existant which is being created by the lircmd daemon. Else you will find errors in Xorg.0.log like: /dev/lircm doesnt exist. So i altered the RCSCRIPT from the SuSE rpm to start before acpid. This fixes this issue for me. And as there dont seem to be any functions existing within SuSE rcscript to start lircmd. I added them. So the second question is. How is this LIRCMD thing started correctly with SuSE rpm? Maybe there is a more efficent easyer way than the one i did? I will provide a diff here, what i did. This made it work for me: (In case there is no easyer way.) I am no profession. But i would be happy to at least offer a proposal for implementation, if it is possible to have this included? :) --- lirc.suse 2009-06-21 19:49:12.000000000 +0200 +++ lirc.neu 2009-06-21 19:48:21.000000000 +0200 @@ -13,10 +13,12 @@ # ### BEGIN INIT INFO # Provides: lirc -# Required-Start: $remote_fs -# Required-Stop: $remote_fs -# Default-Start: 3 5 +# Default-Start: 3 4 5 # Default-Stop: 0 1 2 6 +# Required-Start: +# Required-Stop: +# X-Start-Before: acpid +# X-Stop-After: # Short-Description: lirc daemon # Description: The main task of lircd is to decode the infrared # signals and provide an uniform interface for client applications @@ -24,13 +26,23 @@ # Check for missing binaries (stale symlinks should not happen) lircd_BIN=/usr/sbin/lircd +lircmd_BIN=/usr/sbin/lircmd +lircmd_flag="/etc/lircmd.conf" + test -x $lircd_BIN || exit 5 +test -x $lircmd_BIN || exit 5 # Check for existence of needed config file and read it lircd_CONFIG=/etc/sysconfig/lirc test -r $lircd_CONFIG || exit 6 $lircd_CONFIG +# Check for lircmd config to be available +lircmd_CONFIG=/etc/lircmd.conf +test -r $lircmd_CONFIG || { echo "$lircmd_CONFIG not existing"; + if [ "$1" = "stop" ]; then exit 0; + else exit 6; fi; } + # Source LSB init functions # providing start_daemon, killproc, pidofproc, # log_success_msg, log_failure_msg and log_warning_msg. @@ -142,7 +154,8 @@ ## Start daemon with startproc(8). If this fails ## the return value is set appropriately by startproc. eval startproc $lircd_BIN $(makeargs) - + ## Start the lircmd as daemon (default) (no evaluation) + $lircmd_BIN $lircmd_flag # Remember status and be verbose rc_status -v ;; @@ -152,6 +165,7 @@ ## killproc sets the return value according to LSB. killproc -TERM $lircd_BIN + killproc -TERM $lircmd_BIN # Remember status and be verbose rc_status -v @@ -181,6 +195,7 @@ echo -n "Reload service lircd " ## if it supports it: killproc -HUP $lircd_BIN + killproc -HUP $lircmd_BIN #touch /var/run/lircd.pid rc_status -v @@ -195,6 +210,7 @@ # If it supports signaling: echo -n "Reload service lircd " killproc -HUP $lircd_BIN + killproc -HUP $lircmd_BIN #touch /var/run/lircd.pid rc_status -v @@ -217,6 +233,7 @@ # NOTE: checkproc returns LSB compliant status values. checkproc $lircd_BIN + checkproc $lircmd_BIN # NOTE: rc_status knows that we called this init script with # "status" option and adapts its messages accordingly. rc_status -v I hope i could tell you to the point of my questions. My English is not the best. Many thanks for your time and Help in forward! Greetings, Reproducible: Always Steps to Reproduce: 1.Install IVTV for PVR150 2. Install LIRC 3. Try using lircmd Actual Results: LIRCMD seems to not be implemented in startupconfiguration of SuSE 11.1. Expected Results: Hauppauge PVR150 working out of the Box. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.