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

Re: [alsa-devel] [Alsa-user] Jetway j7f2 via82xx volume problem: sound suddenly stops when increasing volume: "SOLVED" (well ... sort of)
by Zoilo Gomez 03 May '08

03 May '08

(Sorry for cross-posting from alsa-user; however, on 2nd thought I think this really belongs in alsa-devel): === I think I have found what is causing this problem: in ac97_patch.c / int patch_vt1617a(...) there is a line of code: >>> snd_ac97_write_cache(a97, 0x5c, 0x20); According to a comment, this code is supposed to "bring the analog power consumption to normal, like WinXP driver for EPIA SP". If I comment out this line, the problem appears to be solved ... I can now put all volume controls to maximum values and the sound will keep playing. This is consistent with the apparent introduction of this bug in kernel 2.6.19 (includes alsa-driver version 1.0.12rc1): no such problem occurred until 2.6.18, but all kernels since 2.6.19 do suffer from this problem. The line of code above first shows up in linux-2.6.19. Unfortunately, since I do not have a datasheet for the VT1617A chip set, I cannot verify the exact semantics, or suggest an improvement. Can anyone with a datasheet please suggest a proper patch to this line of code? TIA, Z. ====== Zoilo Gomez wrote: > In the mean time I have found that kernels 2.6.15 and 2.6.16 do not > suffer from this problem, whereas 2.6.22 till 2.6.25 do. > > Testing for kernels 2.6.17 till 2.6.21 is somewhat complicated in my > setup, because there are other problems (NFS-related) which I need to > sort out. > > So it looks like there is a bug somehow. > > Providing the dxs_support parameter does not make any difference, no > matter what value I set it to. > > Z. > > > Zoilo Gomez wrote: >> I have several J7F2 boards from Jetway, containing a 8237 via sound >> device on the south bridge. >> >> Using the alsa-driver, when I increase the volume then at some point >> all over sudden the sound stops. On some boards this happens at 75%, >> on others already at 60%, or 90%. Bringing the volume down again does >> not bring the audio back ... >> >> I am using the alsa-drivers with MPlayer. >> >> Although to me this smells like a hardware problem, I understand from >> googling around that this can be fixed with software, but I cannot >> find the correct solution anywhere. I have tested with gentoo kernels >> 2.6.22 and 2.6.24. >> >> AFAIK there are only 2 ways to get the sound back once it has stopped: >> >> 1) reset the mobo >> 2) rmmod snd-via82xx, followed by modprobe snd-via82xx >> >> The strange thing is that in option 2), the problem seems to be gone >> once the driver has been reloaded; from that moment on it is working >> fine ....! >> >> There is a driver from Via Arena (viaudiocombo) that seems to work >> fine, but it is OSS i.o. ALSA, and also a development by Via Arena >> i.o. the Linux community. Besides, I need synchronization features >> from the audio driver, and I do not think that OSS support this (not >> 100% sure). >> >> >> Can anyone help me and shed light on this? >> >> >> TIA! >> >> Zoilo. >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save >> $100. Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java… >> >> _______________________________________________ >> Alsa-user mailing list >> Alsa-user(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/alsa-user >> >> >> > > >

2 9

[alsa-devel] error using aplay
by Will Wagner 02 May '08

02 May '08

I have cross compiled alsa-lib & alsa-utils for my arm platform. All appears to be working as speaker_test works fine (and have had the kernel sound driver working previously). However when I try to play a wav file with aplay it fails. This is because in set_params(), after initialising the hardware (which happens with no errors), it then tries to read back the period_size with the call: snd_pcm_hw_params_get_period_size(params, &chunk_size, 0); Which for the file I am playing should return 2048 but instead returns zero. After that it reallocs the buffer to zero size and exits. To try to work out what's going wrong I have been debugging this and inspecting params get the following: (gdb) p *params $21 = {flags = 0, masks = {{bits = {8, 0, 0, 0, 0, 0, 0, 0}}, {bits = {4, 0, 0, 0, 0, 0, 0, 0}}, {bits = {1, 0, 0, 0, 0, 0, 0, 0}}}, mres = {{ bits = {0, 0, 0, 0, 0, 0, 0, 0}}, {bits = {0, 0, 0, 0, 0, 0, 0, 0}}, { bits = {0, 0, 0, 0, 0, 0, 0, 0}}, {bits = {0, 0, 0, 0, 0, 0, 0, 0}}, { bits = {0, 0, 0, 0, 0, 0, 0, 0}}}, intervals = {{min = 16, max = 16, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 32, max = 32, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 2, max = 2, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 22050, max = 22050, openmin = 0, openmax = 0, integer = 1, empty = 0}, { min = 92879, max = 92880, openmin = 1, openmax = 1, integer = 0, empty = 0}, {min = 2048, max = 2048, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 8192, max = 8192, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 5, max = 5, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 464399, max = 464400, openmin = 1, openmax = 1, integer = 0, empty = 0}, {min = 10240, max = 10240, openmin = 0, openmax = 0, integer = 1, empty = 0}, { min = 40960, max = 40960, openmin = 0, openmax = 0, integer = 1, empty = 0}, {min = 10000, max = 10000, openmin = 0, openmax = 0, integer = 1, empty = 0}}, ires = {{min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}, {min = 0, max = 0, openmin = 0, openmax = 0, integer = 0, empty = 0}}, rmask = 0, cmask = 1048327, info = 65795, msbits = 16, rate_num = 22050, rate_den = 1, fifo_size = 0, reserved = '\0' <repeats 63 times>} My reading of this is that period_size is correct at 2048, however openmin is 0 (dont' know what openmin is all about). So inspecting the code I thought this should all work. However it appears that there is some magic going on with functions being redirected as a backtrace shows: (gdb) bt #0 __snd_pcm_hw_params_get_period_size (params=0xbef44700, val=0xbef44674, dir=0x2166c) at pcm.c:4263 #1 0x4006f1c8 in __old_snd_pcm_hw_params_get_period_size (params=0xbef44700, dir=0x2166c) at pcm.c:6822 #2 0x0000eda0 in set_params () at aplay.c:983 #3 0x00014004 in playback_go (fd=4, loaded=0, count=171008, rtype=2, name=0xbef44de7 "/sdcard/sounds/tada.wav") at aplay.c:1950 #4 0x000147b8 in playback (name=0xbef44de7 "/sdcard/sounds/tada.wav") at aplay.c:2042 #5 0x0000c8c4 in main (argc=3, argv=0xbef44ce4) at aplay.c:615 It seems the call is somehow being redirected through __old_snd_pcm_hw_params_get_period_size and the implementation of this means that I end up returning openmin instead of min for period_size. Can someone explain what is going on here? Why am I being redirected through this old function? Is it correct that I should be reading openmin here? Any help much appreciated. Will. -- ------------------------------------------------------------------------ Will Wagner will_wagner(a)carallon.com Senior Project Engineer Office Tel: +44 (0)20 7371 2032 Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA ------------------------------------------------------------------------

