From: Philippe C. <la-...@or...> - 2012-12-21 17:27:13
|
Le vendredi 21 décembre 2012 à 15:44 +0100, Johannes Treß a écrit : > Hi there, > ok I think I did a few steps further... > Jack is running again now. I managed to install ffado following phils > description but now I still can't get the ffado mixer to run. The > Console tells me: > > Library version mismatch. (required: libffado 2.1.9999-2260, present: > libffado 2.999.0-) So ffado-mixer search for the right library but did not found for it. Next part of the message tells you what is going wrong: > Please run this application against the exact corresponding library > it was compiled for. The most common cause for this is having more > than one version of libffado installed. > > I discovered, that the 2.999.0 library is located in /usr/lib but I > couldn't found the newer one with -2260 ending. > have a You must not still have libffado.so.2.999.0. So discard it (or renamed it as suggested by Tim, if you are afraid) and scons install again. You would have to see libffado 2.1.9999 installed in /usr/lib and two links: libffado.so ->libffado.so. 2, and libffado.so.2->libffado.so.2.1.9999 (svn version won't appear explicitely in these name). Saying that, I imagine you do not have a x86_64 arch, do you ? > Any Suggestions? > > > Yours > > Johannes > > > Am 20.12.2012 23:07, schrieb Philippe Carriere: > > > > > Le jeudi 20 décembre 2012 à 20:51 +0100, Johannes Treß a écrit : > > > > > Hey, > > > > > > > Hi Johannes, > > > > > > > I have Ubuntu Studio 12.04 running and tried now to update via KXstudio > > > Repositories which brought me ffado 2.1.0 but a not working ffado mixer. > > > So I try to downgrade everything right now. > > > > Not the right way; downgrade/uninstall nothing. > > > > > > > Someone from the mailing list told me that I should update to SVN 2250 > > > > Yes; with SVN 2250, support is almost complete. > > > > > > > but that it isn't possible at the moment because of the ffado dev Server... > > > > > > > That's not entirely true. I mean: > > > > $ svn checkout http://subversion.ffado.org/ffado/trunk ffado-svn > > > > works. > > > > Then you can checkout the very last trunk version (SVN 2260) via the > > command above. > > Then > > $ cd ffado-svn/libffado > > > > At that point you have to compile ffado using scons (so you need the > > scons package !). Care that you need a lot of development packages > > (named -dev in Ubuntu if I remember well - I use Fedora) to do so: > > so follow the messages when you will run scons: if scons fails, it > > is almost sure that a devel package is missing: usually it is not so > > hard to detect which devel packages (it might require a lot of > > successive trials ...) are involved (libxml, libraw1394, dbus-c++, > > etc ...). Don't forgot to erase the .sconsign.dblite file each time > > missing packages have been detected. > > > > The second thing to care is that your new ffado install have to > > overwrite your previous install (through an Ubuntu package, I > > imagine). Either you will experience wrong behaviours. > > Have a look to where are exactly installed the various binaries, > > libs and python scripts. Typically: > > > > $ ls -l /usr/bin | grep ffado > > -rwxr-xr-x. 1 root root 49336 13 juin 2012 > > ffado-bridgeco-downloader > > -rwxr-xr-x. 1 root root 236544 13 juin 2012 > > ffado-dbus-server > > -rwxr-xr-x. 1 root root 6871 13 juin 2012 ffado-diag > > -rwxr-xr-x. 1 root root 24392 13 juin 2012 > > ffado-dice-firmware > > -rwxr-xr-x. 1 root root 60968 13 juin 2012 > > ffado-fireworks-downloader > > -rwxr-xr-x. 1 root root 1118 13 juin 2012 ffado-mixer > > -rwxr-xr-x. 1 root root 53192 13 juin 2012 ffado-test > > > > means ffado binaries are in /usr/bin, > > > > $ ls -l /usr/lib64 | grep ffado > > lrwxrwxrwx. 1 root root 19 10 déc. 17:24 libffado.so.2 -> > > libffado.so.2.999.0 > > -rwxr-xr-x. 1 root root 2072496 13 juin 2012 libffado.so.2.999.0 > > > > that libffado is in /usr/lib64 (for a x86_64 arch; for i386, it > > would probably be in /usr/lib), > > > > $ ls -l /usr/lib/python2.7/site-packages/ffado/ > > total 236 > > -rw-r--r--. 1 root root 899 13 juin 2012 config.py > > -rw-r--r--. 2 root root 1380 13 juin 2012 config.pyc > > -rw-r--r--. 2 root root 1380 13 juin 2012 config.pyo > > -rw-r--r--. 1 root root 5384 7 déc. 2010 configuration.py > > -rw-r--r--. 2 root root 5504 13 juin 2012 configuration.pyc > > -rw-r--r--. 2 root root 5504 13 juin 2012 configuration.pyo > > -rw-r--r--. 1 root root 14514 7 déc. 2010 dbus_util.py > > -rw-r--r--. 2 root root 17640 13 juin 2012 dbus_util.pyc > > -rw-r--r--. 2 root root 17640 13 juin 2012 dbus_util.pyo > > -rwxr-xr-x. 1 root root 7351 17 févr. 2010 ffadowindow.py > > -rw-r--r--. 2 root root 7446 13 juin 2012 ffadowindow.pyc > > -rw-r--r--. 2 root root 7446 13 juin 2012 ffadowindow.pyo > > -rw-r--r--. 1 root root 0 30 août 2009 __init__.py > > -rw-r--r--. 2 root root 137 13 juin 2012 __init__.pyc > > -rw-r--r--. 2 root root 137 13 juin 2012 __init__.pyo > > -rw-r--r--. 1 root root 2312 7 déc. 2010 logginghandler.py > > -rw-r--r--. 2 root root 2529 13 juin 2012 logginghandler.pyc > > -rw-r--r--. 2 root root 2529 13 juin 2012 logginghandler.pyo > > drwxr-xr-x. 2 root root 4096 18 déc. 22:22 mixer > > -rw-r--r--. 1 root root 13837 7 déc. 2010 panelmanager.py > > -rw-r--r--. 2 root root 11008 13 juin 2012 panelmanager.pyc > > -rw-r--r--. 2 root root 11008 13 juin 2012 panelmanager.pyo > > -rw-r--r--. 1 root root 1143 30 août 2009 panelmanagerstatus.ui > > -rw-r--r--. 1 root root 4121 19 déc. 2009 regdialog.py > > -rw-r--r--. 2 root root 3883 13 juin 2012 regdialog.pyc > > -rw-r--r--. 2 root root 3883 13 juin 2012 regdialog.pyo > > -rw-r--r--. 1 root root 7129 30 août 2009 regdialog.ui > > -rw-r--r--. 1 root root 7364 7 déc. 2010 registration.py > > -rw-r--r--. 2 root root 6132 13 juin 2012 registration.pyc > > -rw-r--r--. 2 root root 6132 13 juin 2012 registration.pyo > > drwxr-xr-x. 2 root root 4096 18 déc. 22:22 widgets > > > > that python scripts are in /usr/lib (even on a x86_64 arch). > > Now they might be in /usr/local (so use /usr/local/... in the above > > commands); if you really don't find anything, meaning ffado is > > installed in a very unusual location, try (under root): > > # cd / > > # find * -name *ffado* > > you will be able to see where ffado reside. > > > > Now, you will be able to compile ffado as > > $ scons PREFIX=/usr > > > > in the first case, > > $ scons PREFIX=/usr/local > > > > in the second one. > > If ffado is located in a less usual way, do > > $ scons --help > > to see that you would have to indicate the right BINDIR, LIBDIR, > > INCLUDEDIR and PYPKGDIR locations in the command. > > Also you would see that possibly you might be interested in adding > > DEBUG=no so as to do a lot of optimizations. If you plan to only use > > the Pro 24, you also might want to disable other drivers (but you > > would have to install again once you would be interested in trying > > another kind of device). > > When compilation success, then install by > > $ sudo scons install > > > > if you have sudo or else by > > $ su -c 'scons install' > > > > Now check that everything is OK by reiterating the "ls ..." commands > > above and looking at the creation date of each "ffado" file; if > > anything from the old install is still remaining somewhere, discard > > it manually (possibly, install again if some files are thus > > missing). > > > > > > > have you got other advices for me? > > > > > > > Hope it will be of help ! > > > > Regards, > > > > Phil > > -- > > Philippe Carriere <la-...@or...> > > -- Philippe Carriere <la-...@or...> |