- Alsa-devel - mailman.alsa-project.org

Re: [alsa-devel] support for Medion laptops
by albox＠free.fr 24 May '07

24 May '07

I haven't get any news since my last email 2 weeks ago. Can anybody help me to find where the problem comes from ? Quoting albox(a)free.fr: > I have just installed 1.0.14rc4. Here are the logs : > > [ 20.132000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:698: > codec_mask = 0x3 > [ 20.308000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:1820: > hda_codec: model 'medion' is selected for config 161f:2054 (Medion laptop) > [ 21.032000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/../../alsa-kernel/pci/hda/patch_si3054.c:245: > si3054: cannot initialize. EXT MID = 0000 > [ 21.040000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/../../alsa-kernel/pci/hda/patch_si3054.c:257: > Link Frame Detect(FDT) is not ready (line status: 0000) > [ 71.352000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1188: > azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 > [ 71.352000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 > [ 71.360000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 > [ 71.368000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 > [ 71.380000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 > [ 71.480000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 > [ 71.488000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 > [ 71.496000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 > [ 71.504000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 > [ 71.524000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1188: > azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 > [ 71.524000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 > [ 71.532000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 > [ 71.540000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 > [ 71.548000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 > [ 71.560000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x2, stream=0x0, channel=0, format=0x0 > [ 71.568000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x4, stream=0x0, channel=0, format=0x0 > [ 71.576000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x3, stream=0x0, channel=0, format=0x0 > [ 71.584000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x5, stream=0x0, channel=0, format=0x0 > [ 71.752000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1188: > azx_pcm_prepare: bufsize=0x10000, fragsize=0x1000, format=0x11 > [ 71.752000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x11 > [ 71.760000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x4, stream=0x5, channel=0, format=0x11 > [ 71.768000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x3, stream=0x5, channel=0, format=0x11 > [ 71.776000] ALSA > /home/alboot/Sources/alsa1.0.14rc4/alsa-driver-1.0.14rc4/pci/hda/hda_codec.c:630: > hda_codec_setup_stream: NID=0x5, stream=0x5, channel=0, format=0x11 > > If you want more information, let me know...

1 0

[alsa-devel] [PATCH 1/2] Add SB_HW_CS5530 to the SB code
by Ash Willis 23 May '07

23 May '07

