> > > The information dumped by qemu when a triple fault occurs are as follows: > > > > Wikipedia suggests a triple fault can be caused when the IDT is > > corrupted: sounds like a memory sizing / linking issue. > > > > The prex i386 port has a gdb stub - are you using gdb in your debugging? > > > I haven't quite figured out how to attach gdb via qemu, though if I'm right > about it being the boot sector that won't help much. > so gdb doesn't have anything to say. This further leads me on the boot sector path.
I've been fiddling aroud a bunch, and I'm almost 100% certain the bug is in the boot sector. My guess is that the image ends up spanning multiple sectors and the boot sector can't handle reading an image that spans multiple sectors from the fat table.. I sort of get a vague feeling of this from the bootsect.S but on the other hand I also have no experience with asm.. Has anyone booting prex with an image that's larger than 128kb? Any suggestions for what might be done? I'm considering trying to get grub or some other boot sector to load the image and see if that does anything.. Alex PS. I've been hanging out in #prex on freenode, if anyone on the list IRCs you should come hang out there too! ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Prex-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/prex-devel
