Make modules for non detected hardware automatically load at boot (udev?)

Jarod Wilson jwilson at redhat.com
Thu Feb 21 02:24:46 UTC 2008


On Wednesday 20 February 2008 05:43:51 pm Jakub 'Livio' Rusinek wrote:
> Jarod Wilson pisze:
> > On Wednesday 20 February 2008 05:04:16 pm Jakub 'Livio' Rusinek wrote:
> >> I think I should do the same (modify init script) for LIRC, since now I
> >> start it with /etc/rc.local...
> >
> > Why do you start it from rc.local? It works just fine for me if I start
> > it from its initscript. Of course, that's for usb receivers, which have
> > proper modaliases set up, so the drivers auto-load properly... I do
> > vaguely recall writing a little /etc/sysconfig/modules/lirc.modules
> > thingy to auto-load lirc drivers if specified in modprobe.conf... (i.e.,
> > 'alias char-major-61 lirc_i2c' in modprobe.conf would lead to lirc_i2c
> > auto-loading). But certainly, loading from rc.local isn't necessary. But
> > really, I think the best place to fix this is in the lirc drivers
> > themselves. Oh, hrm, serial receivers... Crap. Never mind.
> >
> > But anyhow, I'm a co-maintainer on the lirc packages, and maintain the
> > lirc patches carried in the Fedora kernel, so please keep me in the loop.
> > :)
>
> I need ir-kbd-i2c until LIRC is started. Otherwise, my remote control
> doesn't work.
>
> I'm using remote of my tv card [bttv].

I don't quite follow... You need ir-kbd-i2c *until* lirc is started? Then what 
do you do? Unload it? Or do you mean you need the ir-kbd-i2c module loaded 
*before* lirc is started?

-- 
Jarod Wilson
jwilson at redhat.com




More information about the devel mailing list