From: Dave Phillips <dlphilp@linux-sound.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: problem with ALSA 1.09 and 2.6 kernel (AGNULA/Demudi)
Date: Wed, 27 Jul 2005 11:44:00 -0400 [thread overview]
Message-ID: <42E7ABC0.4010909@linux-sound.org> (raw)
In-Reply-To: <s5hd5p4v3hw.wl%tiwai@suse.de>
Hi Takashi:
Some updates: I now have the CS4232, the PDAudioCF (Thank you!), and
the Midisport 2x2 working with Demudi 1.2.1 and ALSA 1.0.9rc2. My final
hurdle shouldn't be too difficult to get over:
demudi:/home/dlphilp# modprobe snd-virmidi
FATAL: Error inserting snd_virmidi
(/lib/modules/2.6.12-3-multimedia-686/kernel/sound/drivers/snd-virmidi.ko):
No such device
The snd-seq-virmidi module is loaded. What am I missing ?
Best,
dp
Takashi Iwai wrote:
>At Wed, 27 Jul 2005 08:34:13 -0400,
>Dave Phillips wrote:
>
>
>>/proc/asound/cards' reports no soundcards in the system. Ditto if I load
>>the snd-pcaudiocf module. Still no soundcard. I'll try loading the
>>Midisport after I get basic services working. :)
>>
>>
>
>pdaudiocf is a pccard driver. It's usually loaded via cardmgr.
>Adding a config file pdaudiocf.conf (found in alsa-drivers) to
>/etc/pcmcia should work. 2.6.13 kernel will require even no longer
>such a config file.
>
>
>Takashi
>
>
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-27 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 12:34 problem with ALSA 1.09 and 2.6 kernel (AGNULA/Demudi) Dave Phillips
2005-07-27 12:26 ` Takashi Iwai
2005-07-27 15:44 ` Dave Phillips [this message]
2005-07-28 7:59 ` Clemens Ladisch
2005-07-28 14:05 ` Dave Phillips
2005-07-28 13:30 ` 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=42E7ABC0.4010909@linux-sound.org \
--to=dlphilp@linux-sound.org \
--cc=alsa-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.