RE: mountroot> while booting r255342 memstick

> Also, if you can try the 9.2-RC4 image, that would also be appreciated.
> If this is a problem only with 10.0, this is something re_at_ and hselasky_at_
> (bcc'd) needs to be aware of.
> 
> Glen

tried 9.2-RC4 image, (64bit) memstick
same error,
mountroot> ?
List of GEOM managed disk devices:
  ada0s1 ada0 cd0

no diksid compare to 10 current.

and i found one interesting information while scrolling up

let me ascii my laptop usb port below first.
[------] usbus0 top, USB 3.0 (blue)
[------] usbus2 middle, USB 2.0 (black)
[------] usbus1 bottom, USB 2.0 (black)

xhci0: <Intel Panther Point USB 3.0 controller> // my usb 3.0 hole
usbus0 on xhci0
ehci0: <Intel Panther Point USB 2.0 controller> // my usb 2.0 hole first hole
usbus1 on ehci0
ehci1: <Intel Panther Point USB 2.0 controller> // my usb 2.0 hole second hole
usbus2 on ehci1

ugen 1.3: <Kingston> at usbus1 // assume this info is correct
umass0:2:0:-1: Attached to scbus2 // who is using scbus1 and scbus0

i took out my pendrive from usbus1 and plug it into usbus2, off , wait a few second and on the machine since idk how to reboot from mountpoint>.

below the after rebooted info,

ugen0.2: <Kingston> at usbus0 // why?
umass0: <Kingston DT 101 G2, class 0/0, rev 2.00/1.00, addr 1> on usbus0

why usbus0? I didn't plug into USB 3.0?

I scrolled up and this info surprise me, maybe a bug.
xhci0: <Intel Panther Point USB 3.0 controller> // my usb 3.0 hole
usbus0 on xhci0

Is this some sort of error during usbus number assigned?

I hope this information could help everybody to diagnose and solve this issue.

 
> On Fri, Sep 13, 2013 at 11:09:30AM +0900, Lundberg, Johannes wrote:
> > Does it work with the 9.1 image? If it does, you probably have the same
> > problem as I do with the new Macbook Air.
> > Optimisations made to the xhci driver causes it to fail. What I've done is
> > to create a new install image with sys/dev/usb/controller/xhci* reverted
> > back to 243780.
> > 
> > --
> > Johannes Lundberg
> > Project leader and lead developer of Mirama OS (previously Viking OS)
> > BRILLIANTSERVICE CO., LTD.
> > 
> > My blog <http://brilliantobjc.blogspot.com>
> > Mirama homepage <http://www.brilliantservice.co.jp/viking/>
> > blog<http://hmdviking.blogspot.jp>
> > Company homepage <http://www.brilliantservice.co.jp>
> > 
> > 
> > On Thu, Sep 12, 2013 at 11:14 AM, Nathan Whitehorn
> > <nwhitehorn_at_freebsd.org>wrote:
> > 
> > > On 09/11/13 20:42, Uzumaki Naruto wrote:
> > >
> > >> If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't
> > >>> support GPT disk type, because OEM Acer only gave GPT supported BIOS for
> > >>> model that pre-loaded with Windows 8.
> > >>>
> > >> Maybe it helps to clarify, this laptop got no UEFI firmware, I could
> > >> convert my hard disk to GPT type using diskpart command, but the
> > >> functionality to boot from GPT partition is unavailable through BIOS.
> > >>
> > >>
> > > Booting from GPT does not require BIOS support. BIOSes don't (or aren't
> > > supposed to -- some broken ones do) parse the partition table at all.
> > > -Nathan
> > >
> > > ______________________________**_________________
> > > freebsd-current_at_freebsd.org mailing list
> > > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current<http://lists.freebsd.org/mailman/listinfo/freebsd-current>
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_**
> > > freebsd.org <freebsd-current-unsubscribe_at_freebsd.org>"
> > >