[gentoo-user] hotplug doesn't.

[gentoo-user] hotplug doesn't.

[Iain Buchanan]

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.
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Underlying Principle of Socio-Genetics:
	Superiority is recessive.

-- 
gentoo-user@gentoo.org mailing list

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

[James]

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

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

[Iain Buchanan]

On Tue, 2006-07-04 at 14:41 +0000, James wrote:
> Iain Buchanan <iaindb <at> netspace.net.au> writes:
> 
> 
> > hotplug doesn't hotplug!
> 
> 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>

thanks! that did the trick - this may not be the right way, but at least
it works:

1. unplug camera
2. unload all ieee / 1394 modules (may I don't need to do all, but I did
anyway).  iee1394 couldn't be unloaded without first unloading raw1394.
3. load raw1394 and dv1394
4. run udevstart
5. plug in camera

eg:

$ sudo modprobe -r dv1394 raw1394 ohci1394 ieee1394 
$ lsmod | grep 1394
$ sudo modprobe raw1394 
$ sudo modprobe dv1394 
$ sudo udevstart 
$ sudo kino

thanks,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

To avoid criticism, do nothing, say nothing, be nothing.
		-- Elbert Hubbard

-- 
gentoo-user@gentoo.org mailing list