|
-
December 30th, 2002, 07:16 PM
#11
by typing lilo..
that loads the /etc/lilo.conf configurtion and the Linux Loader to the selected part of your harddisk (MBR or something)..
just ( as super user (root) ) type: lilo
that should do the trick
ASCII stupid question, get a stupid ANSI.
When in Russia, pet a PETSCII.
Get your ass over to SLAYRadio the best station for C64 Remixes !
-
December 30th, 2002, 07:37 PM
#12
Member
jinX-- Thanks for you input. LILO is my default boot loader but this new kernel is still not booting up. I'm almost ready
to give up. I followed exactly the readme of kernel-2.4.20.tar.gz but no luck. Did anyone else have any problems
installing the latest stable kernel. If so please let me know how you fixed it. Thanks guys
-
December 31st, 2002, 01:52 AM
#13
Junior Member
Does your new kernel start booting and hangs up during startup,
or doesn't it start at all?
If you misconfigured your kernel, it might happen that some things don't work - like network, soundcard, ... - or when you forget to include the code for using the ext2-filesystem, the kernel won't be able to mount the root partition (for example : /dev/hda1). Your linux system won't be able to start up. This are just examples of what can go wrong. There are a lot more reasons it might not work. I would advise you to check the configuration files for your kernel.
Another possibility is that the kernel didn't finish compiling. Due to misconfiguring or because the kernel is too big (this can happen :-) ). If your kernel is compiled (command 'make', without options), it should end without errors.
Maybe something went wrong when applying LILO. If you execute 'lilo', a list appears with all possible bootoptions. The default bootoption gets a star (*). If this list doesn't appear, or when an error message is present, your MBR wasn't changed, so it will still boot with the old configuration.
Please excuse me if I misinterpreted your descriptions. I hope this will get you on the way...
BTW: I use kernel 2.4.19, without any problems, so I suppose 2.4.20 should work allright. Unless you have just discovered a bug ... :-)
-
December 31st, 2002, 03:21 AM
#14
Member
Does your new kernel start booting and hangs up during startup,
it goes to the lilo prompt and waits for me to choose which kernel i want to bootup with. If I choose 2.4.7-10(RH 7.2 original kernel), it works fine. However, if i choose 2.4.20 it will say
loading kernel............................................ then the machine will automatically reboot.
Another possibility is that the kernel didn't finish compiling. Due to misconfiguring or because the kernel is too big (this can happen :-) ). If your kernel is compiled (command 'make', without options), it should end without errors.
After I run 'bzImage' I get a warning at the end saying that the image file is too big to fit on a disk. I assumed this meant i could not run 'bzDisk' Is this a correct assumption?
BTW: I use kernel 2.4.19, without any problems, so I suppose 2.4.20 should work allright. Unless you have just discovered a bug ... :-)
Yes, I use 2.4.19.8 on my other machine and it fine. I don't think I discovered a bug, but just a frustrated newbie...
Thanks for your suggestions.
-
December 31st, 2002, 05:33 AM
#15
it goes to the lilo prompt and waits for me to choose which kernel i want to bootup with. If I choose 2.4.7-10(RH 7.2 original kernel), it works fine. However, if i choose 2.4.20 it will say
loading kernel............................................ then the machine will automatically reboot.
Your lilo configuration is right.....you set it right...the problem is :
Your new kernel 2.4.20 "not install" in your RH LINUX.. because this one:
[/quote] After I run 'bzImage' I get a warning at the end saying that the image file is too big to fit on a disk. I assumed this meant i could not run 'bzDisk' Is this a correct assumption? [/quote]
You can use this command (make bzImage or make zImage) only if you have "high-density floppy".
So my advice try..to compile it again..
Try this first :
1. $ su
enter root's password
2. # cd /usr/src
3. # wget -c http://www.kernel.org/pub/linux/ker...-2.4.20.tar.bz2
4. # tar -xvjf linux-2.4.20.tar.bz2 (if you using tar.gz just do normal tar xvzf linux-2.4.20.tar.gz)
5. # rm -f linux-2.4 linux
6. # ln -s linux-2.4.20 linux-2.4
7. # ln -s linux-2.4 linux
8. # cd linux
9. # cp /boot/config-2.4.7-10 .config
10. # make xconfig ( customised your one..save and exit..)
11. # make dep
12. # make clean
13. # make bzImage <<<<<< first of all...do it again use this command if still get "warning" use this command " make zlilo"
14. # make modules
15. # make modules_install
16. # make install
17 # /sbin/reboot
I believe this method will work.... please let me know..how it goes
Not an image or image does not exist!
Not an image or image does not exist!
-
January 2nd, 2003, 05:02 AM
#16
Member
Hello people
I just wanted to put a final end to this thread, sweet_angel suggested it, so that it may serve as a tutorial for anyone else who has this same problem. Well the advice sweet_angel worked. It turned out the kernel wasnt booting because I had bad sectors on my harddrive or something. So the problem is easily solved by transfering the new image kernel onto a floppy with the
"make bzdisk" command. The hard part is troubleshooting and realizing that the harddrive is the problem.
Anyways thanks to all who advised.
Peace
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|