|
»
»
»
Focusrite Saffire LE
|
View:
New views
15 Messages
—
Rating Filter:
Alert me
|
 |
Focusrite Saffire LE
by Chris Wenn-2
::
Rate this Message:
Hi All
I'm having significant trouble getting a Saffire LE to work with my setup. I have a Dell XPS M1210, running Ubuntu Studio. Because the inbuilt firewire device is the infamous RICOH chipset, I am forced to use a firewire Expresscard/32, detailed below :~$ lspci -v 0e:00.0 FireWire (IEEE 1394): Texas Instruments XIO2200(A) IEEE-1394a-2000 Controller (PHY/Link) (rev 01) (prog-if 10 [OHCI]) Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 Memory at ecc04000 (32-bit, non-prefetchable) [size=2K] Memory at ecc00000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 I am able to configure and start jack, :~$ /usr/bin/jackd -v -R -P89 -dfreebob -dhw:0 -r48000 -p128 -n3 Which produces getting driver descriptor from /usr/lib/jack/jack_dummy.so getting driver descriptor from /usr/lib/jack/jack_oss.so getting driver descriptor from /usr/lib/jack/jack_freebob.so getting driver descriptor from /usr/lib/jack/jack_alsa.so jackd 0.109.2 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 registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via clock_gettime loading driver .. new client: freebob_pcm, id = 1 type 1 @ 0x806ff40 fd = -1 Freebob using Firewire port 0, node -1 new buffer size 1024 LibFreeBoB MSG: FreeBoB Streaming Device Init LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.7 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 showDevice: not implemented FreeBoB MSG: Register MIDI IN port dev1c_Midi In FreeBoB MSG: Register MIDI OUT port dev1p_Midi Out FreeBoB MSG: Streaming thread running with Realtime scheduling, priority 14 FreeBoB MSG: Registering audio capture port C0_dev1c_Rec 1 FreeBoB MSG: Registering audio capture port C1_dev1c_Rec 2 FreeBoB MSG: Registering audio capture port C2_dev1c_Rec 3 FreeBoB MSG: Registering audio capture port C3_dev1c_Rec 4 FreeBoB MSG: Registering audio capture port C4_dev1c_Rec 5 FreeBoB MSG: Registering audio capture port C5_dev1c_Rec 6 registered port system:capture_1, offset = 4096 registered port system:capture_2, offset = 8192 registered port system:capture_3, offset = 12288 registered port system:capture_4, offset = 16384 registered port system:capture_5, offset = 20480 registered port system:capture_6, offset = 24576 FreeBoB MSG: Don't register capture port for dev1c_Midi In FreeBoB MSG: Registering playback audio port P0_dev1p_Play 1 FreeBoB MSG: Registering playback audio port P1_dev1p_Play 2 FreeBoB MSG: Registering playback audio port P2_dev1p_Play 3 FreeBoB MSG: Registering playback audio port P3_dev1p_Play 4 FreeBoB MSG: Registering playback audio port P4_dev1p_Play 5 FreeBoB MSG: Registering playback audio port P5_dev1p_Play 6 FreeBoB MSG: Registering playback audio port P6_dev1p_Play 7 FreeBoB MSG: Registering playback audio port P7_dev1p_Play 8 FreeBoB MSG: Don't register playback port dev1p_Midi Out registered port system:playback_1, offset = 0 registered port system:playback_2, offset = 0 registered port system:playback_3, offset = 0 registered port system:playback_4, offset = 0 registered port system:playback_5, offset = 0 registered port system:playback_6, offset = 0 registered port system:playback_7, offset = 0 registered port system:playback_8, offset = 0 ++ 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. 20268 waiting for signals Aborted Almost as soon as jack is 'waiting for signals' it aborts, and that's it. Can anyone help me? I'm going crazy! Chris _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE
by Pieter Palmers
::
Rate this Message:
Chris Wenn wrote:
> Hi All > > I'm having significant trouble getting a Saffire LE to work with my > setup. > > I have a Dell XPS M1210, running Ubuntu Studio. Because the inbuilt > firewire device is the infamous RICOH chipset, I am forced to use a > firewire Expresscard/32, detailed below > > :~$ lspci -v > > 0e:00.0 FireWire (IEEE 1394): Texas Instruments XIO2200(A) > IEEE-1394a-2000 Controller (PHY/Link) (rev 01) (prog-if 10 [OHCI]) > Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18 > Memory at ecc04000 (32-bit, non-prefetchable) [size=2K] > Memory at ecc00000 (32-bit, non-prefetchable) [size=16K] > Capabilities: [44] Power Management version 2 > > I am able to configure and start jack, > > :~$ /usr/bin/jackd -v -R -P89 -dfreebob -dhw:0 -r48000 -p128 -n3 > > Which produces > > getting driver descriptor from /usr/lib/jack/jack_dummy.so > getting driver descriptor from /usr/lib/jack/jack_oss.so > getting driver descriptor from /usr/lib/jack/jack_freebob.so > getting driver descriptor from /usr/lib/jack/jack_alsa.so > jackd 0.109.2 > 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 > registered builtin port type 32 bit float mono audio > registered builtin port type 8 bit raw midi > clock source = system clock via clock_gettime > loading driver .. > new client: freebob_pcm, id = 1 type 1 @ 0x806ff40 fd = -1 > Freebob using Firewire port 0, node -1 > new buffer size 1024 > LibFreeBoB MSG: FreeBoB Streaming Device Init > LibFreeBoB MSG: Using FreeBoB lib version libfreebob 1.0.7 > 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 > showDevice: not implemented > FreeBoB MSG: Register MIDI IN port dev1c_Midi In > FreeBoB MSG: Register MIDI OUT port dev1p_Midi Out > FreeBoB MSG: Streaming thread running with Realtime scheduling, priority > 14 > FreeBoB MSG: Registering audio capture port C0_dev1c_Rec 1 > FreeBoB MSG: Registering audio capture port C1_dev1c_Rec 2 > FreeBoB MSG: Registering audio capture port C2_dev1c_Rec 3 > FreeBoB MSG: Registering audio capture port C3_dev1c_Rec 4 > FreeBoB MSG: Registering audio capture port C4_dev1c_Rec 5 > FreeBoB MSG: Registering audio capture port C5_dev1c_Rec 6 > registered port system:capture_1, offset = 4096 > registered port system:capture_2, offset = 8192 > registered port system:capture_3, offset = 12288 > registered port system:capture_4, offset = 16384 > registered port system:capture_5, offset = 20480 > registered port system:capture_6, offset = 24576 > FreeBoB MSG: Don't register capture port for dev1c_Midi In > FreeBoB MSG: Registering playback audio port P0_dev1p_Play 1 > FreeBoB MSG: Registering playback audio port P1_dev1p_Play 2 > FreeBoB MSG: Registering playback audio port P2_dev1p_Play 3 > FreeBoB MSG: Registering playback audio port P3_dev1p_Play 4 > FreeBoB MSG: Registering playback audio port P4_dev1p_Play 5 > FreeBoB MSG: Registering playback audio port P5_dev1p_Play 6 > FreeBoB MSG: Registering playback audio port P6_dev1p_Play 7 > FreeBoB MSG: Registering playback audio port P7_dev1p_Play 8 > FreeBoB MSG: Don't register playback port dev1p_Midi Out > registered port system:playback_1, offset = 0 > registered port system:playback_2, offset = 0 > registered port system:playback_3, offset = 0 > registered port system:playback_4, offset = 0 > registered port system:playback_5, offset = 0 > registered port system:playback_6, offset = 0 > registered port system:playback_7, offset = 0 > registered port system:playback_8, offset = 0 > ++ 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. > 20268 waiting for signals > Aborted > > Almost as soon as jack is 'waiting for signals' it aborts, and that's > it. > > Can anyone help me? I'm going crazy! Have you tried higher/lower period sizes? It might have something to do with a bug/issue present in the firewire stack related to output ISO streams. There is a fix for this in the 2.6.26 kernels. The issue manifests itself in the kernel not requesting any outgoing ISO packets anymore. Hence the jack process cycle doesn't run anymore and jack aborts. I have seen this happen with some cards, but only on a PCI express system (dell d820). With the on-board controller and with a based XIO2200 1394 expresscard. However it could also be something else. I would recommend that you install FFADO to drive the saffire LE, since FFADO has a lot more verbose debugging output, and more checks to catch this kind of issue. http://www.ffado.org/?q=node/613 might help you install it. Then join the ffado-user mailing list to further discuss this. Greets, Pieter Palmers _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE
by Chris Wenn-2
::
Rate this Message:
OK
I have compiled FFADO and the svn Jack, as suggested, and I'm still not winning (see attachment) I've tried 'Force Bus Reset' in gscanbus, rebooting several times, ejecting and reinserting the card, and powering the Saffire LE on and off. If anyone can provide any assistance, I'd be grateful. Chris getting driver descriptor from /usr/lib/jack/jack_dummy.so getting driver descriptor from /usr/lib/jack/jack_firewire.so getting driver descriptor from /usr/lib/jack/jack_oss.so getting driver descriptor from /usr/lib/jack/jack_freebob.so getting driver descriptor from /usr/lib/jack/jack_alsa.so jackd 0.112.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. registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via clock_gettime start poll on 3 fd's loading driver .. new client: firewire_pcm, id = 1 type 1 @ 0x806b0e8 fd = -1 new buffer size 1024 registered port system:capture_1, offset = 4096 registered port system:capture_2, offset = 8192 registered port system:capture_3, offset = 12288 registered port system:capture_4, offset = 16384 registered port system:capture_5, offset = 20480 registered port system:capture_6, offset = 24576 registered port system:midi_capture_1, offset = 4096 registered port system:playback_1, offset = 0 registered port system:playback_2, offset = 0 registered port system:playback_3, offset = 0 registered port system:playback_4, offset = 0 registered port system:playback_5, offset = 0 registered port system:playback_6, offset = 0 registered port system:playback_7, offset = 0 registered port system:playback_8, offset = 0 registered port system:midi_playback_1, offset = 0 ++ jack_sort_graph ++ jack_rechain_graph(): +++ client is now firewire_pcm active ? 1 client firewire_pcm: internal client, execution_order=0. -- jack_rechain_graph() -- jack_sort_graph starting server engine shutdown stopping driver server thread back from poll unloading driver _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE
by Pieter Palmers
::
Rate this Message:
Chris Wenn wrote:
> OK > > I have compiled FFADO and the svn Jack, as suggested, and I'm still not > winning (see attachment) > > I've tried 'Force Bus Reset' in gscanbus, rebooting several times, > ejecting and reinserting the card, and powering the Saffire LE on and > off. If anyone can provide any assistance, I'd be grateful. > Please provide debug logs as described in the README in the ffado tarball. Pieter _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
|
|
|
Re: Focusrite Saffire LE
by Chris Wenn-2
::
Rate this Message:
On Sat, 2008-07-05 at 14:57 +0200, Pieter Palmers wrote:
> > > I also need the output of the diag tool. > > Greets, > > Pieter > OK - sorry. Here it is. [dia.log] FFADO diagnostic utility 0.1 ============================ (C) 2008 Pieter Palmers === CHECK === Base system... kernel version............ 2.6.24-19-rt FIXME: implement test for RT kernel RT patched............... False old 1394 stack present.... True old 1394 stack loaded..... True new 1394 stack present.... False new 1394 stack loaded..... False /dev/raw1394 node present. True /dev/raw1394 permissions.. True Prerequisites... gcc................ gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) g++................ g++ (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) PyQt............... Python User Interface Compiler 3.17.4 for Qt version 3.3.8b jackd.............. jackd version 0.112.0 tmpdir /dev/shm/ protocol 23 path............. /usr/bin/jackd flags............ -ljack -lpthread -lrt libraw1394......... 1.3.0 flags............ -lraw1394 libavc1394......... 0.5.3 flags............ -lavc1394 -lrom1394 -lraw1394 libiec61883........ 1.1.0 flags............ -liec61883 -lraw1394 libxml++-2.6....... 2.20.0 flags............ -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 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0 dbus-1............. 1.1.20 flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 Hardware... Host controllers: 0e:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments XIO2200(A) IEEE-1394a-2000 Controller (PHY/Link) [104c:8235] (rev 01) (prog-if 10 [OHCI]) Subsystem: Unknown device [5678:1234] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (500ns min, 1000ns max) Interrupt: pin A routed to IRQ 18 Region 0: Memory at ecc04000 (32-bit, non-prefetchable) [size=2K] Region 1: Memory at ecc00000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> CPU info: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping : 6 cpu MHz : 2167.000 cache size : 4096 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 4331.16 clflush size : 64 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping : 6 cpu MHz : 2167.000 cache size : 4096 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 4327.54 clflush size : 64 Configuration... IRQ information Hardware Interrupts: -------------------- IRQ 0: PID: None, count: [55323164, 55323164], Sched None (priority None), drivers: ['timer'] IRQ 1: PID: 836, count: [10, 10], Sched FF (priority 50), drivers: ['i8042'] IRQ 8: PID: 801, count: [7, 7], Sched FF (priority 50), drivers: ['rtc'] IRQ 9: PID: 72, count: [3, 3], Sched FF (priority 50), drivers: ['acpi'] IRQ 12: PID: 835, count: [123, 123], Sched FF (priority 50), drivers: ['i8042'] IRQ 14: PID: 2099, count: [101452, 101452], Sched FF (priority 50), drivers: ['libata'] IRQ 15: PID: 2100, count: [72490, 72490], Sched FF (priority 50), drivers: ['libata'] IRQ 16: PID: 6014, count: [453276, 453276], Sched FF (priority 50), drivers: ['nvidia'] IRQ 17: PID: 5726, count: [105825, 105825], Sched FF (priority 50), drivers: ['eth0'] IRQ 18: PID: 11241, count: [96, 96], Sched FF (priority 50), drivers: ['ohci1394'] IRQ 19: PID: 2062, count: [403162, 403162], Sched FF (priority 50), drivers: ['uhci_hcd:usb1', 'ehci_hcd:usb5'] IRQ 20: PID: 2066, count: [3265128, 3265128], Sched FF (priority 50), drivers: ['uhci_hcd:usb2', 'HDA Intel'] IRQ 21: PID: 2067, count: [25, 25], Sched FF (priority 50), drivers: ['uhci_hcd:usb3'] IRQ 22: PID: 2072, count: [1306, 1306], Sched FF (priority 50), drivers: ['uhci_hcd:usb4'] IRQ 219: PID: 3931, count: [37436, 37436], Sched FF (priority 50), drivers: ['iwl3945'] IRQ 220: PID: 4510, count: [1, 1], Sched FF (priority 50), drivers: ['pciehp'] IRQ 221: PID: 4509, count: [0, 0], Sched FF (priority 50), drivers: ['pciehp'] IRQ 222: PID: 4506, count: [0, 0], Sched FF (priority 50), drivers: ['pciehp'] Software Interrupts: -------------------- SoftIRQ block/0-9: PID 9, Sched FF (priority 50), name: softirq-block/0 SoftIRQ block/1-22: PID 22, Sched FF (priority 50), name: softirq-block/1 SoftIRQ high/0-5: PID 5, Sched FF (priority 50), name: softirq-high/0 SoftIRQ high/1-18: PID 18, Sched FF (priority 50), name: softirq-high/1 SoftIRQ hrtimer-12: PID 12, Sched FF (priority 50), name: softirq-hrtimer SoftIRQ hrtimer-25: PID 25, Sched FF (priority 50), name: softirq-hrtimer SoftIRQ net-rx/-21: PID 21, Sched FF (priority 50), name: softirq-net-rx/ SoftIRQ net-rx/-8: PID 8, Sched FF (priority 50), name: softirq-net-rx/ SoftIRQ net-tx/-20: PID 20, Sched FF (priority 50), name: softirq-net-tx/ SoftIRQ net-tx/-7: PID 7, Sched FF (priority 50), name: softirq-net-tx/ SoftIRQ rcu/0-13: PID 13, Sched FF (priority 50), name: softirq-rcu/0 SoftIRQ rcu/1-26: PID 26, Sched FF (priority 50), name: softirq-rcu/1 SoftIRQ sched/0-11: PID 11, Sched FF (priority 50), name: softirq-sched/0 SoftIRQ sched/1-24: PID 24, Sched FF (priority 50), name: softirq-sched/1 SoftIRQ tasklet-10: PID 10, Sched FF (priority 50), name: softirq-tasklet SoftIRQ tasklet-23: PID 23, Sched FF (priority 50), name: softirq-tasklet SoftIRQ timer/0-6: PID 6, Sched FF (priority 50), name: softirq-timer/0 SoftIRQ timer/1-19: PID 19, Sched FF (priority 50), name: softirq-timer/1 === REPORT === FireWire kernel drivers: [PASS] Kernel modules present and correctly loaded. [PASS] /dev/raw1394 node present and accessible. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE
by Pieter Palmers
::
Rate this Message:
Chris Wenn wrote:
> On Sat, 2008-07-05 at 14:57 +0200, Pieter Palmers wrote: >> I also need the output of the diag tool. >> >> Greets, >> >> Pieter >> > > OK - sorry. > > Here it is. > Thanks for the information. Unfortunately I don't have a direct solution for you at the moment. Apparently the device generates a bus reset right after FFADO starts streaming to it. I don't know why this happens. What you can do to help debug this is: in config.h.in change: #define DEBUG_EXTREME_ENABLE 0 to #define DEBUG_EXTREME_ENABLE 1 and recompile/reinstall ffado. Then run jackd with verbose level of 8, but definitely capture the output to a file. it will generate a huge amount of debug output. Send me the output log (private mail is ok). Greets, Pieter _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Pieter Palmers
::
Rate this Message:
Pieter Palmers wrote:
> Chris Wenn wrote: >> On Sat, 2008-07-05 at 14:57 +0200, Pieter Palmers wrote: >>> I also need the output of the diag tool. >>> >>> Greets, >>> >>> Pieter >>> >> OK - sorry. >> >> Here it is. >> > > Thanks for the information. > > Unfortunately I don't have a direct solution for you at the moment. > > Apparently the device generates a bus reset right after FFADO starts > streaming to it. I don't know why this happens. > > What you can do to help debug this is: > in config.h.in change: > > #define DEBUG_EXTREME_ENABLE 0 > to > #define DEBUG_EXTREME_ENABLE 1 > and recompile/reinstall ffado. > > Then run jackd with verbose level of 8, but definitely capture the > output to a file. it will generate a huge amount of debug output. Send > me the output log (private mail is ok). Replying to myself: I see that there is a problem when compiling with extreme debugging enabled. you can grab a corrected version by checking out the libffado-2.0 maintenance branch: svn co http://subversion.ffado.org/ffado/branches/libffado-2.0 libffado-2.0 Greets, Pieter _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Chris Wenn-2
::
Rate this Message:
Hi Pieter and anyone else following this discussion.
After some additional troubleshooting, I've discovered that either the Expresscard or the Expresscard adapter in my M1210 is the culprit in this problem. I hope it's the card, because at least I can throw that out :) I got desperate and tried out the whole setup in Windows (*sigh*), and it didn't work there either. Interestingly, the onboard Ricoh firewire works perfectly - it's total failure to work at all in Linux was the start of this quest, so I'm a bit bewildered. Anyway, thanks to everyone for the help and goodwill. Chris _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Pieter Palmers
::
Rate this Message:
Chris Wenn wrote:
> Hi Pieter and anyone else following this discussion. > > After some additional troubleshooting, I've discovered that either the > Expresscard or the Expresscard adapter in my M1210 is the culprit in > this problem. I hope it's the card, because at least I can throw that > out :) > > I got desperate and tried out the whole setup in Windows (*sigh*), and > it didn't work there either. DELL has some bios updates mentioning expresscard support improvements for some laptops, maybe that's the case for you too? In any case, it should be possible to make it work on windows, or work with DELL to make it work. Usually they are less reluctant to help windows users than they are to help Linux users. They always seem to expect that crappy hardware is due to the Linux OS. > > Interestingly, the onboard Ricoh firewire works perfectly - it's total > failure to work at all in Linux was the start of this quest, so I'm a > bit bewildered. The Ricoh controller is a mistery to me too. I really can't figure out what the exact problem is. In the logs you provided I don't see it though. What version of the Ricoh chip do you have? Greets, Pieter _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Chris Wenn-2
::
Rate this Message:
On Wed, Jul 16, 2008 at 12:51 AM, Pieter Palmers <pieterp@...> wrote:
I'm on rev. A07 and there's an A08, so I'll try to get that to work - seems it has to be installed from the first partition (which Windows isn't) and I've mislaid my documentation for updating from Linux. In any case, using the Saffire via the Expresscard produced really strange timing errors (audio was crackly and slowed down by about 50%, with huge CPU usage) under Windows, however the Ricoh device worked fine.
The 8522, IIRC - integrated with SD/MMC reader. Under Linux (both Ubuntu and 64Studio) it crashes out with an Iso Xmit Error 0, as described here http://freebob.sourceforge.net/index.php/FAQ, which seems to be unrecoverable. In Windows it's working fine - which goes against reports I'd seen of the problem being cross-platform... Chris _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Pieter Palmers
::
Rate this Message:
Chris Wenn wrote:
> > > On Wed, Jul 16, 2008 at 12:51 AM, Pieter Palmers <pieterp@... > <mailto:pieterp@...>> wrote: > > Chris Wenn wrote: > > Hi Pieter and anyone else following this discussion. > > After some additional troubleshooting, I've discovered that > either the > Expresscard or the Expresscard adapter in my M1210 is the culprit in > this problem. I hope it's the card, because at least I can throw > that > out :) > > I got desperate and tried out the whole setup in Windows > (*sigh*), and > it didn't work there either. > > DELL has some bios updates mentioning expresscard support > improvements for some laptops, maybe that's the case for you too? > > In any case, it should be possible to make it work on windows, or > work with DELL to make it work. Usually they are less reluctant to > help windows users than they are to help Linux users. They always > seem to expect that crappy hardware is due to the Linux OS. > > > I'm on rev. A07 and there's an A08, so I'll try to get that to work - > seems it has to be installed from the first partition (which Windows > isn't) and I've mislaid my documentation for updating from Linux. In any > case, using the Saffire via the Expresscard produced really strange > timing errors (audio was crackly and slowed down by about 50%, with huge > CPU usage) under Windows, however the Ricoh device worked fine. > > > > > Interestingly, the onboard Ricoh firewire works perfectly - it's > total > failure to work at all in Linux was the start of this quest, so > I'm a > bit bewildered. > > > The Ricoh controller is a mistery to me too. I really can't figure > out what the exact problem is. In the logs you provided I don't see > it though. What version of the Ricoh chip do you have? > > Greets, > > Pieter > > > The 8522, IIRC - integrated with SD/MMC reader. Under Linux (both Ubuntu > and 64Studio) it crashes out with an Iso Xmit Error 0, as described here > http://freebob.sourceforge.net/index.php/FAQ, which seems to be > unrecoverable. In Windows it's working fine - which goes against reports > I'd seen of the problem being cross-platform... It would be good if you could run the ffado-diag tool such that we can figure out what hardware revision of the ricoh chip you have. Greets, Pieter _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Chris Wenn-2
::
Rate this Message:
On Wed, 2008-07-16 at 10:23 +0200, Pieter Palmers wrote:
> > It would be good if you could run the ffado-diag tool such that we can > figure out what hardware revision of the ricoh chip you have. > > Greets, > > Pieter Hi Pieter Thanks for this... output attached. Chris _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Pieter Palmers
::
Rate this Message:
Chris Wenn wrote:
> On Wed, 2008-07-16 at 10:23 +0200, Pieter Palmers wrote: > >> It would be good if you could run the ffado-diag tool such that we can >> figure out what hardware revision of the ricoh chip you have. >> >> Greets, >> >> Pieter > > Hi Pieter > > Thanks for this... output attached. Thanks for the log. I don't really have time to work on the ricoh issues, but at least the info is stored now. Greets, Pieter _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
|
|
Re: Focusrite Saffire LE (2)
by Chris Wenn-2
::
Rate this Message:
On Sat, 2008-07-26 at 11:37 +0200, Pieter Palmers wrote:
> Chris Wenn wrote: > Thanks for the log. > > I don't really have time to work on the ricoh issues, but at least the > info is stored now. > > Greets, > > Pieter No problem, Pieter. I think it's really a problem with the hardware that won't be fixed until I replace this laptop (sometime next year) Thanks for all your help Chris _______________________________________________ Linux-audio-user mailing list Linux-audio-user@... http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user |
ffado-diag.tar.gz (3K) 
| Free Forum Powered by Nabble | Forum Help |