Stupid... kernel...
I''ve been trying to compile 2.4.21 for about as long as it''s been stable now. I can''t seem to get it to boot: Lilo gets up to Uncompressing Linux and restarts the machine.
Having a stripped down kernel (make mrproper && make dep && make bzImage) also didn''t work.
It also did this when I dropped in my (untested) 2.4.20 kernel, and I''ve made sure I''ve specified the right CPU (K6-2)...
Does anyone have any ideas left?
Resist everyone
Talk on RavForum(tm)
June 29, 2003 08:33 PM
Hi,
Are you over-writing an old kernel, or adding a new entry to the lilo menu? If you are over-writing an older image, make sure that you run lilo after updating the lilo.conf file.
-Spyro
Are you over-writing an old kernel, or adding a new entry to the lilo menu? If you are over-writing an older image, make sure that you run lilo after updating the lilo.conf file.
-Spyro
Have you got all the important stuff compiled in? Things like IDE support (unsless you''re on SCSI), EXT2 fs support, etc, must be compiled in else it''ll compain, though it should still boot into the kernel itself. Hmmm.
Maybe you could try a different boot loader...
More info! Kernel config, lilo.conf, etc.
The following statement is true. The previous statement is false.
Shameless promotion:
FreePop: The GPL Populous II clone.
Maybe you could try a different boot loader...
More info! Kernel config, lilo.conf, etc.
The following statement is true. The previous statement is false.
Shameless promotion:
FreePop: The GPL Populous II clone.
My stuff.Shameless promotion: FreePop: The GPL god-sim.
You can see my lilo.conf Here... my kernel config is the default for 2.4.21, except the processor type has been changed to K6/K6-2/K6-3.
I am booting from a SCSI drive with ext2 (both are compiled into the kernel). My kernel images are stored in /boot, and lilo.conf has an exact route to them (as you can see).
I''d try grub, but I fear that it may do the exact same thing. I think it''s to do with the kernel...
I am booting from a SCSI drive with ext2 (both are compiled into the kernel). My kernel images are stored in /boot, and lilo.conf has an exact route to them (as you can see).
I''d try grub, but I fear that it may do the exact same thing. I think it''s to do with the kernel...
You are booting from a default kernel might be a slight problem. You may be missing some important drivers that need to be compiled in, but are not in the default settings.
If you really wanna cheat, copy the .config file from your working linux directory to your new linux directory (something like /usr/src/linux-2.4.21/) then do your compile again. Copy the file after you make mrproper, i think that deletes the .config file and a few others.
If you really wanna cheat, copy the .config file from your working linux directory to your new linux directory (something like /usr/src/linux-2.4.21/) then do your compile again. Copy the file after you make mrproper, i think that deletes the .config file and a few others.
Hitchhiker90"There's one bitch in the world, one bitch with many faces" -- Jay"What are you people, on dope?" -- Mr. Hand
I did this routine:
make clean
make mrproper
make xconfig
make dep
make bzImage
make modules
make modules_install
And it worked fine: of course, I spent the time to read all of the options in xconfig and added "zlib support" in one of the boxes. I dunno if that did anything, but geez, it booted and I''m typing this on v2.4.21. Congrats to me!
Thanks so much for all your help, guys.
I felt somewhat lost without my resident guru (SHilbert) around this week.
make clean
make mrproper
make xconfig
make dep
make bzImage
make modules
make modules_install
And it worked fine: of course, I spent the time to read all of the options in xconfig and added "zlib support" in one of the boxes. I dunno if that did anything, but geez, it booted and I''m typing this on v2.4.21. Congrats to me!
Thanks so much for all your help, guys.
I felt somewhat lost without my resident guru (SHilbert) around this week.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement