Problem with RH7.1 kernel upgrade from 2.4.2-2 to 2.4.14

Problem with RH7.1 kernel upgrade from 2.4.2-2 to 2.4.14

Post by <=THE=HUNTER=<<< » Sat, 24 Nov 2001 12:27:02



I have just upgraded my RH7.1 kernel from 2.4.2-2 to 2.4.14.
Everything seemed to go well, the system rebooted ok.
I made a symbolic link to my new kernel as well as the System.map.
Here is what is has me stumped.
When I boot the machine, even though I created a new kernel (vmlinuz)
as well as a new support file (System.map) I still get a message
stating that I am still running Linux 2.4.2-2.
If i go to a menu and do a uname -sr it still tells me that I am
working with Linux 2.4.2-2 Where did I go wrong. I made sure that I
changed my lilo.conf file so that image is vmlinuz, which is soft
linked to vmlinuz-2.4.14.

I did notice that whn I looked in the /etc area, the following links
are still pointing to version 2.4.2-2 stuff

kernel.h -> kernel-2.4.2
module-> kernel-2.4.2-2

As I was typing this I ran lilo from /sbin/lilo, now the machine gets
to Loading Linux ..................
then it does nothing but reboot!
I tried using the boot disk and after it loads half way I get a
message stating  Kernel Panic: No init found

any ideas on where I may have went wrong?

Thanks,

If it would help, I can type the steps that I used?

 
 
 

Problem with RH7.1 kernel upgrade from 2.4.2-2 to 2.4.14

Post by S. Par » Wed, 28 Nov 2001 15:34:22



> I have just upgraded my RH7.1 kernel from 2.4.2-2 to 2.4.14. Everything
> seemed to go well, the system rebooted ok. I made a symbolic link to my
> new kernel as well as the System.map. Here is what is has me stumped.
> When I boot the machine, even though I created a new kernel (vmlinuz) as
> well as a new support file (System.map) I still get a message stating
> that I am still running Linux 2.4.2-2. If i go to a menu and do a uname
> -sr it still tells me that I am working with Linux 2.4.2-2 Where did I
> go wrong. I made sure that I changed my lilo.conf file so that image is
> vmlinuz, which is soft linked to vmlinuz-2.4.14.

> I did notice that whn I looked in the /etc area, the following links are
> still pointing to version 2.4.2-2 stuff

> kernel.h -> kernel-2.4.2
> module-> kernel-2.4.2-2

> As I was typing this I ran lilo from /sbin/lilo, now the machine gets to
> Loading Linux ..................
> then it does nothing but reboot!
> I tried using the boot disk and after it loads half way I get a message
> stating  Kernel Panic: No init found

> any ideas on where I may have went wrong?

> Thanks,

> If it would help, I can type the steps that I used?

Did you build modules? Why don't you post how you built the kernel
2.4.14?

Regards.

 
 
 

Problem with RH7.1 kernel upgrade from 2.4.2-2 to 2.4.14

Post by Pascal Schuppl » Sun, 23 Dec 2001 11:08:13



> I have just upgraded my RH7.1 kernel from 2.4.2-2 to 2.4.14. Everything
> seemed to go well, the system rebooted ok. I made a symbolic link to my
> new kernel as well as the System.map. Here is what is has me stumped.
> When I boot the machine, even though I created a new kernel (vmlinuz) as
> well as a new support file (System.map) I still get a message stating
> that I am still running Linux 2.4.2-2. If i go to a menu and do a uname
> -sr it still tells me that I am working with Linux 2.4.2-2 Where did I
> go wrong. I made sure that I changed my lilo.conf file so that image is
> vmlinuz, which is soft linked to vmlinuz-2.4.14.

Uhm, did you run /sbin/lilo on your new lilo.conf? If you don't do this,
changes to lilo.conf have no effect. Quote from the lilo docs: "You can't
run lilo often enough."

Quote:> As I was typing this I ran lilo from /sbin/lilo, now the machine gets to
> Loading Linux ..................
> then it does nothing but reboot!

I once had the same problem after recompiling a kernel. It turned out I'd
configured it to use the wrong kind of CPU. Are you sure you configured
your new kernel correctly, e.g., for your processor type etc? Either you
made a mistake there, or you have a corrupted kernel (corrupted vmlinuz
file?)

