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.
<Sigh>
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:maillist@jdimedia.nl]
> 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
Reply to: