ajxs / uefi-elf-bootloader Goto Github PK

View Code? Open in Web Editor NEW

89.0 6.0 12.0 121 KB

UEFI ELF Bootloader example

License: GNU General Public License v3.0

Makefile 7.60% C 92.27% Shell 0.14%

uefi bootloader uefi-boot kernel osdev gnu-efi efi

uefi-elf-bootloader's People

Stargazers

Watchers

Forkers

gurpreetshanky tearitco williamchatwin lostinspiration ritel126 sprig tylerjaacks wxuefei elbiazo fengjixuchui lichong0309 yds12

uefi-elf-bootloader's Issues

AllocateAddress in src/booloader/src/loader.c makes errors (NotFound)

Recently, I wanted to start developing some kind of simple combination of bootloader and kernel in ZIG (https://ziglang.org) and I searched for an example. Because of that, I found this really cool repo and rewrote it in ZIG.
But, as I executed it, there was the error "NotFound", which, after some research, was obvious to be in src/booloader/src/loader.c:62. Because I have zero experience about programming bootloaders and I wanted (as described above) to have a good example, it would be wonderful to implement physical address handling.
Or is there anything I could read about that on OSDev?

bootloader f*cks up without active serial port

i'm using a moderately modified version of your bootloader:
https://github.com/microNET-OS/microCORE/tree/stable/src/bootloader

and I don't know if it's a me problem or a you problem but the GOP works and shit i got that working i passed framebuffer info to my kernel so I've accomplished graphics. yay. anyway the bootloader doesn't work when i use a computer that doesn't have an active serial port for some reason. i tested it on my pc which has a serial port but it isn't active and it failed to init serial io. i disabled that conditional and made it just spit a warning and then it got like fucked up bad. the memory map failed (buffer too small) and the text was all over the place. any idea why?

Easiest way to test with another pre-built kernel?

Hello,

I am a bit new to bootloaders and have just come across your elf bootloader and wanted to know if there is an easy way to test it with an existing x86_64 elf kernel that I have without having to re-work a number of things in your make files?

Any help would be greatly appreciated.

Build error because of multiple definition in Arch Linux

I'm attempting to run run but I get these errors:

ld: src/error.o:(.bss+0x0): multiple definition of `graphics_service'; src/elf.o:(.bss+0x0): first defined here
ld: src/error.o:(.bss+0x10): multiple definition of `file_system_service'; src/elf.o:(.bss+0x10): first defined here
ld: src/error.o:(.bss+0x18): multiple definition of `serial_service'; src/elf.o:(.bss+0x18): first defined here
ld: src/fs.o:(.bss+0x0): multiple definition of `graphics_service'; src/elf.o:(.bss+0x0): first defined here
ld: src/fs.o:(.bss+0x10): multiple definition of `file_system_service'; src/elf.o:(.bss+0x10): first defined here
ld: src/fs.o:(.bss+0x18): multiple definition of `serial_service'; src/elf.o:(.bss+0x18): first defined here
ld: src/graphics.o:(.bss+0x0): multiple definition of `graphics_service'; src/elf.o:(.bss+0x0): first defined here
ld: src/graphics.o:(.bss+0x10): multiple definition of `file_system_service'; src/elf.o:(.bss+0x10): first defined here
ld: src/graphics.o:(.bss+0x18): multiple definition of `serial_service'; src/elf.o:(.bss+0x18): first defined here
ld: src/loader.o:(.bss+0x0): multiple definition of `graphics_service'; src/elf.o:(.bss+0x0): first defined here
ld: src/loader.o:(.bss+0x10): multiple definition of `file_system_service'; src/elf.o:(.bss+0x10): first defined here
ld: src/loader.o:(.bss+0x18): multiple definition of `serial_service'; src/elf.o:(.bss+0x18): first defined here
ld: src/main.o:(.bss+0x0): multiple definition of `graphics_service'; src/elf.o:(.bss+0x0): first defined here
ld: src/main.o:(.bss+0x10): multiple definition of `file_system_service'; src/elf.o:(.bss+0x10): first defined here
ld: src/main.o:(.bss+0x18): multiple definition of `serial_service'; src/elf.o:(.bss+0x18): first defined here
ld: src/serial.o:(.bss+0x0): multiple definition of `graphics_service'; src/elf.o:(.bss+0x0): first defined here
ld: src/serial.o:(.bss+0x10): multiple definition of `file_system_service'; src/elf.o:(.bss+0x10): first defined here
ld: src/serial.o:(.bss+0x18): multiple definition of `serial_service'; src/elf.o:(.bss+0x18): first defined here
make[1]: *** [makefile:85: build/bootx64.so] Error 1
make[1]: Leaving directory '/home/user/uefi/uefi-elf-bootloader/src/bootloader'
make: *** [makefile:65: bootloader/build/bootx64.efi] Error 2
make: Leaving directory '/home/user/uefi/uefi-elf-bootloader/src'

I've got GCC 12.1.0 x86_64 ELF cross-compiler with binutils 2.38.
GNU EFI and OVMF are latest ones from Arch repositories.

Am I doing something wrong?

AllocateAnyPages shouldn't be used?

When you allocate memory for the segments, you use AllocateAnyPages, which means it will ignore the value of segment_virtual_address and will instead pick the pages randomly.

I dont know if this was on purpose but a couple lines above you printed "Allocating memory at address x".

"Allocation requests of Type AllocateAnyPages allocate any available range of pages that satisfies the
request. On input, the address pointed to by Memory is ignored. "

uefi-elf-bootloader/src/bootloader/src/loader.c

Line 61 in e970318

AllocateAnyPages, EfiLoaderData, segment_page_count,

ajxs / uefi-elf-bootloader Goto Github PK

uefi-elf-bootloader's People

Stargazers

Watchers

Forkers

uefi-elf-bootloader's Issues

AllocateAddress in src/booloader/src/loader.c makes errors (NotFound)

bootloader f*cks up without active serial port

Easiest way to test with another pre-built kernel?

Build error because of multiple definition in Arch Linux

AllocateAnyPages shouldn't be used?

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent