From: Gene Heskett <gene.heskett@verizon.net>
To: For users of Fedora Core releases <fedora-list@redhat.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org,
linux1394-user@lists.sourceforge.net
Subject: Re: raw1394 problems galore FIXED!!!!!
Date: Mon, 16 Oct 2006 22:32:39 -0400 [thread overview]
Message-ID: <453440C7.2060800@verizon.net> (raw)
In-Reply-To: <45342789.2050506@verizon.net>
[...]
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
next prev parent reply other threads:[~2006-10-17 2:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 1:23 raw1394 problems galore Gene Heskett
2006-10-16 16:51 ` 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 ` Gene Heskett [this message]
2006-10-17 6:16 ` raw1394 problems galore FIXED!!!!! 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=453440C7.2060800@verizon.net \
--to=gene.heskett@verizon.net \
--cc=fedora-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-user@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.