From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, Mikael Pettersson <mikpe@it.uu.se>,
linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [discuss] [RFC] make PC Speaker driver work on x86-64
Date: Sun, 30 Apr 2006 16:32:47 +0200 [thread overview]
Message-ID: <878xpnt9ps.fsf@informatik.uni-tuebingen.de> (raw)
In-Reply-To: <200604301046.22369.ak@suse.de> (Andi Kleen's message of "Sun, 30 Apr 2006 10:46:22 +0200")
Andi Kleen <ak@suse.de> writes:
> On Saturday 29 April 2006 20:30, Mikael Pettersson wrote:
>> I have a pair of Athlon64 machines that dual-boot 32-bit and
>> 64-bit kernels. One annoying difference between the kernels
>> is that the PC Speaker driver (CONFIG_INPUT_PCSPKR=y) only
>> works in the 32-bit kernels.
>
> Ah, I would consider this more a feature than a bug but ok :)
>
>> In the 64-bit kernels it remains
>> inactive and doesn't even generate any boot-time initialisation
>> or error messages.
That means that the system wouldn't beep on the console or when you
call "beep", right?
With 2.6.8 x86_64 that worked without problems. Since I updated to
2.6.15 the system is silent.
Could it be that this is a recent problem?
MfG
Goswin
next prev parent reply other threads:[~2006-04-30 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 18:30 Mikael Pettersson
2006-04-29 20:36 ` Jeff Garzik
2006-04-29 21:00 ` Matthieu CASTET
2006-04-30 8:50 ` [discuss] " Andi Kleen
2006-05-02 17:37 ` matthieu castet
2006-05-02 17:50 ` Andi Kleen
2006-05-02 20:33 ` matthieu castet
2006-05-02 20:35 ` Andi Kleen
2006-05-02 20:54 ` Andi Kleen
2006-04-30 8:46 ` [discuss] " Andi Kleen
2006-04-30 14:32 ` Goswin von Brederlow [this message]
2006-04-30 16:29 ` Alistair John Strachan
2006-05-01 7:09 ` Jan Engelhardt
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=878xpnt9ps.fsf@informatik.uni-tuebingen.de \
--to=brederlo@informatik.uni-tuebingen.de \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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
all inboxes | Powered by JetHome®