Re: installing alsa from sources

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le Fri, 09 Feb 2007 15:46:21 +0100,Dragan Noveski <perodog@xxxxxxx> a écrit :
> hi to the list!> > i am running an originally demudi box, which with the  time became a > custom-debian testing one.> in last summer i removed everything from my machine what was depending > an a dabian-jackd package and reinstalled from sources (lot of audio > stuff, kde etc...). this action tooks me about a month, 
Wouhaou! A month! Why do you don't try gentoo? It is a very good pro-audiooverlay with a lot of never versions. Some programs have both released versionsand cvs or svn versions.
http://proaudio.tuxfamily.org/wiki/index.php?title=Main_Page
> but it turned > good, cause all my audio software is not anymora dependent by the debian > packages!> what i wanna do now, is to remove all the debian-packaged alsa stuff, > and reinstall from scratch, but this don´t look easy for me at all, that > is why i wanna ask some questions here.> those are more questions, so here it go:> > 1: i have: alsa-base>                 alsa-oss>                 alsa-tools>                 alsa-tools-gui>                 linux-sound-base, all v1.0.11.1>                >                 libasoun2>                 libasound2-dev, both v1.0.11-3> >                 alsa-utils, v11.0.1-2> >                 alsa-firmware-loaders, v 1.0.9rc3-0.demudi1 (for my > rme-multiface)>                >                 alsmixergui, v 0.9.0rc2-1-9> >                 libclalsadrv (and .dev), v1.0.1-3> > so first i would remove all that stuff!> > 2: i would configure alsadrivers like:> >                 ./configure --with-isapnp=no --with-sequencer=yes > --with-oss=yes --with-pcm-oss-plugins=yes --with-cards=??  > --with-card-options=all> > i have 3 cards using here  -the onboard intel-chip:>                                            0 [I82801DBICH4   ]: ICH4 - > Intel 82801DB-ICH4>                       Intel 82801DB-ICH4 with AD1981B at 0xd0100c00, irq 11>  1 [Modem          ]: ICH-MODEM - Intel 82801DB-ICH4 Modem>                       Intel 82801DB-ICH4 Modem at 0x2400, irq 11> >                                             -the terratec aureon-mkII/ > usb device>                                                   > >                                             - and the rme-multiface(1).> > they all work good here, and if the rme is plugged  in , sometimes  i > have to run alsaconf, but this do not disturbs me at all.> > so the question is, what option should i add to the --with-cards= > argument, or should i just choose "all"?>
http://www.gentoo.org/doc/en/alsa-guide.xml can maybe help you. For the card,it is enough if you chose only the drivers for yours cards. > > i would like to choose only this 3 cards, but what is about options like > "dummy", "virmidi"??
dummy is normally not needed. virmidi can be useful if you want to work withMIDI but is normally not needed.
> all the 3 cards runs well now, should i expect some breakage with the > firmware-loaders 1.0.13?> is somebody here running a multiface on the newest alsa libs /  firmware??> > what should i do with the option `--with-pcmcia-root`??> > 3: my system is now configured so that alsa is started on boot, will > this change after an reinstall?> No> 4: what happens to the other appis (let´s say mplayer, but there are > about 70 self compiled jack-capable appis here!), which are compiled > with the alsapackages i have now? do i have to recompile everything what > is linked to libalsa, or will simply running `ldconfig` make a trick?> It is hard to respond. All is possible. It can work just fine, break things, orcause very subtle bugs. On gentoo where all is compiled from the sources, it isrevdep-rebuild that take care of such problems.
> 5: will jackd recognize the new alsa stuff (since it will be installed > in the same location, as the old stuff is installed in, which is default > as i understood!).> > > 6: i think that once the drivers are well compiled, compiling the libs > is not that difficult. is that true, can i use simply the default stuff > with only `./configure`?> > 7: i am using self-made kernels here, with the i.molnar patches and that > runs very good now!> i don´t think that i have to recompile the kernel, but it could be > possible that i must compile alsa with at least the drivers which are > compiled in the kernel?> You cannot have both the in-kernel alsa drivers and the drivers fromalsa-driver at the same time. You must chose one, install and use it.
> so, that are enough (i know, a lot!) of questions now, i hope that i get > some good answers, so i can make more questions!!> i read alreade the README´s and the stuff on the alsa-site, but i am > still not sure haw to do this reinstallation - but i am sure that i > would like to have an alsa-system which is not depending on the dpkg!> if you need more information on my system in order to being able to help > me, please let me know that!> > cheers,> doc> 
But to be clear, as many debian packages include specific debian patches orimprovements , I thing at it will be simpler to do one of the following:1) As testing and unstable are compatible, add a debian unstable depository insources.list 2) If the programs in unstable are not enough up to date, just use gentoo. 
One of the main gentoo advantages is at you can mix the branches as you want.You can have a stable base system and work system, and in the work system, youcan install the last committed releases by editing just one file and adding akeyword for that packages. It is possible because, as it is compiled fromthe sources by portage, it will depend only of the installed programs/library.
And if the installed libraries don't meet the requirements of the program youwant to install, portage will tell you what to do.
I used suse under many years. I used Demudi and I use now 64 Studio, butnothing can be compared with the way that portage use to deal withdependencies. The first install was hard. I even trashed it completely aftera few months of use. But it have so many advantages as it is my every daydistribution.
At the beginning of the first install, just use a stable system (arch, not~arch) and safe CFLAGS as explained in the handbook and you will get anincredibly fast and stable system. Use ~arch as explained in the handbookonly for specific program where you want the last release.
And don't trust peoples on the forum telling you to use Cflags as"break_my_gentoo" (all the cflags not in the handbook), such cflags needprofiling for each single program and no one have the time to do that for everysingle program in the box. (When needed, such flags are in the ebuild or in thesource code, so don't mess it with break_m_gentoo system flags.)
After the first install, read at least the first chapter of the second part ofthe handbook, the part about using portage.
If you read this to the end, a very comfortable way to install gentoo if youhave at least one free partition is to boot in your existing system and do achrooted install as explained inhttp://www.gentoo.org/doc/en/altinstall.xml#doc_chap6
Good luck,Dominique
-------------------------------------------------------------------------Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier.Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________Alsa-user mailing listAlsa-user@xxxxxxxxxxxxxxxxxxxxxxxxxx://lists.sourceforge.net/lists/listinfo/alsa-user

[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux