Board.KolibriOS.org

bzt

Just a blank black screen after the blue boot screen. So after the blue screen, then this must be the ACPI code. Can it be that ds register isn't set when accessing BOOT_LO variables? Yes. Please try this: diff -r -U 3 aaa/kernel/boot/bootcode.inc bbb/kernel/boot/bootcode.inc --- aaa/kernel/boot/bo...

bzt

Sorry, I still can't get your patch working. What seems to be the problem? Any messages, screenshot? Maybe I'm doing something wrong but the kernel doesn't boot from floppy or hdd. This patch changed nothing about anything related to those. In fact, even the biosboot.bin should be unchanged for tha...

bzt

Okay, thanks for the input, here's the final patch then for the unified kernel! This includes everything we've talked about, has no "if defined UEFI", and the header is the small one with "KolibriOS" as you've asked. Hope it's going to be useful for others as well! Tested on BIOS...

bzt

You were right, I focused on kernel.mnt only, uefi4kos indeed did not compile! I wrote too much AT&T syntax lately, I accidently swapped the parameters. But I agree that check is unnecessary if we're only about to support the latest kernel. I give it a little more thought, and here's a third alt...

bzt

I tried your unified_kernel.zip patch and it doesn't compile. That's strange, maybe different fasm versions? I could compile it, see kernel.mnt in the zip. Anyway, you're right this isn't needed at all, enough to support the latest. I'm afraid that bootbios doesn't zero acpi_rsdp, devicesdat_* It d...

bzt

Okay, here's a patch to help you with the unification. (Again, this does not change boot flow, it just removes the need for "if" macros.) First, this patch moves the BIOS based RSDP search from init.inc to bootcode.inc. This way init.inc can be firmware neutral, it shouldn't care where tha...

bzt

Indeed, jumping directly to the 32-bit code was one of reasons to separate BIOS code to bootbios.asm. Another reason was to avoid dead 16-bit code when booting on modern UEFI systems. Yes, but I think you shouldn't worry about that dead code. It's just a few kilobytes, and it provides backward comp...

bzt

Ah, thank you so much, that was it!

Cheers,
bzt

bzt

Hi, I'm trying to write a boot loader for KolibriOS. It already works in real mode on BIOS, but I also want to support UEFI, so I'm trying to start the Kolibri kernel in protected mode (related topic ). The kernel boots fine, it can use the lfb, memory is detected correctly, everything seems to be w...

bzt

So what do you think? I'd love to have a simple way of locating the protected mode entry point, and then BIOS and UEFI could use the same kernel file.

Cheers,
bzt

bzt

I cannot find the HD_load folder and thus neither the HD_load\mtldr_installer.exe file either. You can download several different files. latest-raw.7z contains kolibri.raw and Rawrite32kos.exe (dd for Windows), while latest-distr.7z contains everything, including the HD_load folder. You have probab...

bzt

Dear KolibriOS developers! First, sorry, I don't speak Russian. Second, I really like what you have done here. So much so, that I've decided to support it in my current project. I'm working on a FOSS, GPL'd boot manager Easyboot , which supports both BIOS and UEFI, and can already load several kerne...

Search found 12 matches

Re: Booting kernel

Re: Booting kernel

Re: Booting kernel

Re: Booting kernel

Re: Booting kernel

Re: Booting kernel

Re: Booting kernel

Re: How to boot Kolibri in protected mode?

How to boot Kolibri in protected mode?

Re: Booting kernel

Re: Installing KollibriOS

Booting kernel