Greetings all;
I'm trying to make my sony trc460 work with kino, but while I can get
video from it, I can't control it from kino-8.0.
I just unloaded all the 1394 related stuffs, ran the /usr/bin/mkrfc2734
from the libavc1394 package to see if that might help, but apparently not.
According to the logs, SELinux is possibly getting in the way from
stanza's like this:
Oct 14 20:44:53 diablo kernel: ieee1394: hpsb_update_config_rom() is
deprecated
Oct 14 20:44:53 diablo kernel: ieee1394: Failed to generate
Configuration ROM image for host 0
Oct 14 20:46:19 diablo kernel: video1394: Removed video1394 module
Oct 14 20:49:09 diablo kernel: ieee1394: raw1394: /dev/raw1394 device
initialized
Oct 14 20:49:09 diablo kernel: audit(1160873349.191:20): avc: denied {
getattr } for pid=23297 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=80146 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Oct 14 20:49:09 diablo kernel: audit(1160873349.191:21): avc: denied {
setattr } for pid=23297 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=80146 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Running 'dvcont play':
root@diablo ~]# dvcont play
couldn't set port: Invalid argument
Then repeating:
[root@diablo ~]# /usr/bin/mkrfc2734
couldn't set port: Invalid argument
an ls of /dev:
[root@diablo ~]# ls /dev
audio dri hda log mem ppp ram2
rtc tty1 tty20 tty31 tty42 tty53 tty7 vcs3 vcsa7
audio1 dsp hda1 loop0 mixer ptmx ram3
sequencer tty10 tty21 tty32 tty43 tty54 tty8 vcs4 X0R
bus dsp1 hda2 loop1 mixer1 pts ram4
sequencer2 tty11 tty22 tty33 tty44 tty55 tty9 vcs5 zero
cdrom dvd hda3 loop2 net ram ram5
shm tty12 tty23 tty34 tty45 tty56 ttyS0 vcs6
cdrom-hdc dvd-hdc hda5 loop3 null ram0 ram6
snapshot tty13 tty24 tty35 tty46 tty57 ttyS1 vcs7
cdrw dvdrw hda6 loop4 nvram ram1 ram7
snd tty14 tty25 tty36 tty47 tty58 ttyS2 vcsa
cdrw-hdc dvdrw-hdc hda7 loop5 par0 ram10 ram8
stderr tty15 tty26 tty37 tty48 tty59 ttyS3 vcsa1
cdwriter dvdwriter hdc loop6 parport0 ram11 ram9
stdin tty16 tty27 tty38 tty49 tty6 urandom vcsa2
cdwriter-hdc dvdwriter-hdc hpet loop7 parport1 ram12 ramdisk
stdout tty17 tty28 tty39 tty5 tty60 usb vcsa3
console fd initctl MAKEDEV parport2 ram13 random
systty tty18 tty29 tty4 tty50 tty61 vcs vcsa4
core full input mapper parport3 ram14 raw1394
tty tty19 tty3 tty40 tty51 tty62 vcs1 vcsa5
disk gpmctl kmsg md0 port ram15 root
tty0 tty2 tty30 tty41 tty52 tty63 vcs2 vcsa6
so it appears that a control devicename is not being created, and the
control device section of the kino prefs is blank:, as shown by the
attached screen snapshot.
Does anyone have a clue? This, FWIW, worked fairly well for kino-7.5
running on an FC2 system with the old kernels. This was before the
major rewrite of the ieee1394 drivers in the kernel that broke ALL
ieee1394 applications at the time. I've bitched about this before for
those with good memories.
Anyway, is there now anything that can be done for this, or are we
forever stuck with a broken ieee1394 interface in linux?
The following is what is logged after a fresh reboot, which I had a hell
of a time with, having to disable wlan0 before I could stop the kernel
panics and complete the boot process.
Anyway, this is whats logged when the camera, already powered up, is
plugged into the 4 pin FW port on this lappy, an HP dv5120us, running
uptodate FC5.
Oct 14 21:18:56 diablo udevd-event[2580]: pass_env_to_socket: passed 422
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 773 forked, pid
[2589], 'add' 'drivers', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2589]: udev_rules_get_run: rule
applied, 'dv1394' is ignored
Oct 14 21:18:56 diablo udevd-event[2588]: run_program: '/sbin/modprobe'
returned with status 0
Oct 14 21:18:56 diablo udevd-event[2584]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2580]: udev_event_run: seq 768 finished
Oct 14 21:18:56 diablo udevd-event[2593]: udev_rules_get_run: rule
applied, 'raw1394' is ignored
Oct 14 21:18:56 diablo udevd-event[2589]: udev_device_event: device
event will be ignored
Oct 14 21:18:56 diablo udevd-event[2588]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Oct 14 21:18:56 diablo udevd-event[2584]: pass_env_to_socket: passed 196
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 774 forked, pid
[2593], 'add' 'module', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2593]: udev_device_event: device
event will be ignored
Oct 14 21:18:56 diablo udevd-event[2589]: udev_event_run: seq 773 finished
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_hotplugd'
Oct 14 21:18:56 diablo udevd-event[2584]: run_program:
'/sbin/pam_console_apply /dev/dv1394-0 '
Oct 14 21:18:56 diablo udevd-event[2593]: udev_event_run: seq 774 finished
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2584]: run_program:
'/sbin/pam_console_apply' returned with status 0
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 768, pid [2580] exit
with 0, 1 seconds old
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_devd'
Oct 14 21:18:56 diablo udevd-event[2584]: udev_event_run: seq 772 finished
Oct 14 21:18:56 diablo udevd-event[2588]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 773, pid [2589] exit
with 0, 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2588]: pass_env_to_socket: passed 422
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 772, pid [2584] exit
with 0, 1 seconds old
Oct 14 21:18:56 diablo udevd-event[2588]: udev_event_run: seq 770 finished
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 774, pid [2593] exit
with 0, 0 seconds old
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 770, pid [2588] exit
with 0, 1 seconds old
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 775 forked, pid
[2597], 'add' 'ieee1394_protocol', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2597]: udev_rules_get_name: rule
applied, 'raw1394' becomes 'raw1394'
Oct 14 21:18:56 diablo udevd[417]: udev_event_run: seq 776 forked, pid
[2598], 'add' 'drivers', 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2598]: udev_rules_get_run: rule
applied, 'raw1394' is ignored
Oct 14 21:18:56 diablo udevd-event[2597]: create_node: creating device
node '/dev/raw1394', major = '171', minor = '0', mode = '0600', uid =
'0', gid = '0'
Oct 14 21:18:56 diablo udevd-event[2598]: udev_device_event: device
event will be ignored
Oct 14 21:18:56 diablo udevd-event[2597]: pass_env_to_socket: passed -1
bytes to socket '/org/kernel/udev/monitor',
Oct 14 21:18:56 diablo udevd-event[2598]: udev_event_run: seq 776 finished
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_hotplugd'
Oct 14 21:18:56 diablo udevd[417]: udev_done: seq 776, pid [2598] exit
with 0, 0 seconds old
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_hotplugd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_devd'
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/lib/udev/udev_run_devd' returned with status 0
Oct 14 21:18:56 diablo udevd-event[2597]: pass_env_to_socket: passed 192
bytes to socket '/org/freedesktop/hal/udev_event',
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/sbin/pam_console_apply /dev/raw1394 '
Oct 14 21:18:56 diablo udevd-event[2597]: run_program:
'/sbin/pam_console_apply' returned with status 0
Oct 14 21:18:56 diablo kernel: audit(1160875136.916:6): avc: denied {
getattr } for pid=2601 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=14070 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Oct 14 21:18:56 diablo udevd-event[2597]: udev_event_run: seq 775 finished
Oct 14 21:18:56 diablo kernel: audit(1160875136.916:7): avc: denied {
setattr } for pid=2601 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=14070 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
What clues can be extracted from all this?, I feel like I'm drowning in
useless data here.
--
Cheers, Gene
