All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001023]: ens1371 pcm not work in 2.6.11 kernel
Date: Sat, 18 Jun 2005 05:19:51 +0200	[thread overview]
Message-ID: <c76702c8dff330a7f3dddd089a02ad98@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1023> 
======================================================================
Reported By:                yafrank
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1023
Category:                   CORE - pcm
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Distribution:               Fedora Core 3
Kernel Version:             2.6.11-1.8_FC3
======================================================================
Date Submitted:             03-30-2005 14:25 CEST
Last Modified:              06-18-2005 05:19 CEST
======================================================================
Summary:                    ens1371 pcm not work in 2.6.11 kernel
Description: 
I'm using FC3 and my Creative SB AudioPCI 64V sound card works fine in 
2.6.10-1.770_FC3 kernel. After I replaced the kernel to 2.6.11 from
kernel.org or 2.6.11-1.8_FC3 from redhat, there is no sound anymore. I
noticed that the 2.6.11 kernel uses alsa 1.0.8 driver, yet userspace
alsa-lib and utility in fc3 are 1.0.6. So I upgrade them to 1.0.8 too.
Still, there is no sound and alsamixer doesn't show any pcm option.
Fortunately, the 1.0.8 lib and utility backward compatible with 1.0.6
driver in 2.6.10 kernel, so they were kept. The sound card uses ens1371
kernel module. And my /etc/modprobe.conf is this:

alias snd-card-0 snd-ens1371
alias sound-slot-0 snd-ens1371
install snd-ens1371 /sbin/modprobe --ignore-install snd-ens1371 &&
/usr/sbin/alsactlrestore >/dev/null 2>&1 || :
remove snd-ens1371 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-ens1371
alias usb-controller uhci-hcd
alias net-pf-10 off
alias ipv6 off
alias eth0 8139too


======================================================================

----------------------------------------------------------------------
 yafrank - 06-18-05 04:26 
----------------------------------------------------------------------
I'm not quite sure if my antique laptop bought in 2k, CII 366M/192M/Intel
BX/20G, contains any ac97 chip on borad. Anyway, I'm compiling
2.6.12-rc6-git8 kernel and 1.0.9b alsa now. Alsa compile using
"./configure --with-kernel=/path/to/kernel --with-build=/path/to/kernel
--with-debug=full --with-cards=ens1371 --with-sequencer=yes; make; make
install-modules". Before doing the test, what are those values represent?

----------------------------------------------------------------------
 yafrank - 06-18-05 05:19 
