mduft / tachyon3 Goto Github PK

I have not tracked down exactly which part of the function causes the reset but it is within this function that causes a physical-machine to reset. This was first discovered when running the ISO image on a Hyper-V machine and re-confirmed when running on real hardware.

I will need to do some more debugging but it is a bit difficult to track down atm, I will be attempting to utilize the named pipes within hyper-v for the COM2 interface to see if that'll help track this down.

This is the entry point to where I started tracing the origin of the bug ...

/* initialize the physical memory */
pmem_init();

edit
Ah - I should also mention that the machine im running on ...
AMD Athlon x640, 16GB Ram

Hi, I am running this on debian/amd64. Standard multiarch gcc-4.6 that come with the distribution.

$ git clone git://github.com/mduft/tachyon3.git
$ cd tachyon3
$ make
Makefile:25: /home/oxygen/bart/src/tachyon3/tachyon3/.package/env.mk: No such file or directory
make: *** No rule to make target `/home/oxygen/bart/src/tachyon3/tachyon3/.package/env.mk'. Stop.

$ mkdir .package
$ touch .package/env.mk
$ make
[CC ] src/abort.c
bash: x86_64-pc-elf-gcc: command not found
make: *** [/home/oxygen/bart/src/tachyon3/tachyon3/.build/x86_64/src/abort.o] Error 127

$ sed -ie 's/x86_64-pc-elf-//' config/x86*.mk
$ make
[CC ] src/abort.c
[CC ] src/bmap.c
...
[AS ] src/spl.S
/tmp/ccsGJy2R.s: Assembler messages:
/tmp/ccsGJy2R.s: Error: .size expression for spl_mine does not evaluate to a constant

Let me know if you need further info.
-Bart

Even today the floppies are still being used, for example - as virtual floppies inside the coreboot open source BIOS. Just imagine: your wonderful OS could be a part of someone's BIOS build! (for coreboot supported motherboard, maybe you have or could get one - see https://www.coreboot.org/Supported_Motherboards )

If you already have a coreboot-supported motherboard, or a real chance to get one, - wouldn't it be cool to be able to launch your own OS straight from the BIOS chip? ;) With one simple command its possible to add any floppy to coreboot BIOS build - and then you see it as a boot entry! Multiple floppies could be added this way (as long as you have enough space left inside the BIOS flash chip, luckily LZMA compression could be used for the stored floppies to reduce their occupied size)