Kernel compile problem after reboot
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: [email protected] [mailto:[email protected]]On Behalf Of Davidovac Zoran
Sent: Tuesday, February 05, 2002 8:00 AM
To: J.S.Souza
Cc: [email protected]
Subject: Re: Kernel compile problem after reboot
Quoted 8 lines · J.S.Souza
Date: Tue, 19 Feb 2002 07:47:54 -0800
From: J.S.Souza <[email protected]>
To: [email protected]
Subject: Kernel compile problem after rebootI 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
Quoted 14 lines
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
Quoted 12 lines
I perform the standard:
make mrproper
make menuconfig
make dep && make bzImage && make modules &&
makemodules_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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Do you have ACPI turned on? On one of my boxes (admittedly a laptop), enabling ACPI causes the computer to reboot before more than "Uncompressing ..." is printed. Disabling it causes the laptop to boot and run fine, although no power management.
Daniel
Quoted 118 lines · On Tue, 19 Feb 2002 13:24:33 -0800 "J.S.Souza" <[email protected]> wrote:
Yes, I did do a 'cp bzImage
/boot/vzlinuz-2.4.17'
I tried the:cp bzImage /dev/fd0 && rdev /dev/fd0 /dev/hda5to 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 = 1200change-rules
reset
vga = normalimage = /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: [email protected] [mailto:[email protected]]On Behalf Of Davidovac Zoran
Sent: Tuesday, February 05, 2002 8:00 AM
To: J.S.Souza
Cc: [email protected]
Subject: Re: Kernel compile problem after rebootQuoted 8 lines · J.S.Souza
Date: Tue, 19 Feb 2002 07:47:54 -0800
From: J.S.Souza <[email protected]>
To: [email protected]
Subject: Kernel compile problem after rebootI 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
Quoted 14 lines
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-onlyQuoted 12 lines
I perform the standard:
make mrproper
make menuconfig
make dep && make bzImage && make modules &&
makemodules_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.17then try this cp bzImage
/dev/fd0
rdev/dev/fd0/dev/hda5try 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
---
Recursion n.:
See Recursion.
-- Random Shack Data Processing Dictionary
No I don't have ACPI on.
You're right, it reboots right before the screen gets to "Uncompressing......."
-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Daniel Gryniewicz
Sent: Tuesday, February 05, 2002 1:45 PM
To: [email protected]
Cc: [email protected]
Subject: Re: Kernel compile problem after reboot
Do you have ACPI turned on? On one of my boxes (admittedly a laptop), enabling ACPI causes the computer to reboot before more than "Uncompressing ..." is printed. Disabling it causes the laptop to boot and run fine, although no power management.
Daniel
Quoted 5 lines · On Tue, 19 Feb 2002 13:24:33 -0800 "J.S.Souza" <[email protected]> wrote:
Yes, I did do a 'cp bzImage
/boot/vzlinuz-2.4.17'
I tried the:cp bzImage /dev/fd0 && rdev /dev/fd0 /dev/hda5to 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
Quoted 56 lines
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 = 1200change-rules
reset
vga = normalimage = /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: [email protected] [mailto:[email protected]]On Behalf Of Davidovac Zoran
Sent: Tuesday, February 05, 2002 8:00 AM
To: J.S.Souza
Cc: [email protected]
Subject: Re: Kernel compile problem after rebootQuoted 5 lines · J.S.Souza
Date: Tue, 19 Feb 2002 07:47:54 -0800
From: J.S.Souza <[email protected]>
To: [email protected]
Subject: Kernel compile problem after reboot
Quoted 9 lines
Quoted 3 lines
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
Quoted 5 lines
new kernel all I get is
Loading Linux........................
Then my computer reboots and this continues to do the same until I
select
Quoted 2 lines
Quoted 2 lines
the old kernel and it reboots fine.
Did I do something wrong in lilo? I merely made a duplicate entry with
a
Quoted 46 lines
Quoted 7 lines
different image= and label= entry:
image =
/boot/vzlinuz-2.4.17
root =/dev/hda5
label = Linux_2.4.17
read-onlyQuoted 12 lines
I perform the standard:
make mrproper
make menuconfig
make dep && make bzImage && make modules &&
makemodules_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.17then try this cp bzImage
/dev/fd0
rdev/dev/fd0/dev/hda5try 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
---
Recursion n.:
See Recursion.
-- Random Shack Data Processing Dictionary
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/