Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19626 - [jack] add firewire (ffado) support

Attached to Project: Arch Linux
Opened by Radosław Szkodziński (AstralStorm) - Friday, 28 May 2010, 15:26 GMT
Last edited by Ray Rashif (schivmeister) - Sunday, 08 August 2010, 13:00 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Ray Rashif (schivmeister)
Dan Griffiths (Ghost1227)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
extra/jack-0.118.0-3 is missing an essential feature: firewire support via libffado.
It's currently the only way to use firewire sound devices in Linux.

This bug depends on ffado and its dependencies being added to extra repository.
There is a working PKGBUILD available on AUR.
Its dependencies are already provided in extra repository.

Additional info:
extra/jack-0.118.0-3
AUR/ffado-2.0.0-1
This task depends upon

Closed by  Ray Rashif (schivmeister)
Sunday, 08 August 2010, 13:00 GMT
Reason for closing:  Implemented
Additional comments about closing:  See testing/jack-0.118.0-4
Comment by CedricR (CedricR) - Monday, 28 June 2010, 09:12 GMT
It is a very good idea to do that!
Comment by Dan Griffiths (Ghost1227) - Thursday, 01 July 2010, 06:05 GMT
ffado is maintained by a developer. If he's willing to move it, I'm willing to rebuild jack to support it.
Comment by CedricR (CedricR) - Thursday, 01 July 2010, 07:10 GMT
Thanks Dan for this news !
Comment by Ray Rashif (schivmeister) - Saturday, 10 July 2010, 13:17 GMT
It's stable enough but we can't bring it in unless it can work with our kernel. The new-stack-old-stack confusion should be gone by now, but there are a couple of things like udev rules (for /dev/fw* instead of /dev/raw1394) that we need to clear up first.
Comment by Ray Rashif (schivmeister) - Wednesday, 21 July 2010, 08:51 GMT
I need one or two firewire users to check out and report their outcome at:

https://bbs.archlinux.org/viewtopic.php?id=100732
Comment by Ray Rashif (schivmeister) - Sunday, 08 August 2010, 12:59 GMT
At this point of time we don't see the need to provide custom rules to enforce a group-writable node, mainly because we don't want to override upstream's method of creating device-based permissions for /dev/fw*. If your gear does not work, annoy ffado to ship some rules with proper device IDs or alternatively, complain to ieee1394 that your /dev/fw1 is not being created with group r/w set (cite 50-udev-default.rules).

What you can do:

1) chmod 660 /dev/fw1 && chown root:video (or audio) and put yourself in that group
2) chmod 666 /dev/fw1 and be done with it
3.1) do (1) or (2) from /etc/rc.local to make it persist -OR-
3.2) write your own udev rule

Further reading: https://ieee1394.wiki.kernel.org/index.php/Juju_Migration#Character_device_files.2C_block_device_files

Loading...