From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org,
For users of Fedora Core releases <fedora-list@redhat.com>
Subject: raw1394 problems galore
Date: Sun, 15 Oct 2006 21:23:29 -0400 [thread overview]
Message-ID: <4532DF11.9060704@verizon.net> (raw)
Greetings all;
After about 4 days of snooping around trying to get kino, either 08.xx
or 0.9.2, to run here, I'm getting noplace at a very high rate of speed.
System is an HP dv5120us lappy, with ddual boot of xp and FC5, with FC5
about as uptodate as can be managed when the kmod stuff is always 1 or 2
versions behind the kernel, so I'm still running 2.6.17-1.2174_FC5 for a
kernel.
Specifically, kino-0.8.0-2.lvn5.i386.rpm can receive and record a/v from
my camera, a Sony TRV-460, but cannot control it via the av/c controls
as it cannot 'see' a device to do the controls in the prefs->ieee1394
screen.
Then kino-0.9.2-1.lvn5.i386.rpm cannot even see the raw1394 interface,
reporting on its screen that the raw1394 kernel module isn't loaded, or
that it cannot read/write /dev/raw1394.
The module is loaded when the cable is plugged in, and the
/etc/security/console.perms.d/50-defaults has been edited so that
/dev/raw1394 as created by the hotplug event now has these perms:
crw-rw-rw- 1 root root 171, 0 Oct 15 20:20 /dev/raw1394
This has had no effect on the performance of either version of kino.
So when do we actually get a functioning firewire interface, which we
DID have 18 months ago in FC2, before someone just had to rewrite the
1394 stuff again?
--
Cheers, Gene
next reply other threads:[~2006-10-16 1:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 1:23 Gene Heskett [this message]
2006-10-16 16:51 ` raw1394 problems galore Stefan Richter
2006-10-16 19:29 ` Gene Heskett
2006-10-16 21:38 ` Stefan Richter
2006-10-16 22:54 ` Gene Heskett
2006-10-17 0:44 ` Gene Heskett
2006-10-17 2:32 ` raw1394 problems galore FIXED!!!!! Gene Heskett
2006-10-17 6:16 ` Stefan Richter
2006-10-17 10:39 ` Gene Heskett
2006-10-17 2:21 ` raw1394 problems galore Dan Dennedy
2006-10-17 2:44 ` Gene Heskett
2006-10-17 2:47 ` Gene Heskett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4532DF11.9060704@verizon.net \
--to=gene.heskett@verizon.net \
--cc=fedora-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox