Visopsys 0.84 - [NEW INSTRUCTIONS] Init failed while booting as a Virtual Floppy from coreboot/SeaBIOS
Posted: Sun Jun 16, 2019 8:22 am
Hi Andy! Hope you're doing well. This is a sequel of viewtopic.php?f=3&t=292 thread. Old testing instruction there got broken, so I made a new one for you - much more user friendly! Simply get this archive - https://github.com/informer2016/shr/raw ... pdebug.zip - then unzip ./visopdebug.zip && cd ./visopdebug/ . You'd need just two commands:
- to replace a previously added visopsys floppy inside coreboot.rom with some new experimental build, using a ./cbfstool binary . It's pre-built for your convenience, however if you'd like to build it from source by yourself - there's a ./cbfstool.sh script as well as ./downloaded/ directory - cd ./downloaded/util/cbfstool/ && make all
- to run this coreboot.rom in QEMU (although you may need to edit this file if your qemu executable is not "qemu-system-x86_64") . Visopsys floppy is always the first boot entry and will get booted automatically.
Currently I'm getting the following error log at Visopsys 0.84 :
Here're your last posts from a previous thread with some ideas - viewtopic.php?f=3&t=292&start=10#p1461
Best regards,
qmastery
Code: Select all
./visopsys.sh ./path_to_a/new_visopsys.img
Code: Select all
./qemu.sh
Currently I'm getting the following error log at Visopsys 0.84 :
Code: Select all
Error: kernel process:kernelFloppyDriver.c:readWriteSectors(696):
Read/write error: Unknown error
Error:kernel process:kernelDisk.c:realReadWrite(400):
Error -24 reading 1 sectors at 0, disk fd0
Error:kernel process:kernelIdeDriver.c:atapiStartStop(715):
Media changed
Error:kernel process:kernelDisk.c:realReadWrite(400):
Error -24 reading 1 sectors at 0, disk cd0
Error:kernel process:kernelDisk.c:identifyBootDisk(2081):
The boot device could not be identified
Error:kernel process:kernelInitialize.c:kernelInitialize(370):
Disk functions initialization failed
Error:kernel process:kernelMain.c:kernelMain(85):
Initialization failed. Press any key (or the "reset" button) to reboot.
If there's anything else I could help with, please let me knowI guess what that Fiwix guy did is to create the ramdisk in the bootloader. So the loader would have to pick a memory address, load the entire emulated floppy into it using the usual int13 calls, then pass that address. But we wouldn't want it to do that under normal circumstances, so there has to be some trigger for it. Perhaps with a custom boot sector.
In the past I've been asked on here about some multiboot stuff, and PXE, and I wonder whether these changes would help to enable all of that - booting from a virtual floppy image.
Rather than a custom boot sector I'd probably go with the creation of an empty file in the image, such /ramdisk, that the bootloader could search for, to trigger this behaviour (as it does with /nograph, which forces text mode operation).
Best regards,
qmastery