[...]
This is going to sound rather silly, because I did try a couple of
earlier kernels before I started posting about this problem.
Tonight, I saw that kernel-2.6.18-1.2200.fc5.i686 was available, along
with the matching kmod-ndiswrapper pieces and kmod-ntfs in versions
2.6.18-1.2200.fc5 were available, so I installed them and rebooted.
Now kino-0.8 works sortof, wants to crash.
And kino-0.9.2 apparently works flawlessly, as does dvcont.
Looking into the logs, I see this during the boot:
Oct 16 20:20:29 diablo kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI):
IRQ=[10] MMIO=[c0209000-c02097ff] Max Packet=[2048] IR/IT contexts=[
4/8]
Oct 16 20:20:29 diablo kernel: audit(1161044396.750:4): avc: denied {
getattr } for pid=1310 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=4494 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Oct 16 20:20:29 diablo kernel: audit(1161044396.750:5): avc: denied {
setattr } for pid=1310 comm="pam_console_app" name="raw1394" dev=tmpfs
ino=4494 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
And I believe the camera was plugged in and powered up during the boot
as there are no further messages in the log & I've been playing with a
very wide grin on my face for about half an hour with it.
So it was a kernel problem all along!
Just one question here. Am I the only idiot that actually wants to do
work on linux? On second thought, I might not like the answer :-)
Anyway, end of thread, till the next time :)
--
Cheers, Gene
