[H-GEN] New Kernel compile fails to boot

[Hilton Travis]

(Note reply-to: being general at humbug.org.au vs "Hilton Travis" <QuarkComputers at email.com>)

Hi Robert,

> > I tried to do my first kernel compile (2.2.10) this afternoon, and all
> > seemed to go relatively well.  When I went to do a "make deps" the
> > /usr/include/errno.h file failed on line 36 due to the following:
> > file not found: bits/errno.h so I changed this line in errno.h to
> > read /usr/include/errno.h and the compile proceeded without any
> > failures.  I then did a make modules and make modules_install with
> > no issues.
> > I ran make bzImage, and the kernel compiled with no errors.
>
> At worst you should only get warnings when compiling a kernel - if you
> get errors, either you have probably done something wrong - as someone
> else suggested, you've probably not got the symlinks for the includes
> right.  The proper methods for compiling the kernel are in the file
> "README" in the top level of the source (this discusses symlinks for
> kernel includes etc).

The links were all correct as far as I could tell.  This system is a
relatively fresh RedHat 6.0 system, and I have not compiled anything else
except Samba 2.04b which went smoothly and is functioning well.

I followed the README documentation religiously!

> > I chose the P/Pro/6x86 config when I ran "make xconfig".  I can
> > email the config file I saved if necessary.
>
> In case you are now in a situation where you can't boot, installation
> disks are useful for booting a machine.  For example, with the redhat
> boot disks, at the prompt you can type vmlinuz root=/dev/hda1 and get it
> to boot your machine (it may complain about module versions but at least
> you have a machine booted up).  Its also good practice to have a
> "backup" kernel in your lilo which you can boot off if you run into
> trouble with a new one.

Hey, I might have been silly enough to get the CPU type wrong (I should have
chosen 586/6x86 instead of PPro/6x86MX) but I'm not that silly.  I modified
lilo to default to the new kernel by linking vmlinuz to vmlinuz-2.2.10, and
adding a new section to boot the old kernel as oldlinux.

As soon as the new kernel failed, I just booted into "oldlinux".

Again, thanks to all who have offered help - I chose the wrong processor
type - easy mistake!  :-)  All seems to work well, with only a failure when
attempting to install NFS.  This is not a problem right now - I will try to
figure out where I went wrong, recompile and fix this before I run NFS on
this box some time in the future.

Regards,
Hilton


--
This is list (humbug) general handled by majordomo at lists.humbug.org.au .
Postings only from subscribed addresses of lists general or general-post.