RE: Kernel error

RE: Kernel error

[Shaun Bryant]

Richard,

I have had two kernel panics in the last 3 days which is why I was looking
in the syslog to find the problem. I ran the command you mentioned and got
the below results.

depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/char/drm/gamma.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/char/drm/i810.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/char/drm/mga.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/char/drm/r128.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/char/drm/radeon.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/i2o/i2o_lan.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/net/defxx.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/net/skfp/skfp.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_base.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_crtc2.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_g450.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_maven.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/net/ipv6/ipv6.o.gz
depmod: *** Unresolved symbols in
/lib/modules/2.4.5/kernel/net/khttpd/khttpd.o.gz

how would I fix the above problems?


Thanks
Shaun

-----Original Message-----
From: Richard Adams [mailto:pa3gcu@zeelandnet.nl]
Sent: Sunday, May 26, 2002 4:46 AM
To: Shaun Bryant; 'linux-newbie@vger.kernel.org'
Subject: Re: Kernel error


On Saturday 25 May 2002 19:54, Shaun Bryant wrote:
> Rich,
>
> Yes I did upgrade the kernel but the system.map seems to be the same date
> (see below). Is there a way to rebuild the system map?

Correct, they are the same timestamp, however to find out wht is wrong you 
could try 'depmod -a' to see if that results in "unresolved symbols".

Sometimes the error you mention is not to be worried about.

Are you having problems with one or other funtion which does not work like
it 
did in your last kernel.

>
> -rw-r--r--    1 root     root       659886 Mar 20 07:53 System.map
> -rw-r--r--    1 root     root       657708 Mar 20 06:42 System.old

> -rw-r--r--    1 root     root      1159361 Mar 20 07:53 vmlinuz
> -rw-r--r--    1 root     root      1154564 Mar 20 06:42 vmlinuz.old
>
> Shaun

--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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
-
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: Kernel error

[Richard Adams]

On Sunday 26 May 2002 14:57, Shaun Bryant wrote:
> Richard,
>
> I have had two kernel panics in the last 3 days which is why I was looking
> in the syslog to find the problem. I ran the command you mentioned and got
> the below results.

If you are having trouble with kernel panic's then i suggest you read;
/usr/src/linux/Documentation/oops-tracing.txt
too find out what is causing the oops'n.

To behonest i doubt if the errors below would cause one as modprobe will not 
load modules with errors like those, so if a module is NOT loaded it should 
NOT cause an oops should it.!.

What you possably did not do was follow the Kernel-HOWTO found in your 
/usr/doc or /usr/share/doc directory's.

>
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/gamma.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/i810.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/mga.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/r128.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/radeon.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/i2o/i2o_lan.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/net/defxx.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/net/skfp/skfp.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_base.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_crtc2.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_g450.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/video/matrox/matroxfb_maven.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/net/ipv6/ipv6.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/net/khttpd/khttpd.o.gz
>
> how would I fix the above problems?
>
>
> Thanks
> Shaun
>
> -----Original Message-----
> From: Richard Adams [mailto:pa3gcu@zeelandnet.nl]
> Sent: Sunday, May 26, 2002 4:46 AM
> To: Shaun Bryant; 'linux-newbie@vger.kernel.org'
> Subject: Re: Kernel error
>
> On Saturday 25 May 2002 19:54, Shaun Bryant wrote:
> > Rich,
> >
> > Yes I did upgrade the kernel but the system.map seems to be the same date
> > (see below). Is there a way to rebuild the system map?
>
> Correct, they are the same timestamp, however to find out wht is wrong you
> could try 'depmod -a' to see if that results in "unresolved symbols".
>
> Sometimes the error you mention is not to be worried about.
>
> Are you having problems with one or other funtion which does not work like
> it
> did in your last kernel.
>
> > -rw-r--r--    1 root     root       659886 Mar 20 07:53 System.map
> > -rw-r--r--    1 root     root       657708 Mar 20 06:42 System.old
> >
> > -rw-r--r--    1 root     root      1159361 Mar 20 07:53 vmlinuz
> > -rw-r--r--    1 root     root      1154564 Mar 20 06:42 vmlinuz.old
> >
> > Shaun
>
> --
> Regards Richard
> pa3gcu@zeelandnet.nl
> http://people.zeelandnet.nl/pa3gcu/
>
> -
> 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

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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: Kernel error

[G Anna]

> Date: Sun, 26 May 2002 07:57:59 -0700
> From: Shaun Bryant <sbryant@ThePit.org>
> Subj: RE: Kernel error

(snip)

> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
> depmod: *** Unresolved symbols in

(snipped depmod error listing)

I am just guessing.  While compiling the kernel did you do

$ make mrproper

before anything else?  I had a similar problem and it was because of
not making the above mentioned target.

Of any help?

anna

-- 

(14) The  hero is not entitled to a last kiss, a last cigarette, or any
     other form of last request. - Peter Anspach in "The Top 100 Things
     I'd Do If I Ever Became An Evil Overlord"

                                            http://www.eviloverlord.com

-
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: Kernel error

[Richard Adams]

On Monday 27 May 2002 04:35, G Anna wrote:
> > Date: Sun, 26 May 2002 07:57:59 -0700
> > From: Shaun Bryant <sbryant@ThePit.org>
> > Subj: RE: Kernel error
>
> (snip)
>
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
> > depmod: *** Unresolved symbols in
>
> (snipped depmod error listing)
>
> I am just guessing.  While compiling the kernel did you do
>
> $ make mrproper
>
> before anything else?  I had a similar problem and it was because of
> not making the above mentioned target.

I can assure you that is not his/her problem.

Unresolved symbols are caused by many things, one is using the wrong 
System.map another is trying to load module "b" before module "a" is loaded, 
why,? because module b is dependant on module a and b will barf at you if 
module a is not loaded.

>
> Of any help?
>
> anna

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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: Kernel error

[Ray Olszewski]

Sorry to come late into this discussion, but I was curious about one thing: 
when did the 2.4.x kernel start storing its modules in gzip format?

I use 2.4.17 (from Debian Sid) here, and my compiled modules are all 
something_appropriate.o, NOT something_appropriate.o.gz . Is this 
difference a distribution variation I'm unacquainted with? Or how am I out 
of date here?

Also, the first path shown in Shaun's list is an unusual one to my eye -- 
the end of it (the arch/i386/kernel/microcode.o.gz part) looks more like 
something I'd expect to see in kernel source (/usr/src/linux/) than in a 
modules path.

At 07:57 AM 5/26/02 -0700, Shaun Bryant wrote:
>Richard,
>
>I have had two kernel panics in the last 3 days which is why I was looking
>in the syslog to find the problem. I ran the command you mentioned and got
>the below results.
>
>depmod: *** Unresolved symbols in
>/lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
>depmod: *** Unresolved symbols in
>/lib/modules/2.4.5/kernel/drivers/char/drm/gamma.o.gz
>depmod: *** Unresolved symbols in
>/lib/modules/2.4.5/kernel/drivers/char/drm/i810.o.gz
[more of the same deleted]


--
-----------------------------------------------"Never tell me the 
odds!"--------------
Ray Olszewski					     -- Han Solo
Palo Alto, California, USA				ray@comarre.com
-------------------------------------------------------------------------------------------

-
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: Kernel error

[Richard Adams]

On Monday 27 May 2002 15:45, Ray Olszewski wrote:
> Sorry to come late into this discussion, but I was curious about one thing:
> when did the 2.4.x kernel start storing its modules in gzip format?

Good job you did come in late, you woke me up, as a slackware user i now see 
the problem and i think i can explain.

