[Bug 207251] stuck at "mountroot: waiting ..." on Toshiba Chromebook 2

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Feb 16 17:40:01 UTC 2016


            Bug ID: 207251
           Summary: stuck at "mountroot: waiting ..." on Toshiba
                    Chromebook 2
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: johnnywhishbone at gmail.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Created attachment 167084
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167084&action=edit
Image of the screen as it get stuck


i try to boot the usb-installer on an Toshiba Chromebook 2 (CB30-B-104) but it
get stuck the moment it tries to find the rootdevice it is booting from.
Keyboard input is not recognized. There seems to be no recognized usb devices.
It doesn't matter if i boot via usb stick or sd card and using amd64 or i386.

Neither OpenBSD, NetBSD nor DragonFly are booting, wether it is the most recent
snapshot. I also makes no difference using i386 or amd64. Linux is working
fine, so i could create a dmesg and lspci from there.

dmesg (Arch Linux): http://pastebin.com/FNEhYdsZ
lspci (Arch Linux): http://pastebin.com/pnFErXqG 

The Chromebook has a flashed Coreboot / SeaBIOS to enable booting alternative
OS besides ChromeOS.

I opened a bug on DragonFlyBSD yesterday, because the installer doesn't boot
too: http://bugs.dragonflybsd.org/issues/2890

Using the latest NetBSD snapshot the kernel crashes and i find myself thrown
into the debugger. This seems to be ACPI related.

idk if these bugs are related, because i'm using a Bay Trail device ("Swanky")
and those are Haswell devices:

Please let me know if i can provide more informations!

Thank you!
-- Ronny Schneider

You are receiving this mail because:
You are on the CC list for the bug.

More information about the freebsd-amd64 mailing list