Mailinglist Archive: opensuse (818 mails)

< Previous Next >
[opensuse] howto get details of 1394 (firewire) device creation on camera plug-in (need BASH test)
Guys,

Working with dvgrab and a firewire link to download digital video, I have run into a problem on camera plug-in to the computer. Sometimes the firewire device is created properly and video downloads fine. Other times, the device is created and is able to control the camera, but cannot download video. Unplugging and replugging the cable in usually cures it. The kernel message for the bad plug-in is:

Sep 24 21:21:18 archangel kernel: [2111415.165895] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
Sep 24 21:21:18 archangel kernel: [2111415.800050] firewire_core: created device fw1: GUID 08004601017ede99, S100

For the successful plug-in, you get:

Sep 24 21:33:54 archangel kernel: [2112171.169381] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
Sep 24 21:33:57 archangel kernel: [2112174.926294] firewire_core: created device fw1: GUID 08004601017ede99, S100, 1 config ROM retries

Note the "1 config ROM retries" appended to the 'fw1' device creation when the plug-in goes correctly.

I don't understand what this is or what it means, but I do need to devise a way to test for a successful plug-in from within a BASH script. Now, granted, it is simple enough to grep the message log and look for "1 config ROM retries" within a reasonable time after the plug in, but I know that is a hack...

When the device is created, where does it go in the /proc tree? How best to test and what to test for the correct creation of the ROM entries before beginning the dvgrab? Anybody run into this before?

--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups