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

[alsa-devel] USB sound card fails to resume from hibernation due to duplicate filename card1/WARNING: sysfs_add_ons, emits symbols
by Avuton Olrich 27 Mar '08

27 Mar '08

After suspending, the usbdisk sound card alsa driver breaks and does not play any further. I believe this is might be due to the trace below from the dmesg. This definitely begins to occur between v2.6.23 and v2.6.23-rc2. I couldn't bisect it down to a single commit. This fails with with all kernels up to at least today's git. Full links at the bottom. Linux tulip 2.6.25-rc6 #6 PREEMPT Wed Mar 19 22:16:23 PDT 2008 i686 AMD Athlon(tm) XP 2700+ AuthenticAMD GNU/Linux Gnu C 4.2.3 Gnu make 3.81 binutils 2.18 util-linux 2.13.1 mount 2.13.1 module-init-tools 3.4 e2fsprogs 1.40.8 xfsprogs 2.9.7 PPP 2.4.4 Linux C Library 2.7 Dynamic linker (ldd) 2.7 Procps 3.2.7 Net-tools 1.60 Kbd 1.13 Sh-utils 6.9 udev 119 Modules Loaded netconsole configfs snd_pcm_oss snd_mixer_oss Relevant looking parts of the dmesg (full dmesg link below): [ 3895.879517] usb 1-4: New USB device found, idVendor=2001, idProduct=f103 [ 3895.879517] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3895.879517] usb 3-1: USB disconnect, address 2 [ 3896.252863] usb 3-1: new full speed USB device using ohci_hcd and address 3 [ 3896.452987] usb 3-1: configuration #1 chosen from 1 choice [ 3896.458877] ALSA /usr/src/linux-2.6/sound/usb/usbaudio.c:2798: 3:1:1: add audio endpoint 0x1 [ 3896.470877] ALSA /usr/src/linux-2.6/sound/usb/usbaudio.c:2798: 3:2:1: add audio endpoint 0x82 [ 3896.482878] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [13] FU [Mic Playback Switch] ch = 1, val = 0/1/1 [ 3896.521857] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:405: cannot set ctl value: req = 0x4, wValue = 0x200, wIndex = 0xd00, type = 4, data = 0x18/0x0 [ 3896.554854] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [13] FU [Mic Playback Volume] ch = 1, val = 0/12240/384 [ 3896.554870] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [9] FU [Speaker Playback Switch] ch = 1, val = 0/1/1 [ 3896.593850] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:405: cannot set ctl value: req = 0x4, wValue = 0x201, wIndex = 0x900, type = 4, data = 0x18/0x0 [ 3896.608842] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [9] FU [Speaker Playback Volume] ch = 2, val = -7264/-16/48 [ 3896.608859] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [10] FU [Mic Capture Switch] ch = 1, val = 0/1/1 [ 3896.647835] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:405: cannot set ctl value: req = 0x4, wValue = 0x200, wIndex = 0xa00, type = 4, data = 0x18/0x0 [ 3896.680836] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [10] FU [Mic Capture Volume] ch = 1, val = 0/6096/384 [ 3896.680849] ALSA /usr/src/linux-2.6/sound/usb/usbmixer.c:988: [10] FU [Auto Gain Control] ch = 1, val = 0/1/1 [ 3896.680880] sysfs: duplicate filename 'card1' can not be created [ 3896.680891] ------------[ cut here ]------------ [ 3896.680893] WARNING: at /usr/src/linux-2.6/fs/sysfs/dir.c:424 sysfs_add_one+0x82/0xa0() [ 3896.680896] Modules linked in: netconsole configfs snd_pcm_oss snd_mixer_oss [ 3896.680903] Pid: 174, comm: khubd Not tainted 2.6.25-rc6 #6 [ 3896.680906] [<c011b0ef>] warn_on_slowpath+0x5f/0x90 [ 3896.680914] [<c0115fde>] __wake_up_common+0x3e/0x70 [ 3896.680918] [<c011b85b>] wake_up_klogd+0x3b/0x40 [ 3896.680922] [<c017d591>] find_inode+0x31/0x60 [ 3896.680927] [<c01a8c40>] sysfs_ilookup_test+0x0/0x10 [ 3896.680930] [<c011c0cb>] printk+0x1b/0x20 [ 3896.680933] [<c01a9012>] sysfs_add_one+0x82/0xa0 [ 3896.680937] [<c01a9dfc>] sysfs_create_link+0x8c/0x100 [ 3896.680940] [<c02f2cb4>] device_add+0x254/0x460 [ 3896.680946] [<c02f2f58>] device_create+0x88/0xc0 [ 3896.680949] [<c038aa06>] snd_card_register+0x276/0x380 [ 3896.680954] [<c03b2ae9>] usb_audio_probe+0x459/0xa00 [ 3896.680959] [<c01a8c40>] sysfs_ilookup_test+0x0/0x10 [ 3896.680963] [<c0342c66>] usb_probe_interface+0xb6/0x140 [ 3896.680969] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.680973] [<c02f4ba1>] driver_probe_device+0x81/0x180 [ 3896.680976] [<c043ecc9>] klist_next+0x69/0xd0 [ 3896.680981] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.680984] [<c02f3e76>] bus_for_each_drv+0x46/0x70 [ 3896.680988] [<c02f4d5b>] device_attach+0x7b/0x80 [ 3896.680991] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.680994] [<c02f3e07>] bus_attach_device+0x47/0x70 [ 3896.680997] [<c02f2dfb>] device_add+0x39b/0x460 [ 3896.681000] [<c0340b4d>] usb_set_configuration+0x30d/0x5d0 [ 3896.681004] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.681007] [<c0349186>] generic_probe+0x76/0xb0 [ 3896.681012] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.681015] [<c0342a20>] usb_probe_device+0x30/0x40 [ 3896.681018] [<c02f4ba1>] driver_probe_device+0x81/0x180 [ 3896.681021] [<c043ecc9>] klist_next+0x69/0xd0 [ 3896.681024] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.681027] [<c02f3e76>] bus_for_each_drv+0x46/0x70 [ 3896.681030] [<c02f4d5b>] device_attach+0x7b/0x80 [ 3896.681033] [<c02f4ca0>] __device_attach+0x0/0x10 [ 3896.681036] [<c02f3e07>] bus_attach_device+0x47/0x70 [ 3896.681039] [<c02f2dfb>] device_add+0x39b/0x460 [ 3896.681042] [<c033b07b>] usb_configure_device+0x5b/0x100 [ 3896.681045] [<c033b33b>] usb_new_device+0x5b/0x180 [ 3896.681048] [<c033c957>] hub_thread+0x637/0xd10 [ 3896.681051] [<c012ddb0>] autoremove_wake_function+0x0/0x40 [ 3896.681058] [<c033c320>] hub_thread+0x0/0xd10 [ 3896.681060] [<c012da82>] kthread+0x42/0x70 [ 3896.681063] [<c012da40>] kthread+0x0/0x70 [ 3896.681066] [<c0104b9f>] kernel_thread_helper+0x7/0x18 [ 3896.681071] ======================= [ 3896.681073] ---[ end trace 87ceb0cbe974168a ]--- [ 3896.689903] input: C-Media USB Headphone Set as /devices/pci0000:00/0000:00:02.1/usb3/3-1/3-1:1.3/input/input9 [ 3896.763158] input: USB HID v1.00 Device [C-Media USB Headphone Set ] on usb-0000:00:02.1-1 [ 3896.763218] usb 3-1: New USB device found, idVendor=0d8c, idProduct=000c [ 3896.763221] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3896.763224] usb 3-1: Product: C-Media USB Headphone Set /proc/modules netconsole 8064 0 - Live 0xf88eb000 configfs 21396 2 netconsole, Live 0xf88f3000 snd_pcm_oss 45280 0 - Live 0xf88fa000 snd_mixer_oss 14784 1 snd_pcm_oss, Live 0xf88e6000 http://avuton.googlepages.com/dmesg-2.6.25-rc6-032008 http://avuton.googlepages.com/iomem-032008 http://avuton.googlepages.com/ioports-032008 http://avuton.googlepages.com/lspci-vvv-032008 http://avuton.googlepages.com/tulip-config -- avuton -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