2 1

[alsa-devel] Another unknown bt878
by John R. 02 May '08

02 May '08

Sound doesn't work on my bt878 based card. Let me know what other information is needed... kernel 2.6.24.2: Apr 14 20:28:38 server kernel: unknown card 0x878-0xaa00:0x1460 Apr 14 20:28:38 server kernel: please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)alsa-project.org> Apr 14 20:28:38 server kernel: ACPI: PCI Interrupt 0000:05:00.1[A] -> GSI 18 (level, low) -> IRQ 18 Apr 14 20:28:38 server kernel: bt87x0: Using board 0, analog, digital (rate 32000 Hz) Apr 14 20:28:38 server kernel: unknown card 0x878-0xaa01:0x1461 Apr 14 20:28:38 server kernel: please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)alsa-project.org> Apr 14 20:28:38 server kernel: ACPI: PCI Interrupt 0000:05:01.1[A] -> GSI 19 (level, low) -> IRQ 19 Apr 14 20:28:38 server kernel: bt87x1: Using board 0, analog, digital (rate 32000 Hz) Apr 14 20:28:38 server kernel: unknown card 0x878-0xaa02:0x1462 Apr 14 20:28:38 server kernel: please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)alsa-project.org> Apr 14 20:28:38 server kernel: ACPI: PCI Interrupt 0000:05:02.1[A] -> GSI 16 (level, low) -> IRQ 16 Apr 14 20:28:38 server kernel: bt87x2: Using board 0, analog, digital (rate 3200 0 Hz) Apr 14 20:28:38 server kernel: unknown card 0x878-0xaa03:0x1463 Apr 14 20:28:38 server kernel: please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)alsa-project.org> Apr 14 20:28:38 server kernel: ACPI: PCI Interrupt 0000:05:03.1[A] -> GSI 17 (level, low) -> IRQ 17 Apr 14 20:28:38 server kernel: bt87x3: Using board 0, analog, digital (rate 32000 Hz) lspci: 05:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 05:01.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:01.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 05:02.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:02.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 05:03.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:03.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) at boot: bttv: driver version 0.9.17 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18 bttv0: Bt878 (rev 17) at 0000:05:00.0, irq: 18, latency: 64, mmio: 0xdfcfe000 bttv0: detected: Provideo PV150A-1 [card=98], PCI subsystem ID is aa00:1460 bttv0: using: ProVideo PV150 [card=98,autodetected] bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init] bttv0: tuner absent bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 => 35468950 .. ok bttv: Bt8xx card found (1). ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 19 (level, low) -> IRQ 19 bttv1: Bt878 (rev 17) at 0000:05:01.0, irq: 19, latency: 64, mmio: 0xdfcfc000 bttv1: detected: Provideo PV150A-2 [card=98], PCI subsystem ID is aa01:1461 bttv1: using: ProVideo PV150 [card=98,autodetected] bttv1: gpio: en=00000000, out=00000000 in=00ffffff [init] bttv1: tuner absent bttv1: registered device video1 bttv1: registered device vbi1 bttv1: PLL: 28636363 => 35468950 .. ok bttv: Bt8xx card found (2). ACPI: PCI Interrupt 0000:05:02.0[A] -> GSI 16 (level, low) -> IRQ 16 bttv2: Bt878 (rev 17) at 0000:05:02.0, irq: 16, latency: 64, mmio: 0xdfcfa000 bttv2: detected: Provideo PV150A-3 [card=98], PCI subsystem ID is aa02:1462 bttv2: using: ProVideo PV150 [card=98,autodetected] bttv2: gpio: en=00000000, out=00000000 in=00ffffff [init] bttv2: tuner absent bttv2: registered device video2 bttv2: registered device vbi2 bttv2: PLL: 28636363 => 35468950 .. ok bttv: Bt8xx card found (3). ACPI: PCI Interrupt 0000:05:03.0[A] -> GSI 17 (level, low) -> IRQ 17 bttv3: Bt878 (rev 17) at 0000:05:03.0, irq: 17, latency: 64, mmio: 0xdfcf8000 bttv3: detected: Provideo PV150A-4 [card=98], PCI subsystem ID is aa03:1463 bttv3: using: ProVideo PV150 [card=98,autodetected] bttv3: gpio: en=00000000, out=00000000 in=00ffffff [init] bttv3: tuner absent bttv3: registered device video3 bttv3: registered device vbi3 bttv3: PLL: 28636363 => 35468950 .. ok

