[gentoo-user] Re: hotplug doesn't.

[James <wireless@tampabay.rr.com>]

Iain Buchanan <iaindb <at> netspace.net.au> writes:


> hotplug doesn't hotplug!  At least for my 1394 video camera.  If I plug
> the camera in at boot, kino can see it and capture from it (and control
> the AVC), but if I plug it in after boot, kino can't even see it.

> I've tried removing and re-adding the module, I tail the logs, I even
> turned on some debugging for ieee1394.agent, but I basically see
> nothing!

> I tried googling, but the terms are so generic, I can't find anything
> useful.

> Can anyone point me in the right direction?  I would appreciate any
> comments, thanks.

Hello Iain,

I've recently discovered these 2 little jewels. They may not help, but
it's worth a whirl.

# udevstart [after you boot and then connect the device to 1394]

# udevinfo -q all -d | grep <camera>

Also devices(/dev/) can be tarred up and auto read upon reboot, 
even if the hardware is not present by adding this to your  
 /etc/conf.d/rc file:

#RC_DEVICE_TARBALL="no"
RC_DEVICE_TARBALL="yes

This method does not allow udev to discover new devices
upon reboot. I have not delved into this mechanism deeper, but, it
would seem logical that once the device is seen by udev, then you
could tar up these devices and have them added to /dev/ and find
a way to let udev do it's 'auto-discover' upon reboot. Sort of a hybrid
method using both udev's auto-discovery mechanism and 
manually providing a list of hardware to the /dev/ dir.

My experiences with udev, are that it is still very much
'a work in progress'.... weak documentation and scant few
examples....

PS. I'm not even saying that udev is the culprit, but it's always
suspect with low level hardware, in the 2.6 kernel series....


ymmv,
hth,

James





-- 
gentoo-user@gentoo.org mailing list