ok ill give the move the sound card a try, and maybe do an apt get update and upgrade with the "gaim url" removed from the sources. list. Ill then re run alsaconf and see if it fixes itself otherwise ill and as for >>>>> you may adress this question to "AGNULA user forum" &lt;users(a)lists.agnula.org&gt;so they can help you demudi and agnula is almost the same thing right now) <<<<< to be honest in an effort to get linux and audio and ardour and jack and and and to work I have come across a barrage of possible forums, distros patchs, kernels, fiddles and such. None of this "ocean of info" helps little me in my dingy (which has a leak) and who cant even see over the next rolling wave. the studio is elsewhere so it will take me a day or more to get back and play thanks tim hall wrote: >Last Wednesday 16 February 2005 23:57, vector was like: > > >>Hi all , sad newbie here :( >> >> > >This too shall pass :-) > > > >>to recap i out a fresh demudi install on our studio machine and got to >>the point where i was confident I could record line in audio etc using >>ardour, and play hydrogen etc etc. >>So the date was set for the band to come in and record. >>I booted the machine and alsa seems broken. errors below,, and i have no >>idea where to start. >> >>Its possible (it was a week ago memory faded with depression) that i >>broke it when i tried to install a second sound card (thinking id get 4 >>inputs, ok I have learnt that doesnt work) but what ever i have done its >>broken. >> >> > >Sounds like a reasonable supposition. > > > >>I removed the 2nd card, >>tried alsaconf >>tried alsactl restore (got some no file found or something) >>still no go :( >> >> > > > > >>now there is a point i had to apt get install gaim with some other >>settings on sources list I wonder if that screwed something up. Im sure >>i had it working after that tho. >> >> > >Did you notice anything else get upgraded at the same time? This shouldn't >have caused any problems. > > > >>PCI: Found IRQ 11 for device 00:0c.0 >>PCI: Sharing IRQ 11 with 00:08.0 >>ALSA ../alsa-kernel/pci/ens1370.c:527: wait source ready timeout 0xec10 >>[0xffffffff] >>lots of the above line, and i mean lots >> >> > >Try moving the soundcard to a different slot - which device is it sharing with >here? > > > >>ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1868: >>AC'97 0 access is not valid [0x0], removing mixer >> >> > >This is interesting, I've no idea what it means. Do you have the right version >of alsa-modules installed? > > > >>depmod: *** Unresolved symbols in >>/lib/modules/2.4.25-1-multimedia-686/kernel/drivers/media/radio/miropcm20.o >>depmod: *** Unresolved symbols in >>/lib/modules/2.4.25-1-multimedia-686/alsa/snd-pdaudiocf.o >>depmod: *** Unresolved symbols in >>/lib/modules/2.4.25-1-multimedia-686/alsa/snd-vx-cs.o >>depmod: *** Unresolved symbols in >>/lib/modules/2.4.25-1-multimedia-686/alsa/snd-vxp440.o >>depmod: *** Unresolved symbols in >>/lib/modules/2.4.25-1-multimedia-686/alsa/snd-vxpocket.o >> >> > >This is normal, you haven't installed the pcmcia modules, presumably because >this isn't a laptop. You can ignore these warnings. > > > >>Loading driver... >>Restoring ALSA mixer settings ... failed: >> You may want to run 'alsactl restore' manually to view any errors. >>Setting default volumes... >> >> > >All this means is that you don't have ALSA configured correctly, you knew that >already. It should be fairly easy to sort out. > >cheers, > >tim hall >http://glastonburymusic.org.uk > > >

Didnt get a chance last night to play but I decided to get some more utp cable and hook the studio box up ot the net so i can fiddle with it remotely. 1 question you said ok you have mentioned that twice now. but Im none the wiser as to what it means. are you saying run alsaconf or is there something else? tim hall wrote: