On Mon, Nov 06, 2000 at 08:14:24PM -0600, phil@ipal.net wrote:
> The CD has this file as /boot/silo.conf in the last version of the ISO
> I got:
>
> partition=1
> default=linux
> read-write
> message=/boot/message
> root=/dev/ram
>
> image[sun4u]=/boot/vmlinux.sun4u
> label=linux
> append="ramdisk_size=5120k"
> initrd=/boot/color.gz
>
> image[sun4c,sun4d,sun4m]=/boot/vmlinux.sun4cdm
> label=linux
> append="ramdisk_size=5120k"
> initrd=/boot/color.gz
>
> This points to where the kernel is for the CD. It may be /.boot in the
> case of an earlier ISO.
The CD is not the issue. The CD works (mostly) fine.
The things I'm trying to work out are:
1) Why can't I boot off the new kernel I built
2) Where the heck is the kernel I'm booting off now?
3) Why won't silo read my /etc/silo.conf (which didn't previously exist
at all)
4) How can I convince my system to boot /vmlinux instead of the mystery
kernel?
> What you need to do is boot the harddrive based system with the CD kernel
> to get back in and try fixing things.
I can get into the system just (mostly) fine.
> Very possibly, the installed kernel
> was at /vmlinuz so your recompile may have replaced it.
I'm 100% positive there was no kernel in / before or after I compiled my
new kernel. The new kernel was copied to / by hand.
> But by booting
> from the CD kernel, you are back up and working to the extent that kernel
> lets you do so. The CD won't be mounted so you could eject it once the
> kernel is loaded. Or you can mount it and reinstall packages, or copy
> files.
>
> To fix things, you'd need to check the silo config and the compilation to
> see what might be wrong.
The silo.conf is fine. Hitting <TAB> at the SILO prompt reveals that it
has only one option and has not read any of the other options that are
in the new silo.conf.
> You might also try to manually load the network
> driver module you need to temporarily get networking working so you can
> transfer files in and out, such as getting a compile log and a copy of
> your silo.conf for us.
After the install I ended up without a /lib/modules directory making it
impossible to config the ethernet interface. I now have modules that I
compiled from the src in /usr/src/linux but of course they're from newer
source than the mystery kernel, which is the only one I can boot.
-Bill
-- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - unfurl@bsdi.com -=| Do Not Taunt Happy Fun Ball(tm)
This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT