Re: signed F11 for XO-1
On Thu, Nov 5, 2009 at 1:55 PM, Mitch Bradley wrote: > In the secure case, initramfs discovers the root device by looking in > the /chosen node of the /ofw device tree. I remember writing initramfs code with the proper algorithm to parse the /ofw tree and discover the root device. IIRC it was a little non-trivial, because there are partitions and other hair to deal with, and we might only deal with the common cases well. But the skeleton is there to read. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: signed F11 for XO-1
In the secure case, initramfs discovers the root device by looking in the /chosen node of the /ofw device tree. Daniel Drake wrote: > 2009/11/5 Esteban Bordon : > >> I saw the OFW code and I did not understand :-/ >> >> I created a ticket (http://dev.laptop.org/ticket/9558) with the issue and >> dsaxena wrote: >> >> "The dracut message happens way after OFW has handed off control." >> >> Then it should be a problem in the kernel included in the image? is a know >> problem? >> > > It's not a kernel problem. It's the communication between OFW and initramfs. > > We need someone who knows both areas to chime in, or for someone who > needs it fixed to do the research themselves and figure out the answer > (you?) :) > > For example here are some questions you could start on... > > If OFW is not passing a root parameter to the kernel command line, > does that mean its not passing any parameters at all? (this is easy to > figure out) > > It must be communicating the root device in some form though, so how? > (look at old initramfs code, I guess) > (if I'm writing initramfs code and OFW doesn't give me a root= > parameter, how am I supposed to know whether to look on SD, NAND or > USB for my root filesystem?) > > Or if some parameters are already passed then which ones are they? > What's the policy for adjusting them? (look at OFW code and/or ask on > this mailing list) > > Daniel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: signed F11 for XO-1
2009/11/5 Esteban Bordon : > I saw the OFW code and I did not understand :-/ > > I created a ticket (http://dev.laptop.org/ticket/9558) with the issue and > dsaxena wrote: > > "The dracut message happens way after OFW has handed off control." > > Then it should be a problem in the kernel included in the image? is a know > problem? It's not a kernel problem. It's the communication between OFW and initramfs. We need someone who knows both areas to chime in, or for someone who needs it fixed to do the research themselves and figure out the answer (you?) :) For example here are some questions you could start on... If OFW is not passing a root parameter to the kernel command line, does that mean its not passing any parameters at all? (this is easy to figure out) It must be communicating the root device in some form though, so how? (look at old initramfs code, I guess) (if I'm writing initramfs code and OFW doesn't give me a root= parameter, how am I supposed to know whether to look on SD, NAND or USB for my root filesystem?) Or if some parameters are already passed then which ones are they? What's the policy for adjusting them? (look at OFW code and/or ask on this mailing list) Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: signed F11 for XO-1
On Wed, Oct 7, 2009 at 1:00 PM, Esteban Bordon wrote: > are the kernel params hardcoded in OFW for secure boot? Yes -- on "insecure boot" boot/olpc.fth is read, but not on secure boot. Notes at http://wiki.laptop.org/go/Boot_Process If you want to see how the kernel params are setup in OFW, you should look at OpenFirmware as of changeset 1145, in the file cpu/x86/pc/olpc/fw.bth http://tracker.coreboot.org/trac/openfirmware/changeset/1145 You want to look for boot-file. Anyway, my quick review of the file is that there doesn't seem to be a usable root parameter for that case. If you look, *nothing* talks about mtd in relation to the boot-file parameter. The initramfs code should check for the secure case, or at least the "missing a root parameter" and set it. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
signed F11 for XO-1
Hi everyone! I'm trying to sign a build of F11-XO1. I could sign the initrd and vmlinuz but during secure boot the XO displays the message: *dracut: FATAL: No or empty root= argument dracut: Refusing to continue Signal caught! Boot has failed, sleeping forever. * are the kernel params hardcoded in OFW for secure boot? Esteban. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
