lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 14 May 2008 12:03:31 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Roberto Oppedisano <roberto.oppedisano@...racom.it>
Cc:	Stas Sergeev <stsp@...et.ru>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Non-working snd-pcsp

At Wed, 14 May 2008 07:35:19 +0200,
Roberto Oppedisano wrote:
> 
> Hello.
> 
> Takashi Iwai wrote:
> > [Changed the subject since it's no real regression]
> >   
> ACK
> > Could you run "alsactl -f somefile store" and show that file?
> > This will contain the full mixer information.
> >   
> Attached.

You turned off both "Master Playback Switch" and "PC Speaker Playback
Switch" of snd-pcsp driver.  Then it cannot work.

And, since you loaded the sound driver for on-board sound chip, you'll
likely have to adjust the mixer of that driver, too.  The beep can be
hooked to the on-board chip once after initialized.

But I'm wondering why "PC Speaker Playback Switch" and Volume don't
appear in the on-board driver.  Which codec (I suppose it's AC97) on
it?


> >> With kmix I can toggle the mute setting (alsamixer still sees it off), but
> >> no sound comes out from the speaker.
> >> I also tried
> >>
> >> echo -e "\a"
> >>
> >> without the module loaded (on old kernel), and the speaker is mute.
> >>     
> > When snd-pcsp is built, the input pcspkr is excluded.  So, the beep
> > won't work unless snd-pcsp is loaded and activated.
> >   
> I tried this on 2.6.25 where:
> 
> roppedisano@...pero1:~$ grep PCSP /boot/config-2.6.25
> roppedisano@...pero1:~$
> 
> So, if I'm not missing something, I think it should have worked

Weird.  If CONFIG_INPUT_PCSPKR isn't there, the box shouldn't beep at
all.  If it still beeps, it must be a bug...


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