Add support for the Cyrix/NatSemi Geode SC5530 chips. This driver is ported from oss/kahlua.c and is made up of two patches. Patch 1/2 adds some stuff to the SB layer to allow for some hardware quirks and is to be applied to alsa-kernel. Patch 2/2 adds the actual driver code to be applied to alsa-driver. Patch 2 depends on patch 1. Signed off by: Ash Willis <ashwillis(a)programmer.net> --- summary: Add SB_HW_CS5530 to the SB code diff -r 45179b325c8e -r b8441e56e853 include/sb.h --- a/include/sb.h Wed May 23 16:27:32 2007 +0200 +++ b/include/sb.h Thu May 24 03:09:49 2007 +0100 @@ -38,6 +38,7 @@ enum sb_hw_type { SB_HW_ALS100, /* Avance Logic ALS100 chip */ SB_HW_ALS4000, /* Avance Logic ALS4000 chip */ SB_HW_DT019X, /* Diamond Tech. DT-019X / Avance Logic ALS-007 */ + SB_HW_CS5530, /* Cyrix/NatSemi 5530 VSA1 */ }; #define SB_OPEN_PCM 0x01 diff -r 45179b325c8e -r b8441e56e853 isa/sb/sb16_main.c --- a/isa/sb/sb16_main.c Wed May 23 16:27:32 2007 +0200 +++ b/isa/sb/sb16_main.c Thu May 24 03:09:49 2007 +0100 @@ -563,6 +563,11 @@ static int snd_sb16_playback_open(struct __open_ok: if (chip->hardware == SB_HW_ALS100) runtime->hw.rate_max = 48000; + if (chip->hardware == SB_HW_CS5530) { + runtime->hw.buffer_bytes_max = 32 * 1024; + runtime->hw.periods_min = 2; + runtime->hw.rate_min = 44100; + } if (chip->mode & SB_RATE_LOCK) runtime->hw.rate_min = runtime->hw.rate_max = chip->locked_rate; chip->playback_substream = substream; @@ -633,6 +638,11 @@ static int snd_sb16_capture_open(struct __open_ok: if (chip->hardware == SB_HW_ALS100) runtime->hw.rate_max = 48000; + if (chip->hardware == SB_HW_CS5530) { + runtime->hw.buffer_bytes_max = 32 * 1024; + runtime->hw.periods_min = 2; + runtime->hw.rate_min = 44100; + } if (chip->mode & SB_RATE_LOCK) runtime->hw.rate_min = runtime->hw.rate_max = chip->locked_rate; chip->capture_substream = substream; diff -r 45179b325c8e -r b8441e56e853 isa/sb/sb_common.c --- a/isa/sb/sb_common.c Wed May 23 16:27:32 2007 +0200 +++ b/isa/sb/sb_common.c Thu May 24 03:09:49 2007 +0100 @@ -128,7 +128,7 @@ static int snd_sbdsp_probe(struct snd_sb minor = version & 0xff; snd_printdd("SB [0x%lx]: DSP chip found, version = %i.%i\n", chip->port, major, minor); - + switch (chip->hardware) { case SB_HW_AUTO: switch (major) { @@ -167,6 +167,9 @@ static int snd_sbdsp_probe(struct snd_sb break; case SB_HW_DT019X: str = "(DT019X/ALS007)"; + break; + case SB_HW_CS5530: + str = "16 (CS5530)"; break; default: return -ENODEV; diff -r 45179b325c8e -r b8441e56e853 isa/sb/sb_mixer.c --- a/isa/sb/sb_mixer.c Wed May 23 16:27:32 2007 +0200 +++ b/isa/sb/sb_mixer.c Thu May 24 03:09:49 2007 +0100 @@ -821,6 +821,7 @@ int snd_sbmixer_new(struct snd_sb *chip) break; case SB_HW_16: case SB_HW_ALS100: + case SB_HW_CS5530: if ((err = snd_sbmixer_init(chip, snd_sb16_controls, ARRAY_SIZE(snd_sb16_controls), @@ -950,6 +951,7 @@ void snd_sbmixer_suspend(struct snd_sb * break; case SB_HW_16: case SB_HW_ALS100: + case SB_HW_CS5530: save_mixer(chip, sb16_saved_regs, ARRAY_SIZE(sb16_saved_regs)); break; case SB_HW_ALS4000: @@ -975,6 +977,7 @@ void snd_sbmixer_resume(struct snd_sb *c break; case SB_HW_16: case SB_HW_ALS100: + case SB_HW_CS5530: restore_mixer(chip, sb16_saved_regs, ARRAY_SIZE(sb16_saved_regs)); break; case SB_HW_ALS4000: =

1 0

Re: [alsa-devel] Can someone verify support for "AzTech Sound Galaxy Nova 16 Extra II-3D - using AZT-2316/R Chipset - FCC-ID:I38-MMSN846" ?
by ramkromberg＠mail.com 23 May '07

23 May '07

