Re: kernel build issue

Re: kernel build issue

[tony seth]

While we're on the jubject, I have a kernel question too.  I'm 
currently running slackware 10.1 and a 2.4 kernel. I rolled my own 2.6 
kernel, and although it mostly went as it should, all my modules seem 
to have a .ko extention rather then the .o extention, and so, for 
example when my sound card loads I get an error that the version is 
incorrect.  How do I fix this, I'm sure I'm doing something wrong, or 
forgetting something obvious, but can't think what it is...
I tried it before and got everything to work before, but don't know I 
did differently. Any help appreciated... thanks much.
Cheereo!

-- 
Email services by FreedomBox.  Surf the Net at the sound of your voice. 
www.freedombox.info

RE: kernel build issue

[Adam Myrow]

2.6 uses ".ko" as the module extension.  You have to rebuild ALSA every time
you compile a new version of the kernel.  Alsa is in the 2.6.X kernels, so I
tend to prefer that version to building it from source every time.
 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of tony seth
Sent: Saturday, April 01, 2006 2:53 AM
To: speakup@braille.uwo.ca
Subject: Re: kernel build issue

While we're on the jubject, I have a kernel question too.  I'm currently
running slackware 10.1 and a 2.4 kernel. I rolled my own 2.6 kernel, and
although it mostly went as it should, all my modules seem to have a .ko
extention rather then the .o extention, and so, for example when my sound
card loads I get an error that the version is incorrect.  How do I fix this,
I'm sure I'm doing something wrong, or forgetting something obvious, but
can't think what it is...
I tried it before and got everything to work before, but don't know I did
differently. Any help appreciated... thanks much.
Cheereo!

--
Email services by FreedomBox.  Surf the Net at the sound of your voice. 
www.freedombox.info

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

Re: kernel build issue

[Gregory Nowak]

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

This isn't a problem. Under 2.6.x, modules now have a .ko extension
rather then a .o extension. To fix the problems you're having, you
want to do 

modprobe modulename

, instead of

modprobe modulename.o

, which is what you should have been doing under 2.4.x anyway.

Greg


On Sat, Apr 01, 2006 at 03:53:21AM -0500, tony seth wrote:
> While we're on the jubject, I have a kernel question too.  I'm 
> currently running slackware 10.1 and a 2.4 kernel. I rolled my own 2.6 
> kernel, and although it mostly went as it should, all my modules seem 
> to have a .ko extention rather then the .o extention, and so, for 
> example when my sound card loads I get an error that the version is 
> incorrect.  How do I fix this, I'm sure I'm doing something wrong, or 
> forgetting something obvious, but can't think what it is...
> I tried it before and got everything to work before, but don't know I 
> did differently. Any help appreciated... thanks much.
> Cheereo!
> 
> -- 
> Email services by FreedomBox.  Surf the Net at the sound of your voice. 
> www.freedombox.info
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFELs8E7s9z/XlyUyARAsziAKCltcCu1xN9EDFEJ1oo9dVU56TdRQCgtdsS
iReTIyQgbu1UKLSuFOU7bVk=
=mauw
-----END PGP SIGNATURE-----

Re: kernel build issue

[Kirk Reiser]

You also have to change your module loading utilities to a newer
version that knows how to deal with the new extensions.  In debian the
package is module-init-tools.  I don't know what it may be in other
distributions.

  Kirk

-- 

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

Re: kernel build issue

[Igor Gueths]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi. The name Module-init-tools is distribution independent; I learned this while building my LFS system.
On Sat, Apr 01, 2006 at 04:09:52PM -0500, Kirk Reiser wrote:
> You also have to change your module loading utilities to a newer
> version that knows how to deal with the new extensions.  In debian the
> package is module-init-tools.  I don't know what it may be in other
> distributions.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
Any society that would give up a little liberty to gain a little
   security will deserve neither and lose both.
