http://qa.mandrakesoft.com/show_bug.cgi?id=2851
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2003-11-12 12:56 -------
Suprisingly, that did the trick. I wasn't aware that nodes stuck around with
devfs. From my previous experiences in the 2.3.x days writing the devfs patches
for the nVidia driver, devfs created _everything_ on the fly as required. I
guess this has changed. Sorry to carry this fault on longer than needed. All
is working now.
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I
am taking
a stab in the dark and assuming that because I run a system with devfs that the module
is not
creating the devfs entry.
Changing /etc/sysconfig/lircd from:
(this results in lircmd and crew not being able to communicate with the kernel space
portion of
this and hence all the problems that arrise from that)
# The device node that communicates with the IR device.
# with devfs enabled
DEVICE=/dev/lirc/0
# without devfs
#DEVICE=/dev/lirc
To:
# The device node that communicates with the IR device.
# with devfs enabled
#DEVICE=/dev/lirc/0
# without devfs
DEVICE=/dev/lirc
Fixes the problem and all other remaining mdk packages work as expected (tested with
irw
and xawtv). I've banged my head about this one for a month or so now since getting my
new
PV951 tuner card and just decided to have another dig at it. Hopefully this will get
fixed for the
final release.
