Re: after new kernel-build booting stops

Am Mon, 14 Jan 2008 22:47:06 -0800 (PST) schrieb tortoise:

Dieter Geyer wrote:
Hi all,

i have an old Motorola PowerStack II (with 300 MHz PPC 604, 256 MB RAM)
and installed (with some tricks) a debian 4.0 R1 (Etch) on this maschine.
This is a PPC PReP achitecture.
It boots from the original boot-kernel into text-based multi-user console.

Now i want to create a new kernel, after compiling and linking (with tool
mkvmlinuz version 32) i get a file "mykernel" without any errors.

But after installing the vmlinuz-file into partition /dev/sda1 (PReP boot)
i get only this messages at boot time (recorded via RS232 console)

you didn't just copy the kernel did you ? you also need to install
/boot and /lib/modules, and new initrd.

did you use debian kernel package to make a .deb or did you build
linus
style ?


#############

loaded at: 00400400 00A75F4C
relocated to: 00800000 00E75B4C
zimage at: 00809DB4 009570CC
initrd at: 00958000 00E6C910
avail ram: 00400000 00800000

Linux/PPC load: console=ttyS0,9600 console=tty0
Uncompressing Linux...done.
Now booting the kernel

##############

after this, no more output occurs, no hdd activity, no keys are accepted.

now my question : what's wrong ?

maybe you made an error in configuring your kernel.

what did you change ? what config tool did you use ? (makeconfig or
what)



I did the old way, make oldconfig, NOTHING changed, i want to test the
compiling/linking/installing a kernel. initrd is the old one, it was read
at the building process into the new kernelfile.
Yes, i have copied the new kernelfile to /dev/sda1,
attention : the PReP actitecture doesnt support bootloader (that's why all
things have to be in one big file) , so /boot is not so important,
but i have copied the new kernel also into it.

I'm wondering, that the boot process stops after "Now booting the kernel".
As you can see, the RAM is containing the zimage and a initrd,
i'm missing the "normal" boot messages .... (this should be working without
modules and initrd, these files will be activated later)

like
....
Linux version 2.6.18 (xxxxx@yyyyy) (gcc version x.y.z) #3 Fri Feb 08
02:47:49 EST 2006
Built 1 zonelists
Kernel command line: console=ttyS0,9600 console=tty0
PID hash table entries: 256 (order: 8, 4096 bytes)
....

Thanks
Dieter
.

Relevant Pages

  • 2.6.28-rc2: REGRESSION in early boot
    ... I've opened a Kernel Bug to track this regression: ... Essentially, the system panics in early boot, resulting in multiple ... commit d6c88a507ef0b6afdb013cba4e7804ba7324d99a ... # Device Drivers ...
    (Linux-Kernel)
  • Re: booting from ISO image on HD?
    ... bootable ISO image should have exactly the same performances as booting ... That is, kernel image, modules, application programs and so ... >> through customized initrd files for each one. ... you can boot the kernel of your ...
    (comp.os.linux.misc)
  • Re: booting from ISO image on HD?
    ... I'm not going to write the pivot root script, ... > through customized initrd files for each one. ... I have to insmod the loop kernel module(e.g. ... The idea is that either you build what you need to boot into your ...
    (comp.os.linux.misc)
  • Re: booting from ISO image on HD?
    ... >> through customized initrd files for each one. ... > between the loopback device and the underlying file (the iso image). ... I have to insmod the loop kernel module(e.g. ... how can you boot it from an initrd??? ...
    (comp.os.linux.misc)
  • Re: booting from ISO image on HD?
    ... I don't think you can predict every concievably thing a distro initrd can do. ... the only purpose of the initrd is to 1) find out what kernel modules are ... there is a hard disk where that iso image resides. ... The normal boot mechanism starts with the bios loading a boot loader ...
    (comp.os.linux.misc)