On 10/31/07, Manoj Srivastava <[EMAIL PROTECTED]> wrote: > > On Wed, 31 Oct 2007 14:54:03 +0000, Joe Bloggs > <[EMAIL PROTECTED]> said: > > > Tried replacing gnome .config files with backups but didn't work. Also > > tried alsaconfig (and have tried previously); it always goes through > > the procedures as though there are no problems, but then no > > sound. Also tried making a new user account, but sound didn't work in > > that either. > > OK, so that is pretty conclusive that the problem lies elsewhere > in the system than your config files. Looking to modules, You said: > --8<---------------cut here---------------start------------->8--- > snd_hda_intel 17332 0 > snd_hda_codec 137856 1 snd_hda_intel > snd_pcm_oss 38368 0 > snd_mixer_oss 15200 1 snd_pcm_oss > snd_pcm 68676 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss > snd_timer 20996 1 snd_pcm > snd 47012 6 snd_hda_intel,snd_hda_codec,snd_pcm_oss, > snd_mixer_oss,snd_pcm,snd_timer > soundcore 9248 1 snd > snd_page_alloc 9640 2 snd_hda_intel,snd_pcm > --8<---------------cut here---------------end--------------->8--- > > I have: > --8<---------------cut here---------------start------------->8--- > __> lsmod | grep snd > snd_rtctimer 6304 0 > snd_hda_intel 309920 4 > snd_pcm_oss 46240 0 > snd_mixer_oss 19264 1 snd_pcm_oss > snd_pcm 87880 3 snd_hda_intel,snd_pcm_oss > snd_seq_dummy 6340 0 > snd_seq_oss 34624 0 > snd_seq_midi 11392 0 > snd_rawmidi 28576 1 snd_seq_midi > snd_seq_midi_event 10304 2 snd_seq_oss,snd_seq_midi > snd_seq 56704 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi, > snd_seq_midi_event > snd_timer 26376 4 snd_rtctimer,snd_pcm,snd_seq > snd_seq_device 10772 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi, > snd_rawmidi,snd_seq > snd 63784 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss, > snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq, > snd_timer,sn_seq_device > soundcore 11040 1 snd > snd_page_alloc 12560 2 snd_hda_intel,snd_pcm > --8<---------------cut here---------------end--------------->8--- > > I am not sure if the difference is significant, but my sound is > working -- and we seem to have intel sound chips. > > manoj > -- > Wake up and don't be careless, but lead a life of well-doing. He who > follows righteousness lives happily in this world and the next. 168 > Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/> > 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C > > > _______________________________________________ > ilugd mailinglist -- ilugd@lists.linux-delhi.org > http://frodo.hserus.net/mailman/listinfo/ilugd > Next Event: http://freed.in - September 28-29, 2007 > Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi > http://www.mail-archive.com/ilugd@lists.linux-delhi.org/ > > Even i think problem lies somewhere else! Here is a possible solution at me... Check for the file ~/.asoundrc or /etc/asoundrc This file (local and global resp) is the plugin file for ALSA, where the default output device the default mixer etc are specified. If this is the culprit then such errors are seen. If this is there then checkout what is the default outpit plugin... (easy to do it, just by reading the file). If it is something else then hw:0 or PCM then make it so (google for that) If not then, why not try installing the latest version of alsa, it will automatically fix any errors. This way you will get added features as well.
Hope it will help..... -- Shamail Tayyab shamail [at] inbox.com 4 2 3 2 4 9 9 9 9 9 - 1 9 + (right to left without spaces) <<Bringing Linux and Mobiles one step closer>> Blog at: http://tuxatwork.blogspot.com $1$29M2A$zTS8baerM42dHVaGwxQdW. _______________________________________________ ilugd mailinglist -- ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd Next Event: http://freed.in - September 28-29, 2007 Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi http://www.mail-archive.com/ilugd@lists.linux-delhi.org/
