dv1394 driver is unsupported

Bug #298533 reported by Carl Karsten
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I plug in a firewire dv cam:

[ 124.557239] ieee1394: Current remote IRM is not 1394a-2000 compliant, resetti
ng...
[ 124.844631] ieee1394: Node added: ID:BUS[0-00:1023] GUID[008088030a613f59]
[ 124.844785] ieee1394: Node changed: 0-00:1023 -> 0-01:1023
[ 125.019452] NOTE: The dv1394 driver is unsupported and may be removed in a fu
ture Linux release. Use raw1394 instead.
[ 125.061687] ieee1394: raw1394: /dev/raw1394 device initialized

carl@dv67:~/temp$ uname -a
Linux dv67 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux

carl@dv67:~/temp$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

I am experiencing various problems with dvgrab: segfault, app stalls (doesn't error or exit, keeps output file open, but stops writing to it.) I will report them when I have a good example, but for this report this might be a good reason to "Use raw1394 instead."

[ 3499.985160] ieee1394: Node changed: 0-01:1023 -> 0-00:1023
[ 3499.985184] ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[008088030a613f59]

Tags: kj-expired
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Carl,

It appears raw1394 is being used based on the line in your dmesg output:

[ 125.061687] ieee1394: raw1394: /dev/raw1394 device initialized

Changed in linux:
status: New → Incomplete
Revision history for this message
Stefan Richter (stefan-r-ubz) wrote :

dvgrab v3 uses only raw1394, not the dv1394 kernel module.

The dv1394 special-purpose driver will actually stay in the kernel as log as the whole ieee1394 driver stack. But the new alternative firewire stack, which is meant to replace the ieee1394 stack eventually, won't provide an interface with binary compatibility to the dv1394 driver's interface.

I guess I should change the dv1394 driver to emit the scary log message only when actually opened by an application, not immediately when the driver is initialized.

Revision history for this message
Stefan Richter (stefan-r-ubz) wrote :

For the record: The capture stalls which Carl mentioned are tracked in bug 298579.

Revision history for this message
Victor Vargas (kamus) wrote :

Since this report have a long time without activity, could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.