Bug#260433: Power4 fails to boot install kernel
Package: installation-reports
Version: sarge-netinstall powerpc 20040718
architecture: powerpc
model: JS20 Blade
memory: 2 Gig
scsi: none
cd-rom: USB over ISD200
network card: broadcom 5704
pcmcia: none
I tried using the sarge netinstall for powerpc on a Power 4 box and ran
into a number of problems. If you want me to break these into separate
bug reports, I can. It's just a hassle.
- yaboot.conf is not located at /etc/yaboot.conf. If you are booting a
chrp box, yaboot expects yaboot.conf to be at /etc/yaboot.conf. I got
around this problem by doing a hardlink.
- The device in yaboot.conf is set to 'cd' and newer versions of
firmware for ppc64 RS6000 have the name 'cdrom', thus it couldn't find
any of the kernels or boot.msg files on the disc image.
- The power4 kernels will cause a default catch in open firmware when
booted. I'm not sure exactly how the power4 kernels are being built,
but every ppc64 box I tried they failed to boot.
I also looked at the compressed kernels w/ the initrd attached without
luck. When I did a hexdump on them, the headers looked much different
from a kernel image that I got booting w/ the debian intaller attached.
Here is a non-bootable image that is currently being built:
# objdump -h vmlinuz-chrp.initrd
vmlinuz-chrp.initrd: file format elf32-big
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00005a0c 00800000 00800000 00010000 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .data 00463000 00806000 00806000 00016000 2**2
CONTENTS, ALLOC, LOAD, DATA
2 .bss 000215e0 00c69000 00c69000 00479000 2**2
ALLOC
3 .note.GNU-stack 00000000 00000000 00000000 00479000 2**0
CONTENTS, READONLY
Here is a version I built that works:
# objdump -h debian-install-2.6.5
debian-install-2.6.5: file format elf32-big
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00004dc4 00400000 00400000 00010000 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .rodata 000006c8 00405000 00405000 00015000 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
2 .data 000003e0 00406000 00406000 00016000 2**2
CONTENTS, ALLOC, LOAD, DATA
3 .kernel:vmlinux 002d32b8 00407000 00407000 00017000 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
4 .kernel:.config 00001d31 006db000 006db000 002eb000 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
5 .kernel:System.map 0005e5b4 006dd000 006dd000 002ed000 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
6 .kernel:initrd 00337feb 0073c000 0073c000 0034c000 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
7 .bss 000215d8 00a74000 00a74000 00684000 2**2
ALLOC
8 .comment 00000090 00000000 00000000 00684000 2**0
CONTENTS, READONLY
Reply to: