Search found 31 matches
- Sun Jun 16, 2019 8:22 am
- Forum: General
- Topic: Visopsys 0.84 - [NEW INSTRUCTIONS] Init failed while booting as a Virtual Floppy from coreboot/SeaBIOS
- Replies: 7
- Views: 37469
Visopsys 0.84 - [NEW INSTRUCTIONS] Init failed while booting as a Virtual Floppy from coreboot/SeaBIOS
Hi Andy! Hope you're doing well. This is a sequel of https://visopsys.org/forums/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/master/visopdebug.zi...
- Sun Feb 24, 2019 6:16 am
- Forum: General
- Topic: Bug reporting thread
- Replies: 47
- Views: 191620
- Fri Feb 22, 2019 4:12 pm
- Forum: General
- Topic: Bug reporting thread
- Replies: 47
- Views: 191620
Re: Issue when getting file size
This is done now, for release in 0.84 or 0.9 (whichever comes first!) Huge thanks to you, Andy! I am going to make a 2.88MB Visopsys floppy sometime in the future (since this rare "ED" floppy format is also supported by coreboot/SeaBIOS ) and your change will be really helpful for making ...
- Fri Jan 04, 2019 8:12 pm
- Forum: General
- Topic: Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
- Replies: 13
- Views: 51656
- Fri Jan 04, 2019 11:25 am
- Forum: General
- Topic: Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
- Replies: 13
- Views: 51656
Re: Visopsys 0.83 - Initialization failed while booting as a Virtual Floppy from coreboot/SeaBIOS
The Visopsys kernel does have a ramdisk driver. Normally you request the creation of a ramdisk (allocates memory, etc) but I could add a function that takes existing memory and uses that. I'd also have to add an extra kernel parameter to pass a memory address instead of a media signature, but again...
- Thu Jan 03, 2019 7:37 pm
- Forum: General
- Topic: Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
- Replies: 13
- Views: 51656
Re: Visopsys 0.83 - Initialization failed while booting as a Virtual Floppy from coreboot/SeaBIOS
It seems to me that this Error:kernel process:kernelDisk.c:identifyBootDisk(2081): The boot device could not be identified is the main problem that causes to fail kernelInitialize(351) and kernelMain(90). Please could we just print a warning message for the identification of BootDisk and just conti...
- Thu Dec 20, 2018 1:48 pm
- Forum: General
- Topic: Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
- Replies: 13
- Views: 51656
Re: Visopsys 0.83 - Initialization failed while booting as a Virtual Floppy from coreboot/SeaBIOS
It seems that PorkChops had a similar problem:
- Sun Dec 16, 2018 9:41 pm
- Forum: General
- Topic: Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
- Replies: 13
- Views: 51656
Re: Visopsys 0.83 - Initialization failed while booting as a Virtual Floppy from coreboot/SeaBIOS
are there any constraints about what kind of code can run within this firmware environment? Is it OK/possible to do things like take over control of various bits of hardware? (such as the interrupt controllers, say) Hi Andy, There are completely no restrictions: after SeaBIOS jumps to a "virtu...
- Tue Dec 11, 2018 10:46 pm
- Forum: General
- Topic: Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
- Replies: 13
- Views: 51656
Visopsys 0.83 - [OLD THREAD] init failed (virtual floppy at coreboot/SeaBIOS)
Finally I put Visopsys 0.83 inside that open source coreboot BIOS of AMD Lenovo G505S laptop - https://visopsys.org/forums/viewtopic.php?f=3&t=281 - and tried booting it ! ;) However I am getting the errors below (re-typed from a screen by hand) , - and I can help you to debug them if you could ...
- Tue Dec 11, 2018 6:35 pm
- Forum: General
- Topic: Bug reporting thread
- Replies: 47
- Views: 191620
Re: Issue when getting file size
. Good day, Andy! A couple of bug reports; this is the first message (+ now with a proposed help-floppy.txt attached ) "help" command prints a quite long list of commands, however not all of these commands are available at the floppy version. Perhaps you've decided to keep the unavailable...