From: Paolo Ornati <ornati@fastwebnet.it>
To: "Slawomir Orlowski" <orlowscy@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with kernel 2.4.26 installation
Date: Wed, 12 May 2004 14:34:43 +0200 [thread overview]
Message-ID: <200405121434.43355.ornati@fastwebnet.it> (raw)
In-Reply-To: <1ec701c4379c$075d5700$4900a8c0@cympak.com>
On Tuesday 11 May 2004 23:07, you wrote:
> Hello there,
>
> I have got Dell server PowerEdge 2500 with dell installed RH 7.2 and
> 2.4.7-10 kernel (rpm installation).
> I wanted to upgrade it to 2.4.26 from source.
>
> So I have done like always:
> make mrproper,
> copied .config from 2.4.7 (did make menuconfig)
> make dep, clean, bzImage, modules, modules_install, install
>
> and I got:
> "
> bsetup.s: Assembler messages:
> bsetup.s:2503: Warning: indirect lcall without `*'
> Root device is (8, 8)
> Boot sector 512 bytes.
> Setup is 4768 bytes.
> System is 835 kB
> + '[' -x /root/bin/installkernel ']'
> + '[' -x /sbin/installkernel ']'
> + exec /sbin/installkernel 2.4.26 bzImage
> /usr/src/linux-2.4.26/System.map ''
> /etc/lilo.conf: No such file or directory
> make[1]: *** [install] Error 1
> make: *** [install] Error 2
As far as I can tell this problem is related to your "/sbin/installkernel"
script... it finds LILO and so calls it, but the lilo configuration file
doesn't exist ;-)!
I think that "/sbin/installkernel" is doing the right thing (from its point
of view)...
Shortly: REMOVE LILO, if you don't use it why is it installed?
Another thing you can do is to change "/sbin/installkernel" to never call
LILO.
Bye
--
Paolo Ornati
Linux v2.6.6
prev parent reply other threads:[~2004-05-12 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 21:07 problem with kernel 2.4.26 installation Slawomir Orlowski
2004-05-12 12:34 ` Paolo Ornati [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200405121434.43355.ornati@fastwebnet.it \
--to=ornati@fastwebnet.it \
--cc=linux-kernel@vger.kernel.org \
--cc=orlowscy@hotpop.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox