Re: gcc-2.91.66 needed for kernel compilation?
* R1nso13@aol.com <R1nso13@aol.com> (2001-07-23 09:00):
> I'm attempting to compile kernel 2.4.6 on 2.2r3. Yes, i know .7 is out, but
> when i tried to unpack the archive I downloaded from ftp.kernel.org i got
> errors using the same method I used to unpack the 2.4.6 kernel successfully
> so i thought i'd just stick with it.
> Anyway, i've gone through the installation proceedure several times and I
> have two reoccuring errors:
> 1. make zImage says that the kernel is too big and to use make bzImage. I
> thought this was odd because i have plenty of extra hdd space.
BzImage is needed if your kernel is larger than a certain size, it
doesn't have anything to do with free space.
> 2. When I use make bzImage I don't get any errors, but when i move the file
> and the System map and everything to the /boot directory (yes, i've been set
> straight a/b the directories) and configure lilo it still doesn't work when i
Although it sounds as though you're following the correct kernel
recompiling procedure, I'd recommend that you use the kernel-package
tool, since it makes everything so much easier, and it makes sure that
you don't forget anything (like running lilo before rebooting).
If you've already configured your kernel, which you have, just install
the kernel package tool (apt-get install kernel-package), cd to your
kernel source directory and run the commands:
make-kpkg clean
make-kpkg --revision=custom.1 kernel_image
This will build the kernel and modules and make it into a deb package
ready for you to install with dpkg -i. Then just move up one
directory and install the kernel-package that you've just made. It
will prompt you to make a boot disk and run lilo. After that, you can
reboot. AFAIR, the kernel-package tool will make a backup entry in
your /etc/lilo.conf for you to use your old kernel if you want
(someone please correct me if I'm wrong on this point).
> try its identifier at the boot prompt. It just says "loading", the hard drive
> LED comes on, and nothing happens.
AFAIK, this could very well be a problem with the CPU setting within
your kernel. With the 2.4.x kernels, its very important to have the
correct processor specified under Processor Type (in menuconfig).
I also had a similar problem when I'd incorrectly configured my
framebuffer device. The machine loaded fine (I could see the hdd led
flashing), I just couldn't see anything on the screen. I'd check that
there was a vga=normal line in your /etc/lilo.conf, and comment out
all other vga= lines or any lines with append=video (or similar).
> I read the README file which suggests using gcc-2.91.66. It says gcc-2.95.xx
> (which i'm currently using) will probably work, but is less safe.
> So, what's going on? is it the compiler, or am I just really messing up the
> config file (I don't think I am, I've checked all my system specs. and I said
> yes to settings I need). Furthermore, if it is the compiler, does debian have
> a packagefile for gcc-2.91.66? I've looked hard but found nothing. They don't
> even have it on gnu.org for download, or not that i've found anyway.
I've compiled kernels on both potato and woody (both with gcc-2.95.xx)
with no problems, I doubt that's whats affecting it.
> Oh, and by the way: I finally got a 'normal' boot disk to work with 'make
> bzdisk', but It was for my existing kernel.
I don't have much experience with boot disks myself, but the
kernel-package tool will create one for you. Install kernel-package
and have a look at /usr/doc/kernel-package for more information on all
it can do.
Cheers,
Sean
--
Sean Quinlan (smq@gmx.co.uk)
Reply to: