Ticket #337 (closed bug: invalid)

Opened 9 years ago

Last modified 9 years ago

ffado dbusd not starting in ubuntu 11.4

Reported by: zimmermann Assigned to:
Priority: minor Milestone:
Component: devices/fireworks Version: FFADO 2.0.1
Keywords: Cc:
The device the bug applies to:

Description

as root, ffado starts and can be connected in qjackctl wit ardour(even ardour cannot play:-( FFADO diagnostic utility 2.999.0- ============================

CHECK

Base system...

kernel version............ 2.6.38-8-generic old 1394 stack present.... False old 1394 stack loaded..... False old 1394 stack active..... False new 1394 stack present.... True new 1394 stack loaded..... True new 1394 stack active..... True /dev/raw1394 node present. False

Prerequisites (dynamic at run-time)...

gcc ............... sh: gcc: not found g++ ............... sh: g++: not found PyQt?4 (by pyuic4) . sh: pyuic4: not found jackd ............. Cannot create thread 1 Operation not permitted

path ............ /usr/bin/jackd flags ........... sh: pkg-config: not found

libraw1394 ........ sh: pkg-config: not found

flags ........... sh: pkg-config: not found

libavc1394 ........ sh: pkg-config: not found

flags ........... sh: pkg-config: not found

libiec61883 ....... sh: pkg-config: not found

flags ........... sh: pkg-config: not found

libxml++-2.6 ...... sh: pkg-config: not found

flags ........... sh: pkg-config: not found

dbus-1 ............ sh: pkg-config: not found

flags ........... sh: pkg-config: not found

Prerequisites (static at compile-time)...

gcc ............... gcc (Ubuntu/Linaro 4.5.2-7ubuntu1) 4.5.2 g++ ............... g++ (Ubuntu/Linaro 4.5.2-7ubuntu1) 4.5.2 PyQt?4 (by pyuic4) . Python User Interface Compiler 4.8.3 for Qt version 4.7.2 jackd ............. sh: jackd: not found

path ............ flags ........... Package jack was not found in the pkg-config search path.

libraw1394 ........ 2.0.6

flags ........... -lraw1394

libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.

flags ........... Package libavc1394 was not found in the pkg-config search path.

libiec61883 ....... 1.2.0

flags ........... -liec61883 -lraw1394

libxml++-2.6 ...... 2.33.1

flags ........... -pthread -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -pthread -L/usr/lib/i386-linux-gnu -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0

dbus-1 ............ 1.4.6

flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -L/usr/lib/i386-linux-gnu -ldbus-1 -lpthread -lrt

Hardware...

Host controllers:

0c:00.0 FireWire? (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 46) (prog-if 10 [OHCI])

Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] Control: I/O+ Mem+ BusMaster?+ SpecCycle?- MemWINV- VGASnoop- ParErr?- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr?- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64 (8000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at b8000000 (32-bit, non-prefetchable) [size=2K] Region 1: I/O ports at 5000 [size=128] Region 2: Memory at b8000800 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied> Kernel driver in use: firewire_ohci Kernel modules: firewire-ohci

CPU info:

Architecture: i686 CPU op-mode(s): 32-bit CPU(s): 1 Thread(s) per core: 1 Core(s) per socket: 1 CPU socket(s): 1 Vendor ID: GenuineIntel? CPU family: 6 Model: 13 Stepping: 8 CPU MHz: 2266.000

Configuration...

IRQ information

Hardware Interrupts:


IRQ 0: PID: None, count: [12530908], Sched None (priority None), drivers: timer? IRQ 1: PID: None, count: [3643], Sched None (priority None), drivers: i8042? IRQ 6: PID: None, count: [3], Sched None (priority None), drivers: floppy? IRQ 7: PID: None, count: [0], Sched None (priority None), drivers: parport0? IRQ 8: PID: None, count: [1], Sched None (priority None), drivers: rtc0? IRQ 9: PID: None, count: [6282], Sched None (priority None), drivers: acpi? IRQ 12: PID: None, count: [633989], Sched None (priority None), drivers: i8042? IRQ 14: PID: None, count: [36188], Sched None (priority None), drivers: ata_piix? IRQ 15: PID: None, count: [135385], Sched None (priority None), drivers: ata_piix? IRQ 16: PID: None, count: [10205874], Sched None (priority None), drivers: ['uhci_hcd:usb2', 'yenta', 'firewire_ohci', 'eth0'] IRQ 17: PID: None, count: [0], Sched None (priority None), drivers: uhci_hcd:usb3? IRQ 18: PID: None, count: [29], Sched None (priority None), drivers: uhci_hcd:usb4? IRQ 19: PID: None, count: [2], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb5'] IRQ 21: PID: None, count: [431204], Sched None (priority None), drivers: ipw2200? IRQ 22: PID: None, count: [1977], Sched None (priority None), drivers: Intel ICH6? IRQ 43: PID: None, count: [390882], Sched None (priority None), drivers: radeon?

Software Interrupts:


REPORT

FireWire? kernel drivers:

The new FireWire? kernel stack is loaded. This is still kind of experimental. If you encounter problems, please also check with the old stack.

as user, even listing is NOK: ffado-test ListDevices? Cannot create thread 1 Operation not permitted


FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org Version: 2.999.0- (C) 2008, Daniel Wagner, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY.


1394 PORT 0

Node id GUID VendorId? ModelId? Vendor - Model

0 0x000a9200d6080267 0x00000A92 0x00010000 PreSonus? - PreSonus? FIREBOX

ERROR: messagebuffer not initialized: 34834125125: Error (configrom.cpp)[ 150] initialize: Could not parse config rom of node 1 on port 0

--- on a centrino laptop with 0c:00.0 FireWire? (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46)

and Presonus Firebox.

Change History

07/08/11 10:21:23 changed by adi

This bug report lacks details.

First: Don't run any ffado or jack related programs as root. Period.

Second: ffado-dbus-server has nothing to do with jackd. Your bug report is somewhat ambiguous. Are you complaining about failing jackd or failing ffado-dbus-server?

Third: Provide logfiles which include the invoking command. It's what's shown in qjackctl's message window. More easily, run

   jackd -d firewire -v3

in the terminal.

For ffado-dbus-server, first make sure to kill all existing instances:

   killall -9 ffado-dbus-server

and then start ffado-mixer. It will start ffado-dbus-server automatically.

If you ran ffado-dbus-server or ffado-mixer as root before, make sure to also kill left-over processes under this user, if any.

You might have a serious problem, there's "Operation not permitted" being shown in ffado-diag's output. If jackd fails to start or fails to stay up, this might due to the lack of POSIX realtime permissions. If so, complain to Ubuntu, not to FFADO.

Cheers

03/27/12 06:59:22 changed by adi

  • status changed from new to closed.
  • resolution set to invalid.

Integration or usage bug. File a bug report against Ubuntu.