[mythtv-users] Jarod's HOWTO for FC3

David Rees drees at greenhydrant.com
Thu Dec 30 02:03:47 UTC 2004

Jarod Wilson wrote:
> I believe you mean /dev/video and /dev/lirc. The OS-provided udev
> rules will take care of creating /dev/videoX when needed, and the
> udev rules listed here...
> http://bugzilla.atrpms.net/show_bug.cgi?id=317
> ...will take care of creating lirc devices.
>> 4. Finally, the instructions for making everything work
>> following a reboot (auto restart) didn't work for me and I ended up
>> putting everything in rc.local (modprobes, ln for /etc/video,
>> lircd, mtd, and mythbackend).
> Yes, that's mentioned at the top of the guide now in the latest news
> part. I'm working on it...

I believe the problem is a bit of a chicken and egg problem.  The
application (mythbackend wants /dev/video[0-9], lircd wants
/dev/lirc[0-9]). Previously when an application would access those
devices, the kernel would see (for example) /dev/lirc0 is mapped to major
61 minor 0, look in /etc/modprobe.conf for char-major-61 and load the
appropriate module.  But with udev the kernel doesn't know that those
applications are probing for those devices as those devices do not exist
until the module is loaded.

If you could get those devices to show up all the time, or manually load
the modules before any applications start, that would solve the clean
reboot problem.

Heh, now that I've thought about it, you can fix this by creating the
appropriate devices in /etc/udev/devices:

# cd /etc/udev.d/devices/
# mknod lirc0 c 61 0
# mknod video0 c 81 0

You may have to create additional devices if you have more than one ivtv
device or a PVR-350 depending on the order mythbackend probes things.


More information about the mythtv-users mailing list