----------------------------------------------------------------------
Boot to newly compiled 2.6.12-rc6-git8 kernel with 1.0.9b alsa driver,
[root@twinhead ~]# cd /proc/asound/card0/codec97#0/
[root@twinhead codec97#0]# echo 18 8000 > ac97#0-0+regs
[root@twinhead codec97#0]# cat ac97#0-0+regs > /tmp/alsa-ac97-test  ##
uploaded
[root@twinhead codec97#0]# grep 18 /tmp/alsa-ac97-test
0:18 = 8101
[root@twinhead codec97#0]# echo 18 000 > ac97#0-0+regs
[root@twinhead codec97#0]# cat ac97#0-0+regs > /tmp/alsa-ac97-test-000
[root@twinhead codec97#0]# grep 18 /tmp/alsa-ac97-test-000
0:18 = 8101
[root@twinhead codec97#0]# echo 18 2020 > ac97#0-0+regs
[root@twinhead codec97#0]# cat ac97#0-0+regs > /tmp/alsa-ac97-test-2020
[root@twinhead codec97#0]# grep 18 /tmp/alsa-ac97-test-2020
0:18 = 8101
[root@twinhead codec97#0]# echo 18 1010 > ac97#0-0+regs
[root@twinhead codec97#0]# cat ac97#0-0+regs > /tmp/alsa-ac97-test-1010
[root@twinhead codec97#0]# grep 18 /tmp/alsa-ac97-test-1010
0:18 = 8101
[root@twinhead codec97#0]# echo 18 0101 > ac97#0-0+regs
[root@twinhead codec97#0]# cat ac97#0-0+regs > /tmp/alsa-ac97-test-0101
[root@twinhead codec97#0]# grep 18 /tmp/alsa-ac97-test-0101
0:18 = 8101
[root@twinhead tmp]# diff alsa-ac97-test alsa-ac97-test-000
1c1
< 0:00 = 0140
---
> 0:00 = 7605
14c14
< 0:1a = 8000
---
> 0:1a = 0000
[root@twinhead tmp]# diff alsa-ac97-test alsa-ac97-test-2020
1c1
< 0:00 = 0140
---
> 0:00 = 7605
8c8
< 0:0e = 8001
---
> 0:0e = 801f
15c15
< 0:1c = 8000
---
> 0:1c = 0000
[root@twinhead tmp]# diff alsa-ac97-test alsa-ac97-test-1010
1c1
< 0:00 = 0140
---
> 0:00 = 7605
6,7c6,7
< 0:0a = ffff
< 0:0c = 811f
---
> 0:0a = 811f
> 0:0c = 801e
14c14
< 0:1a = 8000
---
> 0:1a = 1010
[root@twinhead tmp]# diff alsa-ac97-test alsa-ac97-test-0101
1c1
< 0:00 = 0140
---
> 0:00 = 7605
9c9
< 0:10 = 801f
---
> 0:10 = 8101
14c14
< 0:1a = 8000
---
> 0:1a = 0101

Issue History
Date Modified  Username       Field                    Change              
======================================================================
03-30-05 14:25 yafrank        New Issue                                    
03-30-05 14:25 yafrank        Distribution              => Fedora Core 3   
03-30-05 14:25 yafrank        Kernel Version            => 2.6.11-1.8_FC3  
03-30-05 18:08 tiwai          Note Added: 0004266                          
03-31-05 10:49 yafrank        Note Added: 0004277                          
03-31-05 13:14 yafrank        Note Added: 0004279                          
03-31-05 13:23 perex          Note Added: 0004280                          
03-31-05 17:08 yafrank        Note Added: 0004282                          
04-06-05 18:41 mmadore        Note Added: 0004350                          
04-07-05 16:04 tiwai          Note Added: 0004357                          
04-07-05 18:32 mmadore        Note Added: 0004362                          
04-07-05 18:33 mmadore        File Added: asound.state                     
04-07-05 18:37 mmadore        File Added: ac97#0-0                         
04-07-05 18:38 mmadore        File Added: ac97#0-0+regs                    
04-12-05 05:47 yafrank        Issue Monitored: yafrank                     
04-12-05 06:02 yafrank        Note Added: 0004445                          
04-12-05 16:29 tiwai          Note Added: 0004447                          
04-12-05 19:46 yafrank        Note Added: 0004459                          
04-12-05 20:00 yafrank        Note Added: 0004460                          
04-12-05 21:11 mmadore        Note Added: 0004463                          
04-12-05 21:12 mmadore        File Added: asound.state.new                    
04-24-05 00:15 mycroft        Issue Monitored: mycroft                     
06-17-05 09:55 yafrank        Note Added: 0005065                          
06-17-05 11:45 yafrank        Note Added: 0005067                          
06-17-05 14:44 tiwai          Note Added: 0005073                          
06-18-05 04:26 yafrank        Note Added: 0005082                          
06-18-05 04:52 yafrank        File Added: alsa-ac97-test                    
06-18-05 05:19 yafrank        Note Added: 0005083                          
======================================================================




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

             reply	other threads:[~2005-06-18  3:19 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18  3:19 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-11 14:46 [ALSA - driver 0001023]: ens1371 pcm not work in 2.6.11 kernel bugtrack
2006-07-11 13:02 bugtrack
2006-07-11 12:26 bugtrack
2006-07-11  6:48 bugtrack
2006-07-11  4:28 bugtrack
2006-07-11  4:02 bugtrack
2006-07-10 11:36 bugtrack
2006-07-10 11:01 bugtrack
2006-07-09 12:55 bugtrack
2006-07-09 11:13 bugtrack
2006-07-09  9:59 bugtrack
2006-07-09  9:25 bugtrack
2006-07-09  9:05 bugtrack
2006-07-09  8:58 bugtrack
2006-07-09  8:22 bugtrack
2006-07-07 16:35 bugtrack
2006-07-07 12:37 bugtrack
2006-07-07 12:16 bugtrack
2006-07-07 10:24 bugtrack
2006-07-07 10:08 bugtrack
2006-07-07  8:13 bugtrack
2006-07-07  7:58 bugtrack
2006-07-07  7:21 bugtrack
2006-07-07  7:13 bugtrack
2006-07-07  5:59 bugtrack
2006-07-01  3:26 bugtrack
2006-06-28  2:36 bugtrack
2006-06-27  2:48 bugtrack
2006-06-26 16:09 bugtrack
2006-06-26 16:01 bugtrack
2006-06-26 15:40 bugtrack
2006-06-26 15:36 bugtrack
2006-06-26  2:10 bugtrack
2006-06-26  0:10 bugtrack
2006-06-25 16:13 bugtrack
2006-06-25  6:18 bugtrack
2006-06-25  5:44 bugtrack
2006-06-25  0:04 bugtrack
2006-06-24 19:51 bugtrack
2006-06-24  2:14 bugtrack
2006-06-09  4:51 bugtrack
2006-06-06  7:08 bugtrack
2006-02-04 19:57 bugtrack
2006-02-04 18:18 bugtrack
2006-02-04  9:43 bugtrack
2006-02-02 11:58 bugtrack
2005-12-11  5:43 bugtrack
2005-11-28  4:18 bugtrack
2005-11-15 15:21 bugtrack
2005-11-14  9:01 bugtrack
2005-10-25 13:12 bugtrack
2005-10-25 11:55 bugtrack
2005-09-04  0:09 bugtrack
2005-09-01 16:15 bugtrack
2005-09-01  8:51 bugtrack
2005-07-11 20:52 bugtrack
2005-07-11 14:47 bugtrack
2005-07-11 11:45 bugtrack
2005-07-08  8:24 bugtrack
2005-06-23 14:48 bugtrack
2005-06-20  9:01 bugtrack
2005-06-20  9:00 bugtrack
2005-06-20  8:59 bugtrack
2005-06-18  2:26 bugtrack
2005-06-17 12:44 bugtrack
2005-06-17  9:45 bugtrack
2005-06-17  7:55 bugtrack
2005-04-12 19:11 bugtrack
2005-04-12 18:00 bugtrack
2005-04-12 17:46 bugtrack
2005-04-12 14:29 bugtrack
2005-04-12  4:02 bugtrack
2005-04-07 16:32 bugtrack
2005-04-07 14:04 bugtrack
2005-04-06 16:41 bugtrack
2005-03-31 15:08 bugtrack
2005-03-31 11:23 bugtrack
2005-03-31 11:14 bugtrack
2005-03-31  8:49 bugtrack
2005-03-30 16:08 bugtrack
2005-03-30 12:25 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=c76702c8dff330a7f3dddd089a02ad98@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.