[opensuse] How to set up LIRC?
Well I am lost, so need a few pointers to get me started... I am running SuSE11.1 and need to get the lirc daemon up an running. Searching around on the internet I get quite a bit of difference information that relates to various other distro's or versions and nothing I can find seem to apply to SuSE. I have use YaST to install all the pertinent packages for LIRC, installed the config files for /etc/lircd.conf and .lircrc in my home directory as I was instructed to do. Most of the documentation I have read seem to imply there should be a device - /dev/lirc but I do not find such. Trying to start the lircd service gives me an error saying as much... So what do I have to do to get the lircd service up an running under SuSE11.1? Much appreciate any and all help offered.. Marc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2009-10-25 at 20:48 -0700, Marc Chamberlin wrote:
Well I am lost, so need a few pointers to get me started... I am running SuSE11.1 and need to get the lirc daemon up an running. Searching around on the internet I get quite a bit of difference information that relates to various other distro's or versions and nothing I can find seem to apply to SuSE. I have use YaST to install all the pertinent packages for LIRC, installed the config files for /etc/lircd.conf and .lircrc in my home directory as I was instructed to do. Most of the documentation I have read seem to imply there should be a device - /dev/lirc but I do not find such. Trying to start the lircd service gives me an error saying as much...
So what do I have to do to get the lircd service up an running under SuSE11.1? Much appreciate any and all help offered..
You'll need the appropriate lircd.conf and lircrc files for the device, as well as the appropriate driver module loaded, so start with the device and look for what driver module it uses. I had LIRC up and running under the PAE kernel, but I've switched to the default kernel and will need to redo some of the steps to get mine up and running again, I'd be glad to help if I can, on the proviso that it stays on the mailing list, so there's actually a SuSE specific LIRC thread that can be googled for later. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mike McMullin wrote:
On Sun, 2009-10-25 at 20:48 -0700, Marc Chamberlin wrote:
Well I am lost, so need a few pointers to get me started... I am running SuSE11.1 and need to get the lirc daemon up an running. Searching around on the internet I get quite a bit of difference information that relates to various other distro's or versions and nothing I can find seem to apply to SuSE. I have use YaST to install all the pertinent packages for LIRC, installed the config files for /etc/lircd.conf and .lircrc in my home directory as I was instructed to do. Most of the documentation I have read seem to imply there should be a device - /dev/lirc but I do not find such. Trying to start the lircd service gives me an error saying as much...
So what do I have to do to get the lircd service up an running under SuSE11.1? Much appreciate any and all help offered..
You'll need the appropriate lircd.conf and lircrc files for the device, as well as the appropriate driver module loaded, so start with the device and look for what driver module it uses. I had LIRC up and running under the PAE kernel, but I've switched to the default kernel and will need to redo some of the steps to get mine up and running again, I'd be glad to help if I can, on the proviso that it stays on the mailing list, so there's actually a SuSE specific LIRC thread that can be googled for later.
Thanks Mike for your offer of help, and I certainly will keep all my responses in this mail list! Ok, I think I have the lircd.conf and lircrc files defined and installed appropriately. (I could follow the instructions for that part easily enough.) But you said two things that kinda went over the top of my head. You asked me to "start with the device and look for what driver module it uses" Not being a real SuSE/Linux guru uh how do I do that? You also mentioned the two different types of kernels, and implied that there will be a need to install/config things for each. I have noted, from time to time, when I use SuSE that the powers that be will suddenly give me a new kernel (I note this when the GRUB menu suddenly changes on me and I see a new menu entry for booting up a different version of SuSE. Such things as Xen, and something else which I can't remember anymore from the more distant past, and now this PAE thing has come along, out of the blue, and apparently decided to become the default version for me to use.) I have no idea what this is, but since it got setup and installed, after one of SuSE's security updates, as my default system to use, I just figure I probably am suppose to use it. GRUB still gives me the original version of SuSE to boot up if I want to, I just don't have any idea whether I should go back to it or not.. And I don't really have extra time to try and learn what PAE is right now... Sigh I need a few clones of me! Sorry if my knowledge of Linux/SuSE is not all that robust, I am learning, but it takes time... Marc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2009-10-26 at 14:45 -0700, Marc Chamberlin wrote:
Mike McMullin wrote:
On Sun, 2009-10-25 at 20:48 -0700, Marc Chamberlin wrote:
Well I am lost, so need a few pointers to get me started... I am running SuSE11.1 and need to get the lirc daemon up an running. Searching around on the internet I get quite a bit of difference information that relates to various other distro's or versions and nothing I can find seem to apply to SuSE. I have use YaST to install all the pertinent packages for LIRC, installed the config files for /etc/lircd.conf and .lircrc in my home directory as I was instructed to do. Most of the documentation I have read seem to imply there should be a device - /dev/lirc but I do not find such. Trying to start the lircd service gives me an error saying as much...
So what do I have to do to get the lircd service up an running under SuSE11.1? Much appreciate any and all help offered..
You'll need the appropriate lircd.conf and lircrc files for the device, as well as the appropriate driver module loaded, so start with the device and look for what driver module it uses. I had LIRC up and running under the PAE kernel, but I've switched to the default kernel and will need to redo some of the steps to get mine up and running again, I'd be glad to help if I can, on the proviso that it stays on the mailing list, so there's actually a SuSE specific LIRC thread that can be googled for later.
Thanks Mike for your offer of help, and I certainly will keep all my responses in this mail list!
Ok, I think I have the lircd.conf and lircrc files defined and installed appropriately. (I could follow the instructions for that part easily enough.) But you said two things that kinda went over the top of my head. You asked me to "start with the device and look for what driver module it uses" Not being a real SuSE/Linux guru uh how do I do that?
I have an Hauppage PVR-150 card with the Grey-350 remote, it requires that the lirc_i2c module be loaded, so the simple question here is what device are you trying to get set up?
You also mentioned the two different types of kernels, and implied that there will be a need to install/config things for each. I have noted, from time to time, when I use SuSE that the powers that be will suddenly give me a new kernel (I note this when the GRUB menu suddenly changes on me and I see a new menu entry for booting up a different version of SuSE. Such things as Xen, and something else which I can't remember anymore from the more distant past, and now this PAE thing has come along, out of the blue, and apparently decided to become the default version for me to use.) I have no idea what this is, but since it got setup and installed, after one of SuSE's security updates, as my default system to use, I just figure I probably am suppose to use it. GRUB still gives me the original version of SuSE to boot up if I want to, I just don't have any idea whether I should go back to it or not.. And I don't really have extra time to try and learn what PAE is right now... Sigh I need a few clones of me!
I'm not a fan of the PAE kernel, I have had too many issues because of it, I've tweaked my /boot/grub/menu.lst file to default to the default kernel. The PAE Kernel has Physical Address Extension support in it, which means that it can access more ram than a normal 32-bit kernel can, amongst other things. Unless you have a non-standard device, and require compiling the driver, it should just update with each kernel release. TO find out which kernel you are using, at a terminal prompt do uname -r. Mike@P-733-Lin:~> uname -r 2.6.27.29-0.1-default I'm using the default kernel, and I need to have the lirc-kmp-default package installed, which isn't going to happen due it's not being in the 11.1-oss update repo.
Sorry if my knowledge of Linux/SuSE is not all that robust, I am learning, but it takes time...
Not a problem,these are issues that I have had to deal with getting my PVR up and running, and like you I know how little good SuSE specific info there is out there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mike McMullin wrote:
On Mon, 2009-10-26 at 14:45 -0700, Marc Chamberlin wrote:
Mike McMullin wrote:
On Sun, 2009-10-25 at 20:48 -0700, Marc Chamberlin wrote:
Well I am lost, so need a few pointers to get me started... I am running SuSE11.1 and need to get the lirc daemon up an running. Searching around on the internet I get quite a bit of difference information that relates to various other distro's or versions and nothing I can find seem to apply to SuSE. I have use YaST to install all the pertinent packages for LIRC, installed the config files for /etc/lircd.conf and .lircrc in my home directory as I was instructed to do. Most of the documentation I have read seem to imply there should be a device - /dev/lirc but I do not find such. Trying to start the lircd service gives me an error saying as much...
So what do I have to do to get the lircd service up an running under SuSE11.1? Much appreciate any and all help offered..
You'll need the appropriate lircd.conf and lircrc files for the device, as well as the appropriate driver module loaded, so start with the device and look for what driver module it uses. I had LIRC up and running under the PAE kernel, but I've switched to the default kernel and will need to redo some of the steps to get mine up and running again, I'd be glad to help if I can, on the proviso that it stays on the mailing list, so there's actually a SuSE specific LIRC thread that can be googled for later.
Thanks Mike for your offer of help, and I certainly will keep all my responses in this mail list!
Ok, I think I have the lircd.conf and lircrc files defined and installed appropriately. (I could follow the instructions for that part easily enough.) But you said two things that kinda went over the top of my head. You asked me to "start with the device and look for what driver module it uses" Not being a real SuSE/Linux guru uh how do I do that?
I have an Hauppage PVR-150 card with the Grey-350 remote, it requires that the lirc_i2c module be loaded, so the simple question here is what device are you trying to get set up?
You also mentioned the two different types of kernels, and implied that there will be a need to install/config things for each. I have noted, from time to time, when I use SuSE that the powers that be will suddenly give me a new kernel (I note this when the GRUB menu suddenly changes on me and I see a new menu entry for booting up a different version of SuSE. Such things as Xen, and something else which I can't remember anymore from the more distant past, and now this PAE thing has come along, out of the blue, and apparently decided to become the default version for me to use.) I have no idea what this is, but since it got setup and installed, after one of SuSE's security updates, as my default system to use, I just figure I probably am suppose to use it. GRUB still gives me the original version of SuSE to boot up if I want to, I just don't have any idea whether I should go back to it or not.. And I don't really have extra time to try and learn what PAE is right now... Sigh I need a few clones of me!
I'm not a fan of the PAE kernel, I have had too many issues because of it, I've tweaked my /boot/grub/menu.lst file to default to the default kernel. The PAE Kernel has Physical Address Extension support in it, which means that it can access more ram than a normal 32-bit kernel can, amongst other things. Unless you have a non-standard device, and require compiling the driver, it should just update with each kernel release. TO find out which kernel you are using, at a terminal prompt do uname -r.
Mike@P-733-Lin:~> uname -r 2.6.27.29-0.1-default
I'm using the default kernel, and I need to have the lirc-kmp-default package installed, which isn't going to happen due it's not being in the 11.1-oss update repo.
Sorry if my knowledge of Linux/SuSE is not all that robust, I am learning, but it takes time...
Not a problem,these are issues that I have had to deal with getting my PVR up and running, and like you I know how little good SuSE specific info there is out there.
Thanks again Mike. You have convinced me, I don't have any investment in the PAE version of the kernel either, so will switch my version back to the default also. OK here is where I am headed with my media center. I have the Hauppauge 350 card in my system which has an IR receiver and also the gray remote. I believe I have the correct configuration for the lirc.conf and lircrc files for it. (I had this from a previous version of SuSE before I upgraded my system to 11.1 and lost almost everything else. So am in the process of trying to reset that up as well.) I also have an IR Blaster with runs off the serial port of the computer. With this, I am going to want to control a Dish Network HD settop box and a Harmon Kardon receiver. So I have run the IR transmitters to the front panel of each, in front of their IR receivers. I have tracked down a set of button code definitions for the Dish Network HD settop box and appended them to the lirc.conf file (where I already have the button code definitions for the Hauppauge 350 remote) I have not yet tracked down the Harmon Kardon codes yet, so I may have to generate them myself later. YaST2 reports that I have the lirc-kmp-default and lirc-kmp-pae packages already loaded. Eventually I will want to hook all this into MythTV. And yes, if I can get all this figured out, perhaps I will take the time to update the SuSE wiki. It appears a lot of this info that is lying around on the internet is way out of date. Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2009-10-27 at 11:40 -0700, Marc Chamberlin wrote:
Mike McMullin wrote:
On Mon, 2009-10-26 at 14:45 -0700, Marc Chamberlin wrote:
Mike McMullin wrote:
On Sun, 2009-10-25 at 20:48 -0700, Marc Chamberlin wrote:
Well I am lost, so need a few pointers to get me started... I am running SuSE11.1 and need to get the lirc daemon up an running. Searching around on the internet I get quite a bit of difference information that relates to various other distro's or versions and nothing I can find seem to apply to SuSE. I have use YaST to install all the pertinent packages for LIRC, installed the config files for /etc/lircd.conf and .lircrc in my home directory as I was instructed to do. Most of the documentation I have read seem to imply there should be a device - /dev/lirc but I do not find such. Trying to start the lircd service gives me an error saying as much...
So what do I have to do to get the lircd service up an running under SuSE11.1? Much appreciate any and all help offered..
You'll need the appropriate lircd.conf and lircrc files for the device, as well as the appropriate driver module loaded, so start with the device and look for what driver module it uses. I had LIRC up and running under the PAE kernel, but I've switched to the default kernel and will need to redo some of the steps to get mine up and running again, I'd be glad to help if I can, on the proviso that it stays on the mailing list, so there's actually a SuSE specific LIRC thread that can be googled for later.
Thanks Mike for your offer of help, and I certainly will keep all my responses in this mail list!
Ok, I think I have the lircd.conf and lircrc files defined and installed appropriately. (I could follow the instructions for that part easily enough.) But you said two things that kinda went over the top of my head. You asked me to "start with the device and look for what driver module it uses" Not being a real SuSE/Linux guru uh how do I do that?
I have an Hauppage PVR-150 card with the Grey-350 remote, it requires that the lirc_i2c module be loaded, so the simple question here is what device are you trying to get set up?
You also mentioned the two different types of kernels, and implied that there will be a need to install/config things for each. I have noted, from time to time, when I use SuSE that the powers that be will suddenly give me a new kernel (I note this when the GRUB menu suddenly changes on me and I see a new menu entry for booting up a different version of SuSE. Such things as Xen, and something else which I can't remember anymore from the more distant past, and now this PAE thing has come along, out of the blue, and apparently decided to become the default version for me to use.) I have no idea what this is, but since it got setup and installed, after one of SuSE's security updates, as my default system to use, I just figure I probably am suppose to use it. GRUB still gives me the original version of SuSE to boot up if I want to, I just don't have any idea whether I should go back to it or not.. And I don't really have extra time to try and learn what PAE is right now... Sigh I need a few clones of me!
I'm not a fan of the PAE kernel, I have had too many issues because of it, I've tweaked my /boot/grub/menu.lst file to default to the default kernel. The PAE Kernel has Physical Address Extension support in it, which means that it can access more ram than a normal 32-bit kernel can, amongst other things. Unless you have a non-standard device, and require compiling the driver, it should just update with each kernel release. TO find out which kernel you are using, at a terminal prompt do uname -r.
Mike@P-733-Lin:~> uname -r 2.6.27.29-0.1-default
I'm using the default kernel, and I need to have the lirc-kmp-default package installed, which isn't going to happen due it's not being in the 11.1-oss update repo.
Sorry if my knowledge of Linux/SuSE is not all that robust, I am learning, but it takes time...
Not a problem,these are issues that I have had to deal with getting my PVR up and running, and like you I know how little good SuSE specific info there is out there.
Thanks again Mike. You have convinced me, I don't have any investment in the PAE version of the kernel either, so will switch my version back to the default also.
I'm sure the guys at SuSE have a good reason for this kernel (other than the commercial offerings).
OK here is where I am headed with my media center. I have the Hauppauge 350 card in my system which has an IR receiver and also the gray remote. I believe I have the correct configuration for the lirc.conf and lircrc files for it. (I had this from a previous version of SuSE before I upgraded my system to 11.1 and lost almost everything else. So am in the process of trying to reset that up as well.)
IIRC the grey remote uses the lirc_i2c module the same as mine does, so it's a question of checking to see if the modules is getting loaded and if not then loading it and setting it to load at boot time. A simple way of finding the module location is to grab a shell and do locate lirc_i2: Mike@P-733-Lin:/var/lib> locate lirc_i2 /lib/modules/2.6.27.19-3.2-pae/updates/lirc_i2c /lib/modules/2.6.27.19-3.2-pae/updates/lirc_i2c/lirc_i2c.ko /lib/modules/2.6.27.29-0.1-pae/weak-updates/updates/lirc_i2c /lib/modules/2.6.27.29-0.1-pae/weak-updates/updates/lirc_i2c/lirc_i2c.ko What I did originally was to cd into the directory with the module file and then lsmod | grep lirc*, then modprobe lirc_i2c and then redid the lsmod (why? well it's really the first time I had to load a module and make sure it loaded every time at boot, so I wanted to see the results as I progressed through this). IIRC insmod lirc_i2c is used to have the module load every time, but I could be wrong, I was following the far ranging advice of google.
I also have an IR Blaster with runs off the serial port of the computer. With this, I am going to want to control a Dish Network HD settop box and a Harmon Kardon receiver. So I have run the IR transmitters to the front panel of each, in front of their IR receivers. I have tracked down a set of button code definitions for the Dish Network HD settop box and appended them to the lirc.conf file (where I already have the button code definitions for the Hauppauge 350 remote) I have not yet tracked down the Harmon Kardon codes yet, so I may have to generate them myself later.
You might want to subscribe to the mythtv mailing list for this info.
YaST2 reports that I have the lirc-kmp-default and lirc-kmp-pae packages already loaded.
So what we really need to do is determine which module drives the remote, and get it loading, so google for the 350 and it's remote to see what lirc module it needs.
Eventually I will want to hook all this into MythTV. And yes, if I can get all this figured out, perhaps I will take the time to update the SuSE wiki. It appears a lot of this info that is lying around on the internet is way out of date.
There are a few on this list using mythtv, and the best resource that I've run across is Charles Philip Chan, who's helped me in the past, and looking back at some older messages, you too, but I didn't see any mention of which module you used for LIRC. Yes, the wiki, I did not find much help in it, updating it would be good. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mike McMullin wrote:
IIRC the grey remote uses the lirc_i2c module the same as mine does, so it's a question of checking to see if the modules is getting loaded and if not then loading it and setting it to load at boot time. A simple way of finding the module location is to grab a shell and do locate lirc_i2:
Mike@P-733-Lin:/var/lib> locate lirc_i2 /lib/modules/2.6.27.19-3.2-pae/updates/lirc_i2c /lib/modules/2.6.27.19-3.2-pae/updates/lirc_i2c/lirc_i2c.ko /lib/modules/2.6.27.29-0.1-pae/weak-updates/updates/lirc_i2c /lib/modules/2.6.27.29-0.1-pae/weak-updates/updates/lirc_i2c/lirc_i2c.ko
Hmmm Mike when I use the locate command it just returns with no output.
What I did originally was to cd into the directory with the module file and then lsmod | grep lirc*, then modprobe lirc_i2c and then redid the lsmod (why? well it's really the first time I had to load a module and make sure it loaded every time at boot, so I wanted to see the results as I progressed through this). IIRC insmod lirc_i2c is used to have the module load every time, but I could be wrong, I was following the far ranging advice of google.
Whoosh! Sometimes Linux can give me a real headache! Ok I attempted to follow your route and here is what happened - nova:/var/lib # lsmod | grep lirc* lirc_atiusb 14692 0 lirc_dev 11068 1 lirc_atiusb usbcore 165556 8 snd_usb_audio,snd_usb_lib,lirc_atiusb,ati_remote,usbhid,uhci_hcd,ehci_hcd nova:/etc/modprobe.d # modprobe lirc_i2c nova:/etc/modprobe.d # lsmod | grep lirc* lirc_i2c 7808 0 lirc_atiusb 14692 0 lirc_dev 11068 2 lirc_i2c,lirc_atiusb i2c_core 29892 18 bttv,lirc_i2c,cx88_vp3054_i2c,cx88xx,dvb_pll,tuner_simple,tda9887,tda8290,msp3400,saa7127,saa7115,tuner,ivtv,i2c_algo_bit,v4l2_common,nvidia,tveeprom,i2c_i801 usbcore 165556 8 snd_usb_audio,snd_usb_lib,lirc_atiusb,ati_remote,usbhid,uhci_hcd,ehci_hcd So far that seems pretty good. I have one question. Will this be persistent? In other words do I have to execute this modprobe command, to load the lirc_i2c module, each time I reboot my computer? If so, is there a script or config file somewhere that specifies what kernel modules are to be loaded on boot up? I Googled around and learned a bit about loading kernel modules but nothing answered this question. Also, how in the world is one suppose to be able to discover what kernel modules are available on a system? This seems like a lot of insider knowledge! Is there a tool (with a GUI to guide a poor soul) that helps a user to configure the kernel with appropriate modules? I am looking at all this output and just shudder at trying to understand all this!
I also have an IR Blaster with runs off the serial port of the computer. With this, I am going to want to control a Dish Network HD settop box and a Harmon Kardon receiver. So I have run the IR transmitters to the front panel of each, in front of their IR receivers. I have tracked down a set of button code definitions for the Dish Network HD settop box and appended them to the lirc.conf file (where I already have the button code definitions for the Hauppauge 350 remote) I have not yet tracked down the Harmon Kardon codes yet, so I may have to generate them myself later.
You might want to subscribe to the mythtv mailing list for this info.
Well further Google attempts and a visit to the LIRC website seemed to indicate that I need another module loaded in the kernel called lirc_serial. However when I tried to load it I got the following surprise - nova:/var/lib # modprobe lirc_serial FATAL: Error inserting lirc_serial (/lib/modules/2.6.27.29-0.1-default/weak-updates/updates/lirc_serial/lirc_serial.ko): Device or resource busy I dunno for sure what I am doing, so consider this as a bad guess on my part? I will keep Googling but wowza am I getting in over my head? Sure seems awfully complicated! If you (or anyone else) got any ideas, I sure could use some....
YaST2 reports that I have the lirc-kmp-default and lirc-kmp-pae packages already loaded.
So what we really need to do is determine which module drives the remote, and get it loading, so google for the 350 and it's remote to see what lirc module it needs.
Didn't I just do that already? With the lirc_i2c module? Or are you referring to something else and perhaps I lost you...
There are a few on this list using mythtv, and the best resource that I've run across is Charles Philip Chan, who's helped me in the past, and looking back at some older messages, you too, but I didn't see any mention of which module you used for LIRC. Yes, the wiki, I did not find much help in it, updating it would be good.
Yes I have been down part of this path before, but it was so long ago I have forgotten what I had done to get the Hauppauge IR receiver working... That coupled with a computer crash that lost all the previous configuration did not help matters any. So yeah I will try to capture as much as I can on the wiki for future reference!!! Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2009-10-27 at 21:36 -0700, Marc Chamberlin wrote:
Mike McMullin wrote:
IIRC the grey remote uses the lirc_i2c module the same as mine does, so it's a question of checking to see if the modules is getting loaded and if not then loading it and setting it to load at boot time. A simple way of finding the module location is to grab a shell and do locate lirc_i2:
Mike@P-733-Lin:/var/lib> locate lirc_i2 /lib/modules/2.6.27.19-3.2-pae/updates/lirc_i2c /lib/modules/2.6.27.19-3.2-pae/updates/lirc_i2c/lirc_i2c.ko /lib/modules/2.6.27.29-0.1-pae/weak-updates/updates/lirc_i2c /lib/modules/2.6.27.29-0.1-pae/weak-updates/updates/lirc_i2c/lirc_i2c.ko
Hmmm Mike when I use the locate command it just returns with no output.
All that means is that it found no matches.
What I did originally was to cd into the directory with the module file and then lsmod | grep lirc*, then modprobe lirc_i2c and then redid the lsmod (why? well it's really the first time I had to load a module and make sure it loaded every time at boot, so I wanted to see the results as I progressed through this). IIRC insmod lirc_i2c is used to have the module load every time, but I could be wrong, I was following the far ranging advice of google.
Whoosh! Sometimes Linux can give me a real headache! Ok I attempted to follow your route and here is what happened -
nova:/var/lib # lsmod | grep lirc*
lirc_atiusb 14692 0 lirc_dev 11068 1 lirc_atiusb usbcore 165556 8 snd_usb_audio,snd_usb_lib,lirc_atiusb,ati_remote,usbhid,uhci_hcd,ehci_hcd nova:/etc/modprobe.d # modprobe lirc_i2c nova:/etc/modprobe.d # lsmod | grep lirc* lirc_i2c 7808 0 lirc_atiusb 14692 0 lirc_dev 11068 2 lirc_i2c,lirc_atiusb i2c_core 29892 18 bttv,lirc_i2c,cx88_vp3054_i2c,cx88xx,dvb_pll,tuner_simple,tda9887,tda8290,msp3400,saa7127,saa7115,tuner,ivtv,i2c_algo_bit,v4l2_common,nvidia,tveeprom,i2c_i801 usbcore 165556 8 snd_usb_audio,snd_usb_lib,lirc_atiusb,ati_remote,usbhid,uhci_hcd,ehci_hcd
So far that seems pretty good. I have one question. Will this be persistent? In other words do I have to execute this modprobe command, to load the lirc_i2c module, each time I reboot my computer? If so, is there a script or config file somewhere that specifies what kernel modules are to be loaded on boot up?
Darn I can't remember if it will or not, so I'll have to go back over that, there is a config file for loading modules, but I have never had to adjust it, either insmod or modprobe deals with that.
I Googled around and learned a bit about loading kernel modules but nothing answered this question. Also, how in the world is one suppose to be able to discover what kernel modules are available on a system? This seems like a lot of insider knowledge! Is there a tool (with a GUI to guide a poor soul) that helps a user to configure the kernel with appropriate modules? I am looking at all this output and just shudder at trying to understand all this!
have a look in /sys/module or /lib/modules/
I also have an IR Blaster with runs off the serial port of the computer. With this, I am going to want to control a Dish Network HD settop box and a Harmon Kardon receiver. So I have run the IR transmitters to the front panel of each, in front of their IR receivers. I have tracked down a set of button code definitions for the Dish Network HD settop box and appended them to the lirc.conf file (where I already have the button code definitions for the Hauppauge 350 remote) I have not yet tracked down the Harmon Kardon codes yet, so I may have to generate them myself later.
You might want to subscribe to the mythtv mailing list for this info.
Well further Google attempts and a visit to the LIRC website seemed to indicate that I need another module loaded in the kernel called lirc_serial. However when I tried to load it I got the following surprise -
nova:/var/lib # modprobe lirc_serial FATAL: Error inserting lirc_serial (/lib/modules/2.6.27.29-0.1-default/weak-updates/updates/lirc_serial/lirc_serial.ko): Device or resource busy
Interesting, I was just redoing this on my 11.1 system and got that exact same message.
I dunno for sure what I am doing, so consider this as a bad guess on my part? I will keep Googling but wowza am I getting in over my head? Sure seems awfully complicated! If you (or anyone else) got any ideas, I sure could use some....
Tell me about it. :( I'm seriously beginning to wish I had written down the step by step I did. I too looked all over Puce and back before getting it to work. (Of course my MythBuntu install did all of that grunt work for me!!!!!!!!!!), all I had to do was start using it.
YaST2 reports that I have the lirc-kmp-default and lirc-kmp-pae packages already loaded.
So what we really need to do is determine which module drives the remote, and get it loading, so google for the 350 and it's remote to see what lirc module it needs.
Didn't I just do that already? With the lirc_i2c module? Or are you referring to something else and perhaps I lost you...
Yes the 350 uses the lirc_i2c module, just like the 150 does. I wasn't sure if that was the case when I said to Google it.
There are a few on this list using mythtv, and the best resource that I've run across is Charles Philip Chan, who's helped me in the past, and looking back at some older messages, you too, but I didn't see any mention of which module you used for LIRC.
Yes, the wiki, I did not find much help in it, updating it would be good.
Yes I have been down part of this path before, but it was so long ago I have forgotten what I had done to get the Hauppauge IR receiver working... That coupled with a computer crash that lost all the previous configuration did not help matters any. So yeah I will try to capture as much as I can on the wiki for future reference!!!
I hear ya, while I may well ditch oS as my primary desktop, there's no reason other people shouldn't benefit from other peoples past experience. My next message will be dealing with the config files. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2009-10-27 at 21:36 -0700, Marc Chamberlin wrote:
Yes I have been down part of this path before, but it was so long ago I have forgotten what I had done to get the Hauppauge IR receiver working... That coupled with a computer crash that lost all the previous configuration did not help matters any. So yeah I will try to capture as much as I can on the wiki for future reference!!!
As far as configuration files are concerned, this is what I have :/etc/sysconfig/lircd ## Path: Hardware/Lirc ## Description: lirc (infrared remote control) configuration ## ServiceRestart: lirc ## Type: string ## Default: "660" # # permissions for /dev/lircd # LIRCD_DEV_PERMISSIONS="660" ## Type: string ## Default: "root:video" # # owner and group for /dev/lircd # LIRCD_DEV_OWNER="root:video" ## Type: string ## Default: "" # # use given driver # LIRCD_DRIVER="" ## Type: string ## Default: "" # # read from given device # LIRCD_DEVICE="" ## Type: string(lirc_bt829,lirc_gpio,lirc_i2c,lirc_it87,lirc_parallel,lirc_sir,ir-kbd-i2c,ir-kbd-gpio) ## Default: "" # # load given lirc driver module # LIRC_MODULE="lirc_i2c" ## Type: string ## Default: "" # # listen for network connections on specified port. # WARNING: don't use this on a machine with an internet # connection as lircd is running as root! # LIRCD_LISTENPORT="" ## Type: string ## Default: "" # # connect lircd to specified host # LIRCD_CONNECT="" ---------------------------------------EOF---------------------------- I'm pretty sure there is an error in this config file: I think LIRCD_DEVICE="" ought to be LIRCD_DEVICE="lirc" also note that "LIRC_MODULE="lirc_i2c"" is where the correct driver module for your remote get's listed. :/etc/lircrc This file contains the actions associated with the button pushed on the remote in the form of: # Program Guide begin prog = mythtv button = Guide config = F2 end # Note that you can have definitions for various programs that support LIRC use. Create a soft link to the this file in your home directory called .lircrc, and any updates to the main file show up for the user. :/etc/lircd.conf This file contains the button return codes in the form of: begin remote name Hauppauge_350 bits 13 flags RC5|CONST_LENGTH eps 30 aeps 100 one 969 811 zero 969 811 plead 1097 gap 114605 toggle_bit 2 begin codes Go 0x00000000000017bb Power 0x00000000000017bd TV 0x000000000000179c Mike@P-733-Lin:/etc> ls -l lirc -rw-r--r-- 1 root root 12613 2009-08-15 02:16 lircd.conf -rw-r--r-- 1 root root 9010 2009-08-15 02:18 lircrc Now with all of this in place you need to start the LIRC daemon as root service lirc start, and it should return P-733-Lin:/etc # service lirc start Starting lircd (lirc) done service lirc status Checking for service lircd running Well Mark this is what I have, at this point I ought to be able to invoke irw in a terminal and pointing the remote at the receiver, get button presses back, telling me that my configs are good, and I'm ready to go. (If only reality matched expectation) Sorry that it has taken a couple of months, I got sucked into a few gotta get it done now projects and this fell by the wayside. FWIW, I thought I would install 11.2 and go through the steps again, but the modules seems to have symbols in them that cause insmod to tell me that they (lirc_serial and lirc_i2c) are not loadbable. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Mike McMullin (mwmcmlln@mnsi.net) [20091027 11:00]:
I'm using the default kernel, and I need to have the lirc-kmp-default package installed, which isn't going to happen due it's not being in the 11.1-oss update repo.
KMPs don't necessarily have to change, so I'd try the kmp for 11.0 if that exists. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2009-10-29 at 13:02 +0100, Philipp Thomas wrote:
* Mike McMullin (mwmcmlln@mnsi.net) [20091027 11:00]:
I'm using the default kernel, and I need to have the lirc-kmp-default package installed, which isn't going to happen due it's not being in the 11.1-oss update repo.
KMPs don't necessarily have to change, so I'd try the kmp for 11.0 if that exists.
Actually I tried the KMP from the 11.1 install media and it was not compatible, fortunately the repo issue resolved itself (thanks SuSE guys), and i got it installed, now to get it properly reading the device under irw. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Marc Chamberlin (marc@marcchamberlin.com) [20091026 22:45]:
and now this PAE thing has come along, out of the blue, and apparently decided to become the default version for me to use.)
PAE hasn't sudenly come out but has been there for quite some time, see http://en.wikipedia.org/wiki/Physical_Address_Extension for an explanation. In short, PAE is a means to address more than 4GB of memory on 32 bit machines. That also includes machines with only 4GB but part of it remapped to Addresses beyond 4GB because of the PCI address space. Those machines need the PAE kernel in order to make use of all memory. BTW, X86-64 kernels have that feature enbled all the time so there is no need for a special version. Philipp PS Could you both *please* seriously cut down the amount of mail you're quoting? More then tree levels of quoting IMO show that somebody is too lazy to properly edit his replies. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philipp Thomas wrote:
BTW, X86-64 kernels have that feature enbled all the time so there is no need for a special version.
Why would they enable something they don't need? An x86-64 kernel runs only on an x86-64 CPU, where such tricks aren't needed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* James Knott (james.knott@rogers.com) [20091029 13:29]:
Why would they enable something they don't need? An x86-64 kernel runs only on an x86-64 CPU, where such tricks aren't needed.
You seem to forget the 32bit emulation of x86_64 processors. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philipp Thomas wrote:
* James Knott (james.knott@rogers.com) [20091029 13:29]:
Why would they enable something they don't need? An x86-64 kernel runs only on an x86-64 CPU, where such tricks aren't needed.
You seem to forget the 32bit emulation of x86_64 processors.
No I haven't. The 32 bit mode is for running the 32 bit kernels. The 64 bit kernels run 64 bits and don't need PAE. PAE was a hack to get around the address limitation of a 32 bit CPU. The amount of memory a 64 bit CPU can handle is more than 4 billion times greater than what a 32 bit CPU can do. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* James Knott (james.knott@rogers.com) [20091029 14:54]:
Philipp Thomas wrote: No I haven't. The 32 bit mode is for running the 32 bit kernels.
No, it's also for running 32 bit *applications*.
64 bit kernels run 64 bits and don't need PAE. PAE was a hack to get around the address limitation of a 32 bit CPU. The amount of memory a 64 bit CPU can handle is more than 4 billion times greater than what a 32 bit CPU can do.
I should have been more precise, sorry. x86-64 *processors* always support PAE, as documented in this abbr. contents of /proc/cpuinfo of an AMD quad core: processor : 3 vendor_id : AuthenticAMD [...] flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca ^^^ cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt And this is because it must be able to run PAE kernels. The x86_64 kernel does not need that 36 bit addressing as they support 64 bit addressing (allthough current AMD cpu's only offer 48 bit physical address bits). Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philipp Thomas wrote:
* James Knott (james.knott@rogers.com) [20091029 14:54]:
Philipp Thomas wrote: No I haven't. The 32 bit mode is for running the 32 bit kernels.
No, it's also for running 32 bit *applications*.
64 bit kernels run 64 bits and don't need PAE. PAE was a hack to get around the address limitation of a 32 bit CPU. The amount of memory a 64 bit CPU can handle is more than 4 billion times greater than what a 32 bit CPU can do.
I should have been more precise, sorry. x86-64 *processors* always support PAE, as documented in this abbr. contents of /proc/cpuinfo of an AMD quad core:
processor : 3 vendor_id : AuthenticAMD [...] flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca ^^^ cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
And this is because it must be able to run PAE kernels. The x86_64 kernel does not need that 36 bit addressing as they support 64 bit addressing (allthough current AMD cpu's only offer 48 bit physical address bits).
Philipp
James, Philipp - This seems to be a different subject, perhaps a new thread should be started? Marc Chamberlin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
James Knott -
Marc Chamberlin -
Mike McMullin -
Philipp Thomas