EPPROM ON: OK, I formated that dos partition and simply sys a: c:, then I installed the driver (copying them to the partition from the linux install), in theinstall I selected the defaults settings (220 irq5 dma1...) and rebooted, now in dos again I used diagnose to test the audio and hwset /mr /ms to reset and save the epprom. now I rebooted and loged to linux: sudo modprobe snd-sb8 port=0x220 irq=5 dma8=1 FATAL: Error inserting snd_sb8 (/lib/modules/2.6.20-15-generic/kernel/sound/isa/sb/snd-sb8.ko): No such device dmesg last lines ( [ 319.827327] Sound Blaster soundcard not found or device busy -reboot- EPPROM OFF (SOFTWARE ON): in dos: diagnose works, reboot and back to lin: sudo modprobe snd-sb8 port=0x220 irq=5 dma8=1 no error, no mention in dmesg, but xmms gives the usual error... Heres lsmod just for kicks: Module Size Used by snd_sb8 9216 0 snd_sb8_dsp 12288 1 snd_sb8 snd_sb_common 17792 2 snd_sb8,snd_sb8_dsp snd_opl3_lib 11520 1 snd_sb8 snd_hwdep 9988 1 snd_opl3_lib snd_pcm_oss 44544 0 snd_pcm 79876 3 snd_sb8,snd_sb8_dsp,snd_pcm_oss snd_mixer_oss 17408 1 snd_pcm_oss snd_seq_dummy 4740 0 snd_seq_oss 32896 0 snd_seq_midi 9600 0 snd_rawmidi 25472 2 snd_sb8_dsp,snd_seq_midi snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 23684 3 snd_opl3_lib,snd_pcm,snd_seq snd_seq_device 9100 6 snd_opl3_lib,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 54020 13 snd_sb8,snd_sb8_dsp,snd_sb_common,snd_opl3_lib,snd_hwdep,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 8672 1 snd snd_page_alloc 10888 1 snd_pcm nfs 240876 0 nfsd 218992 17 exportfs 6912 1 nfsd lockd 64904 3 nfs,nfsd sunrpc 161340 12 nfs,nfsd,lockd apm 22752 2 ppdev 10116 0 cpufreq_stats 7360 0 cpufreq_ondemand 9228 0 cpufreq_powersave 2688 0 freq_table 5792 2 cpufreq_stats,cpufreq_ondemand cpufreq_conservative 8200 0 cpufreq_userspace 5408 0 nls_iso8859_1 5120 1 nls_cp437 6784 1 vfat 14208 1 fat 53916 1 vfat ext2 66824 1 lp 12452 0 parport_pc 36388 1 parport 36936 3 ppdev,lp,parport_pc pcspkr 4224 0 ipv6 268704 8 tsdev 8768 0 evdev 11008 1 ext3 133128 1 jbd 59816 1 ext3 mbcache 9604 2 ext2,ext3 ide_disk 17024 5 8139too 27648 0 ide_cd 32672 0 cdrom 37664 1 ide_cd floppy 59524 0 ehci_hcd 34188 0 8139cp 25088 0 mii 6528 2 8139too,8139cp uhci_hcd 25360 0 usbcore 134280 3 ehci_hcd,uhci_hcd piix 10756 0 [permanent] generic 5124 0 [permanent] ata_generic 9092 0 libata 125720 1 ata_generic scsi_mod 142348 1 libata fbcon 42656 0 tileblit 3584 1 fbcon font 9216 1 fbcon bitblit 6912 1 fbcon softcursor 3200 1 bitblit vesafb 9220 0 capability 5896 0 commoncap 8192 1 capability So now atleast we know its not the jumpers ;-) Is their the slight chance xmms is the problem ? gxine crushs too... Is their something like "beep" only for the sound card ? Maybe droping some data to /dev/### to produce a beep ? Ram Kromberg ramkromberg(a)mail.com

4 13

[alsa-devel] No state is present for card CMI8738
by Tomas Pospisek's Mailing Lists 23 May '07

23 May '07

