My laptop will not boot properly I get a message saying can't load mod binfmt-464. In order to save some space I cleaned out the old modules and recompiled the modules. I guess I missed one. I forgot to add the clause to lilo to boot the old kernel. It will not boot from the floppy. Can I interrupt the boot sequence before lilo prompt to manually do something? I've tried pulling the drive and mounting it in another machine and have had no success. It is a Toshiba T2400CT, 24 meg RAM 344 meg HD. Thanks
On Sunday 30 June 2002 22:28, Mike wrote:
My laptop will not boot properly I get a message saying can't load module binfmt-464.
I forgot to add the clause to lilo to boot the old kernel. It's in every other lilo.conf in the house but this one!
It is a Toshiba T2400CT, 24 meg RAM 344 meg HD.
It will not boot from the floppy.
But did when I installed SuSE from a NFS CDrom. I've tried cleaning the floppy drive and have managed a boot failure but still no boot from floppy.
Can I interrupt the boot sequence before lilo prompt to manually do something?
I've now tried linux single linux root=/dev/fd0 linux boot=/dev/fd0 linux image=/boot/vmlinuz
I've tried pulling the drive and mounting it in another machine and have had no success.
On Wed, 3 Jul 2002 19:16:40 -0400
Mike
I've tried cleaning the floppy drive and have managed a boot failure but still no boot from floppy.
Have you checked the bios settings? Some bios have multiple settings needed for booting from floppy. One is the boot order, another is "floppy seek at boot", there may be others.
Can I interrupt the boot sequence before lilo prompt to manually do something?
I've now tried
linux single linux root=/dev/fd0 linux boot=/dev/fd0 linux image=/boot/vmlinuz
at the boot prompt enter: linux init=/bin/sh This will tell the kernel to simply launch a shell instead of starting the init process. So you immediately become root and there's no need to log in (this is the reason why LILO should be password protected and allow passing of kernel parameters only to authorized people; see the documentation in /usr/doc/packages/lilo). Now you are on your own. You have only this little shell but you have the power of root. As the init system didn't run you will have to do everything manually: mount -n -o remount,rw / # re-mount root partition read/write mount /usr # if /usr is on a separate partition vi /etc/passwd # correct your changes umount /usr mount -n -o remount,ro / # re-mount the root partition readonly sync # very important reboot # or press RESET if reboot doesn't work # / is readonly so it's safe Yes, it is THAT easy to break into a system. So, LILO should be password protected and one should not have MS-DOS on the same machine because parameter passing works with loadlin just like with LILO of course. Or make booting DOS a password protected option for LILO, too. -- use Perl; #powerful programmable prestidigitation
On Thursday 04 July 2002 09:00, zentara wrote:
On Wed, 3 Jul 2002 19:16:40 -0400
Mike
wrote: I've tried cleaning the floppy drive and have managed a boot failure but still no boot from floppy.
Have you checked the bios settings? Some bios have multiple settings needed for booting from floppy. One is the boot order, another is "floppy seek at boot", there may be others.
It checks the floppy I got another boot failure today, usually if just skips straight to lilo
Can I interrupt the boot sequence before lilo prompt to manually do something?
I've now tried
linux single linux root=/dev/fd0 linux boot=/dev/fd0 linux image=/boot/vmlinuz
at the boot prompt enter: linux init=/bin/sh
I tired that as well It looks at the hard drive then a few lines after I get kmod failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8 I've tried stopping the scroll after the hda message to catch the last few lines but haven;t be able to.
Yes, it is THAT easy to break into a system. So, LILO should be password protected and one should not have MS-DOS on the same machine because parameter passing works with loadlin just like with LILO of course. Or make booting DOS a password protected option for LILO, too.
I have a MAC with yellow dog that seems to skip the lilo prompt any ideas about getting into that one?
On Thu, 4 Jul 2002 20:06:37 -0400
Mike
at the boot prompt enter: linux init=/bin/sh
I tired that as well
It looks at the hard drive then a few lines after I get
kmod failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8
I've tried stopping the scroll after the hda message to catch the last few lines but haven;t be able to.
I would try going into the init scripts where kmod runs and edit out the line trying to use binfmt. Of course that requires you can boot somehow. You must be able to boot somehow, since it did get installed. Boot from the install disk and cancel the installation, that should give you a prompt. Then mount your / partition and edit . Another thing to try is removing binfmt.o from /lib/modules. Rename it to binfmt.o.bak. Maybe it is corrupt.
I have a MAC with yellow dog that seems to skip the lilo prompt any ideas about getting into that one?
Keep hitting tab while it's booting, you may catch the lilo prompt. The lilo prompt is probably set for 0 seconds delay. -- use Perl; #powerful programmable prestidigitation
On Friday 05 July 2002 09:30, zentara wrote:
On Thu, 4 Jul 2002 20:06:37 -0400
Mike
wrote: at the boot prompt enter: linux init=/bin/sh
I tired that as well
It looks at the hard drive then a few lines after I get
kmod failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8
I've tried stopping the scroll after the hda message to catch the last few lines but haven;t be able to.
I would try going into the init scripts where kmod runs and edit out the line trying to use binfmt. Of course that requires you can boot somehow. You must be able to boot somehow, since it did get installed. Boot from the install disk and cancel the installation, that should give you a prompt. Then mount your / partition and edit .
When I installed I used the boot disk and installed from my network. It doesn't boot from the floppy any more.
Another thing to try is removing binfmt.o from /lib/modules. Rename it to binfmt.o.bak. Maybe it is corrupt.
I cleaned out /lib/modules, that's how I got in this trouble to start with. iirc when I rebuilt the kernel I forgot to add elf or a.out support to the kernel.
On Fri, 5 Jul 2002 20:32:09 -0400
Mike
I cleaned out /lib/modules, that's how I got in this trouble to start with. iirc when I rebuilt the kernel I forgot to add elf or a.out support to the kernel.
Ohh, no elf support, that will get you everytime :-) You just learned the lesson that every kernel compiler goes thru.....always save your orginal working kernel and setup your new kernel with a name like linux-test in lilo.conf. That way you can test it before making it your default. I've done it before myself :-) Looks like you need to find a way to put the default suse kernel back in there. -- use Perl; #powerful programmable prestidigitation
participants (2)
-
Mike
-
zentara