| 189 | | [wagi@halo ~]$ jackd -d firewire |
|---|
| 190 | | jackd 0.102.9 |
|---|
| 191 | | Copyright 2001-2005 Paul Davis and others. |
|---|
| 192 | | jackd comes with ABSOLUTELY NO WARRANTY |
|---|
| 193 | | This is free software, and you are welcome to redistribute it |
|---|
| 194 | | under certain conditions; see the file COPYING for details |
|---|
| 195 | | |
|---|
| 196 | | JACK compiled with System V SHM support. |
|---|
| 197 | | loading driver .. |
|---|
| 198 | | Freebob using Firewire port 0, node -1 |
|---|
| 199 | | libiec61883 warning: Established connection on channel 0. |
|---|
| 200 | | You may need to manually set the channel on the receiving node. |
|---|
| 201 | | libiec61883 warning: Established connection on channel 1. |
|---|
| 202 | | You may need to manually set the channel on the transmitting node. |
|---|
| | 191 | $ jackd -d firewire |
|---|
| | 192 | no message buffer overruns |
|---|
| | 193 | jackd 0.111.0 |
|---|
| | 194 | Copyright 2001-2005 Paul Davis and others. |
|---|
| | 195 | jackd comes with ABSOLUTELY NO WARRANTY |
|---|
| | 196 | This is free software, and you are welcome to redistribute it |
|---|
| | 197 | under certain conditions; see the file COPYING for details |
|---|
| | 198 | |
|---|
| | 199 | JACK compiled with System V SHM support. |
|---|
| | 200 | loading driver .. |
|---|
| | 201 | 3106528665: (ffado.cpp)[ 99] ffado_streaming_init: libffado 1.999.20 built Apr 26 2008 20:26:32 |
|---|
| | 202 | libiec61883 warning: Established connection on channel 0. |
|---|
| | 203 | You may need to manually set the channel on the receiving node. |
|---|
| | 204 | libiec61883 warning: Established connection on channel 1. |
|---|
| | 205 | You may need to manually set the channel on the transmitting node. |
|---|
| 209 | | Under the tests directory there is a test program. You should first |
|---|
| 210 | | try to run this. |
|---|
| 211 | | |
|---|
| 212 | | If you don't have installed libffado then you can adapt your |
|---|
| 213 | | LD_LIBRARY_PATH environment variable to |
|---|
| 214 | | |
|---|
| 215 | | $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:../src/.libs |
|---|
| 216 | | |
|---|
| 217 | | Then you can try running the program without having to install it. |
|---|
| 218 | | |
|---|
| 219 | | With the release version you see something like this: |
|---|
| 220 | | |
|---|
| 221 | | wagi@cruxam:~/src/libffado/tests$ ./test-ffado discover |
|---|
| 222 | | verbose level = 0 |
|---|
| 223 | | Using ffado library version: libffado 0.9.0 |
|---|
| 224 | | |
|---|
| 225 | | port = 2, devices_on_bus = 1 |
|---|
| 226 | | get info for device = 0, node = 1 |
|---|
| 227 | | Direction: 0 (capture) |
|---|
| 228 | | |
|---|
| 229 | | Connection Info |
|---|
| 230 | | =============== |
|---|
| 231 | | |
|---|
| 232 | | Number of connections: 1 |
|---|
| 233 | | |
|---|
| 234 | | Connection 0 |
|---|
| 235 | | ------------- |
|---|
| 236 | | [ 0] Id: 0 |
|---|
| 237 | | [ 0] Port: 2 |
|---|
| 238 | | [ 0] Node: 1 |
|---|
| 239 | | [ 0] Plug: 0 |
|---|
| 240 | | [ 0] Dimension: 7 |
|---|
| 241 | | [ 0] Samplerate: 44100 |
|---|
| 242 | | [ 0] IsoChannel: -1 |
|---|
| 243 | | [ 0] IsMaster: 0 |
|---|
| 244 | | [ 0] Number of stream infos: 8 |
|---|
| 245 | | |
|---|
| 246 | | StreamId Position Location Format Type DPort Name |
|---|
| 247 | | -------------------------------------------------- |
|---|
| 248 | | [ 0]:[ 0] 0x01 0x01 0x06 0x02 0x00 MicIn 1+2 left |
|---|
| 249 | | [ 0]:[ 1] 0x04 0x02 0x06 0x02 0x00 MicIn 1+2 right |
|---|
| 250 | | [ 0]:[ 2] 0x02 0x01 0x06 0x03 0x00 LineIn 1+2 left |
|---|
| 251 | | [ 0]:[ 3] 0x05 0x02 0x06 0x03 0x00 LineIn 1+2 right |
|---|
| 252 | | [ 0]:[ 4] 0x00 0x01 0x06 0x04 0x00 SpdifIn 1 left |
|---|
| 253 | | [ 0]:[ 5] 0x03 0x02 0x06 0x04 0x00 SpdifIn 1 right |
|---|
| 254 | | [ 0]:[ 6] 0x06 0x01 0x0d 0x0a 0x00 MidiIn2 |
|---|
| 255 | | [ 0]:[ 7] 0x06 0x02 0x0d 0x0a 0x00 MidiIn2 |
|---|
| 256 | | |
|---|
| 257 | | |
|---|
| 258 | | Direction: 1 (playback) |
|---|
| 259 | | |
|---|
| 260 | | Connection Info |
|---|
| 261 | | =============== |
|---|
| 262 | | |
|---|
| 263 | | Number of connections: 1 |
|---|
| 264 | | |
|---|
| 265 | | Connection 0 |
|---|
| 266 | | ------------- |
|---|
| 267 | | [ 0] Id: 0 |
|---|
| 268 | | [ 0] Port: 2 |
|---|
| 269 | | [ 0] Node: 1 |
|---|
| 270 | | [ 0] Plug: 0 |
|---|
| 271 | | [ 0] Dimension: 11 |
|---|
| 272 | | [ 0] Samplerate: 44100 |
|---|
| 273 | | [ 0] IsoChannel: -1 |
|---|
| 274 | | [ 0] IsMaster: 0 |
|---|
| 275 | | [ 0] Number of stream infos: 12 |
|---|
| 276 | | |
|---|
| 277 | | StreamId Position Location Format Type DPort Name |
|---|
| 278 | | -------------------------------------------------- |
|---|
| 279 | | [ 0]:[ 0] 0x01 0x01 0x06 0x03 0x00 MultiChannel 7.1 Front left |
|---|
| 280 | | [ 0]:[ 1] 0x06 0x02 0x06 0x03 0x00 MultiChannel 7.1 Front right |
|---|
| 281 | | [ 0]:[ 2] 0x02 0x03 0x06 0x03 0x00 MultiChannel 7.1 Center |
|---|
| 282 | | [ 0]:[ 3] 0x07 0x04 0x06 0x03 0x00 MultiChannel 7.1 Subwoofer |
|---|
| 283 | | [ 0]:[ 4] 0x03 0x05 0x06 0x03 0x00 MultiChannel 7.1 Rear left |
|---|
| 284 | | [ 0]:[ 5] 0x08 0x06 0x06 0x03 0x00 MultiChannel 7.1 Rear right |
|---|
| 285 | | [ 0]:[ 6] 0x04 0x07 0x06 0x03 0x00 MultiChannel 7.1 Surround left |
|---|
| 286 | | [ 0]:[ 7] 0x09 0x08 0x06 0x03 0x00 MultiChannel 7.1 Surround right |
|---|
| 287 | | [ 0]:[ 8] 0x00 0x01 0x06 0x04 0x00 SpdifOut 1 left |
|---|
| 288 | | [ 0]:[ 9] 0x05 0x02 0x06 0x04 0x00 SpdifOut 1 right |
|---|
| 289 | | [ 0]:[10] 0x0a 0x01 0x0d 0x0a 0x00 MidiOut2 |
|---|
| 290 | | [ 0]:[11] 0x0a 0x02 0x0d 0x0a 0x00 MidiOut2 |
|---|
| 291 | | |
|---|
| 292 | | |
|---|
| 293 | | If you don't get this, check if you have multiple host controllers, and |
|---|
| 294 | | use the -p parameter to specify them. If you get any error messages, the |
|---|
| 295 | | best way to help us figure out what the problem might be is to build the |
|---|
| 296 | | debug version (scons ENABLE_DEBUG=1). You can then rerun the test |
|---|
| 297 | | application (with -v5) and send us its output. |
|---|
| 298 | | |
|---|
| | 216 | First of all, check whether your problem is in fact a problem, and |
|---|
| | 217 | whether it is a FFADO problem. The magic tool for this is google. |
|---|
| | 218 | |
|---|
| | 219 | User support is a rather annoying occupation, especially since it sucks |
|---|
| | 220 | time from developers that are not paid for developing, let alone for doing |
|---|
| | 221 | user support. Please make sure that you have checked the following places: |
|---|
| | 222 | http://www.ffado.org/ |
|---|
| | 223 | http://subversion.ffado.org/ |
|---|
| | 224 | http://www.google.com/ |
|---|
| | 225 | (the terms "ffado-devel" "ffado-user" or "freebob-user" work great) |
|---|
| | 226 | Some might consider this a bit arrogant or "newbie-unfriendly", but personally |
|---|
| | 227 | I (Pieter Palmers) consider this a matter of politeness towards the developers. |
|---|
| | 228 | |
|---|
| | 229 | If you have tried to find a solution to your problem, but you couldn't find |
|---|
| | 230 | one or are confused, don't hesitate to ask for help. The preferred way is by |
|---|
| | 231 | signing up to the mailing list as described on http://www.ffado.org/?q=contact. |
|---|
| | 232 | |
|---|
| | 233 | Writing a bug report |
|---|
| | 234 | -------------------- |
|---|
| | 235 | |
|---|
| | 236 | Note that the more effort you put in your bug report, the more effort we |
|---|
| | 237 | will put into helping you. |
|---|
| | 238 | |
|---|
| | 239 | Make sure you have compiled a DEBUG=yes version of |
|---|
| | 240 | libffado. If not there is no way we can trace the problem. |
|---|
| | 241 | |
|---|
| | 242 | When reporting a problem, please run jackd with the --verbose option, |
|---|
| | 243 | and add the -v6 option to the firewire backend: |
|---|
| | 244 | $ jackd --verbose [...] -d firewire -v6 [...] |
|---|
| | 245 | |
|---|
| | 246 | ( [...] = other options ) |
|---|
| | 247 | |
|---|
| | 248 | This will generate an increadible amount of debug output that should |
|---|
| | 249 | contain what we need to track down the problem. If you have troubles |
|---|
| | 250 | saving the output, try redirecting it to a file: |
|---|
| | 251 | |
|---|
| | 252 | $ jackd --verbose -d firewire -v6 2> ffado-jack.log |
|---|
| | 253 | |
|---|
| | 254 | this will create a ffado.log file containing the output. Use CTRL-C |
|---|
| | 255 | to exit jack if necessary. |
|---|
| | 256 | |
|---|
| | 257 | The distribution contains a tool to gather some information about your |
|---|
| | 258 | system. you can run it as follows: |
|---|
| | 259 | |
|---|
| | 260 | $ cd support/tools |
|---|
| | 261 | $ python ffado-diag.py > ffado-diag.log |
|---|
| | 262 | |
|---|
| | 263 | It will check your system for basic problems and gather some information |
|---|
| | 264 | regarding your hardware configuration. This will allow us to diagnose |
|---|
| | 265 | your problem faster. |
|---|
| | 266 | |
|---|
| | 267 | Once the logs have been created you can create a support ticket at |
|---|
| | 268 | http://subversion.ffado.org/newticket |
|---|
| | 269 | |
|---|
| | 270 | Be sure to include the following information: |
|---|
| | 271 | * the log file(s) (zipped/tar.gz'ed and attached) |
|---|
| | 272 | * the device you're trying to use |
|---|
| | 273 | * a description of what went wrong and how to reproduce it. You |
|---|
| | 274 | preferrably try to figure out a sequence of steps that can reliably |
|---|
| | 275 | reproduce the issue on your system. A one-time failure is very difficult |
|---|
| | 276 | to diagnose and/or fix. |
|---|
| | 277 | * the distribution and its version |
|---|
| | 278 | |
|---|
| | 279 | |
|---|