2 3

[alsa-devel] asoc driver for ad1888 available?
by Tzachi Perelstein 27 Mar '08

27 Mar '08

Hello, I'm looking for an asoc ad1888 codec driver. Does anyone know if such driver available somewhere? I couldn't find one with google nor on linux-2.6-asoc.git. Can anyone suggest an alternative AC97 2.3 codec device with AC97- Link which has an available asoc driver? Thanks. - Tzachi

2 1

[alsa-devel] Accessing alsa user space buffer from external io type plugin
by sandeep lahane 27 Mar '08

27 Mar '08

Hello, I am debugging an userspace external io type plugin, written for an ARM based board where the plugin interacts with DSP directly using shared memory. Every time I have to send period_size data to the DSP, I have my own write/read methods to do so. I am having a problem accessing the alsa ring buffer, my transfer function looks like following. static char * temp; static snd_pcm_sframes_t alsa_transfer(snd_pcm_ioplug_t *io, const snd_pcm_channel_area_t *areas, snd_pcm_uframes_t offset, snd_pcm_uframes_t size) { ...... temp = malloc(period_size); memcpy(temp, unsigned char *)areas->addr + (areas->first + areas->step * offset) / 8, period_size); write_to_dsp(temp, period_size); ....... } All the book keeping is done properly, the first chunk of data is sent properly to DSP and pointer() returns correct value, next time when transfer is called, the memcpy gives segfault. ALSA buffer is an interleaved buffer and I am not using mmap mode. Any idea what might be wrong? When I do something like this: memcpy(temp, "test data test data", period_size); the data is sent properly to DSP, but alsa buffer data is not getting accessed properly. -- Regards, Sandeep.

