udev makes /dev/raw1394, but no module

[sean darcy]

I've been setting up dvgrab to get some dv off my camcorder. I kept 
getting an error message raw1394: no such device.

But /dev/raw1394 did exist, as did dv1394.

The problem was that neither the raw1394 nor dv1394 modules were loaded.

udev should be loading the modules, correct? But why is it creating the 
/dev entries if it's not loading the modules?  Is this a feature, or a 
bug? Does udev only create the dev entries, and the user is supposed to 
load the modules?

sean

[Pete Zaitcev]

On Sat, 24 Dec 2005 16:36:48 -0800, sean darcy <seandarcy2(a)gmail.com&gt; wrote:

>  udev should be loading the modules, correct? But why is it creating
> the 
>  /dev entries if it's not loading the modules?  Is this a feature, or a 
>  bug? Does udev only create the dev entries, and the user is supposed to 
>  load the modules? 
Most likely the modules fail the initialization and return from their
probe() with an error.

-- Pete

[sean darcy]

Pete Zaitcev wrote:
>  On Sat, 24 Dec 2005 16:36:48 -0800, sean darcy
> <seandarcy2(a)gmail.com&gt; wrote:
>  
>  
> >udev should be loading the modules, correct? But why is it creating the 
> >/dev entries if it's not loading the modules?  Is this a feature, or a 
> >bug? Does udev only create the dev entries, and the user is supposed to 
> >load the modules?
>  
>  
>  Most likely the modules fail the initialization and return from their
>  probe() with an error.
>   
Maybe, but modprobe raw1394 works, and does not return any error. In 
fact, the way I've hacked this is just to modprobe the 1394 modules in 
rc.local, which works just fine.

sean

[Ralf Ertzinger]

On Sun, Dec 25, 2005 at 02:49:38PM -0800, sean darcy wrote:

>  Maybe, but modprobe raw1394 works, and does not return any error. In
>
>  fact, the way I've hacked this is just to modprobe the 1394 modules in 
>  rc.local, which works just fine. 
This affects everything FireWire, sdp2 (storage) is not autoloaded, too.
Looks like the firewire driver does not hand out hotplug events anymore.
Manually loading the module works just fine and gets attached drives going.

[sean darcy]

Ralf Ertzinger wrote:
>  On Sun, Dec 25, 2005 at 02:49:38PM -0800, sean darcy wrote:
>  
>  
> >Maybe, but modprobe raw1394 works, and does not return any error. In 
> >fact, the way I've hacked this is just to modprobe the 1394 modules in 
> >rc.local, which works just fine.
>  
>  
>  This affects everything FireWire, sdp2 (storage) is not autoloaded, too.
>  Looks like the firewire driver does not hand out hotplug events anymore.
>  Manually loading the module works just fine and gets attached drives going.
>   
Actually it does. I got this from the kino list:

ieee1394 on kernel 2.6 was not exporting enough information within /sys 
in order to make udev a viable solution to this until kernel 2.6.12. 
There is a simple example udev rules configuration on linux1394.org if 
you have 2.6.12 or newer. However, udev rules can be slightly different


Maybe someone who knows udev could see if these could work for fc5?

sean