Visopsys 0.84+ (2019-08-09) cannot detect a harddrive

General discussion about Visopsys. We'll create more specific forums if the number of posts justifies that.
qmastery
Posts: 20
Joined: Mon Nov 19, 2018 8:48 pm

Re: Visopsys 0.84+ (2019-08-09) cannot detect a harddrive

Post by qmastery »

andymc wrote: Thu Jan 09, 2020 11:28 pmFingers crossed, although my suspicions about your problem have returned to the IDE and/or SATA drivers.
Good day Andy, sorry it took me so long to test your image and I'm late for your 0.85 release - have been checking this thread once in a while but worked too much at these new year holidays and forgot to check again :oops:

Recently we have discovered a big problem with IRQ routing at coreboot BIOS source code for AMD boards for 15h family, to which this G505S laptop belongs. This IRQ routing is done in the incorrect way - and while a typical advanced modern OS like Linux works fine, more simple OS like Visopsys may be behaving incorrectly just because of it. Until this is fixed, there's no sure way to know a cause of any problem - coreboot, Visopsys, or a joint one... Now we are fixing all the coreboot-supported fam15h boards code, and - while it takes a long time - hope that eventually we will succeed, and then my testing of Visopsys will be much more productive and maybe some problems will disappear!

Meanwhile I could test Visopsys on a slightly newer fam16h board, the IRQ code of which is guaranteed to be okay. By the way, your 0.85 floppy still doesn't boot if embedded to a BIOS (same errors as your previous releases), so I don't know if your special code - which made 2019-08-09 floppy working as a part of BIOS - has been included to your latest image.
User avatar
andymc
Posts: 561
Joined: Tue Nov 16, 2010 7:20 pm

Re: Visopsys 0.84+ (2019-08-09) cannot detect a harddrive

Post by andymc »

Visopsys gets its IRQ routing info from the multiprocessor tables (not ACPI), if that helps.
qmastery wrote: Sat Jan 25, 2020 6:48 pm By the way, your 0.85 floppy still doesn't boot if embedded to a BIOS (same errors as your previous releases), so I don't know if your special code - which made 2019-08-09 floppy working as a part of BIOS - has been included to your latest image.
Ahh right, you just have to create the file /ramdisk in the root of the floppy image. I didn't think it was maybe worth releasing a whole separate image for that, since it's kind of a specialist thing.
Post Reply