From: Stephen Kitchener <stephen@g6dzj.demon.co.uk>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: System beeper - no sound from mobo's own speaker
Date: Sun, 23 Jan 2005 20:07:21 +0000 [thread overview]
Message-ID: <200501232007.21027.stephen@g6dzj.demon.co.uk> (raw)
In-Reply-To: <20050123225010.0172a6e0.vsu@altlinux.ru>
On Sunday 23 Jan 2005 19:50, Sergey Vlasov wrote:
Hi Sergey,
You know - I've just found that and yes it does help on one system, so I'm 50%
better off - just need to find out where to put the command so that it loads
it on startup...modules.conf would be it I guess.
Thanks for quick reply.
Steve
> On Sun, 23 Jan 2005 19:37:53 +0000 Stephen Kitchener wrote:
> > 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.
>
> Does "modprobe pcspkr" help? In 2.6.x kernels the PC speaker support
> can be built as a loadable module; probably the startup scripts do not
> load it automatically.
--
O o
_\_ o
\\/ o\ .
//\___=
''
Sun, 23 Jan 2005 20:04:43 +0000
20:04:43 up 10:19, 0 users, load average: 1.24, 1.14, 1.10
The crying baby on board your flight is always seated next to you
-- Murphy's Laws for Frequent Flyers n°8
next prev parent reply other threads:[~2005-01-23 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 19:37 Stephen Kitchener
2005-01-23 19:50 ` Sergey Vlasov
2005-01-23 20:07 ` Stephen Kitchener [this message]
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=200501232007.21027.stephen@g6dzj.demon.co.uk \
--to=stephen@g6dzj.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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®