From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001078]: intel8x0 does not work on any (?) 2.6 kernel
Date: Fri, 6 May 2005 09:00:40 +0200 [thread overview]
Message-ID: <698018c74cefb8fadad84830549c7a4c@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1078>
======================================================================
Reported By: columbo
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1078
Category: PCI - intel8x0
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Slackware Linux 10.1
Kernel Version: 2.6.11.7
======================================================================
Date Submitted: 04-26-2005 21:29 CEST
Last Modified: 05-06-2005 09:00 CEST
======================================================================
Summary: intel8x0 does not work on any (?) 2.6 kernel
Description:
After compilation of ALSA drivers, libs, utilities, and after alsaconf ALSA
modules loads correctly, they are visible in lsmod and so on, but all
programs can't see sound card, /dev/dsp and so on. With kernels 2.4.x
everything is OK.
======================================================================
----------------------------------------------------------------------
pzad - 05-06-05 08:59
----------------------------------------------------------------------
Do not use snd-intel8x0m. This is source of your problems. If you load
snd-intel8x0m then it will stop your soundcard. Your modem will not work
with it anyway.
----------------------------------------------------------------------
pzad - 05-06-05 09:00
----------------------------------------------------------------------
When you you do
modprobe -r snd-intel8x0m
modprobe -r snd-intel8x0
modprobe snd-intel8x0
sound should work again.
Do not load snd-intel8x0m module !!!!
Issue History
Date Modified Username Field Change
======================================================================
04-26-05 21:29 columbo New Issue
04-26-05 21:29 columbo Distribution => Slackware Linux 10.1
04-26-05 21:29 columbo Kernel Version => 2.6.11.7
04-29-05 21:06 columbo Issue Monitored: columbo
05-06-05 08:50 gem7 Note Added: 0004590
05-06-05 08:59 pzad Note Added: 0004591
05-06-05 09:00 pzad Note Added: 0004592
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
next reply other threads:[~2005-05-06 7:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 7:00 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 11:44 [ALSA - driver 0001078]: intel8x0 does not work on any (?) 2.6 kernel bugtrack
2005-05-07 7:45 bugtrack
2005-05-06 18:24 bugtrack
2005-05-06 17:04 bugtrack
2005-05-06 7:33 bugtrack
2005-05-06 7:13 bugtrack
2005-05-06 6:59 bugtrack
2005-05-06 6:50 bugtrack
2005-04-26 19:29 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=698018c74cefb8fadad84830549c7a4c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox