p-durlej / newsys Goto Github PK

**dear @p-durlej **, Thank you very much for your OS !
I tested Vanadium OS in a Virtual Box at single user mode --- it is amazing! And, most importantly, it has a live floppy! 👍 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)

I wish you good luck in your project, Vanadium OS is awesome

Hi there @p-durlej ! Finally I tested your wonderful Vanadium OS as a part of coreboot+SeaBIOS image ( #2 ) 😉 to be honest my earlier Vanadium experiences happened inside a VM. So, Vanadium initially seems to boot fine but then it becomes stuck at "Autoconfiguring ..." stage - while "_" symbol is blinking under O letter (Operating System at left upper corner of screen), so at least it's breathing - but still stuck

I am using your build from http://www.durlej.net/v/ - http://www.durlej.net/v/zinit.img.gz , hopefully it matches the latest source code of your newsys repository

Please tell, how could I help to debug these issues? Maybe there's some hidden debug mode to collect some logs, or a way to skip that Autoconfiguring ... (if I don't need to install Vanadium and would like to just run it in a "live floppy" mode)

First of all, as the system works fine in QEMU, props on it, it's pretty nice :)

Before erroring out because no handler for irq 3 the system complains about an unexpected IRQ 7, and the no handler error is on the line after found new hardware: "keyboard" ("keyboard"). Does this mean the IRQ might be keyboard related?

Perhaps there is a way (boot parameter?) to ignore a "no handler for IRQ" error, instead of it leading to a kernel panic?

I can't read the "self-documenting" code because the mov functions have the source and dest operands switched :( I am not sure how this even assembles on intel platforms?

bharat@Bharat:~/os386/src$ ARCH=amd64 s/mkrelse
gmake[2]: /home/bharat/os386/src/../tools/bin/amd64-os386-elf-gcc: Command not found
Makefile:35: recipe for target 'fdboot.bin' failed
gmake[2]: *** [fdboot.bin] Error 127
mk/main.mk:39: recipe for target 'all' failed
gmake[1]: *** [all] Error 2
Makefile:35: recipe for target 'all' failed
gmake: *** [all] Error 2

Hi, I am trying to compile from source but facing this error, all I did is 's/mkall' and 's/mkrelse'. I facing the error on run s/mkrelse. I checked if I have amd64-os386-elf-gcc in tools/bin after s/mkall and I don't have amd64 gcc and also i386 gcc.

I might be missing something trivial, please help.