Re: ALSA Config

2009-01-04 Thread Nigel Henry
On Sunday 04 January 2009 02:21, Dean Chester wrote: > I noticed that this error came up on boot: > alsactl restore error message alsactl: set_control: 1269 : Failed to obtain > info for control #24(no such file or directory) when it was trying to start > alsa. So its to do with alsa not being able

Re: ALSA Config

2009-01-03 Thread Dean Chester
I noticed that this error came up on boot: alsactl restore error message alsactl: set_control: 1269 : Failed to obtain info for control #24(no such file or directory) when it was trying to start alsa. So its to do with alsa not being able to restore the previous volumes properly. Nigel here is the

Re: ALSA Config

2009-01-03 Thread Nigel Henry
On Saturday 03 January 2009 19:30, Dean Chester wrote: > Update: I unloaded alsa with the command: alsa unload. now i can't get it > to resume as it doesn't load any modules. I think this info might help us > find a solution. Outputs of commands > alsa unload: > debian:~# alsa unload > /usr/sbin/al

Re: ALSA Config

2009-01-03 Thread Dean Chester
Update: I unloaded alsa with the command: alsa unload. now i can't get it to resume as it doesn't load any modules. I think this info might help us find a solution. Outputs of commands alsa unload: debian:~# alsa unload /usr/sbin/alsa: Warning: Processes using sound devices: 31575(wish8.5). Unloadi

Re: ALSA Config

2009-01-02 Thread Dean Chester
Thanks for the suggestion yet i have already tried that and just tried it again and it doesn't work. Dean On Fri, Jan 2, 2009 at 5:43 PM, Nigel Henry wrote: > On Friday 02 January 2009 17:53, dean.g.ches...@googlemail.com wrote: > > Hi, > > Here are the results to what Nigel wanted to know: > > B

Re: ALSA Config

2009-01-02 Thread Dean Chester
Hi There is. d...@debian:/etc/rcS.d$ ls README S20module-init-tools S40pcmciautils S01glibc.sh S25libdevmapper1.02 S43portmap S02hostname.sh S30checkfs.sh S44nfs-common S02mountkernfs.shS30procps S45mountnfs.sh S03udev

Re: ALSA Config

2009-01-02 Thread Nigel Henry
On Friday 02 January 2009 17:53, dean.g.ches...@googlemail.com wrote: > Hi, > Here are the results to what Nigel wanted to know: > Before: > d...@debian:~$ cat /proc/asound/cards > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xfebfc000 irq 21 > > After > d...@d

Re: ALSA Config

2009-01-02 Thread dean . g . chester
Hi, Here are the results to what Nigel wanted to know: Before: d...@debian:~$ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfebfc000 irq 21 d...@debian:~$ lsmod | grep snd snd_hda_intel 434776 0 snd_pcm_oss41760 0 snd_

Re: ALSA Config

2009-01-02 Thread Nigel Henry
On Friday 02 January 2009 16:36, Dean Chester wrote: > Hi, > Everytime i boot in to debian(sid im running on a vostro 1400) i have > to run alsaconfg. Is there anyway i can get rid of having to do this > as it annoying. > Dean Hi Dean. Would you post the output of, cat /proc/asound/cards , for be

Re: ALSA Config

2009-01-02 Thread Douglas A. Tutty
On Fri, Jan 02, 2009 at 03:36:26PM +, Dean Chester wrote: > Everytime i boot in to debian(sid im running on a vostro 1400) i have > to run alsaconfg. Is there anyway i can get rid of having to do this > as it annoying. One of the reasons I've found for needing to run alsaconfig is that the mod