Re: sorta solved: "AVC Status: Unknown state" on recent kernels

	Stefan,
thanks for lightning fast laser guided reply,
as well as for the code!

On Sun, Oct 30, 2011 at 07:38:52PM +0100, Stefan Richter wrote:
> > just for the record: kino-1.3.4 rebuilt against libdc1394 at
> Don't you mean libraw1394 or libacv1394?  And if it is
> libraw1394, which exact version are you using now?

I meant libdc1394-22-2.1.2 (just updated the package to 2.1.3
as well) -- went over Debian package diff looking what could
differ.  But guess they rather looked at ffmpeg/ for that matter,
upon having a closer look.

> > AVC Status: Unknown state
[...]
> > The breakage came after updating from a distribution branch
> > with 2.6.32 based kernel to the current one with 3.0.[68]
> > (there was at least one 2.6.32 out there packaged using the
> > former IEEE1394 stack back then).
> What is the precise type of the camcorder?

Sorry, should have mentioned already.  It's Canon MVX-25i; dmesg:

[  210.747460] firewire_core: skipped bus generations, destroying all nodes
[  211.244078] firewire_core: rediscovered device fw1
[  211.244090] firewire_core: giving up on config rom for node id ffc0
[  214.383938] firewire_core: skipped bus generations, destroying all nodes
[  214.880083] firewire_core: rediscovered device fw1
[  214.880101] firewire_core: phy config: card 1, new root=ffc1, gap_count=5
[  219.907652] firewire_core: created device fw2: GUID 0000850000XXXXXX, S100, 1 config ROM retries

> On October 22, I pushed an update to
> git://git.user.in-berlin.de/s5r6/libraw1394.git which improves
> reliability of AV/C control and status polling with some old
> Panasonic and Grundig camcorder models.
> https://redmine.user.in-berlin.de/projects/libraw1394/repository/revisions/8e433bf58413725365654c27fb4fad0aad88b516

Thanks; is it going to be released relatively soon or should
build the patched package in the meantime?

> However, the sort of camcorders which was affected by the
> issue which is fixed in this commit would be borderline
> non-functional with firewire-core of kernels older than v3.1,
> hence I suspect yours is not one of them.  These camcorders
> need this kernel change which was released in v3.1:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=aaff12039ffd812d0c8bbff50b87b6f1f09bec3e
> (The remaining problems whith these camcorders which are
> mentioned in the changelog of that kernel patch have benn fixed
> now by the above libraw1394 patch.)

The camera *is* showing up in dmesg and /dev/fw* gets there,
kino status line is "AV/C enabled" but the control buttons
get weird -- I can try to elaborate on the description
(probably with a screen video) or dvgrab it if that helps;
the camera will travel again for something like a week since
tomorrow but likely to settle at home after that.

The rewind was essentially not working at all yesterday,
today's fiddling with package rebuilds (the kino binary package
and corresponding libs were built a year ago or so and might
have missed kernel header changes) made rewind sort of work.
Actual capture was working after on-camera "rewind" button
and in-kino "record" button, thus the job was done. :)

Is the "giving up on config rom" appearing above the definite
sign of the problem described in aaff120?  That is, what's up
with that message followed by kino being able to capture?

-- 
 ---- WBR, Michael Shigorin <[email protected]>
  ------ Linux.Kiev http://www.linux.kiev.ua/

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev