From: Luka / N. V. <no...@vi...> - 2007-05-14 22:41:57
|
hi! first of all, great respect for all the work done with freebob. makes my music and sound explorations on linux a better world. thank you all for this project. i just got a brand new Edirol FA-101, with great excitement to use it on linux, as reported by freebob to be working well on freebob/ffado.. of course things didn't went working out of the box. so i wanted to ask some questions before i compile kernel, ffado sources, jack etc... my system works with an echo audio indigo DJ card, +alsa, +jackd. jackd works also with my internal soundcard (not so good, but works) i compiled my own kernel for my laptop thinkpad t60p from debian kernel source. it's a 2.6.18 with following: # grep IEEE1394 /boot/config-`uname -r` CONFIG_IEEE1394=m # CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_IEEE1394_OUI_DB is not set CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y CONFIG_IEEE1394_CONFIG_ROM_IP1394=y # CONFIG_IEEE1394_EXPORT_FULL_API is not set CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_OHCI1394=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_IEEE1394_ETH1394=m CONFIG_IEEE1394_DV1394=m CONFIG_IEEE1394_RAWIO=m i'm using via-based pcmcia/pccard for firewire interface. when i insert the pccard, all is ok, syslog reports May 14 22:23:52 wonko kernel: ieee1394: Initialized config rom entry `ip1394' May 14 22:23:52 wonko kernel: ieee1394: Host added: ID:BUS[0-00:1023] GUID[00110600000043dc] if i turn on fa-101 now, the system imediately freezes. however if i unload all ieee1394 drivers (eth1394 and ohci1394 and ieee1394) and turn on the card the system doesn't freeze. if i then load ieee1394 and raw1394, chmod a+rw /dev/raw1394, all is ok but jackd -dfreebob sais: $ jackd -R -dfreebob jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Freebob using Firewire port 0, node -1 Ieee1394Service::initialize: Could not get 1394 handle: Invalid argument Is ieee1394 and raw1394 driver loaded? Fatal (devicemanager.cpp)[68] initialize: Could not initialize Ieee1349Service object Fatal (freebob.cpp)[69] freebob_new_handle: Could not initialize device manager FreeBoB ERR: FREEBOB: Error creating virtual device cannot load driver module freebob Segmentation fault the same is when i first load the ieee1394 and raw1394 and then turn the card on. when unloading ohci1394 i get in syslog: ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00110600000043dc] if i load ohci1394 again when the card is on, then it freezes, so i'm figuring the freeze problem has something to do with this module. is ohci1394 required for this setup to work? any suggestions before i go compiling everything from latest and greatest sources? best, luka -- http://viator.si/ |
From: Pieter P. <pi...@jo...> - 2007-05-15 08:25:40
|
Luka Prinčič / Nova Viator wrote: > > hi! > > first of all, great respect for all the work done with freebob. makes > my music and sound explorations on linux a better world. thank you > all for this project. > > i just got a brand new Edirol FA-101, with great excitement to use it > on linux, as reported by freebob to be working well on > freebob/ffado.. of course things didn't went working out of the box. > so i wanted to ask some questions before i compile kernel, ffado > sources, jack etc... > > my system works with an echo audio indigo DJ card, +alsa, +jackd. > jackd works also with my internal soundcard (not so good, but works) > > i compiled my own kernel for my laptop thinkpad t60p from debian > kernel source. it's a 2.6.18 with following: # grep IEEE1394 > /boot/config-`uname -r` CONFIG_IEEE1394=m # > CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_IEEE1394_OUI_DB is > not set CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y > CONFIG_IEEE1394_CONFIG_ROM_IP1394=y # CONFIG_IEEE1394_EXPORT_FULL_API > is not set CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_OHCI1394=m > CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m # > CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_IEEE1394_ETH1394=m > CONFIG_IEEE1394_DV1394=m CONFIG_IEEE1394_RAWIO=m > > i'm using via-based pcmcia/pccard for firewire interface. when i > insert the pccard, all is ok, syslog reports May 14 22:23:52 wonko > kernel: ieee1394: Initialized config rom entry `ip1394' May 14 > 22:23:52 wonko kernel: ieee1394: Host added: ID:BUS[0-00:1023] > GUID[00110600000043dc] > > if i turn on fa-101 now, the system imediately freezes. can you try removing dv1394? With 'removing' I mean deleting it from the /lib/modules/... directory. dv1394 is know to freeze the system sometimes. > > however if i unload all ieee1394 drivers (eth1394 and ohci1394 and > ieee1394) and turn on the card the system doesn't freeze. if i then > load ieee1394 and raw1394, chmod a+rw /dev/raw1394, all is ok but > jackd -dfreebob sais: > > $ jackd -R -dfreebob jackd 0.103.0 Copyright 2001-2005 Paul Davis and > others. jackd comes with ABSOLUTELY NO WARRANTY This is free > software, and you are welcome to redistribute it under certain > conditions; see the file COPYING for details > > JACK compiled with System V SHM support. loading driver .. Freebob > using Firewire port 0, node -1 Ieee1394Service::initialize: Could not > get 1394 handle: Invalid argument Is ieee1394 and raw1394 driver > loaded? Fatal (devicemanager.cpp)[68] initialize: Could not > initialize Ieee1349Service object Fatal (freebob.cpp)[69] > freebob_new_handle: Could not initialize device manager FreeBoB ERR: > FREEBOB: Error creating virtual device cannot load driver module > freebob Segmentation fault > > > the same is when i first load the ieee1394 and raw1394 and then turn > the card on. > > when unloading ohci1394 i get in syslog: ieee1394: Node removed: > ID:BUS[0-00:1023] GUID[00110600000043dc] > > if i load ohci1394 again when the card is on, then it freezes, so i'm > figuring the freeze problem has something to do with this module. is > ohci1394 required for this setup to work? ohci is essential. > > any suggestions before i go compiling everything from latest and > greatest sources? Try removing DV1394 and see if it helps. I CC'ed the linux1394-devel list as this is more a 1394 problem than it is a freebob/ffado problem. Greets, Pieter |
From: Nova V. <no...@vi...> - 2007-06-18 00:08:00
|
hi all! thanks for all the comments week or two ago on Edirol FA-101 problems with freebob. i finally got time around to continue trying to hack this nifty little box to work under linux. i still haven't managed to get some sound from it, but there is some progress. as it seemed that on my laptop there could be problems with ieee1394 pcmcia card (through which even under 2.6.21 kernel the machine freezed, when i pluged/turned-on fa101), i moved to another machine, a box, with athlon and working firewire card. i built new kernel (2.6.21) and tried. when i turn on the card i get this in dmesg/syslog: Jun 17 23:27:45 localhost kernel: ieee1394: Error parsing configrom for node 0-00:1023 Jun 17 23:27:45 localhost kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023 Jun 17 23:27:48 localhost kernel: doh, someone wants to mess with state set Jun 17 23:27:48 localhost kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0040ab0000c22bb7] Jun 17 23:27:48 localhost kernel: ieee1394: raw1394: /dev/raw1394 device initialized i have configrom checked in kernel, should i not compile it in? so far everything seems ok. however running # jackd -R -v -d freebob returns the following: prak:~# jackd -R -v -d freebob getting driver descriptor from /usr/lib/jack/jack_alsa.so getting driver descriptor from /usr/lib/jack/jack_dummy.so getting driver descriptor from /usr/lib/jack/jack_freebob.so getting driver descriptor from /usr/lib/jack/jack_oss.so jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. server `default' registered loading driver .. registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via clock_gettime running with uid=0 and euid=0, will not try to use capabilites new client: freebob_pcm, id = 1 type 1 @ 0x806fc28 fd = -1 Freebob using Firewire port 0, node -1 new buffer size 1024 showDevice: not implemented FreeBoB MSG: Register MIDI IN port dev1c_MidiPort_1 FreeBoB MSG: Register MIDI OUT port dev1p_MidiPort_1 FreeBoB MSG: Streaming thread running with Realtime scheduling, priority 14 FreeBoB MSG: Registering capture port dev1c_MicIn1 left registered port freebob_pcm:dev1c_MicIn1 left, offset = 4096 FreeBoB MSG: Registering capture port dev1c_MicIn1 right registered port freebob_pcm:dev1c_MicIn1 right, offset = 8192 FreeBoB MSG: Registering capture port dev1c_LineIn 3+4 left registered port freebob_pcm:dev1c_LineIn 3+4 left, offset = 12288 FreeBoB MSG: Registering capture port dev1c_LineIn 3+4 right registered port freebob_pcm:dev1c_LineIn 3+4 right, offset = 16384 FreeBoB MSG: Registering capture port dev1c_LineIn 5+6 left registered port freebob_pcm:dev1c_LineIn 5+6 left, offset = 20480 FreeBoB MSG: Registering capture port dev1c_LineIn 5+6 right registered port freebob_pcm:dev1c_LineIn 5+6 right, offset = 24576 FreeBoB MSG: Registering capture port dev1c_LineIn 7+8 left registered port freebob_pcm:dev1c_LineIn 7+8 left, offset = 28672 FreeBoB MSG: Registering capture port dev1c_LineIn 7+8 right registered port freebob_pcm:dev1c_LineIn 7+8 right, offset = 32768 FreeBoB MSG: Registering capture port dev1c_SpdifIn left registered port freebob_pcm:dev1c_SpdifIn left, offset = 36864 FreeBoB MSG: Registering capture port dev1c_SpdifIn right registered port freebob_pcm:dev1c_SpdifIn right, offset = 40960 FreeBoB MSG: Don't register capture port dev1c_MidiPort_1 FreeBoB MSG: Registering playback port dev1p_LineOut 1+2 left registered port freebob_pcm:dev1p_LineOut 1+2 left, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 1+2 right registered port freebob_pcm:dev1p_LineOut 1+2 right, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 3+4 left registered port freebob_pcm:dev1p_LineOut 3+4 left, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 3+4 right registered port freebob_pcm:dev1p_LineOut 3+4 right, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 5+6 left registered port freebob_pcm:dev1p_LineOut 5+6 left, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 5+6 right registered port freebob_pcm:dev1p_LineOut 5+6 right, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 7+8 left registered port freebob_pcm:dev1p_LineOut 7+8 left, offset = 0 FreeBoB MSG: Registering playback port dev1p_LineOut 7+8 right registered port freebob_pcm:dev1p_LineOut 7+8 right, offset = 0 FreeBoB MSG: Registering playback port dev1p_SpdifOut left registered port freebob_pcm:dev1p_SpdifOut left, offset = 0 FreeBoB MSG: Registering playback port dev1p_SpdifOut right registered port freebob_pcm:dev1p_SpdifOut right, offset = 0 FreeBoB MSG: Don't register playback port dev1p_MidiPort_1 ++ jack_rechain_graph(): client freebob_pcm: internal client, execution_order=0. -- jack_rechain_graph() FreeBoB MSG: MIDI threads running with Realtime scheduling, priority 13 FreeBoB MSG: MIDI queue thread started libiec61883 warning: Established connection on channel 0. You may need to manually set the channel on the receiving node. libiec61883 warning: Established connection on channel 1. You may need to manually set the channel on the transmitting node. 3230 waiting for signals LibFreeBoB MSG: FreeBoB Streaming Device Init LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.0 LibFreeBoB MSG: Device information: LibFreeBoB MSG: Device options: LibFreeBoB MSG: Port : 0 LibFreeBoB MSG: Device Node Id : -1 LibFreeBoB MSG: Samplerate : 48000 LibFreeBoB MSG: Period Size : 1024 LibFreeBoB MSG: Nb Buffers : 3 LibFreeBoB MSG: Directions : 0 LibFreeBoB ERR: possible raw1394 error: Invalid argument LibFreeBoB ERR: Event buffer underrun on capture connection 0 Aborted prak:~# here are 1394 entries in my kernel config: # cat /boot/config-2.6.21 |grep 1394 # IEEE 1394 (FireWire) support CONFIG_IEEE1394=m # CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_OHCI1394=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set # CONFIG_IEEE1394_ETH1394 is not set # CONFIG_IEEE1394_DV1394 is not set CONFIG_IEEE1394_RAWIO=m my libiec61883 seems to be from debian unstable: ii libiec61883-0 1.1.0-2 an partial implementation of IEC 61883 # jackd -V jackd version 0.103.0 tmpdir /dev/shm protocol 16 # COLUMNS=60 dpkg -l |grep 1394 ii libavc1394-0 0.5.3-1 control IEEE 1394 audio/video devices ii libdc1394-13 1.1.0-3 high level programming interface for ii libraw1394-5 0.10.1-1.1 library for direct access to IEEE ii libraw1394-8 1.2.0-0.2 library for direct access to IEEE ii libraw1394-dev 1.2.1-2 library for direct access to IEEE 1394 anyone have any ideas? i'm not sure where i'm having problems this time? on the level of kernel or freebob code? thanks in advance! luka -- QOTD: "Just how much can I get away with and still go to heaven?" + http://viator.si |
From: Daniel W. <wa...@mo...> - 2007-06-18 06:53:44
|
> LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.0 BTW, the current vresion of libfreebob is 1.0.4 (though you can safely use 1.0.3 since 1.0.4 contains only a compile fix). The 1.0.0 version did run for my FA-101 but for sure I did have a different kernel version and different libraries versions. In general I would recommend to upgrade if this is an option. daniel |
From: Pieter P. <pi...@jo...> - 2007-06-18 12:42:41
|
Stefan Richter wrote: > Pieter Palmers wrote: >> I also have seen 'Invalid argument' errors on one of my machines, but I >> did't get to debugging this yet. They started appearing at some point >> on that machine. (around February 2007, or was it when I upgraded to >> Fedora6). This machine was one of my development machines and has 3 >> firewire host controllers that all worked fine before. >> >> Something happened, that's for sure. But I didn't figure it out yet. >> (and it will take another month before I have time to do it). > > Would be good if you could recall which software versions (notably > kernel version) worked and which broke. Indeed it would... but that's part of 'figuring it out' and hence will have to wait for a while :/. Pieter |
From: Pieter P. <pi...@jo...> - 2007-06-20 06:17:19
|
Luka Prinčič / Nova Viator wrote: > i will now try to put it to work on my thinkpad with a > pccard-firewire interface, which seem to be somewhat of a problem. > any suggestions? it seems to be a VIA chip. 16:00.0 FireWire (IEEE > 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) My first suggestion would be to be a little more precise about your problem :). And maybe the -dhw:1 option might help ( jackd ... -d freebob -d hw:1 ... ) Pieter |
From: Stefan R. <st...@s5...> - 2007-05-15 11:00:24
|
Pieter Palmers wrote: > Luka Prinčič / Nova Viator wrote: >> i compiled my own kernel for my laptop thinkpad t60p from debian >> kernel source. it's a 2.6.18 with following: # grep IEEE1394 >> /boot/config-`uname -r` CONFIG_IEEE1394=m # >> CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_IEEE1394_OUI_DB is >> not set CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y >> CONFIG_IEEE1394_CONFIG_ROM_IP1394=y # CONFIG_IEEE1394_EXPORT_FULL_API >> is not set CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_OHCI1394=m >> CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m # >> CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_IEEE1394_ETH1394=m >> CONFIG_IEEE1394_DV1394=m CONFIG_IEEE1394_RAWIO=m These options are OK, although you could leave some of them off. >> i'm using via-based pcmcia/pccard for firewire interface. when i >> insert the pccard, all is ok, syslog reports May 14 22:23:52 wonko >> kernel: ieee1394: Initialized config rom entry `ip1394' May 14 >> 22:23:52 wonko kernel: ieee1394: Host added: ID:BUS[0-00:1023] >> GUID[00110600000043dc] >> >> if i turn on fa-101 now, the system imediately freezes. > can you try removing dv1394? With 'removing' I mean deleting it from the > /lib/modules/... directory. > > dv1394 is know to freeze the system sometimes. Also, when I look at the release notes at http://www.linux1394.org/, we have a locking related bug in the ieee1394 base driver in 2.6.18 and older. So far I though that this bug would never manifest itself. I don't know if this bug causes this freeze. Luka, what if you switch to a text console [Ctrl + Alt + F1] before you turn on the FA-101? You may get a panic message from the kernel. If so, please write the messages down or take a foto, and let us know. >> however if i unload all ieee1394 drivers (eth1394 and ohci1394 and >> ieee1394) and turn on the card the system doesn't freeze. if i then >> load ieee1394 and raw1394, chmod a+rw /dev/raw1394, all is ok but What does "dmesg | grep 1394" show? >> jackd -dfreebob sais: >> >> $ jackd -R -dfreebob jackd 0.103.0 Copyright 2001-2005 Paul Davis and >> others. jackd comes with ABSOLUTELY NO WARRANTY This is free >> software, and you are welcome to redistribute it under certain >> conditions; see the file COPYING for details >> >> JACK compiled with System V SHM support. loading driver .. Freebob >> using Firewire port 0, node -1 Ieee1394Service::initialize: Could not >> get 1394 handle: Invalid argument Is ieee1394 and raw1394 driver >> loaded? Fatal (devicemanager.cpp)[68] initialize: Could not >> initialize Ieee1349Service object Fatal (freebob.cpp)[69] >> freebob_new_handle: Could not initialize device manager FreeBoB ERR: >> FREEBOB: Error creating virtual device cannot load driver module >> freebob Segmentation fault >> >> >> the same is when i first load the ieee1394 and raw1394 and then turn >> the card on. >> >> when unloading ohci1394 i get in syslog: ieee1394: Node removed: >> ID:BUS[0-00:1023] GUID[00110600000043dc] >> >> if i load ohci1394 again when the card is on, then it freezes, so i'm >> figuring the freeze problem has something to do with this module. is >> ohci1394 required for this setup to work? > ohci is essential. > >> any suggestions before i go compiling everything from latest and >> greatest sources? > > Try removing DV1394 and see if it helps. I CC'ed the linux1394-devel > list as this is more a 1394 problem than it is a freebob/ffado problem. Yes. Unless removing dv1394 already prevents the system freeze, it may be necessary to update the kernel. -- Stefan Richter -=====-=-=== -=-= -==== http://arcgraph.de/sr/ |
From: Stefan R. <st...@s5...> - 2007-06-17 22:23:55
|
Nova Viator wrote: > hi all! > > thanks for all the comments week or two ago on Edirol FA-101 problems > with freebob. i finally got time around to continue trying to hack this > nifty little box to work under linux. i still haven't managed to get > some sound from it, but there is some progress. > > as it seemed that on my laptop there could be problems with ieee1394 > pcmcia card (through which even under 2.6.21 kernel the machine freezed, > when i pluged/turned-on fa101), i moved to another machine, a box, with > athlon and working firewire card. > > i built new kernel (2.6.21) and tried. > > when i turn on the card i get this in dmesg/syslog: > > Jun 17 23:27:45 localhost kernel: ieee1394: Error parsing configrom for node 0-00:1023 No problem; this error was recoverable according to the "Node added..." message below. > Jun 17 23:27:45 localhost kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023 > Jun 17 23:27:48 localhost kernel: doh, someone wants to mess with state set This is also harmless. The FA-101 probably tried a valid but not vital access to the "state set" register. > Jun 17 23:27:48 localhost kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0040ab0000c22bb7] > Jun 17 23:27:48 localhost kernel: ieee1394: raw1394: /dev/raw1394 device initialized > > i have configrom checked in kernel, should i not compile it in? This configuration option is unrelated to the message above. (Besides, that option is somewhat pointless and only needed for eth1394. The option will be replaced by an internal automatism in the next kernel release.) > so far everything seems ok. however running > # jackd -R -v -d freebob > returns the following: > > > prak:~# jackd -R -v -d freebob > getting driver descriptor from /usr/lib/jack/jack_alsa.so > getting driver descriptor from /usr/lib/jack/jack_dummy.so > getting driver descriptor from /usr/lib/jack/jack_freebob.so > getting driver descriptor from /usr/lib/jack/jack_oss.so > jackd 0.103.0 > Copyright 2001-2005 Paul Davis and others. > jackd comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > > JACK compiled with System V SHM support. > server `default' registered > loading driver .. > registered builtin port type 32 bit float mono audio > registered builtin port type 8 bit raw midi > clock source = system clock via clock_gettime > running with uid=0 and euid=0, will not try to use capabilites > new client: freebob_pcm, id = 1 type 1 @ 0x806fc28 fd = -1 > Freebob using Firewire port 0, node -1 > new buffer size 1024 > showDevice: not implemented > FreeBoB MSG: Register MIDI IN port dev1c_MidiPort_1 > FreeBoB MSG: Register MIDI OUT port dev1p_MidiPort_1 > FreeBoB MSG: Streaming thread running with Realtime scheduling, priority > 14 > FreeBoB MSG: Registering capture port dev1c_MicIn1 left > registered port freebob_pcm:dev1c_MicIn1 left, offset = 4096 > FreeBoB MSG: Registering capture port dev1c_MicIn1 right > registered port freebob_pcm:dev1c_MicIn1 right, offset = 8192 > FreeBoB MSG: Registering capture port dev1c_LineIn 3+4 left > registered port freebob_pcm:dev1c_LineIn 3+4 left, offset = 12288 > FreeBoB MSG: Registering capture port dev1c_LineIn 3+4 right > registered port freebob_pcm:dev1c_LineIn 3+4 right, offset = 16384 > FreeBoB MSG: Registering capture port dev1c_LineIn 5+6 left > registered port freebob_pcm:dev1c_LineIn 5+6 left, offset = 20480 > FreeBoB MSG: Registering capture port dev1c_LineIn 5+6 right > registered port freebob_pcm:dev1c_LineIn 5+6 right, offset = 24576 > FreeBoB MSG: Registering capture port dev1c_LineIn 7+8 left > registered port freebob_pcm:dev1c_LineIn 7+8 left, offset = 28672 > FreeBoB MSG: Registering capture port dev1c_LineIn 7+8 right > registered port freebob_pcm:dev1c_LineIn 7+8 right, offset = 32768 > FreeBoB MSG: Registering capture port dev1c_SpdifIn left > registered port freebob_pcm:dev1c_SpdifIn left, offset = 36864 > FreeBoB MSG: Registering capture port dev1c_SpdifIn right > registered port freebob_pcm:dev1c_SpdifIn right, offset = 40960 > FreeBoB MSG: Don't register capture port dev1c_MidiPort_1 > FreeBoB MSG: Registering playback port dev1p_LineOut 1+2 left > registered port freebob_pcm:dev1p_LineOut 1+2 left, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 1+2 right > registered port freebob_pcm:dev1p_LineOut 1+2 right, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 3+4 left > registered port freebob_pcm:dev1p_LineOut 3+4 left, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 3+4 right > registered port freebob_pcm:dev1p_LineOut 3+4 right, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 5+6 left > registered port freebob_pcm:dev1p_LineOut 5+6 left, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 5+6 right > registered port freebob_pcm:dev1p_LineOut 5+6 right, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 7+8 left > registered port freebob_pcm:dev1p_LineOut 7+8 left, offset = 0 > FreeBoB MSG: Registering playback port dev1p_LineOut 7+8 right > registered port freebob_pcm:dev1p_LineOut 7+8 right, offset = 0 > FreeBoB MSG: Registering playback port dev1p_SpdifOut left > registered port freebob_pcm:dev1p_SpdifOut left, offset = 0 > FreeBoB MSG: Registering playback port dev1p_SpdifOut right > registered port freebob_pcm:dev1p_SpdifOut right, offset = 0 > FreeBoB MSG: Don't register playback port dev1p_MidiPort_1 > ++ jack_rechain_graph(): > client freebob_pcm: internal client, execution_order=0. > -- jack_rechain_graph() > FreeBoB MSG: MIDI threads running with Realtime scheduling, priority 13 > FreeBoB MSG: MIDI queue thread started > libiec61883 warning: Established connection on channel 0. > You may need to manually set the channel on the receiving node. > libiec61883 warning: Established connection on channel 1. > You may need to manually set the channel on the transmitting node. > 3230 waiting for signals > LibFreeBoB MSG: FreeBoB Streaming Device Init > LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.0 > LibFreeBoB MSG: Device information: > LibFreeBoB MSG: Device options: > LibFreeBoB MSG: Port : 0 > LibFreeBoB MSG: Device Node Id : -1 > LibFreeBoB MSG: Samplerate : 48000 > LibFreeBoB MSG: Period Size : 1024 > LibFreeBoB MSG: Nb Buffers : 3 > LibFreeBoB MSG: Directions : 0 > LibFreeBoB ERR: possible raw1394 error: Invalid argument > LibFreeBoB ERR: Event buffer underrun on capture connection 0 > Aborted > prak:~# Hmm, I'm not experienced with FireWire streaming appliations, so this doesn't tell me a lot. What about "dmesg | tail" right after you got the invalid argument/ buffer underrun error? What card is it? I.e. "lspci" or shorter "lspci | grep 1394". > here are 1394 entries in my kernel config: > > # cat /boot/config-2.6.21 |grep 1394 > # IEEE 1394 (FireWire) support > CONFIG_IEEE1394=m > # CONFIG_IEEE1394_VERBOSEDEBUG is not set > # CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set > CONFIG_IEEE1394_PCILYNX=m > CONFIG_IEEE1394_OHCI1394=m > CONFIG_IEEE1394_VIDEO1394=m > CONFIG_IEEE1394_SBP2=m > # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set > # CONFIG_IEEE1394_ETH1394 is not set > # CONFIG_IEEE1394_DV1394 is not set > CONFIG_IEEE1394_RAWIO=m Looks good. > my libiec61883 seems to be from debian unstable: > ii libiec61883-0 1.1.0-2 an partial implementation of IEC 61883 > > # jackd -V > jackd version 0.103.0 tmpdir /dev/shm protocol 16 > > # COLUMNS=60 dpkg -l |grep 1394 > ii libavc1394-0 0.5.3-1 control IEEE 1394 audio/video devices > ii libdc1394-13 1.1.0-3 high level programming interface for > ii libraw1394-5 0.10.1-1.1 library for direct access to IEEE > ii libraw1394-8 1.2.0-0.2 library for direct access to IEEE > ii libraw1394-dev 1.2.1-2 library for direct access to IEEE 1394 > > > > > anyone have any ideas? i'm not sure where i'm having problems this time? > on the level of kernel or freebob code? > > thanks in advance! > > luka > -- Stefan Richter -=====-=-=== -==- =--=- http://arcgraph.de/sr/ |
From: Nova V. <no...@vi...> - 2007-06-18 00:27:51
|
On Mon, 2007-06-18 at 00:23 +0200, Stefan Richter wrote: > Hmm, I'm not experienced with FireWire streaming appliations, so this > doesn't tell me a lot. What about "dmesg | tail" right after you got > the invalid argument/ buffer underrun error? not a thing. > What card is it? I.e. "lspci" or shorter "lspci | grep 1394". $ lspci | grep 1394 05:07.0 FireWire (IEEE 1394): NEC Corporation uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr (rev 01) ( the cardbus one on my laptop, which seems to be connected to freezes, is 16:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) ) ll. -- ... the HIGHWAY is made out of LIME JELLO and my HONDA is a barbequeued OYSTER! Yum! + http://viator.si |
From: Pieter P. <pi...@jo...> - 2007-06-18 09:14:10
|
Stefan Richter wrote: > Nova Viator wrote: >> hi all! >> [...] >> LibFreeBoB MSG: FreeBoB Streaming Device Init >> LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.0 >> LibFreeBoB MSG: Device information: >> LibFreeBoB MSG: Device options: >> LibFreeBoB MSG: Port : 0 >> LibFreeBoB MSG: Device Node Id : -1 >> LibFreeBoB MSG: Samplerate : 48000 >> LibFreeBoB MSG: Period Size : 1024 >> LibFreeBoB MSG: Nb Buffers : 3 >> LibFreeBoB MSG: Directions : 0 >> LibFreeBoB ERR: possible raw1394 error: Invalid argument >> LibFreeBoB ERR: Event buffer underrun on capture connection 0 >> Aborted >> prak:~# > > Hmm, I'm not experienced with FireWire streaming appliations, so this > doesn't tell me a lot. What about "dmesg | tail" right after you got > the invalid argument/ buffer underrun error? > > What card is it? I.e. "lspci" or shorter "lspci | grep 1394". > I also have seen 'Invalid argument' errors on one of my machines, but I did't get to debugging this yet. They started appearing at some point on that machine. (around February 2007, or was it when I upgraded to Fedora6). This machine was one of my development machines and has 3 firewire host controllers that all worked fine before. Something happened, that's for sure. But I didn't figure it out yet. (and it will take another month before I have time to do it). Greets, Pieter |
From: Stefan R. <st...@s5...> - 2007-06-18 12:06:02
|
Pieter Palmers wrote: > I also have seen 'Invalid argument' errors on one of my machines, but I > did't get to debugging this yet. They started appearing at some point > on that machine. (around February 2007, or was it when I upgraded to > Fedora6). This machine was one of my development machines and has 3 > firewire host controllers that all worked fine before. > > Something happened, that's for sure. But I didn't figure it out yet. > (and it will take another month before I have time to do it). Would be good if you could recall which software versions (notably kernel version) worked and which broke. -- Stefan Richter -=====-=-=== -==- =--=- http://arcgraph.de/sr/ |
From: Luka / N. V. <no...@vi...> - 2007-06-20 01:19:21
|
On Mon, 18 Jun 2007 14:42:35 +0200 Pieter Palmers <pi...@jo...> wrote: > Stefan Richter wrote: > >> Something happened, that's for sure. But I didn't figure it out yet. > >> (and it will take another month before I have time to do it). > > Would be good if you could recall which software versions (notably > > kernel version) worked and which broke. > Indeed it would... but that's part of 'figuring it out' and hence will > have to wait for a while :/. hi all! thanks for all the responses. i managed to put the thing to work and it was quite simple, and, unfortunately i don't know what caused previous malfunctions. all i did was the following on my debian unstable machine i just apt-get all build-dependencies for libraw1394, libfreebob0 and jackd. i then apt-got -b source libraw1394, libfreebob0 and jackd, which means apt-get fetched the source packages and built them. i then installed all binary packages, and it just worked. to wrap it up, it's a kernel 2.6.21 and libraw1394-8 1.2.1-3 libraw1394-dev 1.2.1-3 libfreebob0 1.0.3+svn443-2 libfreebob0-dev 1.0.3+svn443-2 jackd 0.103.0-5 hope someone helps this. i will now try to put it to work on my thinkpad with a pccard-firewire interface, which seem to be somewhat of a problem. any suggestions? it seems to be a VIA chip. 16:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) ll. -- I have a map of the United States. It's actual size. I spent last summer folding it. People ask me where I live, and I say, "E6". -- Steven Wright + http://viator.si |
From: Luka P. / N. V. <no...@vi...> - 2007-07-13 00:28:31
|
On Wed, 20 Jun 2007 08:17:08 +0200 Pieter Palmers <pi...@jo...> wrote: > Luka Prinčič / Nova Viator wrote: > > > i will now try to put it to work on my thinkpad with a > > pccard-firewire interface, which seem to be somewhat of a problem. > > any suggestions? it seems to be a VIA chip. 16:00.0 FireWire (IEEE > > 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) > > My first suggestion would be to be a little more precise about your > problem :). And maybe the -dhw:1 option might help ( jackd ... -d > freebob -d hw:1 ... ) hi all a while ago i reported some freeze problems connecting my edirol fa-101 to my thinkpad laptop using a cardbus firewire card. http://sourceforge.net/mailarchive/forum.php?thread_name=20070515001823.0a2ab3e4.nova%40viator.si&forum_name=ffado-devel i just wanted to report that i eliminated fa-101 as a problem, because i finally managed to find a dv cam which i connected to this cardbus firewire card and that caused a freeze too. i'm not sure how to handle this now, but i guess i will be looking for another cardbus pcmcia card. the card i'm using was bought through thomman.de and it's a "SUNIX 1394A cardBus" and is reported as 16:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) with lspci. as i wrote before fa-101 works fine on my other machine with a pci firewire card. thanks to freebob efforts! thanks everyone for that! l, luka -- If something has not yet gone wrong then it would ultimately have been beneficial for it to go wrong. + http://viator.si |
From: Stefan R. <st...@s5...> - 2007-07-13 07:07:35
|
Luka Princic / Nova Viator wrote: > the card i'm using was bought through > thomman.de and it's a "SUNIX 1394A cardBus" and is reported as > 16:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host > Controller (rev 80) with lspci. Is it a 3-port card or 2-port card? http://www.sunix.com.tw/it/en/Product_Sub.php?cate=2&class_a_id=23&class_b_id=65 I have a card whose package was branded as Digitus (no brand on the card itself) and which looks exactly like the 3-port Sunix card. Alas it has a different chip than your card: 06:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) But I also have an onboard chip which seems to be the sam as on your card: 05:04.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) I observed no problem with it, but I haven't tried it with a streaming-capable device yet. Right now I have not much time for tests; what we need is a kernel panic message (which can be difficult to get, may require serial console or netconsole) and ideally a way to reproduce the problem. I could try sometime, but don't know when. Your card might be defective though, and if so, the maximum we would be unable to make it fully operational. But that's just speculation for now. -- Stefan Richter -=====-=-=== -=== -==-= http://arcgraph.de/sr/ |