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: Wed, 6 Apr 2005 18:41:19 +0200	[thread overview]
Message-ID: <296d22f627f6aca0245cd5cc83dc78fb@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:              04-06-2005 18:41 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 - 03-31-05 17:08 
----------------------------------------------------------------------
Here is what I did:
[root@twinhead alsa-driver-1.0.9rc2]# rpm -i
/usr/local/src/kernel/kernel-2.6.11-1.8_FC3.src.rpm
[root@twinhead alsa-driver-1.0.9rc2]# rpmbuild -bp --target=i686
/usr/src/redhat/SPECS/kernel-2.6.spec
[root@twinhead kernel]# ln -s
/usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11/include/sound/version.h
/usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11/include/linux/
[root@twinhead alsa-driver-1.0.9rc2]# ./configure --with-redhat=yes
--with-cards=ens1371
--with-kernel=/usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11
--with-sequencer=yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory...
/usr/local/src/kernel/alsa-driver-1.0.9rc2
checking cross compile...
checking for directory with kernel source...
/usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11
checking for directory with kernel build...
/lib/modules/2.6.11-prep/build
checking for kernel version... 0.0.0
checking for GCC version... Kernel compiler:  Used compiler: gcc (GCC)
3.4.2 20041017 (Red Hat 3.4.2-6.fc3)

*** NO PREDEFINED KERNEL COMPILER IS DETECTED
*** Assuming the same compiler is used with the current system compiler.

*** Please make sure that the same compiler version was used for building
kernel.

checking for built-in ALSA... "no"
checking for existing ALSA module... "no"
checking for Red Hat kernel... "yes"
checking for SUSE kernel... "auto"
checking for SUSE kernel... "no"
checking to modify of kernel linux/kmod.h... "no"
checking for kernel linux/compiler.h... "yes"
checking for kernel linux/pm.h... "yes"
checking for kernel linux/spinlock.h... "yes"
checking for kernel linux/irq.h... "yes"
checking for kernel linux/threads.h... "yes"
checking for kernel linux/rwsem.h... "yes"
checking for kernel linux/gameport.h... "yes"
checking for kernel linux/devfs_fs_kernel.h... "yes"
checking for kernel linux/highmem.h... "yes"
checking for kernel linux/workqueue.h... "yes"
checking for kernel linux/dma-mapping.h... "yes"
checking for kernel asm/hw_irq.h... "no"
checking for kernel linux/device.h... "yes"
checking for kernel linux/jiffies.h... "yes"
checking for kernel linux/compat.h... "yes"
checking for kernel linux/adb.h... "yes"
checking for kernel linux/cuda.h... "yes"
checking for kernel linux/pmu.h... "yes"
checking for kernel linux/moduleparam.h... "yes"
checking for kernel linux/syscalls.h... "yes"
checking for kernel linux/firmware.h... "yes"
checking for exported symbol dump_stack... grep:
/usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11/kernel/ksyms.c: No such
file or directory
"no"
checking for kernel module symbol versions... "no"
checking for PCI support in kernel... "no"
checking for I2C driver in kernel... unknown
checking for firmware loader... unknown
checking for directory to store kernel modules... /lib/modules/0.0.0/misc
checking for verbose printk... on
checking for debug level... none
checking for processor type... "unknown"
checking for SMP... "no"
checking for ISA PnP driver in kernel... yes
checking for PnP driver in kernel... yes
checking for Kernel ISA-PnP support... "no"
checking for Kernel ISA-PnP module support... "no"
checking for strlcpy... "no"
checking for snprintf... "no"
checking for vsnprintf... "no"
checking for scnprintf... "no"
checking for sscanf... "no"
checking for vmalloc_to_page... "no"
checking for old kmod... "yes"
checking for PDE... "no"
checking for pci_set_consistent_dma_mask... "no"
checking for pci_dev_present... "no"
checking for msleep... "no"
checking for tty->count is the atomic type... "no"
checking for remap_pfn_range... "no"
checking for new remap_page_range... "no"
checking for kcalloc... "no"
checking for saved_config_space in pci_dev... "no"
checking for old kill_fasync... "no"
checking for dma_addr_t... "no"
checking for MUTEX macros... "no"
checking for driver version... 1.0.9rc2
checking for sequencer support... yes
checking for OSS/Free emulation... yes
checking for RTC callback support in kernel... "no"
checking for HPET support... "no"
checking for Procfs support... "no"
checking for USB support... "no"
checking for USB module support... "no"
checking for PC-Speaker hook... "no"
checking for kernel PCMCIA
checking for PCMCIA support... "no"
checking for PCMCIA module support... "no"
checking for PC9800 support in kernel... "no"
checking for parallel port support... "no"
checking for parallel port module support... "no"
checking for which soundcards to compile driver for... configure: error:
Unsupportedsoundcard ens1371

----------------------------------------------------------------------
 mmadore - 04-06-05 18:41 
----------------------------------------------------------------------
Hi,

I am seeing the same behavior.

The sound card is a Creative Labs CT4730 (Ectiva EV1938 - PCI-ID
1102:8938)

Under stock kernel 2.6.10, the mixer works correctly and I can hear sounds
playing.  After upgrading to 2.6.11 or higher, the PCM channel is missing
from alsamixer.  Trying to play any sounds results in silence, and there
aren't any error messages.

I also tried the 1.0.9rc2 drivers, libs and utilities with the same
results.

What can I do to help debug this problem?

Mike

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                          
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-04-06 16:41 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 16:41 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  3:19 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-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=296d22f627f6aca0245cd5cc83dc78fb@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.