Bug 10606 - [Test Case 196] Install from USB device to HDD on NUC is failing
Summary: [Test Case 196] Install from USB device to HDD on NUC is failing
Status: RESOLVED DUPLICATE of bug 9525
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-intel-corei7-64 (show other bugs)
Version: 2.2
Hardware: NUC x86_64
: Medium normal
Target Milestone: 2.2 M4
Assignee: California Sullivan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-04 19:03 UTC by Juan Ramos
Modified: 2016-11-07 19:05 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
Install on NUC (3.34 MB, image/jpeg)
2016-11-04 19:03 UTC, Juan Ramos
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramos 2016-11-04 19:03:15 UTC
Created attachment 3525 [details]
Install on NUC

STATUS: IDLE
BUILD: meta-intel-6.0 : 6c9f6b5f70ab3ee194b2c2c6f3bd462c994848fa
ENVIRONMENT: corei7 on NUC
STEPS TO REPRODUCE: 1. plugin usb which contains live image burned
2. configure device BIOS to firstly boot from USB if necessary
3. boot the device and select option "Install"  from boot menu
4. proceed through default install process
5. Remove USB, and reboot into new installed system.


Note: 

If installation was successfully completed and received this message ""(sdx): Volume was not properly unmounted...Please run fsck."" ignore it because this was whitelisted according to bug 9652.

EXPECTED OUTCOME: 1. User can choose install system from usb stick onto harddisk from boot menu or command line option
2. Installed system can boot up

Actual Results: When "Graphics console install" is selected, boot process start but not progress, some issues detecting USB, last message says:
"kernel validity duration has 14390 minute(s) remaining"
This happens selecting "Graphics console Install" or "Serial console install"
Screenshoot attached.
Comment 1 Juan Ramos 2016-11-04 19:43:20 UTC
(In reply to comment #0)
> Created attachment 3525 [details]
> Install on NUC
> 
> STATUS: IDLE
> BUILD: meta-intel-6.0 : 6c9f6b5f70ab3ee194b2c2c6f3bd462c994848fa
> ENVIRONMENT: corei7 on NUC
> STEPS TO REPRODUCE: 1. plugin usb which contains live image burned
> 2. configure device BIOS to firstly boot from USB if necessary
> 3. boot the device and select option "Install"  from boot menu
> 4. proceed through default install process
> 5. Remove USB, and reboot into new installed system.
> 
> 
> Note: 
> 
> If installation was successfully completed and received this message
> ""(sdx): Volume was not properly unmounted...Please run fsck."" ignore it
> because this was whitelisted according to bug 9652.
> 
> EXPECTED OUTCOME: 1. User can choose install system from usb stick onto
> harddisk from boot menu or command line option
> 2. Installed system can boot up
> 
> Actual Results: When "Graphics console install" is selected, boot process
> start but not progress, some issues detecting USB, last message says:
> "kernel validity duration has 14390 minute(s) remaining"
> This happens selecting "Graphics console Install" or "Serial console install"
> Screenshoot attached.

Image: core-image-sato-sdk-intel-corei7-64.hddimg downloaded from:
http://yocto-ab-master.jf.intel.com/pub/releases/yocto-2.2.rc1/machines/
Comment 2 California Sullivan 2016-11-07 19:05:33 UTC
This is a combination of being in legacy boot mode and the issue described in bug 9525.

Because you're in legacy boot mode and using an iso, you don't have RMC, and you get the default kernel command line, which includes console=ttyS0. With the 4.8 kernel the install prompt is going to serial if that console entry exists on the kernel command line, instead of the last console= defined like on previous kernels.

For now you can work around this by removing console=ttyS0 entries from the kernel command line. You could also change to UEFI boot mode.

*** This bug has been marked as a duplicate of bug 9525 ***