From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: emu10k1 compilation problms.
Date: Mon, 4 Jun 2007 22:36:24 -0600 [thread overview]
Message-ID: <005501c7a72b$1359c0f0$6401a8c0@GRANDMA> (raw)
In-Reply-To: <20070605043342.GC842@ourhouse.brannan.name>
It installed snd_emu10k1. but somehow, /dev/dsp got deleted.
I'm working on retrieving that.
Thanks,
Thanks,
~~TheCreator~~
[My programs don't have bugs; just randomly added features]
msn:
compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
vertigo head coder
web: tysdomain.com
----- Original Message -----
From: "Buddy Brannan" <buddy@brannan.name>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, June 04, 2007 10:33 PM
Subject: Re: emu10k1 compilation problms.
> On Mon, Jun 04, 2007 at 10:26:08PM -0600, Littlefield, Tyler wrote:
> > hello,
> > I found it in my modules dir, but I can't modprobe for it.
>
> Why not? Is your modprobe broke?
>
> Or do you actually mean that modprobe for it nets you a negative
> result?
>
> If that's what you actually mean, we can't really help much without
> knowing what that negative result is.
>
> In English:
>
> What happens when you type (as root)
> modprobe snd_emu10k1
> ?
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Zachary Kline
` Littlefield, Tyler
` Kerry Hoath
` Buddy Brannan
` Littlefield, Tyler
` Kerry Hoath
` Littlefield, Tyler
` Doug Smith
` Littlefield, Tyler
` Doug Smith
` Littlefield, Tyler
` Kerry Hoath
` Alex Snow
` Littlefield, Tyler
` Buddy Brannan
` Littlefield, Tyler [this message]
` Kerry Hoath
` Littlefield, Tyler
` Alex Snow
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='005501c7a72b$1359c0f0$6401a8c0@GRANDMA' \
--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).