Re: ALSA devices: NOT ENABLED IN CONFIG

2009-03-03 Thread Arthur Marsh
Mark Neidorff wrote, on 2009-02-18 01:21: Is there a solution to configuring sound? If not, where is the proper place to ask for one? There is an alsa-user mailing list http://www.alsa-project.org/main/index.php/Mailing-lists I've found part of the fun being that there isn't a clear mappin

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-17 Thread Mark Neidorff
On Sunday 15 February 2009 11:25 am, T o n g wrote: > > Hi, > > My recent upgrade caused my sound card not working any more. Checking back > at my packages version log, the only related upgrade is that > alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4. > The rest are still the same:

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-16 Thread T o n g
On Mon, 16 Feb 2009 10:42:51 +0100, Florian Kulzer wrote: > Maybe the grml kernel is for some reason not compatible with Debian's > ALSA setup. . . Thanks a lot for the analysis Florian. Basing it, I diverted the discussion to grml . Thanks again. -- Tong (remove underscore(s) to reply) htt

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-16 Thread Florian Kulzer
On Mon, Feb 16, 2009 at 05:00:50 +, T o n g wrote: [...] > Done as you suggested. Here are the results: > > # modprobe -r snd_via82xx gameport snd_ac97_codec ac97_bus snd_pcm > snd_page_alloc snd_mpu401_uart snd_seq_midi snd_seq_midi_event snd_rawmidi > snd_seq snd_timer snd_seq_device s

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-15 Thread T o n g
On Sun, 15 Feb 2009 20:33:05 +0100, Florian Kulzer wrote: > [ snip: You checked all the usual suspects already; I did not notice > anything that gave me a clue what is going on. ] Thank you Florian for your reply. >> But I can't go any further via googling. E.g., among many other >> tryings, f

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-15 Thread Florian Kulzer
On Sun, Feb 15, 2009 at 16:25:19 +, T o n g wrote: > [warning, long post] > > Hi, > > My recent upgrade caused my sound card not working any more. Checking back > at my packages version log, the only related upgrade is that > alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4. >

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-15 Thread T o n g
On Sun, 15 Feb 2009 16:25:19 +, T o n g wrote: > My "amixer: Mixer attach default error" problem was solved by > > % aptitude install libesd-alsa0 > > (Ref: > http://www.linuxquestions.org/questions/debian-26/no-sound-debian-lenny-amd64-gigabyte-ga- > ma78gm-s2h-amd-780g-677646/) Hmm, not

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-15 Thread T o n g
On Sun, 15 Feb 2009 12:17:00 -0500, Michael Pobega wrote: > Have you tried running alsaconf as root? Usually when there are upgrades > to alsa you have to do it, things tend to change pretty often in the > ALSA setup. Yes. 1st thing that I did. thanks all the same. -- Tong (remove underscore(s

Re: ALSA devices: NOT ENABLED IN CONFIG

2009-02-15 Thread Michael Pobega
On Sun, Feb 15, 2009 at 04:25:19PM +, T o n g wrote: > [warning, long post] > > Hi, > > My recent upgrade caused my sound card not working any more. Checking back > at my packages version log, the only related upgrade is that > alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4.

ALSA devices: NOT ENABLED IN CONFIG

2009-02-15 Thread T o n g
[warning, long post] Hi, My recent upgrade caused my sound card not working any more. Checking back at my packages version log, the only related upgrade is that alsa-base_1.0.17.dfsg-2 is upgraded to alsa-base_1.0.17.dfsg-4. The rest are still the same: alsa-oss_1.0.15-1 alsa-utils_1.0.16-