public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Timothy Miller <theosib@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: HELP:  Cannot get ALSA working on via82xx
Date: Thu, 15 Jul 2004 12:08:47 -0400	[thread overview]
Message-ID: <40F6AC0F.1010309@techsource.com> (raw)
In-Reply-To: <s5hk6x9cseh.wl@alsa2.suse.de>

Thank you for responding!


Takashi Iwai wrote:
> At Wed, 07 Jul 2004 14:26:54 -0400,
> Timothy Miller wrote:
> 
>>I must once again reiterate my begging for help on this topic.  I've 
>>gotten lots of help on the gentoo forum, but none of it's fixed my 
>>problems, and I've only gotten one response on LKML.
>>
>>*BEG* *BEG* *BEG*
>>
>>Please, won't someone take pity on me?  :)  Thanks!
> 
> 
> via82xx doesn't support MPU401 by itslef although via686 does.

I'm not sure if I have via686 or not.  Various tools like lspci don't 
seem to reveal much.

That's one of the problems I keep running into with Linux.  There aren't 
good tools for finding out what you have, and even when you do find out 
what you have, it's hard to figure out which modules you need, because 
the module names don't correspond well with the chipset name. 
Furthermore, there doesn't seem to be a good way to relate module names 
with menuconfig entries.  When someone says to use xyz module, I can't 
figure out which menuconfig option to select, so I have to compile ALL 
of them as modules, and when someone tells me to use a given menu 
option, I can't figure out which module corresponds to it.

> You can try snd-mpu401 module instead.  

Well, I have a module snd-mpu401, but when I modprobe it, I get an error 
about a non-existant device.

 > When ACPI is enabled, the
> configuration will be done automatically.
> The midi device can be available as the second card.

Ah, well, I had nightmares trying to use ACPI.  I use just APM for 
things like power-off (power-off works with APM, but not with ACPI). 
Maybe some of the experts can help me to figure out how to get it all to 
work.

I'm about ready to give up on ALSA and go back to OSS.  Maybe someone 
can help me to figure out how to get MIDI sequencing to work with OSS 
instead.  OSS would at least do audio right without noise and popping 
sounds, etc.

I apologize for the impatient nature of this post... I've been 
struggling for weeks to get audio working right with ALSA, but every 
piece of advise I get seems only to make things worse.

 From what I read on various web sites, ALSA for via82xx is so buggy 
that it's really not worth using yet.


  reply	other threads:[~2004-07-15 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05  4:06 HELP: Cannot get ALSA working on via82xx Timothy Miller
2004-07-05 19:53 ` Marcel Sebek
2004-07-07 18:26 ` Timothy Miller
2004-07-12 12:38   ` Takashi Iwai
2004-07-15 16:08     ` Timothy Miller [this message]
2004-07-15 16:09       ` Takashi Iwai
2004-07-15 18:29       ` Gene Heskett
  -- strict thread matches above, loose matches on Subject: below --
2004-07-16 14:35 Timothy Miller
2004-07-16 14:41 ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40F6AC0F.1010309@techsource.com \
    --to=miller@techsource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=theosib@hotmail.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox