[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: getting KEVS for booting DFly

From: Daniel Kiper
Subject: Re: getting KEVS for booting DFly
Date: Fri, 8 Mar 2019 11:57:05 +0100
User-agent: NeoMutt/20170113 (1.7.2)

I am not familiar with BSD but...

On Thu, Mar 07, 2019 at 04:42:47PM +0000, Artsimovich, Wladislav wrote:
> Dear GRUB team,
> I'm interested in getting DragonFlyBSD to boot without a BIOS environment 
> (e.g. using coreboot / libreboot with the coreboot-grub payload to load the 
> kernel directly) and require some help getting information to relay to the 
> DFly devs to make this possible.
> Booting the kernel directly is possible for FreeBSD via the kfreebsd command. 
> DragonFlyBSD, a fork of FreeBSD doesn't work with this command and crashes / 
> gets stuck without producing any error and freezes the screen. Also the DFly 
> boot loader doesn't run without a BIOS environment either.
> It was explained to me in the FreeBSD IRC channel, that kfreebsd passes a 
> bunch of "KEVS" (Kernel environment variables) to the kernel to make it boot. 
> The theory that the channel proposed is that these KEVS are incompatible with 
> DFly's Kernel. The DFly team however has no time to investigate this.
> I would like to compile a list of KEVS, that kfreebsd passes to the FreeBSD 
> kernel to make it boot and give that list to the DFly devs. Then they would 
> compare the list with what the DFLY kernel expects and figure out what is 
> incompatible and whether it is possible to make it compatible within a 
> reasonable time frame.
> I have no experience with such low level stuff however.
> Where can I find how many and which KEVS are passed to the kernel by kfreebsd?
> Which source files would I have to go through to compile such a list?


> What am I looking for when parsing said source files?

In general I think that "grep -Iir kfreebsd" in GRUB source directory is
your friend.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]