public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.S.Souza" <jss@pacbell.net>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Kernel compile problem after reboot
Date: Tue, 19 Feb 2002 13:24:33 -0800	[thread overview]
Message-ID: <PGEMINDOPMDNMJINCKBNCECLCAAA.jss@pacbell.net> (raw)

Yes, I did do a 'cp bzImage /boot/vzlinuz-2.4.17'
I tried the:
	cp bzImage /dev/fd0 && rdev /dev/fd0 /dev/hda5
to no success.  It does the same thing as before, just slower since it's
from a floppy (reboots the machine).  This time I did configure the kernel a
bit and recompile with still no success.  If you have anymore options or
suggestions, please feel free to pass them on.
Here's my machine setup since you asked:

Intel 233
192 meg Ram
10 gb Maxtor HDD (partitioned as hda1:/boot hda5:/ hda?:/swap)
Intel chipset (PCIset)


Here's my lilo.conf file:

===============================
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200

change-rules
	reset
vga = normal

image = /vmlinuz
	root = /dev/hda5
	label = Linux
	read-only
image = /vmlinuz-2.4.17
root = /dev/hda5
label = Linux-2.4.17
read-only
================================

It's got to be my configuration or lilo setup (I think) because I can
install Slackware,Redhat and others on it just fine with their default
setup.  Anyways, please pass on any info you think might help.



-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Davidovac Zoran
Sent: Tuesday, February 05, 2002 8:00 AM
To: J.S.Souza
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel compile problem after reboot




On Tue, 19 Feb 2002, J.S.Souza wrote:

> Date: Tue, 19 Feb 2002 07:47:54 -0800
> From: J.S.Souza <jss@pacbell.net>
> To: linux-kernel@vger.kernel.org
> Subject: Kernel compile problem after reboot
>
> I am using Slack 8 with 2.2.19 and trying to install 2.4.17.  The whole
> compile process goes as planned until I reboot.  After reconfiguring
> lilo.conf and running lilo to update changes, I reboot and when I select
the
> new kernel all I get is
>
> Loading Linux........................
>
> Then my computer reboots and this continues to do the same until I select
> the old kernel and it reboots fine.
> Did I do something wrong in lilo?  I merely made a duplicate entry with a
> different image= and label= entry:
>
> image = /boot/vzlinuz-2.4.17
> root = /dev/hda5
> label = Linux_2.4.17
> read-only
>
> I perform the standard:
> make mrproper
> make menuconfig
> make dep && make bzImage && make modules &&
> make modules_install
> cp System.map to /boot
> cp bzImage to /boot
> edit lilo.conf
> run lilo
> reboot
> swear at the computer.
>
do configure the kernel! Do not use defaults!

when you did cp bzImage to /boot
I hope you did cp bzImage /boot/vzlinuz-2.4.17

then try this cp bzImage /dev/fd0
rdev /dev/fd0 /dev/hda5

try to boot from floppy

if that is ok , reconfigure kernel try to boot it.
If it still don't boot perhaps your bios can't reach kernel
for some reason.

if still don't work post description on
what hardware / disk ?

regards,

 Zoran

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


             reply	other threads:[~2002-02-05 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 21:24 J.S.Souza [this message]
2002-02-05 21:45 ` Kernel compile problem after reboot Daniel Gryniewicz
2002-02-19 22:36   ` J.S.Souza
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19 15:47 J.S.Souza
2002-02-05 15:59 ` Davidovac Zoran

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=PGEMINDOPMDNMJINCKBNCECLCAAA.jss@pacbell.net \
    --to=jss@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    /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