Click to See Complete Forum and Search --> : 2.4.1 kernel woes (hanging)


mindwarp.out
02-03-2001, 09:46 PM
You need to upload modutils and a few other things most likely.. and make sure you have compiled in support for all of your hardware.. I would use rpmfind.net, find the newest modutils rpms, and install them..

but

You could just as well upgrade to 2.2.18.. 2.4 isnt nessicary..

Ah well

Mindwarp

Fandelem
02-03-2001, 09:47 PM
here is my lilo.conf:


boot=/dev/hda
map=/System.map
prompt
timeout=50
default=linux

image=/boot/vmlinuz-2.2.13-13abit
label=linux
initrd=/boot/initrd-2.2.13-13abit.img
read-only
root=/dev/hda7
image=/vmlinuz
label=newlinux
initrd=/boot/initrd-2.4.1.img
root=/dev/hda7

other=/dev/hda1
label=dos


everything is there (/vmlinuz, /system.map, /boot/initrd-2.4.1.img) but it hangs right after, "Uncompressing Linux.. Ok, booting the kernel.." [hang]

I currently have 2.2.13 (redhat), and I downloaded 2.4.1 (full, 24megs).

It compiled fine (albeit me having to get the new modutils) and everything was seeming like it was going so well.. then when i reboot, it hangs.

anyone know where i can even *start* to debug and find where/why it is hanging?

*any* help would be much appreciated; i'm new to kernel upgrading as it is, and there might be something i'm unaware of when going from 2.2 to 2.4

~kyle

mindwarp.out
02-03-2001, 09:47 PM
One more thing... did you copy /usr/src/linux-2.4.0/arch/i386/boot/bzImage to /boot/vmlinuz-2.4.0 and symlink it?

If not that could be why.. most people use /usr/src/linux-2.4.0/vmlinuz, but its better to use the bzImage..

Fandelem
02-03-2001, 10:31 PM
You need to upload modutils and a few other things most likely..


like which other things? ;o)



2.4 isnt nessicary..


2.4 is suppose to have some great Toshiba Laptop features that I wanted to look into.. and I re-linked all that, and it still didn't work :o( any other suggestions?

~kyle

sch3k
02-04-2001, 12:26 AM
i think most people said they got the stall at uncompressing when they selected the wrong cpu when compiling the kernel. under 2.4 it selects a pIII as the cpu by default. so that might be your problem.

anyways i upgraded my redhat 6.2 system from 2.2.16 to 2.4.1 with no problems at all. from what it seems, i think you copied the system.map and other stuff to the wrong dirs (if you do make install at the end it copies the files automatically to the right place and updates the links to point to the 2.4 files), i think everything should be in /boot for redhat systems. anyways, this is the steps i did it in:

1. unpacked the 2.4.1 kernel in my /root dir
2. cd to the linux dir that was made after unpacking and did make mrproper
3. read the /root/linux/Documentation/Changes and upgraded everything to meet the minimal requirements, i think for me the only two things i needed to upgrade was utils-linux and and e2fsprogs.
4. make menuconfig
5. make dep
6. make clean
7. make bzImage
8. make modules modules_install install
9. edit /etc/lilo.conf, mine looks like this

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
linear
default=linux

image=/boot/vmlinuz-2.2.14-5.0
label=oldlinux
read-only
root=/dev/hda5

image=/boot/vmlinuz-2.2.16
label=oldlinux2
read-only
root=/dev/hda5

image=/boot/vmlinuz-2.4.1
label=linux
read-only
root=/dev/hda5

10. lilo -v
11. shutdown -r now

and that's it. hope that helps

[ 03 February 2001: Message edited by: sch3k ]