Re: PinePro64 does not go past mountroot

Archimedes Gaviola <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <CAJFbk7GXvhEE=0E+Zp8DGHGb8Av9r=2XeE1nbKXZDrWE7NpuoA@mail.gmail.com>
On Thu, Aug 3, 2023 at 11:44 AM José Pérez <[email protected]> wrote:

> Hi,
> want to give my PinePro64 another option with FreeBSD, so I downloaded
> FreeBSD-14.0-CURRENT-arm64-aarch64-PINE64-20230727-474708c334a7-264358.img
> and dd'd it to a USB drive.
>
> The Pine boots from SPI, flashed with U-Boot 2021.04-11556-g9ecacf77d2
> and make it to FreeBSD, but does not go past mountroot:
> ...
> WARNING: WITNESS option enabled, expect reduced performance.
> ugen2.1: <Generic EHCI root HUB> at usbus2
> Trying to mount root from ufs:/dev/ufs/rootfs [rw]...
> uhub0 on usbus2
> uhub0: <Generic EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on
> usbus2
> ugen4.1: <Synopsys XHCI root HUB> at usbus4
> ugen5.1: <Synopsys XHCI root HUB> at usbus5
> ugen3.1: <Generic OHCI root HUB> at usbus3
> ugen1.1: <Generic OHCI root HUB> at usbus1
> uhub1 on usbus4
> uhub1: <Synopsys XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on
> usbus4
> uhub2 on usbus5
> uhub4 on usbus3
> uhub2: <Synopsys XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on
> usbus5
> uhub4: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on
> usbus3
> uhub3 on usbus1
> uhub3: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on
> usbus1
> ugen0.1: <Generic EHCI root HUB> at usbus0
> uhub5 on usbus0
> uhub5: <Generic EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on
> usbus0
> uhub4: 1 port with 1 removable, self powered
> uhub3: 1 port with 1 removable, self powered
> uhub1: 2 ports with 2 removable, self powered
> uhub2: 2 ports with 2 removable, self powered
> uhub0: 1 port with 1 removable, self powered
> uhub5: 1 port with 1 removable, self powered
> mountroot: waiting for device /dev/ufs/rootfs...
> Mounting from ufs:/dev/ufs/rootfs failed with error 19.
>
> Loader variables:
>    vfs.root.mountfrom=ufs:/dev/ufs/rootfs
>    vfs.root.mountfrom.options=rw
>
> Manual root filesystem specification:
>    <fstype>:<device> [options]
>        Mount <device> using filesystem <fstype>
>        and with the specified (optional) option list.
>
>      eg. ufs:/dev/da0s1a
>          zfs:zroot/ROOT/default
>          cd9660:/dev/cd0 ro
>            (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
>
>    ?               List valid disk boot devices
>    .               Yield 1 second (for background tasks)
>    <empty line>    Abort manual input
>
> mountroot> ?
>
> List of GEOM managed disk devices:
>
>
> mountroot>
>
>
> Can anyone suggest how to solve this?
>
> Thank you.
>
>
>
> --
> José Pérez
>
>
Hi,

Though I'm not familiar with your hardware but did you see something like
umass*, pass* and da* for USB storage-related device drivers loaded upon
kernel boot-up? I could be wrong but it seems like the root filesystem
wasn't found because your USB storage driver is missing.

Thanks,
Archimedes
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.