Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Naranjo <manuel@aircable.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Mute Beep (was Regression on alsa-driver-1.0.18a on HDA for Dell Inspiron 1521)
Date: Fri, 14 Nov 2008 10:34:16 -0200	[thread overview]
Message-ID: <491D7048.9070401@aircable.net> (raw)
In-Reply-To: <s5hiqqqk895.wl%tiwai@suse.de>


> Could you check the debug messages with the patch below?
>
>
> thanks,
>
> Takash
Sure no problem. I'm not getting any GENERATE BEEP, or BEEP EVENT on 
dmesg, just the enable disable when I press the enable disable button. 
The switch reflects the correct state.

I've gone through the patch over and over, but I can't figure out why 
would it stop working. Shouldn't the switch alert the beep part about 
changes?

Also how should I test? I tried with 'echo -e "\\a"', beep and the old 
way that was driving me crazy (pressing del in pidgin when there's no 
more text).

Anyway here's the log just in case:
snd: Not freed snd_alloc_kmalloc = 18
snd: kmalloc(9) from f8ed1d9a not freed
snd: kmalloc(9) from f8ed1d9a not freed
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ALSA /home/manuel/tmp/alsa/alsa-driver/pci/hda/hda_codec.c:2596: 
hda_codec: model 'dell-m42' is selected
ALSA /home/manuel/tmp/alsa/alsa-driver/pci/hda/hda_codec.c:3312: 
autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0)
ALSA /home/manuel/tmp/alsa/alsa-driver/pci/hda/hda_codec.c:3316:    
speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA /home/manuel/tmp/alsa/alsa-driver/pci/hda/hda_codec.c:3320:    
hp_outs=1 (0xa/0x0/0x0/0x0/0x0)
ALSA /home/manuel/tmp/alsa/alsa-driver/pci/hda/hda_codec.c:3321:    
mono: mono_out=0x0
ALSA /home/manuel/tmp/alsa/alsa-driver/pci/hda/hda_codec.c:3329:    
inputs: mic=0xb, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0
ALSA 
/home/manuel/tmp/alsa/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2786: 
dac_nids=1 (0x10/0x0/0x0/0x0/0x0)
input: HDA Digital PCBeep as /class/input/input18
input: HDA ATI SB at 0xfebfc000 irq 16 Mic at Ext Left Jack as 
/class/input/input19
input: HDA ATI SB at 0xfebfc000 irq 16 HP Out at Ext Left Jack as 
/class/input/input20
hda-intel: Invalid position buffer, using LPIB read method instead.
XXX BEEP SW 0
XXX BEEP SW 1

      reply	other threads:[~2008-11-14 12:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 14:06 Regression on alsa-driver-1.0.18a on HDA for Dell Inspiron 1521 Manuel Naranjo
2008-11-12 14:08 ` Takashi Iwai
     [not found]   ` <491AE4D5.9000004@aircable.net>
2008-11-12 14:17     ` Takashi Iwai
2008-11-12 14:22   ` Manuel Naranjo
2008-11-12 19:05   ` Ozan Çağlayan
2008-11-13  7:41     ` Takashi Iwai
2008-11-12 14:11 ` Manuel Naranjo
2008-11-12 14:15   ` Takashi Iwai
2008-11-12 14:28     ` Manuel Naranjo
2008-11-12 14:57       ` Takashi Iwai
2008-11-12 15:04         ` Jaroslav Kysela
2008-11-12 15:06           ` Takashi Iwai
2008-11-12 18:52             ` Mute Beep (was Regression on alsa-driver-1.0.18a on HDA for Dell Inspiron 1521) Manuel Naranjo
2008-11-13 12:03               ` Takashi Iwai
2008-11-13 14:44                 ` Takashi Iwai
2008-11-14  2:16                   ` Manuel Naranjo
2008-11-14  8:43                     ` Takashi Iwai
2008-11-14 12:34                       ` Manuel Naranjo [this message]

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=491D7048.9070401@aircable.net \
    --to=manuel@aircable.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox