From: Stephen Kitchener <stephen@g6dzj.demon.co.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: System beeper - no sound from mobo's own speaker
Date: Sun, 23 Jan 2005 19:37:53 +0000 [thread overview]
Message-ID: <200501231937.53099.stephen@g6dzj.demon.co.uk> (raw)
Hi,
I seem to have a problem that, in that when I am using the kernel supplied
with Mandrake 10.0 and 10.1 and also fedora 3, there seems to be a distinct
lack of beeps coming from the system, once it is up and running. I am NOT
talking about sounds that might be coming from any sound card that might be
connected to the system, but the plain old speaker that sits in the PC case.
This, to my mind, is not very usefull for a server or a laptop that might
generate system beeps, ie inserting a wifi card for instance on a laptop.
As I'm running Mandrake I have posted this to them, but as of yet I have had
no responce or reaction. I did do a search and I found at least one user of
Redhat reporting the same sort of problem, so I am guessing that it's not a
problem that is of Mandrakes doing, ie they forgot to include it in the
kernel that they bult for their distribution.
I have installed the latest kernel from fedora 2.6.10, but that didn't change
things.
Please let me know if I have posted something that is a known problem, and
I'll shut up and wait for a new kernel to be release that has this fixed. I
cannot beleive that this has been missed in testing, but at the same time I
have no beeps at all from any of the 3 machines that I have tested and it has
been reported to me, by a friend that is running Mandrake 10.1, he is running
different hardware, and can confirm that it was working before the upgrade.
The only common thing before we changed as that we were both running 2.4
kernels.
I can supply details of hardware if wanted.
--
O o
_\_ o
\\/ o\ .
//\___=
''
Sun, 23 Jan 2005 18:58:38 +0000
18:58:38 up 9:13, 0 users, load average: 1.30, 1.15, 1.05
Basic Definitions of Science:
If it's green or wiggles, it's biology.
If it stinks, it's chemistry.
If it doesn't work, it's physics.
next reply other threads:[~2005-01-23 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 19:37 Stephen Kitchener [this message]
2005-01-23 19:50 ` Sergey Vlasov
2005-01-23 20:07 ` Stephen Kitchener
2005-01-23 21:58 ` Anssi Hannula
2005-01-24 18:55 ` Stephen Kitchener
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=200501231937.53099.stephen@g6dzj.demon.co.uk \
--to=stephen@g6dzj.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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®