2 4

[alsa-devel] ESI Juli@/Ice1724
by Mark Trompell 27 Mar '08

27 Mar '08

Hi, when, trying to use audacity for recording, my system completly hangs. I wonder if this is the problem descriped in http://mailman.alsa-project.org/pipermail/alsa-devel/2007-April/000563.html http://mailman.alsa-project.org/pipermail/alsa-devel/2008-February/005987.h… and maybe https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1860 Is it already fixed or is this bug still there? Regards Mark P.S I'm not subcribed to the list, so please cc me.

2 3

Re: [alsa-devel] ALSA driver for Native Instruments sound hardware
by kyr 27 Mar '08

27 Mar '08

O/H Daniel Mack ??????: > Hi, > > On Mar 21, 2008, at 2:07 PM, kyr wrote: >> I'd like to know if this driver support all of the 8 inputs/outputs >> channels, >> and if someone test it with xwax (xwax.co.uk). > > All inputs and outputs are supported, and the developer of xwax wanted > to test his software with this interface. However, I don't know about > his results or if he ever really did it. Maybe ask on their mailing list? > > Best regards, > Daniel > > Daniel hi, There is a xwax user with the audio8dj interface but he has some trouble to get it work well with xwax. The device is working almost well with plughw:1,0,0 for the first channel and plughw:1,0,1 for the second one. But with very high latency. Also refers that the alsamixer does not have any adjustments for in/outs. How can you adjust the input/output levels? and the frequency? 44100, 48000 or 96000Hz? Thanks in advance, Kyriakos

2 1

[alsa-devel] Getting wrong offset and size value alsa library
by Leonidas . 26 Mar '08

26 Mar '08

Hi, I am trying to make my user space audio driver work, in my drivers transfer function, I get wrong values of offset and size and because of this the alsa buffer is not accessible to me and I get a segfault in transfer. The offset should range from 0 to n-1 where n is the buffer size, is this correct? I can transfer the first chunk of data and first time the offset as well as size are correct, but when the transfer function is called again for second period, offset values and size values are wrong, they are some astronomical numbers. -leo

1 0

[alsa-devel] Vostro 1400 patch
by Martin van Es 26 Mar '08

26 Mar '08

