Guys-
I actually succeeded with the direct kernel method. I think I didn't fully
clean my coreboot build before. I do want to get the floppy method working
too as a learning experience next, but here's what I did so far:
- Build coreboot with the built-in SeaBIOS
- Add my kernel to the cbfs with:
Rafael Send wrote:
> I actually had NOT come across mkelfimage!
I see. The old wiki pages I linked to in a previous mail show it
being used. It's a very old tool from LinuxBIOS v1 times, since
replaced by functionality built into cbfstool.
Hi Peter-
I actually had NOT come across mkelfimage!
It may have to do with the fact that this page appears to be a stub:
https://www.coreboot.org/Mkelfimage
and searching on the new documentation site yields no hits.
Interestingly, the Google result for that page does show some text. Maybe
an
Peter, I believe we shouldn't put it like "ELF versus Floppy" because
these ways are not mutually exclusive: they could be tried in
parallel, especially since Rafael's pursuit towards a working solution
also involves waiting for helpful replies from the mailing lists ;-)
Also, regarding SeaBIOS: I
Rafael Send wrote:
> I had already testes the coreboot + Linux kernel without SeaBIOS,
> that works fine.
That's a great start! So did you look into what happens under the
hood when you do that, to learn?
The original common case for coreboot payloads was also ELF files, so
there is much overlap
Mike Banon wrote:
> "Loading vmlinuz...CHS: Error 0101 reading sector 18277 (8/59/6) ---
Don't spend too much time on the arcane CHS concept, it is really
obsolete and that's for the better.
You're trying to hack a data structure and interface to do what you
want, which is something I can
I was asking about
"Loading vmlinuz...CHS: Error 0101 reading sector 18277 (8/59/6) ---
that sector is situated at X kilobytes since the beginning of floppy
Loading core.gz...CHS: Error 0101 reading sector 457 (0/16/1)" ---
that sector is situated at Y kilobytes since the beginning of floppy
