kernel compilation

kernel compilation

[Cláudio Haase]

Hi all.
I have some questions:
Speakup can work with a linux kernel 2.4.4?
I'm using the braille and speak speech synthesizer.
After I compile the kernel with speakup, I recieve the
message "error in CRC system halted", when I reboot
the system.
I need a more detailed instructions of how to compile
the kernel with speakup, because I'm a inexperient in
kernel compilation.
I'm using slackware 7.1.
Can someone help me?

Thanks.


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

Re: kernel compilation

[Rich Caloggero]

I too will be taking on the task of patching a running linux. Any advice on
this would be greatly appreciated. I programmed in C on unix in the 80s, but
that ain't linux now!
Thanx from an almost novice.
                    Rich


----- Original Message -----
From: "ClXudio Haase" <claudiomh@yahoo.com>
To: <speakup@braille.uwo.ca>
Sent: 03 May, 2001 11:24 PM
Subject: kernel compilation



Hi all.
I have some questions:
Speakup can work with a linux kernel 2.4.4?
I'm using the braille and speak speech synthesizer.
After I compile the kernel with speakup, I recieve the
message "error in CRC system halted", when I reboot
the system.
I need a more detailed instructions of how to compile
the kernel with speakup, because I'm a inexperient in
kernel compilation.
I'm using slackware 7.1.
Can someone help me?

Thanks.


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: kernel compilation

[Kirk Reiser]

My guess is you may have forgotten to run lilo after putting your
kernel in place.  If not then you need to give us more information
about what you did, what version you were patching and errors/warnings
you got along the way.  It's kind of tough to help with a problem
without any information.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: Kernel Compilation

[ace]

Well, I got my sound card working; it seems as though I needed to compile 
the emu10k1 driver.  I went back in and installed it as a module.  I still 
can't find the PC speaker option in make menuconfig (if anyone knows where 
it is, I'd like to know) but that's no big deal.  I didn't find it where 
Alex suggested.


At 12:46 PM 1/10/2005, you wrote:
>One thing I did when compiling a kernel is copy my working config file to
>.config in the kernel source tree.  Obviously that won't work for 2.4 to 2.6
>kernels.  You may be able to get away with using a config from a pre-compiled
>kernel which is not modified and then using make altconfig with the patched
>kernel.  Really don't if that would work.Keep your working kernel around what
>ever you do.
>----- Original Message -----
>From: "ace" <ace@talkingirc.com>
>To: <speakup@braille.uwo.ca>
>Sent: Friday, January 07, 2005 11:58 PM
>Subject: Kernel Compilation
>
>
> > Hello,
> >
> > I am running Slackware version 10.0 freshly installed.  I have a few
> > questions.  I've installed Linux on a few older computers but did not have
> > the chance to really mess around with it bc those systems sucked.
> >
> > Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it
> > work with the latest 2.6.X kernel if I download it from kernel.org and
> > patched it with the latest Speakup sources?
> >
> > I have never successfully compiled a kernel before.  Last time, it was on
> > my friend's box and I severely screwed it.  What are the steps one must go
> > through to compile a kernel?  Must I pay attention to each individual
> > option that the configure script asks?  There are over hundreds it seems
> > and I can barely understand any of them.
> >
> > Thanks for any information.
> >
> > Robby
> >
> > Network Administrator of
> > irc.talkingirc.com
> > http://www.talkingirc.com
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Network Administrator of
irc.talkingirc.com
http://www.talkingirc.com 

Re: Kernel Compilation

[Sean McMahon]

One thing I did when compiling a kernel is copy my working config file to
.config in the kernel source tree.  Obviously that won't work for 2.4 to 2.6
kernels.  You may be able to get away with using a config from a pre-compiled
kernel which is not modified and then using make altconfig with the patched
kernel.  Really don't if that would work.Keep your working kernel around what
ever you do.
----- Original Message ----- 
From: "ace" <ace@talkingirc.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, January 07, 2005 11:58 PM
Subject: Kernel Compilation


