public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: sound and linux?
Date: Mon, 29 May 2006 08:41:48 -0600	[thread overview]
Message-ID: <003b01c6832e$0698f6a0$6401a8c0@grandmasfury> (raw)
In-Reply-To: <20060529101846.GB2801@genaj.plus.com>

Hello,
That one was sorta my fault, I new it was snd-emu10k1, but I forgot the snd- 
prefix. appologies there...
----- Original Message ----- 
From: "Georgina Joyce" <gena@genaj.plus.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, May 29, 2006 4:18 AM
Subject: Re: sound and linux?


> Hi
>
> So you jumped in without a clue to what your talking about?  You are right 
> in that over history, there has been changes.  However, you'll note that 
> I'm using the newest drivers and the snd prefix is there.
>
> You have a problem with someone encouraging someone to read about their 
> particular system?
>
> Your intervention is not helping the lister at all, your just looking for 
> a fight, why?
>
> The question didn't include a number of essential facts, like what 
> distribution, and whether a stock kernel is being used or a custom built 
> one.  Because the complaint was that modprobe emu10k1 did not work, then 
> snd-emu10k1 might.  So why are you insisting that it is without the snd 
> prefix when the original question stated that it doesn't work?
>
> Gena
> On Sun, May 28, 2006 at 10:24:18PM -0400, ace wrote:
>> I would quote it but I am not on Linux right now to do so.  Read the
>> INSTALL file in the source package for the Alsa driver and it says
>> that the snd_ prefix was removed.  So I am not sure the reason for this 
>> case.
>>
>>
>> At 07:14 PM 5/28/2006, you wrote:
>> >On Sun, May 28, 2006 at 03:41:07PM -0400, ace wrote:
>> > > Actually, the snd- part was removed; thus making it emu10k1.  So,
>> > > should you be talking about reading docs?
>> >Well here's my list and I'm running from this source
>> >alsa-driver-1.0.11.tar.bz2 but there's no snd there is there.
>> >
>> >snd_mpu401_uart         6440  -
>> >snd_emu10k1           124164  -
>> >snd_rawmidi            20512  -
>> >snd_ac97_codec         93384  -
>> >snd_ac97_bus            1800  -
>> >snd_pcm_oss            39040  -
>> >snd_mixer_oss          16456  -
>> >snd_pcm                80848  -
>> >snd_seq_device          7092  -
>> >snd_timer              21164  -
>> >snd_page_alloc          8528  -
>> >snd_util_mem            3272  -
>> >snd_hwdep               7276  -
>> >snd                    49984  -
>> >ndiswrapper           168400  -
>> >pl2303                 19148  -
>> >u
>> > >
>> > >
>> > > At 03:04 PM 5/28/2006, you wrote:
>> > > >On Sat, May 27, 2006 at 09:24:32PM -0600, Tyler Littlefield wrote:
>> > > > > Hay,
>> > > > > I was told to do a modprobe a while back for emu-10k1, and that
>> > > > hasn't helped, I still don't have any sound,
>> > > > > Are there any other ideas?
>> > > >
>> > > >Don't you read any docs yourself.  Do you think we're got nothing
>> > > >better to do than sit here waiting for you to fire your next 
>> > > >question?
>> > > >
>> > > >I don't know who gave you the above command but the module for the
>> > > >sound blaster live is snd-emu10k1 thus your command would be:
>> > > >
>> > > >modprobe snd-emu10k1
>> > > >
>> > > >That's as much spoon feeding your going to get, there's more modules
>> > > >to be loaded.
>> > > >
>> > > >Gena
>> > > > > Thanks,
>> > > > > ___________
>> > > >____________________________________
>> > > > > Speakup mailing list
>> > > > > Speakup@braille.uwo.ca
>> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> > > >---end quoted text---
>> > > >
>> > > >--
>> > > >2E0AXU
>> > > >
>> > > >Freedom & Power provided by debian GNU Linux
>> > > >
>> > > >_______________________________________________
>> > > >Speakup mailing list
>> > > >Speakup@braille.uwo.ca
>> > > >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> > >
>> > >
>> > > _______________________________________________
>> > > Speakup mailing list
>> > > Speakup@braille.uwo.ca
>> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >---end quoted text---
>> >
>> >--
>> >2E0AXU
>> >
>> >Freedom & Power provided by debian GNU Linux
>> >
>> >_______________________________________________
>> >Speakup mailing list
>> >Speakup@braille.uwo.ca
>> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> ---end quoted text---
>
> -- 
> 2E0AXU
>
> Freedom & Power provided by debian GNU Linux
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 




  reply	other threads:[~ UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Georgina Joyce
   ` ace
     ` Tyler Littlefield
       ` ace
       ` Georgina Joyce
     ` Georgina Joyce
       ` ace
         ` Georgina Joyce
           ` Tyler Littlefield [this message]
           ` ace
             ` Thomas Stivers
 ` randy turner
   ` Tyler Littlefield
     ` randy turner
       ` Tyler Littlefield
         ` randy turner
     ` Georgina Joyce
 Charles Hallenbeck
 ` ace
 Georgina Joyce
 ` Tyler Littlefield
   ` Georgina Joyce

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='003b01c6832e$0698f6a0$6401a8c0@grandmasfury' \
    --to=compgeek13@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).