Since alsa-user is rather ... errr ... silent, I dare to repost the same question here. I've seen that Alsa likes the Terratec cards, however since they're also based on the CMI chipset, and at least /my/ onboard CMI chipset here sucks badly I wonder what low cost card I can use? I hope somebody can give me a clue, *t PS: Mic input is barely loud enough with my onboard sound. Mic boost has no effect. -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- ---------- Forwarded message ---------- Date: Mon, 14 May 2007 14:39:36 +0200 (CEST) From: Tomas Pospisek's Mailing Lists <tpo2(a)sourcepole.ch> To: alsa-user(a)lists.sourceforge.net Subject: [Alsa-user] No state is present for card CMI8738 The following is my problem: $ alsactl -f .alsavoip restore No state is present for card CMI8738 I see this "sometimes". Sometimes the above works and sometimes it returns with that error message. It needs to be noted that I am suspending to ram. Nevertheless, the behaveour is not consistent in between "s2ram"s and I don't know whether that has anything to do with it either. It also needs to be noted that alsamixer *never* has any problems accessing the card. But even after changing the card settings with alsamixer, alsactl will keep on repeating that error message. * $ lspci 00:0d.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) * alsa userspace is at 1.0.13 * kernel is Debian's 2.6.18-4-686 Further, minor problems: * After waking up from suspend the card looses its microphone settings - that is - "Mic Capture" is allway reset to zero. * Further on the choice to hide the microphone setting "Mic Capture" in alsamixer behind F5 irritates me a bit - there are *a lot* of very obscure settings (such as "IEC958 5V" - huh?), that are displayed by default. What's up with that error above? What does it mean? Is there any way I can fix or circumvent it? Anybody a hint? *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Alsa-user mailing list Alsa-user(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user

2 4

[alsa-devel] A52 plugin segfault and patch
by Fabian van der Werf 23 May '07

23 May '07

Hi All, I bumped into segfault when trying to use the a52 plugin. I linked the plugin with the latest svn revision of ffmpeg (r9102). Starting program: /usr/bin/aplay -Dsurround test.wav Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1211078432 (LWP 9835)] Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1211078432 (LWP 9835)] av_crc (ctx=0x0, crc=0, buffer=0x8072c14 , length=1116) at crc.c:77 77 if(!ctx[256]) (gdb) bt #0 av_crc (ctx=0x0, crc=0, buffer=0x8072c14 , length=1116) at crc.c:77 #1 0xb78ce8a1 in output_frame_end (s=0x0) at ac3enc.c:1135 #2 0xb78d1010 in AC3_encode_frame (avctx=0x806d3c0, frame=0x8072c10 "\vw", buf_size=6136, data=0x806e400) at ac3enc.c:1261 #3 0xb7730f68 in avcodec_encode_audio (avctx=0x806d3c0, buf=0x8072c10 "\vw", buf_size=6136, samples=0x0) at utils.c:863 #4 0xb772f66c in convert_data (rec=0x805c868) at pcm_a52.c:57 #5 0xb7730101 in a52_transfer (io=0x805c868, areas=0x80551f0, offset=0, size=1536) at pcm_a52.c:197 #6 0xb7efcf11 in ioplug_priv_transfer_areas (pcm=0x806c138, areas=0x80551f0, offset=0, size=0) at pcm_ioplug.c:521 #7 0xb7efcfd6 in snd_pcm_ioplug_mmap_commit (pcm=0x806c138, offset=0, size=1536) at pcm_ioplug.c:590 #8 0xb7ebf7b7 in snd_pcm_mmap_commit (pcm=0x0, offset=0, frames=1536) at pcm.c:6305 #9 0xb7ecc7e4 in snd_pcm_plugin_write_areas (pcm=0x8054f48, areas=0xbfc8ea10, offset=0, size=1536) at pcm_plugin.c:282 #10 0xb7ebfc42 in snd_pcm_write_areas (pcm=0x8054f48, areas=0xbfc8ea10, offset=0, size=1536, func=0xb7ecc740 <snd_pcm_plugin_write_areas>) at pcm.c:6492 #11 0xb7ecbdff in snd_pcm_plugin_writei (pcm=0x8054f48, buffer=0x8074410, size=1536) at pcm_plugin.c:353 #12 0xb7eb7da5 in snd_pcm_writei (pcm=0x8068488, buffer=0x8074410, size=0) at pcm_local.h:401 #13 0x0804d05a in pcm_write (data=0x8074410 "", count=1536) at aplay.c:1260 #14 0x0804d66f in playback_go (fd=8, loaded=0, count=48457728, rtype=2, name=0xbfc8fa1d "test.wav") at aplay.c:1986 #15 0x0804e9b2 in playback (name=0xbfc8fa1d "test.wav") at aplay.c:2044 #16 0x08050ea9 in main (argc=3, argv=0xbfc8ed64) at aplay.c:601 The patch below fixes this segmentation fault by adding a call to avcodec_init() diff -Naur alsa-plugins-1.0.13/a52/pcm_a52.c alsa-plugins-1.0.13-patched/a52/pcm_a52.c --- alsa-plugins-1.0.13/a52/pcm_a52.c 2006-09-29 13:51:37.000000000 +0200 +++ alsa-plugins-1.0.13-patched/a52/pcm_a52.c 2007-05-22 18:49:56.000000000 +0200 @@ -676,6 +676,7 @@ rec->channels = channels; rec->format = format; + avcodec_init(); avcodec_register_all(); rec->codec = avcodec_find_encoder(CODEC_ID_AC3); if (! rec->codec) { Regards, Fabian

2 1

Re: [alsa-devel] bios update alters hda-intel and alsamixer
by Tobin Davis 23 May '07

23 May '07

On Wed, 2007-05-23 at 01:21 -0500, Chris Pemberton wrote: > On 5/23/07, Tobin Davis <tdavis(a)dsl-only.net> wrote: > > Could you post the output from this script: > > http://bulletproof.servebeer.com/alsa/scripts/alsa-info.sh > > > > It was written by a user on the #alsa irc channel, and has been very > > helpful in debugging sound driver issues, at least for me. > > > > Tobin > > > > On Tue, 2007-05-22 at 23:55 -0500, Chris Pemberton wrote: > > > > > After updating the bios on a Lenovo notebook, my hda-intel sound "changed" > > > > > > Before the bios update I used kernel 2.6.20.3, external > > > alsa-driver-1.0.14rc3 and the attached patch_realtek.c (in-kernel alsa > > > wouldn't work) > > > > > > After the bios update I use just the alsa contained in kernel 2.6.20.3. > > > > > > Before bios update, my mixer contained many items: including master, > > > front, mic, pcm, etc. > > > > > > Now it only contains master and pcm. > > > > > > So, I have a few questions: > > > > > > How can I determine what items are "supposed" to show up in alsamixer? > > > > > > Where can I submit my laptop soundcard information to help finalize > > > support of this model/card? > > > > > > Thank you > > > _______________________________________________ > > > Alsa-devel mailing list > > > Alsa-devel(a)alsa-project.org > > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > > > -- > > Tobin Davis <tdavis(a)dsl-only.net> > > _______________________________________________ > > Alsa-devel mailing list > > Alsa-devel(a)alsa-project.org > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > > > It is located here: > > http://pastebin.ca/504675 Ok, according to what I can tell, you don't have the most recent version of the driver (your original post didn't have an attachement). I do know that the Lenovo support for the ALC861VD was added after 1.0.14rc4 snapshot was made. Try installing the most recent HG daily snapshot from ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver . If that doesn't fix it, rerun the alsa-info.sh script and repost the new data. -- Tobin Davis <tdavis(a)dsl-only.net>

