Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
I need some assistance in troubleshooting problem with passing a modprobe parameter to the lirc_zilog module. I'm running Fedora 19 with the most recent updates: # uname -r 3.12.11-201.fc19.x86_64 I have a file /etc/modprobe.d/lirc_zilog.conf file that contains the following: # cat /etc/modprobe.d/lirc_zilog.conf options lirc_zilog tx_only=1 This file previously worked to disable the IR receive mode on the lirc_zilog module but something seems to have changed to prevent this from happening. The above parameter is being ignored since the lirc_zilog module is running both transmit and receive. Here is the command to receive IR signals: #irw 17b5 00 play Hauppauge 17b5 01 play Hauppauge 17b5 02 play Hauppauge The lirc_zilog module is being loaded at system boot time: # lsmod | grep lirc lirc_zilog 22473 0 i2c_core 38476 8 drm,i915,i2c_i801,hdpvr,lirc_zilog,drm_kms_helper,i2c_algo_bit,videodev lirc_dev 19504 1 lirc_zilog rc_core26896 1 lirc_dev The systemd-modules-load.service appears to have completed normally: # systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel ModulesLoaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)Active: active (exited) since Mon 2014-02-24 18:06:33 EST; 1min 46s ago Docs: man:systemd-modules-load.service(8)man:modules-load.d(5) Process: 214 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Feb 24 18:06:32 divo systemd[1]: Starting Load Kernel Modules... The tx_only option is a valid option for lirc_zilog: # modinfo lirc_zilog filename: /lib/modules/3.12.11-201.fc19.x86_64/kernel/drivers/staging/media/lirc/lirc_zilog.ko alias: lirc_pvr150 license:GPL author: Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus, Ulrich Mueller, Stefan Jahn, Jerome Brock, Mark Weaver, Andy Walls description:Zilog/Hauppauge infrared transmitter driver (i2c stack) depends:i2c-core,lirc_dev staging:Y intree: Y vermagic: 3.12.11-201.fc19.x86_64 SMP mod_unload signer: Fedora kernel signing key sig_key:FC:A0:01:2C:8A:A6:A3:A0:0F:CC:4E:16:E4:8C:17:FD:D9:C6:31:21 sig_hashalgo: sha256 parm: minor:Preferred minor device number (int) parm: debug:Enable debugging messages (bool) parm: tx_only:Only handle the IR transmit function (bool) I can manually unload the lirc_zilog module and manually reload lirc_zilog with the tx_only=1 option and lirc_zilog module works as desired with IR receive disabled. I've tried various filenames.conf and the different directories (/lib/modprobe.d) for modprobe without success. If I run dmesg and grep for IR, I see that lirc_zilog is probing for IR Rx and IR Tx. [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C (i2c-8) [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-8) done. Waiting on IR Tx. [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-8) done [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-8) [Mon Feb 24 18:06:34 2014] lirc_zilog: IR unit on Hauppage HD PVR I2C (i2c-8) registered as lirc0 and ready [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-8) done Previously when the tx_only=1 option was being properly processes, the lirc_zilog module was only probing for IR Tx. Looking at the systemd entries from dmesg doesn't give any hints for why the lirc_zilog.conf options file isn't being read. Looking at the output from journalctl -b doesn't provide any clues. I've exhausted my ability to troubleshoot the systemd-modules-load.service to see the details of what is going on during the boot process. I need help with how to enable debug on the systemd-modules-load process or help of where to look next to resolve this issue. Thanks in advance for any assistance you can provide.I think you're saying that if you manually unload the module and then load it the .conf file is honored and loaded as you want.If so, did you run dracut to create a new initramfs with the changes you made?Thanks for your help. You were correct that it was a problem with the kernel needing to be rebuilt after adding/changing files to the /etc/modules-load.d and /etc/modprobe.d directory.Made a copy of the existing /boot/initramfs-$(uname -r).img file and re-ran the command to rebuild the kernel file:# dracut -f /boot/initramfs-$(uname -r).img $(uname -r)I went back and checked the man pages on modules-load.d and modprobe.d and neither mentions having to run dracut or mkinitrd after adding file to these directories. Lesson learned. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct:
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
On 03/01/14 07:14, dennismccl...@earthlink.net wrote: Thanks for your help. You were correct that it was a problem with the kernel needing to be rebuilt after adding/changing files to the /etc/modules-load.d and /etc/modprobe.d directory. Made a copy of the existing /boot/initramfs-$(uname -r).img file and re-ran the command to rebuild the kernel file: # dracut -f /boot/initramfs-$(uname -r).img $(uname -r) I went back and checked the man pages on modules-load.d and modprobe.d and neither mentions having to run dracut or mkinitrd after adding file to these directories. Lesson learned. You're welcome. I don't know where that information may be documented. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
On 02/28/2014 03:23 PM, Ed Greshko issued this missive: On 03/01/14 07:14, dennismccl...@earthlink.net wrote: Thanks for your help. You were correct that it was a problem with the kernel needing to be rebuilt after adding/changing files to the /etc/modules-load.d and /etc/modprobe.d directory. Made a copy of the existing /boot/initramfs-$(uname -r).img file and re-ran the command to rebuild the kernel file: # dracut -f /boot/initramfs-$(uname -r).img $(uname -r) I went back and checked the man pages on modules-load.d and modprobe.d and neither mentions having to run dracut or mkinitrd after adding file to these directories. Lesson learned. You're welcome. I don't know where that information may be documented. It wouldn't be. If the device in question is hot-pluggable, then the act of plugging it in after boot would cause the udev stuff to invoke the modprobe. Since the device isn't hot-pluggable (it's there when you boot the machine), then the module must be loaded in the initrd image to be active at boot. Hence the need to run dracut. As far as I know, this has always been the case. If you need the module at boot, you need to have it in the initrd image. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- -I'm afraid my karma just ran over your dogma- -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
On 03/01/14 08:43, Rick Stevens wrote: It wouldn't be. If the device in question is hot-pluggable, then the act of plugging it in after boot would cause the udev stuff to invoke the modprobe. Since the device isn't hot-pluggable (it's there when you boot the machine), then the module must be loaded in the initrd image to be active at boot. Hence the need to run dracut. As far as I know, this has always been the case. If you need the module at boot, you need to have it in the initrd image. Sure, it probably has been always the case. I don't know how I came to know that. And, I don't know how those who don't know it will come to know it. Apparently, they won't come to know it by reading any available documentation. That is the entirety of my point. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
On 02/28/2014 04:46 PM, Ed Greshko issued this missive: On 03/01/14 08:43, Rick Stevens wrote: It wouldn't be. If the device in question is hot-pluggable, then the act of plugging it in after boot would cause the udev stuff to invoke the modprobe. Since the device isn't hot-pluggable (it's there when you boot the machine), then the module must be loaded in the initrd image to be active at boot. Hence the need to run dracut. As far as I know, this has always been the case. If you need the module at boot, you need to have it in the initrd image. Sure, it probably has been always the case. I don't know how I came to know that. And, I don't know how those who don't know it will come to know it. Apparently, they won't come to know it by reading any available documentation. That is the entirety of my point. Ah, I see. Yes, I don't know that it's documented anywhere that clearly. The old /usr/src/doc/kernel-(version)/Documentation/initrd.txt file sort of describes it as does the man page for dracut. I'm sure I learned it long ago when I started building kernels and drivers for some (at the time) esoteric hardware and now it's self-evident to me. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - I haven't lost my mind. It's backed up on tape somewhere, but - - probably not recoverable.- -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
I need some assistance in troubleshooting problem with passing a modprobe parameter to the lirc_zilog module. I'm running Fedora 19 with the most recent updates: # uname -r 3.12.11-201.fc19.x86_64 I have a file /etc/modprobe.d/lirc_zilog.conf file that contains the following: # cat /etc/modprobe.d/lirc_zilog.conf options lirc_zilog tx_only=1 This file previously worked to disable the IR receive mode on the lirc_zilog module but something seems to have changed to prevent this from happening. The above parameter is being ignored since the lirc_zilog module is running both transmit and receive. Here is the command to receive IR signals: #irw 17b5 00 play Hauppauge 17b5 01 play Hauppauge 17b5 02 play Hauppauge The lirc_zilog module is being loaded at system boot time: # lsmod | grep lirc lirc_zilog 22473 0 i2c_core 38476 8 drm,i915,i2c_i801,hdpvr,lirc_zilog,drm_kms_helper,i2c_algo_bit,videodev lirc_dev 19504 1 lirc_zilog rc_core26896 1 lirc_dev The systemd-modules-load.service appears to have completed normally: # systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Mon 2014-02-24 18:06:33 EST; 1min 46s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 214 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Feb 24 18:06:32 divo systemd[1]: Starting Load Kernel Modules... The tx_only option is a valid option for lirc_zilog: # modinfo lirc_zilog filename: /lib/modules/3.12.11-201.fc19.x86_64/kernel/drivers/staging/media/lirc/lirc_zilog.ko alias: lirc_pvr150 license:GPL author: Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus, Ulrich Mueller, Stefan Jahn, Jerome Brock, Mark Weaver, Andy Walls description:Zilog/Hauppauge infrared transmitter driver (i2c stack) depends:i2c-core,lirc_dev staging:Y intree: Y vermagic: 3.12.11-201.fc19.x86_64 SMP mod_unload signer: Fedora kernel signing key sig_key:FC:A0:01:2C:8A:A6:A3:A0:0F:CC:4E:16:E4:8C:17:FD:D9:C6:31:21 sig_hashalgo: sha256 parm: minor:Preferred minor device number (int) parm: debug:Enable debugging messages (bool) parm: tx_only:Only handle the IR transmit function (bool) I can manually unload the lirc_zilog module and manually reload lirc_zilog with the tx_only=1 option and lirc_zilog module works as desired with IR receive disabled. I've tried various filenames.conf and the different directories (/lib/modprobe.d) for modprobe without success. If I run dmesg and grep for IR, I see that lirc_zilog is probing for IR Rx and IR Tx. [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C (i2c-8) [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-8) done. Waiting on IR Tx. [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-8) done [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-8) [Mon Feb 24 18:06:34 2014] lirc_zilog: IR unit on Hauppage HD PVR I2C (i2c-8) registered as lirc0 and ready [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-8) done Previously when the tx_only=1 option was being properly processes, the lirc_zilog module was only probing for IR Tx. Looking at the systemd entries from dmesg doesn't give any hints for why the lirc_zilog.conf options file isn't being read. Looking at the output from journalctl -b doesn't provide any clues. I've exhausted my ability to troubleshoot the systemd-modules-load.service to see the details of what is going on during the boot process. I need help with how to enable debug on the systemd-modules-load process or help of where to look next to resolve this issue. Thanks in advance for any assistance you can provide. I think you're saying that if you manually unload the module and then load it the .conf file is honored and loaded as you want. If so, did you run dracut to create a new initramfs with the changes you made? No, what I mean by manual reload is the following command: modprobe lirc_zilog tx_only=1 K -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
On 02/25/14 16:42, dennismccl...@earthlink.net wrote: No, what I mean by manual reload is the following command: modprobe lirc_zilog tx_only=1 I just noticed that you said # cat /etc/modprobe.d/lirc_zilog.conf options lirc_zilog tx_only=1 Don't you want simply options tx_only=1 After making that change. Can you manually reload the module with simply modprobe lirc_zilog and have it pick up the options? -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
Never mind options lirc_zilog tx_only=1 is correctSorry, a bit late here. But the question would still remain. Does modprobe lirc_zilog pick up the options? If it does, then I think you will need to recreate the initramfs so these changes are picked up at boot time -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored
On 02/25/14 07:56, dennismccl...@earthlink.net wrote: I need some assistance in troubleshooting problem with passing a modprobe parameter to the lirc_zilog module. I'm running Fedora 19 with the most recent updates: # uname -r 3.12.11-201.fc19.x86_64 I have a file /etc/modprobe.d/lirc_zilog.conf file that contains the following: # cat /etc/modprobe.d/lirc_zilog.conf options lirc_zilog tx_only=1 This file previously worked to disable the IR receive mode on the lirc_zilog module but something seems to have changed to prevent this from happening. The above parameter is being ignored since the lirc_zilog module is running both transmit and receive. Here is the command to receive IR signals: #irw 17b5 00 play Hauppauge 17b5 01 play Hauppauge 17b5 02 play Hauppauge The lirc_zilog module is being loaded at system boot time: # lsmod | grep lirc lirc_zilog 22473 0 i2c_core 38476 8 drm,i915,i2c_i801,hdpvr,lirc_zilog,drm_kms_helper,i2c_algo_bit,videodev lirc_dev 19504 1 lirc_zilog rc_core26896 1 lirc_dev The systemd-modules-load.service appears to have completed normally: # systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Mon 2014-02-24 18:06:33 EST; 1min 46s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 214 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Feb 24 18:06:32 divo systemd[1]: Starting Load Kernel Modules... The tx_only option is a valid option for lirc_zilog: # modinfo lirc_zilog filename: /lib/modules/3.12.11-201.fc19.x86_64/kernel/drivers/staging/media/lirc/lirc_zilog.ko alias: lirc_pvr150 license:GPL author: Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus, Ulrich Mueller, Stefan Jahn, Jerome Brock, Mark Weaver, Andy Walls description:Zilog/Hauppauge infrared transmitter driver (i2c stack) depends:i2c-core,lirc_dev staging:Y intree: Y vermagic: 3.12.11-201.fc19.x86_64 SMP mod_unload signer: Fedora kernel signing key sig_key:FC:A0:01:2C:8A:A6:A3:A0:0F:CC:4E:16:E4:8C:17:FD:D9:C6:31:21 sig_hashalgo: sha256 parm: minor:Preferred minor device number (int) parm: debug:Enable debugging messages (bool) parm: tx_only:Only handle the IR transmit function (bool) I can manually unload the lirc_zilog module and manually reload lirc_zilog with the tx_only=1 option and lirc_zilog module works as desired with IR receive disabled. I've tried various filenames.conf and the different directories (/lib/modprobe.d) for modprobe without success. If I run dmesg and grep for IR, I see that lirc_zilog is probing for IR Rx and IR Tx. [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C (i2c-8) [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-8) done. Waiting on IR Tx. [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-8) done [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-8) [Mon Feb 24 18:06:34 2014] lirc_zilog: IR unit on Hauppage HD PVR I2C (i2c-8) registered as lirc0 and ready [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-8) done Previously when the tx_only=1 option was being properly processes, the lirc_zilog module was only probing for IR Tx. Looking at the systemd entries from dmesg doesn't give any hints for why the lirc_zilog.conf options file isn't being read. Looking at the output from journalctl -b doesn't provide any clues. I've exhausted my ability to troubleshoot the systemd-modules-load.service to see the details of what is going on during the boot process. I need help with how to enable debug on the systemd-modules-load process or help of where to look next to resolve this issue. Thanks in advance for any assistance you can provide. I think you're saying that if you manually unload the module and then load it the .conf file is honored and loaded as you want. If so, did you run dracut to create a new initramfs with the changes you made? -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
