From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: RE: 2.6.0 kernel compile overview-the unfolding saga
Date: Mon, 5 Jan 2004 16:49:45 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.58.0401051644080.3636@localhost> (raw)
In-Reply-To: <Pine.LNX.4.53.0401060016240.842@grinch.ro>
On Tue, 6 Jan 2004 caszonyi@rdslink.ro wrote:
> On Mon, 5 Jan 2004, James Miller wrote:
>
> > Ok. It turns out the system speaker is enabled in the .config file:
> >
> > # Input Device Drivers
> > #
> > CONFIG_INPUT_KEYBOARD=y
> > CONFIG_KEYBOARD_ATKBD=y
> > # CONFIG_KEYBOARD_SUNKBD is not set
> > # CONFIG_KEYBOARD_XTKBD is not set
> > # CONFIG_KEYBOARD_NEWTON is not set
> > CONFIG_INPUT_MOUSE=y
> > CONFIG_MOUSE_PS2=y
> > CONFIG_MOUSE_PS2_SYNAPTICS=y
> > # CONFIG_MOUSE_SERIAL is not set
> > # CONFIG_INPUT_JOYSTICK is not set
> > # CONFIG_INPUT_TOUCHSCREEN is not set
> > CONFIG_INPUT_MISC=y
> > CONFIG_INPUT_PCSPKR=y
>
> this ^^^^^^^^^^^^^ makes the speeker beep :-)
> works for me :-)
>
> maybe you forgot to reinstall kernel.
> Or maybe the kernel build system got confused ?
>
> do a make clean and then a make bzImage to regenerate the kernel
>
Just to be clear, this *is* the config for the running kernel. I didn't
try any recompiling yet, not being sure if it would help since the speaker
seems already to be enabled in the kernel. In which case doing "make
clean" and "make bzImage" don't seem like they would make much difference,
as I understand it. So, you're saying that the console beep/system
speaker works fine on your system with the 2.6 kernel? If so, I'll
presume the problem lies in some peculiarity in my system (dang thing
worked fine under the 2.4.21 Gentoo used for the install!).
Thanks, James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-01-05 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 19:39 2.6.0 kernel compile overview EXT-Reimer, Jim D
2004-01-05 20:09 ` James Miller
2004-01-05 22:08 ` 2.6.0 kernel compile overview-the unfolding saga James Miller
2004-01-05 22:19 ` caszonyi
2004-01-05 22:49 ` James Miller [this message]
2004-01-05 23:12 ` caszonyi
2004-01-06 6:05 ` Theo. Sean Schulze
2004-01-06 14:42 ` James Miller
2004-01-06 20:56 ` caszonyi
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=Pine.LNX.4.58.0401051644080.3636@localhost \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@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