> Hello,
>
> I am running Slackware version 10.0 freshly installed.  I have a few
> questions.  I've installed Linux on a few older computers but did not have
> the chance to really mess around with it bc those systems sucked.
>
> Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it
> work with the latest 2.6.X kernel if I download it from kernel.org and
> patched it with the latest Speakup sources?
>
> I have never successfully compiled a kernel before.  Last time, it was on
> my friend's box and I severely screwed it.  What are the steps one must go
> through to compile a kernel?  Must I pay attention to each individual
> option that the configure script asks?  There are over hundreds it seems
> and I can barely understand any of them.
>
> Thanks for any information.
>
> Robby
>
> Network Administrator of
> irc.talkingirc.com
> http://www.talkingirc.com
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Kernel Compilation

[ace]

Given these steps, is it necessary for me to type make install_modules 
after make modules?  In the README, it says:

  - If you configured any of the parts of the kernel as `modules', you
    will also have to do "make modules_install".

I'm not sure if it configures modules on its own or not, that's why I am 
asking.  Thanks.

At 10:42 AM 1/8/2005, you wrote:
>Hi there:
>I don't use Slackware, but I am sure you can compile the kernel for it.
>I compile the 2.6.x kernel all the time, so here are the steps and some
>notes about it.
>Firstable, you don't have to distroy your install when testing a new
>kernel.  You can install the new kernel and keep your old kernel also,
>so if your new kernel does not work, you can just reboot to your old
>one.  When you configure lilo or grub to boot your system, just leave
>your entry for the original kernel and add a new entry for the new
>kernel.
>
>Anyway, here is what you do:
>
>1. Patch the kernel from kernel.org with speakup and/or whatever else
>you need.
>
>2. from the kernel source directory (/usr/src/linux) type:
># make menuconfig
>As someone pointed out, this is a much nicer interface than, make
>config.
>3. After you are done configuring the kernel, type:
># make bzImage
>This will build the static part of the kernel.  You want to do this
>first, because if there are compilation problems in this part, there is
>no point in compiling the kernel modules.  The kernel modules usually
>take a lot longer to compile.
>
>4. Now build the modules:
># make modules
>
>5. If you did not get any errors, it is now time to install your kernel.
># cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.x.xx-whatever
># make modules_install
>
>6. Now, depending on your GNU/Linux distro, you might have to make a
>initrd image.  This can be very important, so you want to research this
>point.  Look in /boot on your system and look for something called
>initrd-2.4.xxx or something like that.
>
>7.  Now, configure your boot loader.  If it is lilo, don't forget to
>run:
># lilo
>after you edit the config file.  You should not get any errors from
>lilo.  If you do, then there is some kind of problem.
>
>Notes:
>
>1. If you want to clean your kernel source directory completely type:
># make mrproper
>You should do this before compiling your kernel again.  Important, make
>sure you make a copy of your .config file.  If you don't, you will have
>to do the entire configuration all over again.
>
>2. The 2.6.x kernels do not require the:
># make dep
>command for building them.  So, you don't need to use it.
>
>3. To have an idea of what configuration options to pick, look at the
>current configuration for your 2.4.x kernel.  You should not use the
>same .config file, but you should use it as a guide.  Just do a make
>menuconfig on the 2.4.x sources from your install and follow it as you
>configure the new kernel.
>
>4. I am not sure about this, but you might need to upgrade your modprobe
>and other module related utilities also.  As someone that knows or look
>it up on the web.
>
>5. Most important, don't give up, it can be done and it gets easier
>every time!
>
>
>David Bruzos
>
>On Sat, Jan 08, 2005 at 01:58:19AM -0500, ace wrote:
> > Hello,
> >
> > I am running Slackware version 10.0 freshly installed.  I have a few
> > questions.  I've installed Linux on a few older computers but did not have
> > the chance to really mess around with it bc those systems sucked.
> >
> > Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it
> > work with the latest 2.6.X kernel if I download it from kernel.org and
> > patched it with the latest Speakup sources?
> >
> > I have never successfully compiled a kernel before.  Last time, it was on
> > my friend's box and I severely screwed it.  What are the steps one must go
> > through to compile a kernel?  Must I pay attention to each individual
> > option that the configure script asks?  There are over hundreds it seems
> > and I can barely understand any of them.
> >
> > Thanks for any information.
> >
> > Robby
> >
> > Network Administrator of
> > irc.talkingirc.com
> > http://www.talkingirc.com
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Network Administrator of
irc.talkingirc.com
http://www.talkingirc.com 

Re: Kernel Compilation

[Chuck Hallenbeck]

Ace,

You have the arguments in the wrong order on your ln command. You want
the linux-2.6.10 to come before the linux argument. The way you did it
was asking that a symbolic link be created called "linux-2.6.10", and
you want your symbolic link to be called "linux".

Chuck


On Sun, 9 Jan 2005, ace wrote:

> How come when I perform the make mrproper command I get something like
> auc: cmd. line 2: fatal, cannot open file 
> /usr/src/linux-2.6.10/include/linux/version.h: for reading, no such file or 
> directory
> I made a symlink to /usr/src/linux-2.6.10 by typing
> ln -s linux linux-2.6.10
> in the /usr/src directory.  The symlink seems to be working fine bc I was 
> able to run checkout and patch the tree with Speakup successfully.
>
> Thanks
>
> At 11:25 AM 1/9/2005, you wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> I would like to add some additional comments about kernel
>> recompilation if possible.  I am currently using a 2.6.9 kernel on my
>> Slackware 10.0 settup here.
>> 
>> When untarring the kernel source from ftp.kernel.org, let it go ahead
>> and dump into linux-2.6.10 (or whatever version) into /usr/src.  in
>> Slackware /usr/src/linux is symbolicly linked to the current version
>> anyway.  The current configuration generated by a 'make menuconfig' is
>> .config built at the top of the linux source tree.  As suggested
>> earlier, I would copy this .config file into a safe place like your
>> personal home directory so it can be brought back in the next time you
>> do a kernel compile.  From what I've read in the README in linux-2.6
>> kernels, you only have to type 'make' to build kernel static source
>> and modules.  I just then do a separate 'make modules_install' when
>> I'm ready to install the modules for prime time use.  I also have a
>> couple simple shell scripts that copy the compiled kernel from the
>> ../../../boot directory of the kernel source tree over to the /boot
>> directory.  I also use lilo to maintain a separate boot label with
>> this kernel image and preserve one older one incase I break it.
>> 
>> Hope this helps.
>> 
>> - --
>> HolmesGrown Solutions
>> The best solutions for the best price!
>> http://ld.net/?holmesgrown
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>> 
>> iD8DBQFB4VrwWSjv55S0LfERAmIhAJ4r6TLDKPAwcs2o/yc3lU+dyEbFRwCePf6t
>> f7kVrPBs1UriBqv3BrQ40Ng=
>> =+UQV
>> -----END PGP SIGNATURE-----
>> 
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> Network Administrator of
> irc.talkingirc.com
> http://www.talkingirc.com 
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
The Moon is Waning Crescent (1% of Full)
"Things are in the saddle, and they ride mankind." Ralph Waldo Emerson
Personal site www.hhs48.com, Download site www.mhcable.com/~chuckh

Re: Kernel Compilation

[David Bruzos]

Hi:
You only do:
# make mrproper
after you have already compiled the kernel once.  This command just 
cleans all of the files generated when you last built your kernel.  So, 
yes, the command will output an error if the kernel source tree is 
already clean.  Remember to backup your .config file before doing the 
mrproper thing, or you will lose your entire configuration.

David Bruzos
On Sun, Jan 09, 2005 at 12:18:51PM -0500, ace wrote:
> How come when I perform the make mrproper command I get something like
> auc: cmd. line 2: fatal, cannot open file 
> /usr/src/linux-2.6.10/include/linux/version.h: for reading, no such file or 
> directory
> I made a symlink to /usr/src/linux-2.6.10 by typing
> ln -s linux linux-2.6.10
> in the /usr/src directory.  The symlink seems to be working fine bc I was 
> able to run checkout and patch the tree with Speakup successfully.
> 
> Thanks
> 
> At 11:25 AM 1/9/2005, you wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >I would like to add some additional comments about kernel
> >recompilation if possible.  I am currently using a 2.6.9 kernel on my
> >Slackware 10.0 settup here.
> >
> >When untarring the kernel source from ftp.kernel.org, let it go ahead
> >and dump into linux-2.6.10 (or whatever version) into /usr/src.  in
> >Slackware /usr/src/linux is symbolicly linked to the current version
> >anyway.  The current configuration generated by a 'make menuconfig' is
> >.config built at the top of the linux source tree.  As suggested
> >earlier, I would copy this .config file into a safe place like your
> >personal home directory so it can be brought back in the next time you
> >do a kernel compile.  From what I've read in the README in linux-2.6
> >kernels, you only have to type 'make' to build kernel static source
> >and modules.  I just then do a separate 'make modules_install' when
> >I'm ready to install the modules for prime time use.  I also have a
> >couple simple shell scripts that copy the compiled kernel from the
> >../../../boot directory of the kernel source tree over to the /boot
> >directory.  I also use lilo to maintain a separate boot label with
> >this kernel image and preserve one older one incase I break it.
> >
> >Hope this helps.
> >
> >- --
> >HolmesGrown Solutions
> >The best solutions for the best price!
> >http://ld.net/?holmesgrown
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.2.4 (GNU/Linux)
> >
> >iD8DBQFB4VrwWSjv55S0LfERAmIhAJ4r6TLDKPAwcs2o/yc3lU+dyEbFRwCePf6t
> >f7kVrPBs1UriBqv3BrQ40Ng=
> >=+UQV
> >-----END PGP SIGNATURE-----
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> Network Administrator of
> irc.talkingirc.com
> http://www.talkingirc.com 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Kernel Compilation

[ace]

How come when I perform the make mrproper command I get something like
auc: cmd. line 2: fatal, cannot open file 
/usr/src/linux-2.6.10/include/linux/version.h: for reading, no such file or 
directory
I made a symlink to /usr/src/linux-2.6.10 by typing
ln -s linux linux-2.6.10
in the /usr/src directory.  The symlink seems to be working fine bc I was 
able to run checkout and patch the tree with Speakup successfully.

Thanks

At 11:25 AM 1/9/2005, you wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>I would like to add some additional comments about kernel
>recompilation if possible.  I am currently using a 2.6.9 kernel on my
>Slackware 10.0 settup here.
>
>When untarring the kernel source from ftp.kernel.org, let it go ahead
>and dump into linux-2.6.10 (or whatever version) into /usr/src.  in
>Slackware /usr/src/linux is symbolicly linked to the current version
>anyway.  The current configuration generated by a 'make menuconfig' is
>.config built at the top of the linux source tree.  As suggested
>earlier, I would copy this .config file into a safe place like your
>personal home directory so it can be brought back in the next time you
>do a kernel compile.  From what I've read in the README in linux-2.6
>kernels, you only have to type 'make' to build kernel static source
>and modules.  I just then do a separate 'make modules_install' when
>I'm ready to install the modules for prime time use.  I also have a
>couple simple shell scripts that copy the compiled kernel from the
>../../../boot directory of the kernel source tree over to the /boot
>directory.  I also use lilo to maintain a separate boot label with
>this kernel image and preserve one older one incase I break it.
>
>Hope this helps.
>
>- --
>HolmesGrown Solutions
>The best solutions for the best price!
>http://ld.net/?holmesgrown
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.4 (GNU/Linux)
>
>iD8DBQFB4VrwWSjv55S0LfERAmIhAJ4r6TLDKPAwcs2o/yc3lU+dyEbFRwCePf6t
>f7kVrPBs1UriBqv3BrQ40Ng=
>=+UQV
>-----END PGP SIGNATURE-----
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Network Administrator of
irc.talkingirc.com
http://www.talkingirc.com 

Re: Kernel Compilation

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I would like to add some additional comments about kernel
recompilation if possible.  I am currently using a 2.6.9 kernel on my
Slackware 10.0 settup here.

When untarring the kernel source from ftp.kernel.org, let it go ahead
and dump into linux-2.6.10 (or whatever version) into /usr/src.  in
Slackware /usr/src/linux is symbolicly linked to the current version
anyway.  The current configuration generated by a 'make menuconfig' is
.config built at the top of the linux source tree.  As suggested
earlier, I would copy this .config file into a safe place like your
personal home directory so it can be brought back in the next time you
do a kernel compile.  From what I've read in the README in linux-2.6
kernels, you only have to type 'make' to build kernel static source
and modules.  I just then do a separate 'make modules_install' when
I'm ready to install the modules for prime time use.  I also have a
couple simple shell scripts that copy the compiled kernel from the
../../../boot directory of the kernel source tree over to the /boot
directory.  I also use lilo to maintain a separate boot label with
this kernel image and preserve one older one incase I break it.

Hope this helps.

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://ld.net/?holmesgrown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB4VrwWSjv55S0LfERAmIhAJ4r6TLDKPAwcs2o/yc3lU+dyEbFRwCePf6t
f7kVrPBs1UriBqv3BrQ40Ng=
=+UQV
-----END PGP SIGNATURE-----

Re: Kernel Compilation

[ace]

I don't understand exactly how the menuconfig works.  Do I just arrow to 
each option, press y/n, then arrow down to the next one and repeat the 
process?  It seems a little confusing.  Also, is it necessary for me to go 
through every setting?  My last kernel was speakup.s from the Slackware 
distro; this probably used default settings.  Can't I just accept what make 
menuconfig gives me and just close the config and save it?  One more 
question: where in this menuconfig may I find the Speakup 
configuration?  That's really all I care about altering.

Thanks
Robby
At 12:15 PM 1/8/2005, you wrote:
>yeah. what you could also do is rename your current kernel
>/boot/vmlinuz to something like /boot/vmlinuz-2.4 and make the new
>kernel vmlinuz-2.6. then you could configure your lilo.conf so you
>have two configurations. one for 2.4 and 1 for 2.6. therefore if 2.6
>doesnt work you can always boot 2.4.
>so after you run make modules_install do cp arch/i386/boot/bzImage
>/boot/vmlinuz-2.6, then edit your lilo.conf and rerun lilo.
>On Sat, Jan
>08, 2005 at 12:00:49PM -0500, ace wrote:
> > Thanks, Alex.  Now, what all should be backed up before I install a new
> > kernel?  Would I be fine if I just back up /boot?
> >
> >
> > At 09:12 AM 1/8/2005, you wrote:
> > >Hi.
> > >Yes slackware 10.0 is full 2.6 ready. the latest 2.6 kernel (2.6.10 I
> > >think) should run fine.
> > >
> > >The way I usually configure kernels is with make menuconfig. That's a
> > >much nicer interface then make config. just go through each catigory
> > >and make sure what you need is selected. much easier then answering
> > >all those questions from make config. so the steps you follow after
> > >patching speakup in (I assume you know how to do this) are:
> > >cd /usr/src/linux
> > >make mrproper
> > >make menuconfig
> > >make dep
> > >make modules
> > >make bzImage
> > >make modules_install.
> > >On Sat, Jan
> > >08, 2005 at 01:58:19AM -0500, ace wrote:
> > >> Hello,
> > >>
> > >> I am running Slackware version 10.0 freshly installed.  I have a few
> > >> questions.  I've installed Linux on a few older computers but did not
> > >have
> > >> the chance to really mess around with it bc those systems sucked.
> > >>
> > >> Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it
> > >> work with the latest 2.6.X kernel if I download it from kernel.org and
> > >> patched it with the latest Speakup sources?
> > >>
> > >> I have never successfully compiled a kernel before.  Last time, it 
> was on
> > >> my friend's box and I severely screwed it.  What are the steps one must
> > >go
> > >> through to compile a kernel?  Must I pay attention to each individual
> > >> option that the configure script asks?  There are over hundreds it seems
> > >> and I can barely understand any of them.
> > >>
> > >> Thanks for any information.
> > >>
> > >> Robby
> > >>
> > >> Network Administrator of
> > >> irc.talkingirc.com
> > >> http://www.talkingirc.com
> > >>
> > >>
> > >> _______________________________________________
> > >> Speakup mailing list
> > >> Speakup@braille.uwo.ca
> > >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >--
> > >Look, I'm about to buy me a double barreled sawed off shotgun and show
> > >Linus what I think about backspace and delete not working.
> > >        -- some anonymous .signature
> > >
> > >_______________________________________________
> > >Speakup mailing list
> > >Speakup@braille.uwo.ca
> > >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > Network Administrator of
> > irc.talkingirc.com
> > http://www.talkingirc.com
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>--
> > > Other than the fact Linux has a cool name, could someone explain why I
> > > should use Linux over BSD?
> >
> > No.  That's it.  The cool name, that is.  We worked very hard on
> > creating a name that would appeal to the majority of people, and it
> > certainly paid off: thousands of people are using linux just to be able
> > to say "OS/2? Hah.  I've got Linux.  What a cool name".  386BSD made the
> > mistake of putting a lot of numbers and weird abbreviations into the
> > name, and is scaring away a lot of people just because it sounds too
> > technical.
>         -- Linus Torvalds' follow-up to a question about Linux
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Network Administrator of
irc.talkingirc.com
http://www.talkingirc.com 

Re: Kernel Compilation

[Alex Snow]

yeah. what you could also do is rename your current kernel 
/boot/vmlinuz to something like /boot/vmlinuz-2.4 and make the new 
kernel vmlinuz-2.6. then you could configure your lilo.conf so you 
have two configurations. one for 2.4 and 1 for 2.6. therefore if 2.6 
doesnt work you can always boot 2.4.
so after you run make modules_install do cp arch/i386/boot/bzImage 
/boot/vmlinuz-2.6, then edit your lilo.conf and rerun lilo.
On Sat, Jan 
08, 2005 at 12:00:49PM -0500, ace wrote:
> Thanks, Alex.  Now, what all should be backed up before I install a new 
> kernel?  Would I be fine if I just back up /boot?
> 
> 
> At 09:12 AM 1/8/2005, you wrote:
> >Hi.
> >Yes slackware 10.0 is full 2.6 ready. the latest 2.6 kernel (2.6.10 I
> >think) should run fine.
> >
> >The way I usually configure kernels is with make menuconfig. That's a
> >much nicer interface then make config. just go through each catigory
> >and make sure what you need is selected. much easier then answering
> >all those questions from make config. so the steps you follow after
> >patching speakup in (I assume you know how to do this) are:
> >cd /usr/src/linux
> >make mrproper
> >make menuconfig
> >make dep
> >make modules
> >make bzImage
> >make modules_install.
> >On Sat, Jan
> >08, 2005 at 01:58:19AM -0500, ace wrote:
> >> Hello,
> >>
> >> I am running Slackware version 10.0 freshly installed.  I have a few
> >> questions.  I've installed Linux on a few older computers but did not 
> >have
> >> the chance to really mess around with it bc those systems sucked.
> >>
> >> Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it
> >> work with the latest 2.6.X kernel if I download it from kernel.org and
> >> patched it with the latest Speakup sources?
> >>
> >> I have never successfully compiled a kernel before.  Last time, it was on
> >> my friend's box and I severely screwed it.  What are the steps one must 
> >go
> >> through to compile a kernel?  Must I pay attention to each individual
> >> option that the configure script asks?  There are over hundreds it seems
> >> and I can barely understand any of them.
> >>
> >> Thanks for any information.
> >>
> >> Robby
> >>
> >> Network Administrator of
> >> irc.talkingirc.com
> >> http://www.talkingirc.com
> >>
> >>
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@braille.uwo.ca
> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >--
> >Look, I'm about to buy me a double barreled sawed off shotgun and show
> >Linus what I think about backspace and delete not working.
> >        -- some anonymous .signature
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> Network Administrator of
> irc.talkingirc.com
> http://www.talkingirc.com 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
> > Other than the fact Linux has a cool name, could someone explain why I
> > should use Linux over BSD?
>
> No.  That's it.  The cool name, that is.  We worked very hard on
> creating a name that would appeal to the majority of people, and it
> certainly paid off: thousands of people are using linux just to be able
> to say "OS/2? Hah.  I've got Linux.  What a cool name".  386BSD made the
> mistake of putting a lot of numbers and weird abbreviations into the
> name, and is scaring away a lot of people just because it sounds too
> technical.
	-- Linus Torvalds' follow-up to a question about Linux

Re: Kernel Compilation

[ace]

Thanks, Alex.  Now, what all should be backed up before I install a new 
kernel?  Would I be fine if I just back up /boot?


At 09:12 AM 1/8/2005, you wrote:
>Hi.
>Yes slackware 10.0 is full 2.6 ready. the latest 2.6 kernel (2.6.10 I
>think) should run fine.
>
>The way I usually configure kernels is with make menuconfig. That's a
>much nicer interface then make config. just go through each catigory
>and make sure what you need is selected. much easier then answering
>all those questions from make config. so the steps you follow after
>patching speakup in (I assume you know how to do this) are:
>cd /usr/src/linux
>make mrproper
>make menuconfig
>make dep
>make modules
>make bzImage
>make modules_install.
>On Sat, Jan
>08, 2005 at 01:58:19AM -0500, ace wrote:
> > Hello,
> >
> > I am running Slackware version 10.0 freshly installed.  I have a few
> > questions.  I've installed Linux on a few older computers but did not have
> > the chance to really mess around with it bc those systems sucked.
> >
> > Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it
> > work with the latest 2.6.X kernel if I download it from kernel.org and
> > patched it with the latest Speakup sources?
> >
> > I have never successfully compiled a kernel before.  Last time, it was on
> > my friend's box and I severely screwed it.  What are the steps one must go
> > through to compile a kernel?  Must I pay attention to each individual
> > option that the configure script asks?  There are over hundreds it seems
> > and I can barely understand any of them.
> >
> > Thanks for any information.
> >
> > Robby
> >
> > Network Administrator of
> > irc.talkingirc.com
> > http://www.talkingirc.com
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>--
>Look, I'm about to buy me a double barreled sawed off shotgun and show
>Linus what I think about backspace and delete not working.
>         -- some anonymous .signature
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Network Administrator of
irc.talkingirc.com
http://www.talkingirc.com 

Re: Kernel Compilation

[David Bruzos]

Hi there:
I don't use Slackware, but I am sure you can compile the kernel for it.  
I compile the 2.6.x kernel all the time, so here are the steps and some 
notes about it.
Firstable, you don't have to distroy your install when testing a new 
kernel.  You can install the new kernel and keep your old kernel also, 
so if your new kernel does not work, you can just reboot to your old 
one.  When you configure lilo or grub to boot your system, just leave 
your entry for the original kernel and add a new entry for the new 
kernel.

Anyway, here is what you do:

1. Patch the kernel from kernel.org with speakup and/or whatever else 
you need.

2. from the kernel source directory (/usr/src/linux) type:
# make menuconfig
As someone pointed out, this is a much nicer interface than, make 
config.
3. After you are done configuring the kernel, type:
# make bzImage
This will build the static part of the kernel.  You want to do this 
first, because if there are compilation problems in this part, there is 
no point in compiling the kernel modules.  The kernel modules usually 
take a lot longer to compile.

4. Now build the modules:
# make modules

5. If you did not get any errors, it is now time to install your kernel.
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.x.xx-whatever
# make modules_install

6. Now, depending on your GNU/Linux distro, you might have to make a 
initrd image.  This can be very important, so you want to research this 
point.  Look in /boot on your system and look for something called 
initrd-2.4.xxx or something like that.

7.  Now, configure your boot loader.  If it is lilo, don't forget to 
run:
# lilo
after you edit the config file.  You should not get any errors from 
lilo.  If you do, then there is some kind of problem.

Notes:

1. If you want to clean your kernel source directory completely type:
# make mrproper
You should do this before compiling your kernel again.  Important, make 
sure you make a copy of your .config file.  If you don't, you will have 
to do the entire configuration all over again.

2. The 2.6.x kernels do not require the:
# make dep
command for building them.  So, you don't need to use it.

3. To have an idea of what configuration options to pick, look at the 
current configuration for your 2.4.x kernel.  You should not use the 
same .config file, but you should use it as a guide.  Just do a make 
menuconfig on the 2.4.x sources from your install and follow it as you 
configure the new kernel.

4. I am not sure about this, but you might need to upgrade your modprobe 
and other module related utilities also.  As someone that knows or look 
it up on the web.

5. Most important, don't give up, it can be done and it gets easier 
every time!


David Bruzos

On Sat, Jan 08, 2005 at 01:58:19AM -0500, ace wrote:
> Hello,
> 
> I am running Slackware version 10.0 freshly installed.  I have a few 
> questions.  I've installed Linux on a few older computers but did not have 
> the chance to really mess around with it bc those systems sucked.
> 
> Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it 
> work with the latest 2.6.X kernel if I download it from kernel.org and 
> patched it with the latest Speakup sources?
> 
> I have never successfully compiled a kernel before.  Last time, it was on 
> my friend's box and I severely screwed it.  What are the steps one must go 
> through to compile a kernel?  Must I pay attention to each individual 
> option that the configure script asks?  There are over hundreds it seems 
> and I can barely understand any of them.
> 
> Thanks for any information.
> 
> Robby
> 
> Network Administrator of
> irc.talkingirc.com
> http://www.talkingirc.com 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Kernel Compilation

[Alex Snow]

Hi.
Yes slackware 10.0 is full 2.6 ready. the latest 2.6 kernel (2.6.10 I 
think) should run fine.

The way I usually configure kernels is with make menuconfig. That's a 
much nicer interface then make config. just go through each catigory 
and make sure what you need is selected. much easier then answering 
all those questions from make config. so the steps you follow after 
patching speakup in (I assume you know how to do this) are:
cd /usr/src/linux
make mrproper
make menuconfig
make dep
make modules
make bzImage
make modules_install.
On Sat, Jan 
08, 2005 at 01:58:19AM -0500, ace wrote:
> Hello,
> 
> I am running Slackware version 10.0 freshly installed.  I have a few 
> questions.  I've installed Linux on a few older computers but did not have 
> the chance to really mess around with it bc those systems sucked.
> 
> Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it 
> work with the latest 2.6.X kernel if I download it from kernel.org and 
> patched it with the latest Speakup sources?
> 
> I have never successfully compiled a kernel before.  Last time, it was on 
> my friend's box and I severely screwed it.  What are the steps one must go 
> through to compile a kernel?  Must I pay attention to each individual 
> option that the configure script asks?  There are over hundreds it seems 
> and I can barely understand any of them.
> 
> Thanks for any information.
> 
> Robby
> 
> Network Administrator of
> irc.talkingirc.com
> http://www.talkingirc.com 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
Look, I'm about to buy me a double barreled sawed off shotgun and show
Linus what I think about backspace and delete not working.
	-- some anonymous .signature

Kernel Compilation

[ace]

Hello,

I am running Slackware version 10.0 freshly installed.  I have a few 
questions.  I've installed Linux on a few older computers but did not have 
the chance to really mess around with it bc those systems sucked.

Firstly, I am aware that Slackware 10 comes with kernel 2.4.26.  Will it 
work with the latest 2.6.X kernel if I download it from kernel.org and 
patched it with the latest Speakup sources?

I have never successfully compiled a kernel before.  Last time, it was on 
my friend's box and I severely screwed it.  What are the steps one must go 
through to compile a kernel?  Must I pay attention to each individual 
option that the configure script asks?  There are over hundreds it seems 
and I can barely understand any of them.

Thanks for any information.

Robby

Network Administrator of
irc.talkingirc.com
http://www.talkingirc.com