On Wed, Sep 01, 2004 at 09:23:46PM +0200, Nicolas Raspail wrote: > Sven Luther wrote: > > >On Wed, Sep 01, 2004 at 09:31:41AM +0200, Nicolas Raspail wrote: > > > >>Hi, > >> > >>I've tried to netboot the vmlinux-prep/chrp.initrd and none works for me. > >>Here is some logs extract > > > > > >Ok, since now we know that your box is a chrp one, we can tell a bit more > >about this : > > > > > >>0 > boot net:10.252.82.254,,10.252.82.229 > >>LOAD: Waiting 60 seconds for Spanning Tree > >>BOOTP R = 1 BOOTP S = 1 > >>FILE: /install/tftpboot/vmlinuz-prep.initrd > >>Load Addr=0x4000 Max Size=0xbfc000 > >>FINAL Packet Count = 11055 Final File Size = 5660139 bytes. > >> > >>Unexpected Firmware Error: > >>DEFAULT CATCH!, code=fff00300 at %SRR0: 00c1b030 %SRR1: 00003030 > > > > > >This is expected, since you are trying to boot a prep kernel on a chrp box. > > > > > >>0 > boot net:10.252.82.254,,10.252.82.229 > >>LOAD: Waiting 60 seconds for Spanning Tree > >>BOOTP R = 1 BOOTP S = 1 > >>FILE: /install/tftpboot/vmlinuz-chrp.initrd > >>Load Addr=0x4000 Max Size=0xbfc000 > >>FINAL Packet Count = 11188 Final File Size = 5727838 bytes. > >>CLAIM failed > >>ok > >>0 > > > > > > >Ok, claim is used in the bootloader. I don't really know if this is > >happening > >while the OF is claiming space for the kernel (i somehow don't think so, > >because it has already loaded it somewhere), or if the actual kernel > >boot-loader is trying to claim in the arch/ppc/boot/openfirmware/main.c. > > > > > >>0 > setenv load-base 100000 ok > >>0 > boot net:10.252.82.254,,10.252.82.229 > >>LOAD: Waiting 60 seconds for Spanning Tree > >>BOOTP R = 1 BOOTP S = 1 > >>FILE: /install/tftpboot/vmlinuz-chrp.initrd > >>Load Addr=0x100000 Max Size=0xb00000 > >>FINAL Packet Count = 11188 Final File Size = 5727838 bytes. > >><REBOOT> > >>LOAD: Waiting 60 seconds for Spanning Tree > >>BOOTP R = 1 BOOTP S = 1 > >>FILE: /install/tftpboot/vmlinuz-chrp.initrd > >>Load Addr=0x4000 Max Size=0xbfc000 > >>FINAL Packet Count = 11188 Final File Size = 5727838 bytes. > >>CLAIM failed > > > > > >This should have helped. I naturally have no idea how the IBM OF is set > >out, > >where the actual OF code is located, and what the free space is. Could you > >try > >other load-base entries ? > > > >And BTW, how much memory you have on that box anyway ? > > > >Also, could provide the output of powerpc/netboot/2.4/vmlinuz-chrp.initrd > >as > >well, and try to boot a standalone (without initrd) 2.6 kernel, by > >installing > >kernel-image-2.6.8-powerpc, and running > > > > mkvmlinuz -n -o /tftpboot/vmlinuz-2.6.8-powerpc -k > > /boot/vmlinux-2.6.8-powerpc > > > >and then booting the resulting kernel. You would need mkvmlinuz version 9 > >or > >higher. > > > >Friendly, > > > >Sven Luther > > > > > > For the mkvmlinuz, I've found an old 7043-140 (Prep box, Ram 768 Mo, 2 > go hd) and tried to install Debian as it's easier I think, but I got > kernel panic after netbooting the DI vmlinuz-prep.initrd. After some > reading, I need to have 512 Mo max for RAM (if more are present, memory > maps change and the prep loader doesn't work), so I remove some RAM and > now it boots. I can configure the keyboard but it doesn't see my > hardisk. I'm connected with minicom so it seems I can't switch to > another virtual console to see any message. Do you have any idea for the > non detection of my scsi hardisk and card ?
Yes, you probably have a sym53c8xx based driver, and it needs the scsi_transport module which Jens mentioned was missing. Jens added it to the modules, but i am waiting for Jens to rebuild a powerpc kernel based on the 2.6.8-5 kernel-source to make a new upload. This should fix this problem. In any case, could you go to console 2, and give us the content of /proc/pci and /proc/bus/pci/devices, so we can confirm that this is it ? > Back to my 7043-150. My box have 1 Go of RAM, so perhaps, I'm having the > same problem. Tomorrow I'll downgrade it to 256 Mo and try the last DI > build to see if I've the same CLAIM failed. If this doesn't work, I'll > try to install debian on my 7043-140 and use the mkvmlinux tip Ok. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]