From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000440]: Gateway Solo 250 nma2 - no soundcard detected
Date: Tue, 30 Aug 2005 12:18:30 +0200 [thread overview]
Message-ID: <a8bd8fc7d0465a0cacc7ba86e8f79f04@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=440>
======================================================================
Reported By: thelight
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 440
Category: PCI - nm256
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Fedora Core 2
Kernel Version: 2.6.6-1.435.2.3
======================================================================
Date Submitted: 08-14-2004 19:38 CEST
Last Modified: 08-30-2005 12:18 CEST
======================================================================
Summary: Gateway Solo 250 nma2 - no soundcard detected
Description:
The laptops specs say it has a 'neomagic nma 2' sound card onboard. From
what I can tell this is some sort of NeoMagic nm256 equivalent.
My main problem is that I simply get no sound. The fedora core 2 program
system-config-soundcard doesnt actually detect a soundcard at all. Im
using the 1.0.3 rpms of alsa which came with fedora.
======================================================================
----------------------------------------------------------------------
tiwai - 08-20-04 15:09
----------------------------------------------------------------------
Then try alsaconf and probe legacy cards.
It may detect and set up your device.
----------------------------------------------------------------------
jdthood - 08-30-05 12:18
----------------------------------------------------------------------
Hi. What's the status of this bug. Any improvement in later ALSA
releases?
Issue History
Date Modified Username Field Change
======================================================================
08-14-04 19:38 thelight New Issue
08-14-04 19:38 thelight Distribution => Fedora Core 2
08-14-04 19:38 thelight Kernel Version => 2.6.6-1.435.2.3
08-18-04 11:59 tiwai Note Added: 0001577
08-18-04 15:37 thelight Note Added: 0001582
08-18-04 15:45 tiwai Note Added: 0001584
08-20-04 15:03 thelight Note Added: 0001599
08-20-04 15:09 tiwai Note Added: 0001600
08-30-05 12:18 jdthood Note Added: 0005969
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-30 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 10:18 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 6:57 [ALSA - driver 0000440]: Gateway Solo 250 nma2 - no soundcard detected bugtrack
2004-08-20 13:09 bugtrack
2004-08-20 13:03 bugtrack
2004-08-18 13:45 bugtrack
2004-08-18 13:37 bugtrack
2004-08-18 9:59 bugtrack
2004-08-14 17:38 bugtrack
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=a8bd8fc7d0465a0cacc7ba86e8f79f04@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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.