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

Re: [alsa-devel] [regression] 2.6.25-rc4 snd-es18xx broken on Alpha
by Rene Herman 31 Mar '08

31 Mar '08

On 10-03-08 08:34, Michael Cree wrote: > Bob Tracy wrote: >> Supposedly with the ES1888, dma1 is for capture, dma2 is for playback. >> dma2 == 5 is a 16-bit channel, yes? That could explain much... It is, but what would it explain? You're only having playback problems, right? >> >> As for the values "chosen" for dma1 and dma2, they are the ones that >> keep showing up in the Alpha sound "howto" postings/documents. > > Running 'show config' in SRM on my Alphas (PWS500au and XP1000) reveals > the settings (except possibly for mpu_port) for the ESS1888 sound chip. > I recall that they are as reported in Alpha sound howtos. Can it be forced to use dma2=0 (an 8-bit channel, and the usual capture channel on es18xx)? However, that might not be the issue anyway: > I hadn't been using the ESS1888 for awhile, but have just tried it out > since you reported problems. I am running kernel 2.6.24.3 and Debian > testing on the XP1000. I tried playing a number of wav files with > alsa's aplay, sox's play and with mocp. I found that aplay and mocp > worked reliably through the ESS1888. Sox's play on some files did play > back a small extra segment of the file - particularly on short files and > usually some section near the end of the file - once it had completed > playing the file once; maybe this is what you are also observing. This sounds very suspiciously like a difference with playing through the native ALSA interface and the OSS emulaion. Could you and/or Bob confirm that sox is using the OSS emulation and not ALSA natively? I could very well imagine the ALSA OSS emulation being broken on Alpha. I doubt any of teh developers has an Alpha. And if aplay works correctly this seems very likely. "sox" _can_ use ALSA natively as well by the way (see manpage for the version you have installed). > More onerously, my testing eventually ended in a complete system lock up! > I ran play (or was it aplay - sorry can't remember now) Vital if play is using the OSS interface... > and the system locked up. Got a response with ping across the network but > couldn't log in via ssh. Have been playing mplayer through the ESS1888 > for the last couple of days (don't like it though - the sound quality of > the ESS1888 is not good enough for my ears) and haven't had another one > of those lockups since. Mmm. Rene.

7 50

[alsa-devel] ATI HDMI with 780/sb700 chipset: no audio
by mikp 30 Mar '08

30 Mar '08