- -- Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iQIVAwUBRC8Tzae2pgKIdGq4AQp2Lg/9G0vWJb+spkO2R8OPfsN8xwxbVX4P+mfb
iD6hDO2HhngqLVB+jPReBQ1EZsetIiyLqyPWBdlOFaoGGkTwd/0aM2ofGRnmar54
izpdbMfs62Xu+x0lkQM4xAeaZYpyUcIq0aJ7VjHiTdkyXMFZvfZOODJBMIMtnxT8
pJ0vXu6qpAHHG7UCCbfd3FCsK+sfRyP3IUkGcA/DHX9ChE+JVoGm8E7uiBZrqfQ7
0ACIRPEQokLlSuGfX0EkxmDpH+Dghu0lczqbsHi6OaaeeMiHbrMNLp4pWTYV4w5I
LGRkxc4QQnIpaqBlfNsLBFwNF449h/Eb2/DRuujjT0NoCvsTVSWQih0aDnaDQi5v
i3HdaNgTh4eQaSCT3ET5kotUA3QW9OCBraRJU1mN2TDfMSIWVqkyRGwjbVZiT5TT
txgObrTo6FFPGYKHsOuMQ5RpIrbeNPxr8LLPeQQY0Ad0HBzcCxcjlu1yG6OhlqBM
xrPW4MMY4qBvkCjX4FNVMEWpK8lP9I+Wnvealz5yHhApwaMRy5S8OxRVbQK/G4Lk
rEujrp79caFNeyuamY5/y+wdPKqr6WXwAgvbu1jwy4BtaleZo4tUNArilDXuOogg
Vy2iz0UaNByjn1R1iex5zNr2okqGsxcdopMhaeAX1kYcXCrodPhdDrSFEnAblTC8
Yhu8aR7Id8g=
=t58r
-----END PGP SIGNATURE-----

kernel build issue

[Juan Hernandez]

                    Hello everyone,
I just installed fedora core 5, and am now building a speakup enabled
kernel.
I got the kernel source from
www.kernel.org
I ran the checkout script for speakup.
I then proceeded to configure my kernel.
version 2.6.16.1
Id did the following steps
in /usr/src/linux
make mrproper
make config
-- answered all of the questions
make
make modules
make modules install
on make modules install, I got the following errors:
my version of speakup is cvs checkout date: 3/30/2006
CC      drivers/char/speakup/speakup.o
drivers/char/speakup/speakup.c: In function
speakup_bits':
drivers/char/speakup/speakup.c:2421: error:
pb_edit' undeclared (first use in this function)
drivers/char/speakup/speakup.c:2421: error: (Each undeclared identifier
is reported only once
drivers/char/speakup/speakup.c:2421: error: for each function it appears
in.)
drivers/char/speakup/speakup.c:2424: error:
edit_bits' undeclared (first use in this function)
make[3]: *** [drivers/char/speakup/speakup.o] Error 1
make[2]: *** [drivers/char/speakup] Error 2
make[1]: *** [drivers/char] Error 2
Can someone please help me?
I would greatly appreciate it.
Thanks

Re: kernel build issue

[Kirk Reiser]

Hello Juan:  I am not sure why you are getting those errors exactly.
The variable it is complaining about in your code snip is declared
global further up in speakup.c.  There are a couple of other points
though I'd like to make because they sound strange after the way you
listed the commands you used to compile.  In 2.6.xx kernels you only
need run make after the configuration stage.  It also compiles the
modules.  Make modules_install is one word with an underscore in it so
what you ran would have attempted to make the modules after it had
already made them and then tried to install I don't know what if that
had succeeded.  You should have got that error when you just ran the
make command so I am quite confused.  Did you save the output to the
entire process?

I think What I would suggest is you run make clean and try again from
scratch.  You won't need to redo the configuration stage which is the
worst part of the whole process.  Then compile it again and keep the
entire output with a command like this:

make >make.out 2>&1 &

This will compile the whole package and save all the output to the
file make.out.  If that completes with a done you're in good shap and
can go on to the next bit if not send me the make.out file.  You
should compile that first portion as yourself or a regular user
account.  The next bit:

make modules_install

You should run as root.  After that you have to put the kernel and
System.map in place and run lilo or just reboot if you're using grub.

good luck.
  Kirk

-- 

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