From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: ieee1394 problems
Date: Sun, 30 Jan 2005 14:34:04 +0000 [thread overview]
Message-ID: <1107095644.4700.37.camel@localhost.localdomain> (raw)
In-Reply-To: <41F85C6F.6060200@paradise.net.nz>
On Thu, 2005-01-27 at 16:13 +1300, Robert Walter wrote:
> Many thanks for your work in helping produce a superior alternative. I seek
> your assistance in resolving a problem with ieee1394 encountered while
> upgrading. I'm using Fedora Core 3 x86_64. I have and MSI 7030 motherboard with
> onboard ieee1394.
> There is no /dev/ieee1394 device created when the modules are installed..
The current ieee1394 code does not create the needed event for udev to
create the node. To work around this, you need to do a manual:
mknod /dev/raw1394 c 171 0
chmod 666 /dev/raw1394
The needed changes are already in the maintainers CVS:
http://marc.theaimsgroup.com/?l=linux1394-devel&m\x110256535312105&w=2
http://www.linux1394.org/viewcvs/ieee1394/trunk/raw1394.c?r1\x1239&r2\x1240&p1=trunk/raw1394.c&p2=trunk/raw1394.c
So this issue may be solved sooner than later.
Good luck,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-01-30 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 3:13 ieee1394 problems Robert Walter
2005-01-27 7:24 ` Kay Sievers
2005-01-30 14:34 ` Kay Sievers [this message]
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=1107095644.4700.37.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).