Problem to boot Chrome OS image (kernel 3.14) by USB on Lenovo T430

[lukaha Liu]

Hi folks
    I built chromium image follow the instruction from http://www.chromium.org/chromium-os/developer-guide, and flash image to usb disk. but there is nothing coming out after "decompress linux" message when I try to boot it. I saw the screen light up, I guess this issue may be related to VGA driver.

I am using Lenovo T430 come with Intel Core i5, the display interface is Intel® HD Graphics 4000 and NVIDIA® NVS 5400M Graphics with Optimus™ Technology.

The issue was not happen on the image I had built two months ago, but after I re-sync the chromium source, I got this issue.

Because there was no message pop out in my screen, so I can't provide any log.

Is any one have this issue? Could someone told me how to fix this issue?

Here is my chrome build version information.

ChromeOS version information:
    CHROME_BRANCH=41
    CHROME_VERSION=
    CHROMEOS_VERSION_STRING=6469.0.2014_11_14_1642
    CHROME_BASE=

Thanks

Regards,

Alan Liu

[Prathmesh Prabhu Chromium]

Hi Alan,

To check whether this is video driver issue, you can try building with USE="chromeless_tty"

So, 

  USE="chromeless_tty" ./build_packages ...

  USE="chromeless_tty" ./build_image ...

Also, I'd like to know what boot flow you're using. Do you see a grub menu when you boot (efi boot), or does it directly jump to the "decompressing kernel" stage (syslinux boot).

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[lukaha Liu]

Hi Prathmesh

After I rebuilt image by your comment below.  The Chromium image in USB can boot my T430, but there is no GUI display on screen. It is better now I can get into console mode to get log for debug.
I saw few crash memory dump within kernel log, do you think they are related to VGA? Are they know issue and have solution yet?

>>Also, I'd like to know what boot flow you're using. Do you see a grub menu when you boot (efi boot), or does it directly jump to the "decompressing kernel" stage (syslinux boot).

I post the message here.

Loading VmlinuZ. A..................
.... ready

early console in setup code
early console in decompress_kernel
KASLR using RDRAND RDTSC..
Decompressing Linux..........

[    0.224651] [drm] Driver supports precise vblank timestamp query.
[    0.238052] ------------[ cut here ]------------
[    0.238060] WARNING: CPU: 1 PID: 1 at /mnt/host/source/src/third_party/kernel/3.14/drivers/gpu/drm/drm_modes.c:119 drm_mode_probed_add+0x30/0x4d()
[    0.238061] Modules linked in:
[    0.238065] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.14.0 #2
[    0.238066] Hardware name: LENOVO 2347EP7/2347EP7, BIOS G1ETA5WW (2.65 ) 04/15/2014
[    0.238067]  0000000000000000 00000000caacfc75 ffff8802355498a8 ffffffffb2f78439
[    0.238070]  0000000000000000 ffff8802355498e0 ffffffffb2a3c605 ffffffffb2cbde50
[    0.238072]  ffff88023469a000 ffff880235659c00 00000000000003a2 ffff880235549a10
[    0.238074] Call Trace:
[    0.238079]  [<ffffffffb2f78439>] ? dump_stack+0x45/0x56
[    0.238082]  [<ffffffffb2a3c605>] ? warn_slowpath_common+0x7f/0x98
[    0.238085]  [<ffffffffb2cbde50>] ? drm_mode_probed_add+0x30/0x4d
[    0.238088]  [<ffffffffb2a3c716>] ? warn_slowpath_null+0x1a/0x1c
[    0.238090]  [<ffffffffb2cbde50>] ? drm_mode_probed_add+0x30/0x4d
[    0.238092]  [<ffffffffb2cc0903>] ? do_detailed_mode+0x337/0x383
[    0.238095]  [<ffffffffb2e19730>] ? i2c_trylock_adapter+0xe/0x32
[    0.238097]  [<ffffffffb2e19760>] ? i2c_transfer+0xc/0x7b
[    0.238099]  [<ffffffffb2cc05cc>] ? do_established_modes+0xc6/0xc6
[    0.238101]  [<ffffffffb2cbebb1>] ? drm_for_each_detailed_block+0x39/0x101
[    0.238103]  [<ffffffffb2cc1838>] ? drm_add_edid_modes+0xf5/0x5a4
[    0.238106]  [<ffffffffb2d074ae>] ? intel_lvds_init+0x2e0/0x6cc
[    0.238108]  [<ffffffffb2d03b6b>] ? intel_modeset_init+0x788/0xd6f
[    0.238111]  [<ffffffffb2cd43ec>] ? i915_driver_load+0xa26/0xcac
[    0.238116]  [<ffffffffb2cb3182>] ? drm_get_minor+0x198/0x1dd
[    0.238118]  [<ffffffffb2cb3280>] ? drm_dev_register+0xb9/0x122
[    0.238120]  [<ffffffffb2cb5537>] ? drm_get_pci_dev+0x103/0x1ce
[    0.238122]  [<ffffffffb2cd1871>] ? i915_pci_probe+0x4c/0x6d
[    0.238125]  [<ffffffffb2c1b717>] ? pci_device_probe+0x73/0xd4
[    0.238128]  [<ffffffffb2d5e413>] ? driver_probe_device+0xa9/0x1f4
[    0.238129]  [<ffffffffb2d5e621>] ? __driver_attach+0x5d/0x7f
[    0.238131]  [<ffffffffb2d5e5c4>] ? __device_attach_driver+0x66/0x66
[    0.238133]  [<ffffffffb2d5d581>] ? bus_for_each_dev+0x89/0xb1
[    0.238135]  [<ffffffffb2d5dfc8>] ? driver_attach+0x1e/0x20
[    0.238137]  [<ffffffffb2d5dbb5>] ? bus_add_driver+0xe9/0x1ec
[    0.238139]  [<ffffffffb2d5ed2b>] ? driver_register+0x8e/0xca
[    0.238142]  [<ffffffffb2c1ab56>] ? __pci_register_driver+0x60/0x63
[    0.238145]  [<ffffffffb35031c5>] ? ttm_init+0x60/0x60
[    0.238147]  [<ffffffffb2cb566b>] ? drm_pci_init+0x69/0xea
[    0.238148]  [<ffffffffb35031c5>] ? ttm_init+0x60/0x60
[    0.238150]  [<ffffffffb350322f>] ? i915_init+0x6a/0x6c
[    0.238153]  [<ffffffffb2a002c1>] ? do_one_initcall+0x93/0x12d
[    0.238156]  [<ffffffffb2a57300>] ? parameqn+0x14/0x3b
[    0.238158]  [<ffffffffb2a574cb>] ? parse_args+0x180/0x23b
[    0.238161]  [<ffffffffb34d0ec3>] ? kernel_init_freeable+0x112/0x197
[    0.238163]  [<ffffffffb34d075d>] ? do_early_param+0x88/0x88
[    0.238166]  [<ffffffffb2f74a70>] ? rest_init+0x74/0x74
[    0.238168]  [<ffffffffb2f74a7e>] ? kernel_init+0xe/0xda
[    0.238171]  [<ffffffffb2f7cdec>] ? ret_from_fork+0x7c/0xb0
[    0.238173]  [<ffffffffb2f74a70>] ? rest_init+0x74/0x74
[    0.238177] ---[ end trace f4157ae51b96ebb0 ]---

