Ticket #163 (closed bug: worksforme)

Opened 15 years ago

Last modified 15 years ago

input in flex scanner failed

Reported by: muranyia Assigned to:
Priority: blocker Milestone: FFADO 2.0
Component: Version: FFADO SVN (trunk)
Keywords: jack jackd flex Cc:
The device the bug applies to:

Description

$ jackd -R -d firewire no message buffer overruns jackd 0.113.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 .. 22295677771: (ffado.cpp)[ 99] ffado_streaming_init: libffado 2.0.900-1352 built Sep 29 2008 06:06:05 input in flex scanner failed no message buffer overruns

Change History

10/07/08 13:18:28 changed by muranyia

  • keywords set to jack jackd flex.
  • priority changed from major to blocker.
  • device_name set to MOTU 828mkII ?.

10/07/08 15:15:57 changed by nettings

should be fixed as of changeset:1353.

10/07/08 19:05:15 changed by muranyia

jackd 0.113.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 .. 21922227308: (ffado.cpp)[ 99] ffado_streaming_init: libffado 2.0.900-1357 built Oct 8 2008 03:32:37 input in flex scanner failed no message buffer overruns

10/08/08 02:29:36 changed by nettings

sorry, i should have been more explicit. the problem needs manual intervention: go to /usr/local/share/libffado and delete the configuration/ directory. then do "sudo scons install". the cause of this problem was a mistake in the installer script, which would install the file named "configuration" in a new subdirectory named "configuration". the presence of this subdirectory prevents the new fixed installer from doing its job, so purge it manually. please report back and close the bug if the issue is fixed for you.

10/08/08 11:18:31 changed by muranyia

sorry me because i am not an expert on compiling.

somehow now i seem to have two installations of libffado; build 1355 and 1357.

build 1355 looks like working, however i could not get to test the sound.

build 1357 gives the above flex error, also having purged the configuration.

am i messing up versions here?

$ whereis -b jackd

jackd: /usr/bin/jackd /usr/local/bin/jackd

$ whereis -b libffado

libffado: /usr/lib/libffado.so /usr/lib64/libffado.so /usr/local/lib/libffado.so /usr/include/libffado /usr/share/libffado

10/09/08 03:10:35 changed by nettings

  • status changed from new to closed.
  • resolution set to worksforme.
  • device_name deleted.

your problem is most likely related to those two concurrent installations, not to the original bug. let's move this to the mailing list, ok?

10/13/08 17:51:49 changed by muranyia

  • status changed from closed to reopened.
  • resolution deleted.

Ok i got rid of the extra installation, and i get this, so i'm reopening:

$ jackd -R -dfirewire -dhw:0

no message buffer overruns jackd 0.113.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 .. 30054485517: (ffado.cpp)[ 99] ffado_streaming_init: libffado 2.0.900-1358 built Oct 14 2008 02:37:49 input in flex scanner failed no message buffer overruns

FYI:

$ ./motuprobe

libraw1394 version is 1.3.0 Running with RT scheduling, priority=50 ieee1394 device successfully opened

Found 1 port(s) Port 0:

Number of nodes: 2 Port name: ohci1394

port 0 node 0: Bus info block length: 4 port 0 node 0: unit directory length is 3 quadlets Port 0 node 0:

vendor ID: 0x000001f2 model ID: 0x00100800 GUID: 0x000000000000e3e2 sw version: 0x00000003 -> possible MOTU device found: MOTU 828 mkII at port 0 node 0

port 0 node 1: Bus info block length: 4 Port 0 node 1:

vendor ID: 0x0000e081 model ID: 0x00000000 GUID: 0x0000000000240909 sw version: 0x00000000

Using first MOTU fw audio interface found: port 0 node 0

10/13/08 19:16:26 changed by jwoithe

Just to avoid any confusion if people view this ticket later on, this problem is not model specific. The fact that motuprobe reports that a MOTU has been found proves that the ieee1394 is more or less working correctly. However, the flex scanner error is independent of the device in use.

In relation to the problem under discussion, have you double-checked that the second ffado has been removed from the system? It might be a good idea to explicitly remove both ffado versions and restart from scratch. Also double-check that the bogus configuration/ directory is gone.

The other thing which springs to mind is to wonder whether jackd needs to be recompiled once you are certain there is only one ffado version present on the system.