Hi, I recently bought a Dell Vostro 1400 and thought I'd let you know my experiences with Alsa: I use Kubuntu Gutsy distribution as a base, but follow kernel at a close pace so I use compiled 2.6.24. This didn't support the hda-intel as I expected (don't remember exactly, but master/front/pcm/surround were all in the game but not as expected and I couldn't get built-in mic to work, but this may be due to too little testing). So I decided to google around and found the model=3stack, dell-3stack options and tried those. Still no luck. Next I dl'ed alsa 1.0.16 and noticed a mail describing a vostro 1400 PCI quirck patch (model dell-bios). So I tried that, but no luck. After that I experimented with all 3stack variants I could find in the code and concluded that dell-3stack is the best. I now have sound, master/front/pcm volume sliders that work but above all: built-in mic (Digital 1) recording (and skype) works! I don't know if it's of any value: I immediately flashed the standard A06 Bios to A07 when I found the update on the Dell site and can not tell if the dell-bios model worked for the preloaded A06 version bios. Hope this helps. If there's anything else I can provide I'd be more than happy to collect the data. Regards, Martin -- if but was of any use, it would be a logic operator

1 0

Re: [alsa-devel] PXA2xx/3xx AC97 Driver(s)
by Mark Brown 26 Mar '08

26 Mar '08

On Wed, Mar 26, 2008 at 01:52:39PM +0000, Oliver Ford wrote: > The machine no longer reboots out of linux though. I assume there were > some changes in 2.6.25-rc4 mainline that aren't in the asoc-v2-dev yet. > I will wait for the pxa3xx stuff to be merged into the mainline for > this. What version of the mainline kernel is the latest asoc-v2-dev > branch based on. (I'm still a little hazy on the git stuff I'm afraid). The last version that was merged in appears to be 2.6.25-rc2 (say 'git log' then search for 'Merge.*v2\.6'). For production use I would recommend going with ASoC v1 at the moment. The PXA3xx support should be straightforward to backport (I wouldn't be suprised if the patches introducing it could just applied against mainline but I've not actually tried yet). > > I know that there are a number of users currently using the tree for > > that use case so the asoc-v2-dev branch should hopefully work for you. > > If you run into trouble please let me know. > The WM97xx touchscreen driver only appears to be in the linux-2.6-touch > repository (dev branch, iirc), rather than linux-2.6-asoc where the > pxa3xx support is. Since I want both the wm97xx touchscreen and pxa3xx > support, is there a simple way I can get the necessary changes in one > applied to the other? You can track both multiple git trees using the remotes feature of git - see git-remote(1) for usage information. For example, this: git remote add wolfson-touch \ git://opensource.wolfsonmicro.com/linux-2.6-touch will tell git to track the Wolfson touch drivers using the name 'wolfson-touch'. If you do that and then say: git remote update git merge wolfson-touch/dev it will fetch the current state of all remote trees it knows about and then merge the current dev branch of the Wolfson touch drivers git into your current working copy. The touchscreen drivers and git usage are both rather off-topic for either list, though - probably best to follow up off-list or on linux-input.

1 0

[alsa-devel] Plugin default and sw_params
by Emmanuel Milou 26 Mar '08

26 Mar '08

Hi all, I have some questions about the /default/ plugin. I am developping a softphone based on ALSA on Ubuntu 7.10. I use read/write IO. When I open a device with the /plughw /plugin, quite everything works fine, the quality sound is good. But with the /default/ plugin or the /dmix/ plugin ( the user can choose one of them ), I can't set my own hw parameters or sw parameters. Actually I set my own value of period size, buffer size, start threshold, stop threshold, but when I check in /proc/asound/cardx/pcm0p/sub0/sw_params or /proc/asound/cardx/pcm0p/sub0/hw_params, the values are totally different. For instance, the start threshold is set to 1 even if I set it to period_size. As a result, I get crackling sound. I suspect this is due to buffer underrun. Maybe if I could change the start threshold or the period size, the sound would be better. So my question: is it possible to modify this values for /default/ plugin without changing the alsa config file ( asoundrc ) ? Thank you very much Manu

1 0

[alsa-devel] snd-bt87x
by Bizon 26 Mar '08

26 Mar '08

Hello! I have WinTV TV card based on BT878A, correctly detected by driver. But there is no sound. I have just something like a single tone. How to fix it? For compare i have also Flyvideo 98 card based on BT878, detected as unknown - it works well. Here is it's lsmod : 00:0b.1 0480: 109e:0878 (rev 02) Subsystem: 1852:1852 Thanks Karol

1 0