[meta-intel] How to support the NUC Kit DE3815TYKHE?

Darren Hart dvhart at linux.intel.com
Fri Apr 3 09:01:31 PDT 2015


Please don't drop the list.

I would agree that something is wrong with the grub kernel command line.
There is more than just the root= being ignored. I see that the there are
kernel messages, despite "quiet" being on the list. It also lists the mmc
devices, but no USB devices, this suggests to me that "rootwait" is also
being ignored.

I'm fairly confident you have a problem with your grub.conf file. Did you
modify it manually after mkefidisk.sh created the image? I'm wondering if
there is a bogus character, bad character set, wrong cr/nl type, something
along those lines.

Does the gummiboot solution print to the serial console?

If so, and I suspect it does, the crash with GRUB is due to "rootwait" not
being passed to the kernel, and all the other parameters as well - but
that's the error you hit first.

-- 
Darren Hart
Intel Open Source Technology Center

From:  Yong Li <sdliyong at gmail.com>
Date:  Thursday, April 2, 2015 at 10:28 PM
To:  Darren Hart <dvhart at linux.intel.com>
Subject:  Re: [meta-intel] How to support the NUC Kit DE3815TYKHE?

> Thanks Darren for your patience. During the boot process, I cannot use the
> dmesg or other commands to capture the boot messages. The UART console does
> not print any message.  Since I can boot the device after replaced the
> grub(with gummiboot), I am thinking the kernel should be okay, this issue is
> related to the grub(cannot support NUC?).
> 
> Regarding the boot image, it is the core-image-minimal, I modified the BIOS to
> set the boot mode as Linux(the default is WIndows 8), then use the USB disk to
> boot the device. Attached is the screen capture of the "kernel panic". I do
> not know how to capture all these boot messages.
> 
> 2015-04-03 0:11 GMT+08:00 Darren Hart <dvhart at linux.intel.com>:
>> 
>> From:  Yong Li <sdliyong at gmail.com>
>> Date:  Thursday, April 2, 2015 at 6:46 AM
>> To:  Darren Hart <dvhart at linux.intel.com>
>> Cc:  <meta-intel at yoctoproject.org>
>> Subject:  Re: [meta-intel] How to support the NUC Kit DE3815TYKHE?
>> 
>> 
>>> >
>>> >2015-04-02 5:16 GMT+08:00 Darren Hart <dvhart at linux.intel.com>:
>>> >
>>> >ge are you building?
>>> >
>>> >
>>> >
>>> >I am using the intel-corei7-64.
>> 
>> That is the machine/bsp, not the image. Which bitbake image (target) did
>> you build? Core-image-minimal? Core-image-sato? Something else?
>> 
>>> >The kernel repots panic on the last step "cannot open root device
>>> >"(null)", since the kernel commad is incorrect.
>> 
>> This is the most common Linux boot error people run into.
>> 
>> Prior to that some information is displayed about which devices the kernel
>> did find, and which one it was trying to open.
>> 
>> I've asked for full details and logs about four times. If you would
>> provide *all* the information instead of me fishing for it, we would
>> arrive at a solution much more quickly. [1], but specifically [2]
>> 
>> 
>> The first few lines of boot will display the kernel command line it is
>> using.
>> 
>> The last few lines up to the panic will list which block devices the
>> kernel did find.
>> 
>> 1. http://www.catb.org/esr/faqs/smart-questions.html
>> 2. http://www.catb.org/esr/faqs/smart-questions.html#beprecise
>> 
>> 
>> 
>> --
>> Darren
>> 
>> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-intel/attachments/20150403/54409cdc/attachment.html>


More information about the meta-intel mailing list