[    0.616555] ------------[ cut here ]------------
[    0.616564] WARNING: CPU: 2 PID: 6 at /mnt/host/source/src/third_party/kernel/3.14/drivers/gpu/drm/i915/intel_display.c:765 intel_wait_for_vblank+0xdd/0x1ca()
[    0.616564] vblank wait timed out
[    0.616566] Modules linked in:
[    0.616569] CPU: 2 PID: 6 Comm: kworker/u16:0 Tainted: G        W    3.14.0 #2
[    0.616571] Hardware name: LENOVO 2347EP7/2347EP7, BIOS G1ETA5WW (2.65 ) 04/15/2014
[    0.616578] Workqueue: events_unbound async_run_entry_fn
[    0.616582]  0000000000000000 0000000071892233 ffff8802355676d8 ffffffffb2f78439
[    0.616584]  ffff880235567720 ffff880235567710 ffffffffb2a3c605 ffffffffb2cf8637
[    0.616587]  ffff880234548000 0000000000070040 000000000000025b 00000000fffb6e7d
[    0.616587] Call Trace:
[    0.616594]  [<ffffffffb2f78439>] ? dump_stack+0x45/0x56
[    0.616600]  [<ffffffffb2a3c605>] ? warn_slowpath_common+0x7f/0x98
[    0.616604]  [<ffffffffb2cf8637>] ? intel_wait_for_vblank+0xdd/0x1ca
[    0.616608]  [<ffffffffb2a3c67a>] ? warn_slowpath_fmt+0x5c/0x73
[    0.616612]  [<ffffffffb2cf8637>] ? intel_wait_for_vblank+0xdd/0x1ca
[    0.616616]  [<ffffffffb2cf935b>] ? intel_enable_pipe+0x138/0x143
[    0.616620]  [<ffffffffb2cfd788>] ? ironlake_crtc_enable+0x279/0xae9
[    0.616625]  [<ffffffffb2d0008b>] ? __intel_set_mode+0x10a6/0x1184
[    0.616629]  [<ffffffffb2d01ede>] ? intel_set_mode+0x14/0x2a
[    0.616632]  [<ffffffffb2d02884>] ? intel_crtc_set_config+0x888/0x925
[    0.616637]  [<ffffffffb2cb9378>] ? drm_mode_set_config_internal+0x58/0xe2
[    0.616641]  [<ffffffffb2ca9536>] ? restore_fbdev_mode+0x16f/0x191
[    0.616644]  [<ffffffffb2ca9568>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x10/0x12
[    0.616647]  [<ffffffffb2caab35>] ? drm_fb_helper_set_par+0x44/0x64
[    0.616653]  [<ffffffffb2c39f4f>] ? fbcon_init+0x328/0x426
[    0.616657]  [<ffffffffb2c92376>] ? visual_init+0xbb/0x110
[    0.616660]  [<ffffffffb2c93e94>] ? do_bind_con_driver+0x174/0x283
[    0.616664]  [<ffffffffb2c94479>] ? do_take_over_console+0x137/0x165
[    0.616668]  [<ffffffffb2c377dd>] ? do_fbcon_takeover+0x5b/0x9f
[    0.616672]  [<ffffffffb2c3b54c>] ? fbcon_event_notify+0x3d2/0x6fe
[    0.616676]  [<ffffffffb2a5c8ab>] ? notifier_call_chain+0x3c/0x5e
[    0.616680]  [<ffffffffb2a5cb13>] ? __blocking_notifier_call_chain+0x46/0x5f
[    0.616683]  [<ffffffffb2a5cb40>] ? blocking_notifier_call_chain+0x14/0x16
[    0.616686]  [<ffffffffb2c2ec29>] ? fb_notifier_call_chain+0x1b/0x1d
[    0.616689]  [<ffffffffb2c3033d>] ? register_framebuffer+0x2e3/0x317
[    0.616693]  [<ffffffffb2caaf2b>] ? drm_fb_helper_initial_config+0x3d6/0x4a1
[    0.616699]  [<ffffffffb2a09b94>] ? native_sched_clock+0x3a/0x3c
[    0.616703]  [<ffffffffb2d36244>] ? intel_fbdev_initial_config+0x1a/0x1c
[    0.616706]  [<ffffffffb2a5e3c4>] ? async_run_entry_fn+0x5f/0x115
[    0.616710]  [<ffffffffb2a53440>] ? process_one_work+0x1e0/0x308
[    0.616714]  [<ffffffffb2a54085>] ? worker_thread+0x13c/0x26f
[    0.616717]  [<ffffffffb2a53f49>] ? manage_workers.isra.28+0x1d7/0x1d7
[    0.616720]  [<ffffffffb2a58f75>] ? kthread+0xff/0x107
[    0.616723]  [<ffffffffb2a58e76>] ? __kthread_parkme+0x61/0x61
[    0.616728]  [<ffffffffb2f7cdec>] ? ret_from_fork+0x7c/0xb0
[    0.616730]  [<ffffffffb2a58e76>] ? __kthread_parkme+0x61/0x61
[    0.616732] ---[ end trace f4157ae51b96ebb2 ]---

Thanks

Regards,

Alan Liu

[Prathmesh Prabhu Chromium]

I've seen the intel module warning before. I strongly suspect that you already have console on VT2 at this point.

Try Ctr-Alt-F2. You should see a login prompt there.

As for display, the USE flag I mentioned actually disabled some video drivers as well as chromium. This does not solve your problem, merely let's me verify that there's nothing wrong with your boot sequence.

For digging deeper into what's actually wrong, please see vapier@'s comment above about missing video drivers. You'll mostly have to include additional video drivers in the kernel config. See http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/kernel-configuration

[lukaha Liu]

Yes, I can see login prompt after set "USE="chromeless_tty" flag by Ctrl-Alt-F2. I will try to include addtional video driver, will update status here.

By the way can I try USE="chromeless_tty" in command below?  Sorry to ask these stupid question.

ex: 

 USE="chromeless_tty" cros_workon start sys-kernel/chromeos-kernel-3_14
 USE="chromeless_tty" cros_workon_make sys-kernel/chromeos-kernel-3_14
 USE="chromeless_tty" cros_workon_make sys-kernel/chromeos-kernel-3_14 --install
 USE="chromeless_tty" cros_workon stop sys-kernel/chromeos-kernel-3_14

Thanks

Regards,

Alan Liu

[lukaha Liu]

Hi Prathmesh

>>For digging deeper into what's actually wrong, please see vapier@'s comment above about missing video drivers

   Sorry to bother you again, where can I find this information? I can't find it.

Thanks

Regards,

Alan Liu

[Prathmesh Prabhu Chromium]

On Tue, Nov 18, 2014 at 12:12 PM, lukaha Liu <liuku...@gmail.com> wrote:

Hi Prathmesh

>>For digging deeper into what's actually wrong, please see vapier@'s comment above about missing video drivers

   Sorry to bother you again, where can I find this information? I can't find it.

my bade: I must've crossed streams. I referenced non-existing comments.

But I still believe that you need to enable the correct drivers for your device.

[Joon Hyub Lee]

hey lukaha,

did you get it to work on T430?

I own a T430, and couldn't find an chrome os image that works for me.

If you did create a working image, would you like to share?

Thanks!