RE: 2.6.0 kernel compile overview

RE: 2.6.0 kernel compile overview

[EXT-Reimer, Jim D]

> 
> I can't find the reference right now, but I think step 3 
> should actually be 'make install' if you want to get a 
> compressed kernel image and System.map file moved to either / 
> or /boot (if you have edited the Makefile to install to 
> /boot).  If I am wrong, someone please correct me.
> 

Here's an "overviewish" page covering the process:
http://kerneltrap.org/node/view/799

-jdr-
-
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

RE: 2.6.0 kernel compile overview

[James Miller]

On Mon, 5 Jan 2004, EXT-Reimer, Jim D wrote:

> > 
> > I can't find the reference right now, but I think step 3 
> > should actually be 'make install' if you want to get a 
> > compressed kernel image and System.map file moved to either / 
> > or /boot (if you have edited the Makefile to install to 
> > /boot).  If I am wrong, someone please correct me.
> > 
> 
> Here's an "overviewish" page covering the process:
> http://kerneltrap.org/node/view/799
> 
Great link - thanks for providing it.  It's got just about all I need to 
proceed with this.

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

RE: 2.6.0 kernel compile overview-the unfolding saga

[James Miller]

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
# CONFIG_INPUT_UINPUT is not set

I looked through that file for other entries relevant to system speaker 
functioning, but nothing jumped out at me (not that I'd know what to make 
of it if it did).  I also searched a bit online for "system speaker" or 
"console beep", narrowed further by "2.6", but didn't find much helpful.  
As a next step, just to convince myself that there aren't maybe some 
issues regarding the system speaker using the 2.6 kernel, can I ask here 
if anyone using that kernel can get system speaker output?  echo -e "\a" - 
is the traditional command line way of making the system speaker sound.  
If you run this kernel and can report results of this command (or whatever 
else you might do to sound the system speaker), I would apreciate it.

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

RE: 2.6.0 kernel compile overview-the unfolding saga

[caszonyi]

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


> # CONFIG_INPUT_UINPUT is not set
>
> I looked through that file for other entries relevant to system speaker
> functioning, but nothing jumped out at me (not that I'd know what to make
> of it if it did).  I also searched a bit online for "system speaker" or
> "console beep", narrowed further by "2.6", but didn't find much helpful.
> As a next step, just to convince myself that there aren't maybe some
> issues regarding the system speaker using the 2.6 kernel, can I ask here
> if anyone using that kernel can get system speaker output?  echo -e "\a" -
> is the traditional command line way of making the system speaker sound.
> If you run this kernel and can report results of this command (or whatever
> else you might do to sound the system speaker), I would apreciate it.
>
> 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
>

--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
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

RE: 2.6.0 kernel compile overview-the unfolding saga

[James Miller]

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

RE: 2.6.0 kernel compile overview-the unfolding saga

[caszonyi]

On Mon, 5 Jan 2004, James Miller wrote:

> 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!).
>

yes it works. I had the same problem until i realised that i hadn't
CONFIG_INPUT_PCSPKR in my kernel
here is the relevant part from my config (comments stripped)

CONFIG_INPUT=y

CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768

CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y

CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y


> Thanks, James
> -


Calin
--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
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

Re: 2.6.0 kernel compile overview-the unfolding saga

[Theo. Sean Schulze]

Just a shot in the dark here, but do you have the volume turned up?  I am using the ALSA sound modules, and they, as default, start up with the sound muted.  I haven't gotten around to fixing it yet, so every time I reboot that machine, I have to reset the sound levels to something higher than zero.

On Mon, Jan 05, 2004 at 04:08:07PM -0600, James Miller hunted and pecked out:
> 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
> # CONFIG_INPUT_UINPUT is not set
> 
> I looked through that file for other entries relevant to system speaker 
> functioning, but nothing jumped out at me (not that I'd know what to make 
> of it if it did).  I also searched a bit online for "system speaker" or 
> "console beep", narrowed further by "2.6", but didn't find much helpful.  
> As a next step, just to convince myself that there aren't maybe some 
> issues regarding the system speaker using the 2.6 kernel, can I ask here 
> if anyone using that kernel can get system speaker output?  echo -e "\a" - 
> is the traditional command line way of making the system speaker sound.  
> If you run this kernel and can report results of this command (or whatever 
> else you might do to sound the system speaker), I would apreciate it.
> 
> 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

-- 
Theo. Sean Schulze
tschulze@teamfinders.org
-
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

Re: 2.6.0 kernel compile overview-the unfolding saga

[James Miller]

On Tue, 6 Jan 2004, Theo. Sean Schulze wrote:

> Just a shot in the dark here, but do you have the volume turned up?  I am using the ALSA sound modules, and they, as default, start up with the sound muted.  I haven't gotten around to fixing it yet, so every time I reboot that machine, I have to reset the sound levels to something higher than zero.
> 

And a brilliant shot in the dark it was!  I ran across, somewhere on the
web, the "alsamixer" command and even ran it (that's my kind of app -
colors and shapes in a console).  I saw "PCSpeaker" there, and even turned
up the volume, but that didn't get me any console beep.  Well, I just had
a look at it again after reading your post.  This time, I noted that
certain of the items listed there had an "off" flag by them - among these
the PCSpeaker.  I toggled that flag and - voila! - system speaker!  So, it
woiks, it woiks!  I just would never have guessed that alsa was something
that governs the PC's speaker - I thought that was a separate "low level"  
(however that parses out in my benighted understanding of these things)  
item.  Can anyone help clarify this for me?  Anyway, thanks to all for 
input on this - it's now fixed (provided the settings I did stick).

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

Re: 2.6.0 kernel compile overview-the unfolding saga

[caszonyi]

On Tue, 6 Jan 2004, James Miller wrote:

> On Tue, 6 Jan 2004, Theo. Sean Schulze wrote:
>
> > Just a shot in the dark here, but do you have the volume turned up?  I am using the ALSA sound modules, and they, as default, start up with the sound muted.  I haven't gotten around to fixing it yet, so every time I reboot that machine, I have to reset the sound levels to something higher than zero.
> >
>
> And a brilliant shot in the dark it was!  I ran across, somewhere on the
> web, the "alsamixer" command and even ran it (that's my kind of app -
> colors and shapes in a console).  I saw "PCSpeaker" there, and even turned
> up the volume, but that didn't get me any console beep.  Well, I just had
> a look at it again after reading your post.  This time, I noted that
> certain of the items listed there had an "off" flag by them - among these
> the PCSpeaker.  I toggled that flag and - voila! - system speaker!  So, it
> woiks, it woiks!  I just would never have guessed that alsa was something
> that governs the PC's speaker - I thought that was a separate "low level"
> (however that parses out in my benighted understanding of these things)
> item.  Can anyone help clarify this for me?  Anyway, thanks to all for
> input on this - it's now fixed (provided the settings I did stick).
>

It seems that some on-board sound controllers seem to be able to control
the pc speaker. At least at my work we have some windoz machines which
have this "feature"

> Thanks, James
> -

Calin

--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
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