2 2

[alsa-devel] Alsa Problem
by prabhu 02 May '08

02 May '08

Respected Sir............ My name is prabhu working in one of the software company in india. when i was trying to use arecord and aplay command in my console(fedora-2.6.11-1.1369_FC4) i am getting following report.... So please kindly describe me for solve this problem...i am newbie in linux... [root@localhost cards]# arecord ALSA lib conf.c:1578:(snd_config_load1) _toplevel_:56:23:No such file or directory ALSA lib conf.c:2821:(snd_config_hook_load) /etc/alsa/cards/aliases.conf may be old or corrupted: consider to remove or fix it ALSA lib conf.c:2684:(snd_config_hooks_call) function snd_config_hook_load returned error: No such file or directory ALSA lib pcm.c:1959:(snd_pcm_open_conf) Invalid type for PCM default definition (id: default, value: cards.pcm.default) arecord: main:564: audio open error: Invalid argument [root@localhost cards]# Thanks &b Regards Prabhu P

1 0

[alsa-devel] help with idt 92hd206 codec for intel hda?
by Greg Zornetzer 02 May '08

02 May '08

Hi all, I recently acquired an ECS GF7100PVT-M3 motherboard, which appears to use the IDT 92HD206 codec for HDA. Unfortunately, it doesn't appear to have full support under ALSA. It gets detected as another Sigmatel chip. Analog stereo output appears to work, but the mixer doesn't find any of the normal inputs. I found the tech specs for the chip at http://www.idt.com/products/getDoc.cfm?docID=13461840 I've attached an lspci output and the codec file to this email. I'm not much of an driver hacker, but if someone could give me an idea of what needs to go into the patch_sigmatel.c file to make this thing work, I'd be willing to try. I'm also more than willing to test out patches on my setup. Thanks in advance for your help. -Greg

