http://qa.mandrakesoft.com/show_bug.cgi?id=2851
------- Additional Comments From [EMAIL PROTECTED] 2003-03-06 18:45 ------- I'm using the default driver with the hardware driver lirc_i2c. This is a PV951 board which is bt878 based. Some more possibly relevant information from dmesg: lirc_dev: IR Remote Control driver registered, at major 61 lirc_i2c: probe 0x1a @ bt848 #0: no lirc_i2c: probe 0x18 @ bt848 #0: no lirc_i2c: probe 0x4b @ bt848 #0: yes lirc_i2c: chip found @ 0x4b (PV951 IR) lirc_dev (lirc_i2c[0]): poll thread started lirc_dev: plugin lirc_i2c registered at minor number = 0 lirc_i2c: probe 0x64 @ bt848 #0: no lirc_i2c: probe 0x30 @ bt848 #0: no ------- 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: UNCONFIRMED 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.
