RE: Booting custom kernel
Yep, That did it. It must be either specifying the full path or doing a silo -f. After those 2, the new kernel booted. Alas, it doesn't recognize my 2nd CPU (Solaris and OpenBootPROM do) and even with bridge-utils64, bridging still doesn't work. I guess if I was a real hacker, I would dive into the kernel code and fix it! <> Jim > -Original Message- > From: Igmar Palsenberg [mailto:[EMAIL PROTECTED] > Sent: Monday, March 08, 2004 12:34 PM > To: Small, Jim > Cc: debian-sparc@lists.debian.org > Subject: Re: Booting custom kernel > > > > Unfortunately, I have not been able to figure out how to boot it. I > install > > the kernel in /boot and run silo, but when I boot I get this: > > Add an image directive like this : > > image=/boot/vmlinuz-2.4.25-sun4u > label=linux > read-only > > Make sure the labels differ, else in your eyes strange things will happen > :). > > The simply reboot, no need to rerun silo, as it can read ext2 / ext3 > > > Cannot find /boot/vmlinux-2.4.25 (Unknown ext2 error) > > > > Image not found try again > > boot: > > > > > > > > I have tried booting a compressed (vmlinuz-2.4.25) and uncompressed > > (vmlinux-2.4.25) kernel. I am running the latest of everything > (unstable). > > > > /boot is an ext3 partition, and I have compiled in ext3 support (in > kernel, > > not module). > > > > Ideas? Any suggestions would be greatly appreciated. > > You're sure the image actually exists ? I use gzipped images to boot. Also > make sure it's a 64 binary. > > > > Regards, > > Igmar
Re: Booting custom kernel
> Unfortunately, I have not been able to figure out how to boot it. I install > the kernel in /boot and run silo, but when I boot I get this: Add an image directive like this : image=/boot/vmlinuz-2.4.25-sun4u label=linux read-only Make sure the labels differ, else in your eyes strange things will happen :). The simply reboot, no need to rerun silo, as it can read ext2 / ext3 > Cannot find /boot/vmlinux-2.4.25 (Unknown ext2 error) > > Image not found try again > boot: > > > > I have tried booting a compressed (vmlinuz-2.4.25) and uncompressed > (vmlinux-2.4.25) kernel. I am running the latest of everything (unstable). > > /boot is an ext3 partition, and I have compiled in ext3 support (in kernel, > not module). > > Ideas? Any suggestions would be greatly appreciated. You're sure the image actually exists ? I use gzipped images to boot. Also make sure it's a 64 binary. Regards, Igmar
RE: Booting custom kernel
Hi Jim, It seems like it can't find the file. Make sure that the name of the kernel file in /boot has the exact same name and path in the silo.conf file. Create a link in "/" pointing to "/boot/your-kernel-image". Make sure you have a config like the following for your new image : image = /boot/vmlinux # Your kernel image name root = /dev/hda1 # Your root partition label = Linux# Or something else read-only# Mount root as read only Save and run the silo command and it should be ready. If not, another test you could run is by booting your new kernel directly from the boot prompt. BG's Neil -Mensaje original- De: Small, Jim [mailto:[EMAIL PROTECTED] Enviado el: lunes, 08 de marzo de 2004 17:01 Para: debian-sparc@lists.debian.org Asunto: Booting custom kernel Thanks to Igmar, I can now build a custom kernel (Sparc64) for my Ultra 60. Unfortunately, I have not been able to figure out how to boot it. I install the kernel in /boot and run silo, but when I boot I get this: Sun Ultra 60 UPA/PCI (2 X UltraSPARC-II 450MHz), No Keyboard OpenBoot 3.17, 2048 MB memory installed, Serial #11419681. Ethernet address 8:0:20:ae:40:21, Host ID: 80ae4021. Rebooting with command: boot Boot device: disk File and args: SILO Version 1.4.4 \ Linux debian 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64 GNU/Linux The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. boot: Allocated 8 Megs of memory at 0x4000 for kernel Cannot find /vmlinuz (Unknown ext2 error) Image not found try again boot: /boot/vmlinuz-2.4.25 Allocated 8 Megs of memory at 0x4000 for kernel Cannot find /boot/vmlinuz-2.4.25 (Unknown ext2 error) Image not found try again boot: /boot/vmlinux-2.4.25 Allocated 8 Megs of memory at 0x4000 for kernel Cannot find /boot/vmlinux-2.4.25 (Unknown ext2 error) Image not found try again boot: I have tried booting a compressed (vmlinuz-2.4.25) and uncompressed (vmlinux-2.4.25) kernel. I am running the latest of everything (unstable). /boot is an ext3 partition, and I have compiled in ext3 support (in kernel, not module). Ideas? Any suggestions would be greatly appreciated. Thanks, <> Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