Quote:> I tried using the boot disk and after it loads half way I get a
> message stating  Kernel Panic: No init found

This sounds like an unrelated problem. init is the very first program
that the kernel starts. So, this usually happens when the kernel can't
find the correct root file system (usually, init is on it). If you're
using an initial ramdisk, then something may be wrong with that.
Or you could have forgotten to build support for your root filesystem
into the kernel (NOT as a module). Or maybe the bootdisk you use is old
and you've moved your root filesystem to a new partition.

Hope some of this helps.

Pascal

--
They say the grass is greener on the other side, but have you ever flipped it over?

-----=  Posted via Newsfeeds.Com, Uncensored Usenet News  =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
 Check out our new Unlimited Server. No Download or Time Limits!
-----==  Over 80,000 Newsgroups - 19 Different Servers!  ==-----

 
 
 

Problem with RH7.1 kernel upgrade from 2.4.2-2 to 2.4.14

Post by Pascal Schuppl » Sun, 23 Dec 2001 11:31:30


As an afterthought, you do know that you need to use the right gcc
version (probably egcs 2.91.66) to compile a kernel, right? I forgot this
the other day and had horrible results which I couldn't explain, until
someone reminded me to use the correct compiler.

On RedHat 7.0, they included this stupid broken gcc 2.96 implementation.
I'm not sure if that's still the case in RH7.1. If it is, edit the
makefile to use kgcc instead of gcc. Or replace the compiler.

--
They say the grass is greener on the other side, but have you ever flipped it over?

-----=  Posted via Newsfeeds.Com, Uncensored Usenet News  =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
 Check out our new Unlimited Server. No Download or Time Limits!
-----==  Over 80,000 Newsgroups - 19 Different Servers!  ==-----

 
 
 

Problem with RH7.1 kernel upgrade from 2.4.2-2 to 2.4.14

Post by Rex Diete » Sun, 23 Dec 2001 05:56:38




> As an afterthought, you do know that you need to use the right gcc
> version (probably egcs 2.91.66) to compile a kernel, right? I forgot this
> the other day and had horrible results which I couldn't explain, until
> someone reminded me to use the correct compiler.

> On RedHat 7.0, they included this stupid broken gcc 2.96 implementation.

Oh, god... not another digressing thread about that icky, horrible,
stoopy-poopy gcc 2.96 again...

gcc 2.96 compiles kernels just fine... stop spreading inaccuracies and fud.

--
Rex Dieter
Computer System Administrator
Department of Mathematics and Statistics
University of Nebraska Lincoln

 
 
 

1. Unwanted Swapping in 2.4.14-pre8, no swapping in 2.4.14-pre6aa1

Yes. Currently, the kernel "tries" to keep the LRU list of pages with 90%
of mapped pages and 10% of cache when there is memory pressure.

By looking at mm/vmscan.c::shrink_cache() you can see:

        int max_scan = nr_inactive_pages / priority;
        int max_mapped = nr_pages << (9 - priority);

"max_scan" is the max. number of pages the kernel will scan on the
inactive list (the inactive list is usually 1/3 of the total amount of
pages) each time "shrink_cache()" is called.

"max_mapped" is the (roughly) maximum number of non-cache (anonymous)
pages the kernel will scan _before_ it tries to search for data to map to
swap. So basically right now we will scan

You should try to increase "max_mapped" to "nr_pages << (10 - priority)"
and so on until you get good tuning for your workload.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Core dumps

3. Memory accounting problem in 2.4.13, 2.4.14pre, and possibly 2.4.14

4. mailing list for security patches

5. Upgrading kernel to 2.4.14 on RH 7.2 with EXT3 fs.

6. Intel anypoint doesn't work at all?

7. swapping problem on kernel >= 2.4.14

8. ELM 2.4 pl25 - TMPDIR...

9. Problems with compling 2.4.14 on SMP and kernel versioning on modules set.

10. Kernel 2.4.14 bug(let), and kernel compilation error

11. SAMBA 2.2.1a Kernel 2.4.14 NFS problems

12. Dual Athlon: Kernel 2.4.14 IDE problems

13. Kernel 2.4.14 ARP-Problem