From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: soundcard not working after debian install
Date: Sun, 21 Sep 2008 17:13:49 -0600 [thread overview]
Message-ID: <001101c91c3f$b693d9b0$4200a8c0@tdsportable> (raw)
In-Reply-To: <E5B9DC8EEBC841F8A848480FCF227F44@randy3>
hello:
You can get a list of modules from the alsa site.
It took a couple different modprobes before I found mine, but that's where I
got the module name from.
HTH,
Thanks,
_|_|_|_|_| _| _|_|_|_|
_| _|_|_| _| _|_|_|
_| _| _| _|_|_| _|
_| _| _| _| _|
_| _| _| _|_|_|_| _|_|_|
Visit TDS for quality software and website production
http://tysdomain.com
msn: tyler@tysdomain.com
aim: st8amnd2005
skype: st8amnd127
----- Original Message -----
From: "Kitty Litter" <n8kl@insightbb.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, September 21, 2008 5:11 PM
Subject: soundcard not working after debian install
>I installed the Sept. 15 daily build and compiled a new kernel 2.6.26.5.
>However my NVidia HD onboard soundcard is not working in both kernels. I
>think the reason for this is because of the snd-hd-intel module. Does
>anyone know which parameters might work for this onboard NVidia card?
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3458 (20080921) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Kitty Litter
` Tyler Littlefield [this message]
` Kristoffer Gustafsson
` Tyler Littlefield
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='001101c91c3f$b693d9b0$4200a8c0@tdsportable' \
--to=tyler@tysdomain.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).