public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing	Beep
Date: Thu, 29 Jul 2010 11:15:17 +0200	[thread overview]
Message-ID: <20100729091517.GA8902@darkside.kls.lan> (raw)
In-Reply-To: <s5h39v2acvf.wl%tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Thu, Jul 29, 2010 at 10:52:36AM +0200, Takashi Iwai wrote:
> Usually the codec SSID isn't checked in other places, so passing a
> bogus value should be OK.  Pass a value like 2:

Mh, 1 probably :)

$ cat /etc/modprobe.d/local-alsa.conf 
options snd-hda-intel model=asus-p5q
install snd-hda-intel /sbin/modprobe --ignore-install snd-hda-intel $CMDLINE_OPTS && { cd /sys/class/sound/hwC0D0; echo -n 1 > subsystem_id; echo -n 1 > reconfig; : ; }

Yep, Beep is back :)

Btw...

On Thu, Jul 29, 2010 at 10:26:22AM +0200, Takashi Iwai wrote:
> So, the fix is likely to override SSID value, or create a special
> quirk rule to enable PC-beep for known white-list, supposing BIOS
> won't be fixed in any future...

Well, the Board is from 2007, the last BIOS is from Aug 2009. I don't
think Asus will provide an update just for that :)


Thanks for your help
   Mario
-- 
Unfortunately, the chip vendors have delayed the availability of the
long-promised crystal-ball peripherals yet again, forcing the governor
code to rely on heuristics; once again, software must make up for
deficiencies in the hardware.                  -- Jonathan Corbet, LWN

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 482 bytes --]

  reply	other threads:[~2010-07-29  9:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 14:49 Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing Beep Mario 'BitKoenig' Holbe
2010-07-28 15:35 ` [alsa-devel] " Takashi Iwai
2010-07-28 16:03   ` Takashi Iwai
2010-07-28 21:27     ` Mario 'BitKoenig' Holbe
2010-07-29  5:44       ` Takashi Iwai
2010-07-29  8:09         ` Mario 'BitKoenig' Holbe
2010-07-29  8:26           ` Takashi Iwai
2010-07-29  8:41             ` Mario 'BitKoenig' Holbe
2010-07-29  8:52               ` Takashi Iwai
2010-07-29  9:15                 ` Mario 'BitKoenig' Holbe [this message]
2010-07-29  9:42                   ` Takashi Iwai
2010-07-29 13:25                     ` Mario 'BitKoenig' Holbe
2010-07-29 13:33                       ` Takashi Iwai

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=20100729091517.GA8902@darkside.kls.lan \
    --to=mario.holbe@tu-ilmenau.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.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