Thanks for the feedback, I greatly appreciate it.<br><br>Can you attach you .modules files for reference.<br><br>I am in fact using a PVR-150 (ivtv).<br><br>I already had a lirc.modules file; but I added a ivtv.modules file.<br><br>I also removed:<br><br>alias char-major-61 lirc_i2c<br> install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c<br><br>from the modprobe.conf file; not sure if I should have.<br><br>I rebooted and there is still no /dev/lirc0<br><br>Any other things to try?<br><br><b><i>Nick Morrott <knowledgejunkie@gmail.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On 26/05/07, Tye Newman <newman_t@sbcglobal.net> wrote:<br>> Thanks for the suggestions.<br>><br>> I have done the following:<br>><br>> Moved all the lirc stuff to the top of modprobe.conf<br>> Changed the permissions on /etc/udev/lirc.rules so anyone can access
it.<br>> Manually started lirc by entering /sbin/service lircd start<br>> It returned with OK<br>> I viewed /dev/li* and found /dev/lircd and /dev/lirc0<br>> entered irw and things worked great. Load MythTV work there too.<br>><br>> Rebooted the system and things stoped working again.<br>><br>> I have lsmod and it shows lirc_i2c and lirc_dev<br><br>Good<br><br>> I then tried:<br>><br>> ADDED: (to rc.local)<br>><br>> /sbin/rmmod lirc_dev<br>> /sbin/modprobe lirc_dev<br><br>lirc_dev is not the key LIRC module for your device, that is lirc_i2c.<br>You should normally use 'modprobe -r' instead of rmmod to remove a<br>module.<br><br>> /usr/sbin/lircd --device=/dev/lirc0<br><br>Good.<br><br>> Rebooted, no luck.<br>> I then REMOVED the above lines.<br>><br>> Here is a view of my lirc.rules<br>><br>> KERNEL=="lirc[0-9]*", NAME="lirc%n"<br>> KERNEL=="lirc0", SYMLINK="lirc"<br><br>Good.<br><br>> I am totally
confused. How can it work, then after reboot stop working.<br>><br>> I am currently starting lirc manually after reboot (/sbin/service...) and<br>> testing it with irw.<br>><br>> Also, how do I modify the $PATH so I don't have to enter /sbin/... for<br>> commands such as lsmod; and could this be part of the problem.<br><br>If you are not logged in as root, /sbin/ will probably not be in your path.<br><br>> HELP PLEASE!<br><br>Getting LIRC running well seems to create problems for a lot of users.<br>On Fedora, I would suggest you do the following (at least, this is<br>what I do):<br><br>i) Create a file called /etc/sysconfig/modules/lirc.modules containing<br>the following line<br><br>modprobe <LIRC_MODULE_NAME><br><br>This file is read at every boot, and any modprobe commands are run<br>automatically. It also means that modules are loaded before the<br>services that depend on them, such as lircd.<br><br>NOTE:<br><br>If you are using a LIRC module that
requires another module loaded<br>beforehand (like ivtv if using a PVR card with the lirc_i2c module)<br>you can either create another file called<br>/etc/sysconfig/modules/ivtv.modules (the name of the file needs to be<br>alphabetically less than the name of the lirc.modules file) containing<br>a 'modprobe ivtv' to preload the ivtv module, OR you can update the<br>/etc/modprobe.conf file to have ivtv automatically loaded whenever the<br>LIRC module is.<br><br><br>ii) Have the lircd service start at boot - to do this, as root run<br><br># chkconfig --level 345 lircd on<br><br>To check it is set to start at boot, run<br><br># chkconfig --list lircd<br><br>This will list each run level and whether lircd is set automatically start.<br><br>iii) Reboot. You should find that your LIRC modules are automatically<br>loaded (lirc_dev plus the module for your specific device) and that<br>you have the /dev/lirc0 device and /dev/lirc symlink created. Starting<br>the lircd service
automatically at boot should also create the<br>/dev/lircd socket, and at this point irw - and your remote - should<br>work.<br><br><br>Note that you *do not* have to have the LIRC modules listed first in<br>/etc/modprobe.conf. Also, when Geoff mentioned altering the<br>permissions for the LIRC udev rules, he meant altering the rules<br>themselves, rather than updating the permissions on the actual rules<br>file itself (I can't tell which of these you did above).<br><br>-- <br>Nick<br><br>MythTV Official wiki:<br>http://mythtv.org/wiki/<br>MythTV users list archive:<br>http://www.gossamer-threads.com/lists/mythtv/users<br><br>"An investment in knowledge always pays the best interest." - Benjamin Franklin<br>_______________________________________________<br>mythtv-users mailing list<br>mythtv-users@mythtv.org<br>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users<br></LIRC_MODULE_NAME></newman_t@sbcglobal.net></blockquote><br>