I am trying to get HDMI audio from a ECS 780G mainboard with sb700 and built-in graphics Chipset: "ATI Radeon HD 3200 Graphics" (ChipID = 0x9610). The HDMI video is working with the xf86-video-ati driver. aplay -l **** List of PLAYBACK Hardware Devices **** card 0: HDMI [HDA ATI HDMI], device 0: HDA Generic [HDA Generic] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI_1 [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 and from hwinfo: 31: PCI 14.2: 0403 Audio device [Created at pci.301] UDI: /org/freedesktop/Hal/devices/pci_1002_4383 Unique ID: 5Dex.2J+_taPgpb9 SysFS ID: /devices/pci0000:00/0000:00:14.2 SysFS BusID: 0000:00:14.2 Hardware Class: sound Model: "Elitegroup SBx00 Azalia" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x4383 "SBx00 Azalia" SubVendor: pci 0x1019 "Elitegroup Computer Systems" SubDevice: pci 0x2816 Driver: "HDA Intel" Driver Modules: "snd_hda_intel" Memory Range: 0xfe7f4000-0xfe7f7fff (rw,non-prefetchable) IRQ: 16 (13305 events) Module Alias: "pci:v00001002d00004383sv00001019sd00002816bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown cat /proc/asound/card1/codec\#0 Codec: ATI ATI RS690/780 HDMI Address: 0 Vendor Id: 0x1002791a Subsystem Id: 0x791a00 Revision Id: 0x100000 No Modem Function Group found Default PCM: rates [0x40]: 48000 bits [0x2]: 16 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x02 [Audio Output] wcaps 0x201: Stereo Digital Converter: stream=0, channel=0 Digital: Enabled Digital category: 0x0 Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x0894: OUT Detect R/L Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x02 running alsamixer -c1 i can unmute the IEC958, but i get no HDMI audio. Note the "...Digital Out at Int HDMI" _not_ SPDIF Out at Int HDMI. In order to get the 'card1 with IEC958' to show up i had to add my pci-id to alsa-driver-hg20080323/sound/pci/hda/hda_intel.c /* ATI HDMI */ { PCI_DEVICE(0x1002, 0x4383), .driver_data = AZX_DRIVER_ATIHDMI }, The original hda_intel.c has { 0x1002, 0x4383, PCI_ANY_ID, PCI_ANY_ID, 0, 0, AZX_DRIVER_ATI }, Any help getting this working appreciated. Thanks.

1 0

[alsa-devel] Cannot change volume on Plantronics Audio 910 USB Headset
by cklein＠mpi-sb.mpg.de 29 Mar '08

29 Mar '08

Hi, I recently got a Plantronics .audio 910 USB headset. It is correctly detected by snd-usb-audio and works, but I cannot change the volume of the PCM output or the MIC input. When executing alsamixer -c 1, the volumes seem to be locked and cannot be changed as usual. Unfortunately the microphone volume is at 0, leading to very poor quality of the recorded voice (especially in Skype, which seems to try to compensate the low volume and fails miserably). Does anyone know how to fix this? I found similar reports on the internet for various usb headsets, but no real fix for the situation. I already asked on alsa-users some weeks ago, but did not get any response. I tried the headset on three different PCs, all with the same result. A desktop at work running Fedora 7, a Thinkpad R50p running debian/testing and the 2.6.22 kernel provided in debian/testing. The third one is a Dell precision M65 with debian/unstable. There, I used a vanilla 2.6.24.2 kernel and latest alsa drivers from the mercurial repository when I asked on alsa-users, but in the meantime I upgraded to 2.6.24.3 and hg snapshots from 2008-03-13 06:41 (alsa-driver) and 2008:03:17 05:23 (alsa-kernel), but still got the same behaviour. On all I get some message about "no or invalid class specific endpoint descriptor" in the kernel log (see below). When loading the snd-usb-audio module, dmesg shows the following kernel output (on the M65): usb 2-2: new full speed USB device using uhci_hcd and address 5 usb 2-2: configuration #1 chosen from 1 choice input: Plantronics Plantronics BT Adapter as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.3/input/input10 input: USB HID v1.11 Device [Plantronics Plantronics BT Adapter] on usb-0000:00:1d.1-2 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver ALSA /usr/src/kernel-modules/alsa-driver-d20080313_0641-k20080317_0523/usb/usbaudio.c:2787: 5:1:1 : no or invalid class specific endpoint descriptor ALSA /usr/src/kernel-modules/alsa-driver-d20080313_0641-k20080317_0523/usb/usbaudio.c:2787: 5:2:1 : no or invalid class specific endpoint descriptor usbcore: registered new interface driver snd-usb-audio I posted the output of alsa-info.sh and lsusb -v on pastebin (both taken on the M65). alsa-info.sh: http://pastebin.ca/915715 lsusb -v: http://pastebin.ca/915723 -- CU, Christian Klein http://www.garfield.com/comics/comics_archives_strip.html?1979-ga790520 Homepage: http://www.mpi-sb.mpg.de/~cklein

1 1

[alsa-devel] [BUG] USB sounds card doesn't work - Device 0x4fa:0x4201
by Natalie Protasevich 28 Mar '08

28 Mar '08

Hello ALSA developers, This problem with the USB sounds card has been reported a while ago, and just been confirmed with latest kernel. ==================================================================== $ cat /proc/asound/cards 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 Intel 82801DB-ICH4 with AD1981B at 0xc0000c00, irq 11 1 [U0x4fa0x4201 ]: USB-Audio - USB Device 0x4fa:0x4201 USB Device 0x4fa:0x4201 at usb-0000:00:1d.1-2, full speed If I attempt to play a song using mpg123 or xmms, I get nothing, only maybe click at beggining. I'm using in-kernel OSS emulation. pavel@amd:/mnt/mp3.ptacek/Tanita_Tikaram$ cat /proc/asound/card1/pcm0p/info card: 1 device: 0 subdevice: 0 stream: PLAYBACK id: USB Audio name: USB Audio subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 pavel@amd:/mnt/mp3.ptacek/Tanita_Tikaram$ I tried unmuting everything using aumix. cat /bin/bash > /dev/dsp1 fails to produce any sound, too. =================================================================== Full bug report is here : http://bugzilla.kernel.org/show_bug.cgi?id=6576 It sure needs some helping hand, maybe someone can take a look into this. Thanks, --Natalie

1 0

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

28 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 28 Mar '08

28 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 . 27 Mar '08

27 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