Bug 10304 - 3: lircd could not get file information for /dev/lirc0
Summary: 3: lircd could not get file information for /dev/lirc0
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Anssi Hannula
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-27 02:19 CEST by Bit Twister
Modified: 2015-03-31 16:09 CEST (History)
2 users (show)

See Also:
Source RPM: lirc-0.9.0-9.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2013-05-27 02:19:41 CEST
Description of problem:

/usr/sbin/lircd could not get file information for /dev/lirc0

# systemctl status lircd

lircd.service - LIRC Infrared Signal Decoder
          Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled)
          Active: active (running) since Sun, 2013-05-26 18:31:16 CDT; 15min ago
         Process: 10310 ExecStart=/usr/sbin/lircd --driver=default --device=/dev/lirc0 (code=exited, status=0/SUCCESS)
        Main PID: 10311 (lircd)
          CGroup: name=systemd:/system/lircd.service
                  รข 10311 /usr/sbin/lircd --driver=default --device=/dev/lirc0

     : accepted new client on /var/run/lirc/lircd
     : could not get file information for /dev/lirc0
     : default_init(): No such file or directory
     : Failed to initialize hardware
     : removed client

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. urpmi lirc
2. systemctl start lircd.service
3. systemctl status lircd.service

Guessing kernel/drivers/media/IR/lirc_dev.ko and 
kernel/drivers/staging/lirc/lirc_serial.ko
were not created/installed which create /dev/lirc files/links upon boot.

# ls -al /var/run/lirc
total 4
drwxr-xr-x  2 root root  80 May 26 18:31 .
drwxr-xr-x 33 root root 960 May 26 19:01 ..
srw-rw-rw-  1 root root   0 May 26 18:31 lircd
-rw-r--r--  1 root root   6 May 26 18:31 lircd.pid


# ls -al /dev/lirc*
ls: cannot access /dev/lirc*: No such file or directory



Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-28 19:37:22 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => anssi.hannula

Comment 1 Doug Laidlaw 2013-06-09 13:05:16 CEST
kernel/drivers/staging/lirc/lirc_serial.ko.xz exists on my system.

My mobo doesn't have an IRC contact.  The dealer sold me a gaming computer without asking me what I wanted.

CC: (none) => laidlaws

Comment 2 Bit Twister 2013-06-09 13:17:03 CEST
(In reply to Doug Laidlaw from comment #1)
> kernel/drivers/staging/lirc/lirc_serial.ko.xz exists on my system.

They exists on my system also. The question I have, are the actual modules supposed to be .ko.xz or .ko that are loaded by the system?

# lsmod | grep lirc
#
Comment 3 Doug Laidlaw 2013-06-09 15:03:04 CEST
(In reply to Bit Twister from comment #2)
> (In reply to Doug Laidlaw from comment #1)
> > kernel/drivers/staging/lirc/lirc_serial.ko.xz exists on my system.
> 
> They exists on my system also. The question I have, are the actual modules
> supposed to be .ko.xz or .ko that are loaded by the system?
> 
> # lsmod | grep lirc
> #

That, I can't answer.  Can a zipped module be loaded?  One link has "Note: lirc_serial.ko ..." None say what the actual module should be, but rpmfind links say that Mga2 kernel rpm has lirc_serial.ko.xz.  In my case, mplayer has always said that it can't load the lirc modules.  With nothing to drive, I took that as normal.

Just trying to narrow the inquiry.  You know more than I do.
Comment 4 Bit Twister 2013-06-16 18:48:58 CEST
(In reply to Bit Twister from comment #0)
> Description of problem:
> 
> /usr/sbin/lircd could not get file information for /dev/lirc0

Workaround Solution:
create /etc/modules-load.d/lirc.conf with
lirc_dev
lirc_serial

I also made the /usr/lib/udev/rules.d/lirc.rules change defined in bug 10537
Bit Twister 2014-01-18 16:36:33 CET

CC: (none) => junknospam

Comment 5 Marja Van Waes 2015-03-31 16:03:22 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 6 Doug Laidlaw 2015-03-31 16:09:01 CEST
My computer does not have an IR connector, so this bug doesn't affect me.

Note You need to log in before you can comment on or make changes to this bug.