10/13/08 19:17:06 changed by muranyia

  • device_name set to MOTU 828mkII.

10/13/08 19:26:43 changed by muranyia

$ whereis libffado

libffado: /usr/lib/libffado.so /usr/lib64/libffado.so /usr/include/libffado /usr/share/libffado

I hope its alright.

Jack sure needs to be recompiled, and i did recompile it. The configuration is under usr/share, shall I purge it before compiling?

Sorry if this doesn't fit here at the end, the maillist didn't help. Thanks for any help, at least we test one renegade MOTU unit ;)

10/13/08 19:28:41 changed by muranyia

  • device_name deleted.

Understood, not MOTU specific.

10/13/08 19:46:11 changed by jwoithe

You'll have to excuse me here since I don't have any 64-bit machines myself - is it normal on 64-bit machines to have a ffado library in both /usr/lib/ and /usr/lib64/? I would have thought that a particular installation from ffado source would only create a library in one of these locations, not both.

Is /usr/share/libffado/configuration a directory or a file on this system, currently?

(follow-up: ↓ 14 ) 10/14/08 06:43:22 changed by muranyia

I don't either know much about what is normal because my first 64 bit install was a FC6 and it didn't handle libraries so well, this Ubuntu is the second one and it works much better. /usr/lib/libffado.so and /usr/lib64/libffado.so seem to be identical by filesize/date, unfortunately i'm at work so i cannot see checksums or if it is a link.

/usr/share/libffado/configuration is a file, afair.

(in reply to: ↑ 13 ; follow-up: ↓ 16 ) 10/14/08 13:39:24 changed by muranyia

Replying to muranyia:

/usr/share/libffado/configuration is a file, afair.

Nope, the file is /usr/share/libffado/configuration/configuration

And the libs are identical:

$ md5sum /usr/lib/libffado.so

31164b6f88dea60461546db3b0ae2d69 /usr/lib/libffado.so

$ md5sum /usr/lib64/libffado.so

31164b6f88dea60461546db3b0ae2d69 /usr/lib64/libffado.so

10/14/08 14:09:37 changed by muranyia

Some more info:

$ ./test-ffado Discover

verbose level = 0

Using ffado library version: libffado 2.0.900-1358

02128280905: Debug (Configuration.cpp)[ 62] openFile: Could not open file: ~/.ffado/configuration

input in flex scanner failed

no message buffer overruns

$ ./test-ffado ListDevices?

verbose level = 0

Using ffado library version: libffado 2.0.900-1358

1394 PORT 0

Node id GUID VendorId? ModelId? Vendor - Model

0 0x0001f2000000e3e2 0x000001F2 0x00100800 -

1 0x00e0810000240909 0x0000E081 0x00000000 Linux - ohci1394 -

no message buffer overruns

(in reply to: ↑ 14 ; follow-up: ↓ 17 ) 10/14/08 15:42:20 changed by jwoithe

/usr/share/libffado/configuration is a file, afair.

Nope, the file is /usr/share/libffado/configuration/configuration

Ok. According to comment number 4, /usr/share/libffado/configuration should be the actual configuration file, not a directory containing the configuration file. As per that comment, the configuration/ directory was created by a glitch in the install script which is reportedly now fixed. It is the presence of /usr/share/libffado/configuration/ as a directory which is causing the flex error according to earlier comments, and if this exists as a directory the "fixed" install script doesn't work correctly.

So, I would suggest you do

rm -r /usr/share/libffado/configuration

and then reinstall the latest ffado. Retest and see if the flex error is still a problem.

And the libs are identical

Ok. Like I said, I don't know if this is normal or not - someone else with 64-bit machines may have to comment.

(in reply to: ↑ 16 ) 10/14/08 17:17:31 changed by muranyia

  • status changed from reopened to closed.
  • resolution set to worksforme.

It is the presence of /usr/share/libffado/configuration/ as a directory which is causing the flex error according to earlier comments, and if this exists as a directory the "fixed" install script doesn't work correctly.

Sorry it may have been my English that I have just got it. Deleting /usr/share/libffado/configuration/ works and the flex error is over. Sorry for the mess!

Now i have other errors i will look into.

And the libs are identical

Ok. Like I said, I don't know if this is normal or not - someone else with 64-bit machines may have to comment.

No, it's nothing wrong, I just thought you were interested. Sorry again and thanks!