1 0

[alsa-devel] bios update alters hda-intel and alsamixer
by Chris Pemberton 23 May '07

23 May '07

After updating the bios on a Lenovo notebook, my hda-intel sound "changed" Before the bios update I used kernel 2.6.20.3, external alsa-driver-1.0.14rc3 and the attached patch_realtek.c (in-kernel alsa wouldn't work) After the bios update I use just the alsa contained in kernel 2.6.20.3. Before bios update, my mixer contained many items: including master, front, mic, pcm, etc. Now it only contains master and pcm. So, I have a few questions: How can I determine what items are "supposed" to show up in alsamixer? Where can I submit my laptop soundcard information to help finalize support of this model/card? Thank you

2 1

Re: [alsa-devel] I don't understand snd_pcm_ops
by Ash Willis 22 May '07

22 May '07

> First off, I thought PCM stood for Pulse Code Modulation, but that > just describes the > format of the digital data. I don't understand what a PCM operation could be. Exactly, it described the format of the digital data used i audio processing. PCM does stand for pulse code modulation, but here it is a reference to a device that processes sample based digital audio i.e not midi etc. The ALSA middle layer (which includes PCM) takes care of all the common stuff that all drivers need to do. In sound drivers, we have multiple types of devices: PCM, midi, mixers etc. The PCM layer is responsible for doing all the digital audio work. I.e preparing the card for playback, initiaing transfer to and from the device etc. In short, if you want to playback or capture sound, you're going to need a PCM :) snd_pcm_ops is a structure of callbacks that relate to different events regarding the PCM interface. Use this to run your own code at specific events. I.e. it's most probable that you'll want to prepare the device in some manner before audio transfer starts, so you would put the code to do this into your prepare callback. > > I've seen documentation where PCM is considered an alternative to > I2S or AC97. But if you > look at eti_b1_wm8731.c, you'll see this: > > #include "at91-pcm.h" > #include "at91-i2s.h" > > So is the AT91 a PCM device or an I2S device??? None of these are alternatives to each other. They're all different things. The anser to your question would be that this is an i2c device that has a PCM. Have you read "Writing an ALSA driver"? It generally describes ALSA drivers as they relate to PCI, and how to write them, but it does a good job at explaining the general ALSA driver architecture. Ash =

2 1

[alsa-devel] [PATCH] Fix ASoC s3c24xx-pcm spinlock bug
by Zoltan Devai 22 May '07

22 May '07

Hi, This should fix a spinlock lockup bug on the s3c24xx arch. Regards, Zoltan --- --- a/sound/soc/s3c24xx/s3c24xx-pcm.c +++ b/sound/soc/s3c24xx/s3c24xx-pcm.c @@ -337,6 +337,8 @@ static int s3c24xx_pcm_open(struct snd_p if (prtd == NULL) return -ENOMEM; + spin_lock_init(&prtd->lock); + runtime->private_data = prtd; return 0; }

2 1

[alsa-devel] Broken JACK plugin in alsa-plugins and a way to fix it.
by Jasiu 22 May '07

22 May '07

Hi. I want to note that JACK plugin in alsa-plugins in broken. (At least on my two systems.) It just plays for a few seconds and then stops hanging the application that was sending data to it. When it hangs jackd spits out this: subgraph starting at alsa-jack.jackP.3635.0 timed out (subgraph_wait_fd=7, status = 0, state = Running) What I want to note is that there is a fix to that and I would like it to be included in the tree. I'm not sure if it doesn't break anything else, but it works for me ok. Open pcm_jack.c and on the line 146 you'll find: write(jack->fd, buf, 1); /* for polling */ Deleting this seems to get rid of the problem. So please if you can patch this out. (I didn't make a patch myself since this is so tiny fix that it isn't really worth.) Cheers.

2 3