4 11

[alsa-devel] When turning up the volume, the sound dies and I'm forced to reboot...
by Sean Thayne 02 May '08

02 May '08

Hi All, I've got a via8237 audio card, and I'm using the latest alsa driver via82xx, and I got a problem. Basically if I start playing say a music file, and then turn the volume up above 75%, My sound craps out and I get a muffled, very low volume version of the song, the only way I've found to fix this is to reboot. This also happens randomly at low volume. I thought it might be a hardware issue, but I've tried it on 3 other boxes with the same card. Thanks for any input at all... -- Sean Thayne

2 1

[alsa-devel] How to support several sound cards using same driver?
by Cliff Cai 01 May '08

01 May '08

Hi all, I have a sound card which has 8 DAC/ADC pairs,and each DAC/ADC pair can be seen as an independent sub-card.An 8-slot buffer struct is introduced to feed/get data to/from one of the 8 sub-cards.For example,if an application wants to play muic using No.7 sub-card,the driver only need to copy the pcm data from PCM layer to No.7 slot and fill the other 7 slots with zero.The driver has been implemented. The problem is how to expose the 8 sub-cards to application developers,so they can see 8 independent device nodesunder /dev?They should be /dev/dsp0,/dev/dsp1,.../dev/dsp7 and card0,card1,...card7.Also when a sub-card is opened(i.e. /dev/dsp7),the driver must know the sub-card's index ,here is 7,so it can choose a relevant slot to feed/get data. Any suggestion is appreciated! Best Regards Cliff _________________________________________________________________ 新年换新颜，快来妆扮自己的MSN给心仪的TA一个惊喜！ http://im.live.cn/emoticons/?ID=18

1 0

[alsa-devel] How to support several cards using the same driver?
by Cliff Cai 01 May '08

01 May '08

Hi all, I have a sound card which has 8 DAC/ADC pairs,and each DAC/ADC pair can be seen as an independent sub-card. An 8-slot buffer struct is introduced to feed/get data to/from the 8 sub-cards.For example, if an application wants to play music using No.x(x,from 0 to 7) sub-card,the driver only need to copy the data from pcm layer to NO.x slot in the buffer struct and fill the other 7 slots with zero. The driver has been implemented now. The problem is how to expose the 8 sub-cards to application,So the application developer can see 8 independant device nodes under /dev.Those are /dev/dsp0,/dev/dsp1,...dev/dsp7(for oss emulation) or card0,card1...card7(for alsa).When one sub-card is opened the driver need to get the index of the sub-card,so it can feed/get data to/from the relevant slot.For example ,if an application opens /dev/dsp7, then the index "7" can be seen by the driver,and the driver know that No.7 slot will be used. Have I made myself clear?Any suggestion is appreciated! Best Regards Cliff . _________________________________________________________________ 多个邮箱同步管理，live mail客户端万人抢用中 http://get.live.cn/product/mail.html

1 0