Slackware does indeed install "distribution kernel modules" at install time 
in *.gz format and it does install them in 
/lib/modules/2.4.5/kernel/arch/i386/kernel/* or at least the spesified 
module, microcode.o.gz which is why i did not comment on it, what i did miss 
was the microcode.o.gz, as i just mention modules.o.gz only appier in a 
distro kernel.

What Shaun has NOT done i susspect is the following.
make modules modules_install         after something like
make config
make dep clean bzImage

Now as Steven pointed out, (something which i always recomend) is the use of 
EXTRAVERSION defined in the topdir makefile.
That should overcome old or obsolite modules getting used or called as i 
belive is the case here.

Thanks Ray for the kick in the !!!! to wake me up and thanks to Steven for 
pointing the EXTRAVERSION out..

So my advice would be as follows to Shaun.

cd /usr/src/linux
vi Makefile # or emacs or joe, your editor.
edit line 4 make it look like.
EXTRAVERSION = -1
save file
make oldconfig ( or completey start a new) make config
make dep clean bzImage && make modules modules_install

(A small note) the above 'make oldconfig' is only applicable when one has 
already configured his kernel before with make config/menuconfig/xconfig and 
he/she has not done a make distclean which will wipe out a file called 
.config which contains all the confuguration details.

After the compile is complete we can copy our kernel and System.map to /boot.

cp /arch/i386/boot/bzImage /boot/vmlinuz-2.4.5-1
cp System.map /boot/System.map-2.4.5-1

Now edit /etc/lilo.conf

vi /etc/lilo.conf
Make sure one has the following at the top of the file;

prompt
timeout=100

add a new entry as follows somewhere below your old kernel entry,

image=/boot/vmlinuz-2.4.5-1
        label=2.4.5-1
        read-only
        root=/dev/hdXx
Change Xx for ones root partition.

Save the file and type;

/sbin/lilo -t
If one gets a return like;
root@unix:/usr/src/linux# /sbin/lilo -t
Added 2.4.5 *
Added 2.4.5-1
The boot sector and the map file have *NOT* been altered.

That means all went well, you can safely rerun lilo and install the new 
kernel.
/sbin/lilo

Reboot of course is the next step and hope you did not forget anything 
"needed in you new kernel"..

All kernel modules AFAIK will now be under /lib/modules/2.4.5-1/* and will 
not be in .gz format, simply module.o.

Now i could be wrong in my assumption(s) but i think i am on the right track.

>
> I use 2.4.17 (from Debian Sid) here, and my compiled modules are all
> something_appropriate.o, NOT something_appropriate.o.gz . Is this
> difference a distribution variation I'm unacquainted with? Or how am I out
> of date here?
>
> Also, the first path shown in Shaun's list is an unusual one to my eye --
> the end of it (the arch/i386/kernel/microcode.o.gz part) looks more like
> something I'd expect to see in kernel source (/usr/src/linux/) than in a
> modules path.
>
> At 07:57 AM 5/26/02 -0700, Shaun Bryant wrote:
> >Richard,
> >
> >I have had two kernel panics in the last 3 days which is why I was looking
> >in the syslog to find the problem. I ran the command you mentioned and got
> >the below results.
> >
> >depmod: *** Unresolved symbols in
> >/lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
> >depmod: *** Unresolved symbols in
> >/lib/modules/2.4.5/kernel/drivers/char/drm/gamma.o.gz
> >depmod: *** Unresolved symbols in
> >/lib/modules/2.4.5/kernel/drivers/char/drm/i810.o.gz
>
> [more of the same deleted]
>
>
> --
> -----------------------------------------------"Never tell me the
> odds!"--------------
> Ray Olszewski					     -- Han Solo
> Palo Alto, California, USA				ray@comarre.com
> ---------------------------------------------------------------------------
>----------------
>

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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: Kernel error

[Steven Smith]

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/arch/i386/kernel/microcode.o.gz
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.5/kernel/drivers/char/drm/gamma.o.gz
<snip>

The only explanation which immediately comes to mind is that you've
recompiled a kernel without setting EXTRAVERSION in the Makefile.
Normally, when you make modules_install for a new kernel, it obliterates
the old contents of /lib/modules/<version>, to avoid odd crashes
from using modules compiled for the wrong kernel. If you then reverted
to an old kernel which had the same version, you'd have the new modules
and an old kernel, which can sometimes give this sort of error.

My suggestion would be to compile a new kernel, and set EXTRAVERSION.
If the new kernel is version 2.4.5<extra>, then put the System.map
in /boot/System.map-2.4.5<extra>.

This doesn't explain why all of your modules are gzipped, though.
Is this a distribution-specific kernel, or one compiled from the sources at
www.kernel.org?

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Setting EXTRAVERSION (was Re: Kernel error)

[G Anna]

> Date: Mon, 27 May 2002 17:50:31 +0100
> From: Steven Smith <sos22@cam.ac.uk>
> Subj: Re: Kernel error

(snip)

> My suggestion would be to compile a new kernel, and set
> EXTRAVERSION.  If the new kernel is version 2.4.5<extra>, then put
> the System.map in /boot/System.map-2.4.5<extra>.

I installed RH 7.1.  It came with 2.4.2-2 kernel.  I then upgraded the
kernel to 2.4.16.  While compiling the new 2.4.16 kernel I didn't not
set the EXTRAVERSION in /usr/src/linux/Makefile. Will this cause any
problem in the future?

What is the significance of this EXTRAVERSION?  Can I choose any value
for this variable?  Also, should this value always start with -, by
convention?

$ ls /lib/modules
2.4.16
2.4.2-2

$ uname -a
Linux wobble 2.4.16 #8 Tue May 14 14:15:58 IST 2002 i686 unknown

Thank you all for your time.

Cheers,
anna

-- 

(16) I  will  never  utter the sentence "But before I kill you, there's
     just one thing I want to know." - Peter Anspach in "The Top 100 
     Things I'd Do If I Ever Became An Evil Overlord"

                                            http://www.eviloverlord.com

-
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: Setting EXTRAVERSION (was Re: Kernel error)

[Ray Olszewski]

At 09:14 PM 5/28/02 +0530, G Anna wrote:
>[...]
> > My suggestion would be to compile a new kernel, and set
> > EXTRAVERSION.  If the new kernel is version 2.4.5<extra>, then put
> > the System.map in /boot/System.map-2.4.5<extra>.
>
>I installed RH 7.1.  It came with 2.4.2-2 kernel.  I then upgraded the
>kernel to 2.4.16.  While compiling the new 2.4.16 kernel I didn't not
>set the EXTRAVERSION in /usr/src/linux/Makefile. Will this cause any
>problem in the future?

Not if you only need one compiled version of 2.4.16 on your system at any 
time. If you compile and completely install a new version, its modules tree 
will replace the prior one. If that is never a problem, you are fine. If it 
is (or might be), then you should be using EXTRAVERSION.

>What is the significance of this EXTRAVERSION?

It allows you to distinguish different variants of the same kernel. It is 
useful in two sorts of instances that I can think of --

1. If you use a workstation to compile specialized kernels for other Linux 
hosts (say a dedicated Web server or a firewall/router). It lets you keep 
better track of things. (It also works nicelty with Debian's system for 
packaging custom kernel binaries; if other distros have something similar, 
it probably works nicely with them too.)

2. If you have an existing 2.4.x kernel on your workstation, and you want 
to compile a second one to experiment with some new features ... but you 
want to be sure your old kernel is available as fallback. In this instance, 
it keeps the two compiled module trees separated.

>Can I choose any value
>for this variable?

Not *quite* any value. You need to choose a value that contains only 
characters that are legal as part of directory and file names, since the 
kernel version name gets used in the compiled modules tree. For example, no 
embedded spaces (and especially no trailing spaces; they indroduce 
hard-to-spot errors).

>Also, should this value always start with -, by
>convention?

Yes.

>$ ls /lib/modules
>2.4.16
>2.4.2-2
>
>$ uname -a
>Linux wobble 2.4.16 #8 Tue May 14 14:15:58 IST 2002 i686 unknown

--
-----------------------------------------------"Never tell me the 
odds!"--------------
Ray Olszewski					     -- Han Solo
Palo Alto, California, USA				ray@comarre.com
-------------------------------------------------------------------------------------------

-
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: Setting EXTRAVERSION (was Re: Kernel error)

[Steven Smith]

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

> > My suggestion would be to compile a new kernel, and set
> > EXTRAVERSION.  If the new kernel is version 2.4.5<extra>, then put
> > the System.map in /boot/System.map-2.4.5<extra>.
> I installed RH 7.1.  It came with 2.4.2-2 kernel.  I then upgraded the
> kernel to 2.4.16.  While compiling the new 2.4.16 kernel I didn't not
> set the EXTRAVERSION in /usr/src/linux/Makefile. Will this cause any
> problem in the future?
Usually not. Occasionally, though, especially if you compile the same
version several times, you get odd errors, and of course you'll overwrite
the modules from the previous compilation.

Generally, it's safer to set it, even if you don't think you need it.

> What is the significance of this EXTRAVERSION?
It allows you to distinguish different kernels which have the same
official version number but were compiled with different configurations.

> Can I choose any value for this variable?
Within reason. Numbers, letters, and dashes are probably safe.

> Also, should this value always start with -, by convention?
That's the convention. There's no real reason for it, though, except
to make things easier to read.

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: Setting EXTRAVERSION (was Re: Kernel error)

[Richard Adams]

On Tuesday 28 May 2002 15:44, G Anna wrote:
> > Date: Mon, 27 May 2002 17:50:31 +0100
> > From: Steven Smith <sos22@cam.ac.uk>
> > Subj: Re: Kernel error
>
> (snip)
>
> > My suggestion would be to compile a new kernel, and set
> > EXTRAVERSION.  If the new kernel is version 2.4.5<extra>, then put
> > the System.map in /boot/System.map-2.4.5<extra>.
>
> I installed RH 7.1.  It came with 2.4.2-2 kernel.  I then upgraded the
> kernel to 2.4.16.  While compiling the new 2.4.16 kernel I didn't not
> set the EXTRAVERSION in /usr/src/linux/Makefile. Will this cause any
> problem in the future?

Not in this instance, however if you recompile a 2.4.16 kernel again it will 
be a problem as the compile will overwrite modules in /lib/modules/2.4.16 or 
leave old modules lying around which will cause error messages like 
"unresolved sysbols" of which we see so many message here. It is then 
recomended to use the EXTRAVERSTION when compiling multiple copies of the 
same kernel version.

>
> What is the significance of this EXTRAVERSION?  Can I choose any value
> for this variable?  Also, should this value always start with -, by
> convention?

Just about any symbol or letter or number, about convention, cant say i have 
seen it documented but the acceped thing is a "-" for simple reasons as 
explained below.

2.4.16-1000001
2.4.16-anna123
2.4.16-anna1st-try

If you do not use a - sign and say only a "1" then your kernel version number 
will look like,
2.4.161 or 2.4.16anna123

> Thank you all for your time.
>
> Cheers,
> anna

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/

-
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: Setting EXTRAVERSION (was Re: Kernel error)

[Chuck Gelm]

G Anna wrote:
<snip> 

>  Can I choose any value
> for this variable?

Yes.

>  Also, should this value always start with -, by
> convention?

Uh, no, I think,
 especially if the extraversion starts with a non numeral.  ;-)

I used
EXTRAVERSION = wireless

i.e. '2.2.19wireless'
-
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