Can't get 11.0-RELEASE to boot on Banana PI M3
Mark Millard
markmi at dsl-only.net
Fri Dec 2 23:35:53 UTC 2016
On 2016-Dec-2, at 3:58 AM, Michael Sperber <sperber at deinprogramm.de> wrote:
> Mark Millard <markmi at dsl-only.net> writes:
>
>> But none of the explains why it could not mount the root
>> file system in the first place and the attempt may just
>> fail as well.
>
> A closer look revealed this:
>
> da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
> da0: <USB TO I DE/SATA Device 0016> Fixed Direct Access SPC-2 SCSI device
> da0: Serial Number 000000000033
> da0: 40.000MB/s transfers
> da0: Attempt to query device size failed: NOT READY, Medium not present
> da0: quirks=0x2<NO_6_BYTE>
/dev/da0 is not the same as /dev/mmcsd0 . /dev/da0 is the
interface to the SATA port. That hardware is accessed over
USB on the BPi-M3.
I get the same messages as you report, even the fake Serial
Number. I do not have a SATA drive plugged in. With a SATA
drive in place it likely would show differently.
I do not have anything plugged into the lower USB port
currently.
I've a SSD that I use as the root file system plugged
into the upper USB port and it shows:
umass1 on uhub2
umass1: <OWC Envoy Pro mini, class 0/0, rev 2.10/1.00, addr 4> on usbus0
da1 at umass-sim1 bus 1 scbus1 target 0 lun 0
da1: <OWC Envoy Pro mini 0> Fixed Direct Access SPC-4 SCSI device
da1: Serial Number <OMITTED>
da1: 40.000MB/s transfers
da1: 228936MB (468862128 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
There is also the information:
# dmesg | grep usbphy
awusbphy0: <Allwinner USB PHY> on simplebus0
# dmesg | grep umass
umass0 on uhub2
umass0: <vendor 0x05e3 USB Storage, class 0/0, rev 2.00/0.16, addr 3> on usbus0
da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
umass1 on uhub2
umass1: <OWC Envoy Pro mini, class 0/0, rev 2.10/1.00, addr 4> on usbus0
da1 at umass-sim1 bus 1 scbus1 target 0 lun 0
(But I have that external root file system SSD plugged in
that causes the umass1, da2, and umass-sim1.)
> So maybe the SD card was just slow.
/dev/da0 is not the same as where the SD card is plugged in.
Those messages above are not about the sd card.
/dev/mmcsd0 is for where the sd card is plugged in. A normal
massage for mine looks like:
mmcsd0: 32GB <SDHC 00000 1.0 SN A1535564 MFG 09/2015 by 27 SM> at mmc0 50.0MHz/4bit/65535-block
/dev/mmcsd1 is for the 8 GByte emmc that is built in. To
my knowledge FreeBSD does not support it yet. It has a
message:
mmcsd1: 8GB <MMCHC 8WPD3R 0.0 SN E7C6641B MFG 01/2000 by 21 0x0000> at mmc1 50.0MHz/8bit/65535-block
(There are earlier messages that mention "mmc" but not "sd".
I'm not going to show them all. There are "a10_mmc1" error
messages involved for the 8 GByte emmc.)
> And indeed, with:
>
>> ufs:/dev/ufsid/582fa82db6b4890b
As stands this indirectly references /dev/mmcsd0 and the
sd card that is in it.
> I get to a login prompt.
Good but it is not clear why the selection was not
automatic.
> I tried this in /boot/loader.conf:
>
> kern.cam.boot_delay="10000"
> kern.cam.scsi_delay="3000"
>
> ... but that didn't help.
I do have the kern.cam.boot_delay line because
of the external SSD that I use for the root file
system. It was not needed for just using the
sd card that I'm using. (And the BPi-M3 has to
read from that sd card before the setting
applies.)
I do not have the scsi_delay line.
> Now, I see this:
>
> # dmesg | fgrep net
>
> awg0: <Allwinner Gigabit Ethernet> mem 0x1c30000-0x1c300ff on simplebus0
Other related messages. . .
# dmesg | grep rgephy
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy1: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
# dmesg | grep awg
awg0: <Allwinner Gigabit Ethernet> mem 0x1c30000-0x1c300ff on simplebus0
miibus0: <MII bus> on awg0
awg0: Ethernet address: f2:00:1a:f1:d9:c8
awg0: link state changed to DOWN
awg0: link state changed to UP
# dmesg | grep net
awg0: <Allwinner Gigabit Ethernet> mem 0x1c30000-0x1c300ff on simplebus0
awg0: Ethernet address: f2:00:1a:f1:d9:c8
I do not know why you do not get the "Ethernet address".
You might look for other related messages. For some of
the terminology used, see the above messages that I
report. There could be more that I've not noticed.
# more /etc/rc.conf
hostname="<SOME-NAME>"
ifconfig_awg0="DHCP"
sshd_enable="YES"
> ... but no Ethernet interface here:
>
> # ifconfig -a
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> inet 127.0.0.1 netmask 0xff000000
> groups: lo
> nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Mine shows a "awg0" and its information but it also
earlier showed what I reported above.
> Any ideas on that one?
Nothing specific.
> (BTW, thanks for your patience - very helpful!)
No problem.
> --
> Regards,
> Mike
===
Mark Millard
markmi at dsl-only.net
More information about the freebsd-arm
mailing list