Hi,
After compiling 2.4.0-test12 on my (P2-266, 440LX) Debian 2.2 system (make
bzdisk), i am unable to boot the kernel. When I boot up with the floppy
disk, I do get the Loading...... screen (I think it does load completely),
but afterwards I get this error:
0224
AX:0212
BX:BC00
CX:5101
DX:000.
This error keeps repeating itself. It seems that it keeps reading the boot
floppy every time it prints the error, because the floppy drive light is on,
and when I remove the floppy the error prints faster. At first I thought the
diskette was to blame. However, testing several different diskettes,
including ones I boot earlier 2.2.x kernels on, the problem kept occurring.
The BX and CX values differed though (BX:7400 and CX:5001).
Then, I thought it was ACPI. So I compiled without ACPI, but that didn't
help eiter. I couldn't find any useful info on the list, nor on any search
engine (+kernel +boot +"0224").
Does anyone have any ideas?
Thanks in advance.
Regards,
infernix
On Sat, 16 Dec 2000, infernix wrote:
> Hi,
>
> After compiling 2.4.0-test12 on my (P2-266, 440LX) Debian 2.2 system (make
> bzdisk), i am unable to boot the kernel. When I boot up with the floppy
> disk, I do get the Loading...... screen (I think it does load completely),
> but afterwards I get this error:
>
> 0224
> AX:0212
> BX:BC00
> CX:5101
> DX:000.
>
I've seen this a few times too. It's normally caused by a bad floppy.
Try another floppy.
--
Niels Kristian Bech Jensen -- [email protected] -- http://www.image.dk/~nkbj/
----------->> Stop software piracy --- use free software! <<-----------
----- Original Message -----
From: "Niels Kristian Bech Jensen" <[email protected]>
To: "infernix" <[email protected]>
Cc: "Linux kernel developer's mailing list"
<[email protected]>
Sent: Saturday, December 16, 2000 5:22 AM
Subject: Re: Unable to boot 2.4.0-test12 (0224 AX:0212 BX:BC00 CX:5101
DX:000.)
> I've seen this a few times too. It's normally caused by a bad floppy.
> Try another floppy.
Or try booting from harddisk...
Jens
Hi,
I found the cause. I read somewhere in a debian bugreport that bootsect.S
can't handle really big (b)vmlinuz images (over 500kb orso). However, I am
wondering why 'make bzdisk' doesn't give me an error or a warning. I mean,
the only purpose of 'make bzdisk' is to build a kernel bootable on a
floppy right?
Regards,
infernix
[infernix]
> I found the cause. I read somewhere in a debian bugreport that
> bootsect.S can't handle really big (b)vmlinuz images (over 500kb
> orso). However, I am wondering why 'make bzdisk' doesn't give me an
> error or a warning.
As someone (Jeff Garzik?) was saying a week or two ago, can we please
kill the x86 boot sector already? With today's kernels, 'over 500k or
so' is probably the common case. Is there *anything* the builtin code
can do better than syslinux?
Peter
> As someone (Jeff Garzik?) was saying a week or two ago, can we please
> kill the x86 boot sector already? With today's kernels, 'over 500k or
> so' is probably the common case. Is there *anything* the builtin code
> can do better than syslinux?
Its just plain easier to use
scp arch/i386/boot/bzImage somebox:/dev/fd0
ssh root@somebox reboot
is how I do at least part of my testing
[me]
> > Is there *anything* the builtin code can do better than syslinux?
[ac]
> scp arch/i386/boot/bzImage somebox:/dev/fd0
> ssh root@somebox reboot
Never thought of that one. I would probably instead use
scp arch/i386/boot/bzImage somebox:/tmp
ssh root@somebox 'mcopy -o /tmp/bzImage a: && reboot'
with a known good syslinux floppy in place, but I suppose your method
*is* somewhat simpler.
Peter