Hi !

there is a very good reading at
http://www.undeadly.org/cgi?action=article&sid=20170409123528&mode=flat%20%EF%BF%BC
.

i only follow it .


sd card A USB card reader :Rpi3:micro sd card B in it's slot

at this state , i install openbsd into sd0 ( namely sd card A)

and reboot
at this state is the same
namely
sd card A USB card reader :Rpi3:micro sd card B in it's slot

but at boot

setenv boot_targets usb0 mmc0 pxe dhcp
saveenv
boot

-----------------
details is next

<power on>

minicom -s

Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Sep  6 2015, 19:49:19.
Port /dev/ttyUSB0, 14:15:36

Press CTRL-A Z for help on special keys



U-Boot 2017.03 (Apr 01 2017 - 04:27:09 -0600)

DRAM:  944 MiB
RPI 3 Model B (0xa02082)
MMC:   bcm2835_sdhci: 0
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

In:    serial
Out:   lcd
Err:   lcd

Net:   Net Initialization Skipped

No ethernet found.

starting USB...

USB0:   Core Release: 2.80a

scanning bus 0 for devices... 4 USB Device(s) found

       scanning usb for storage devices... 1 Storage Device(s) found

       scanning usb for ethernet devices... 1 Ethernet Device(s) found

Hit any key to stop autoboot:  0

U-Boot> setenv boot_targets usb0 mmc0 pxe dhcp   <---######################

U-Boot> saveenv <---######################

Saving Environment to FAT...

writing uboot.env

Error: Invalid FAT entry: 0xffffffe2

Invalid FAT entry

FAT: Misaligned buffer address (000000003ab2ab50)

sdhci_send_command: MMC: 0 busy timeout increasing to: 200 ms.

sdhci_send_command: MMC: 0 busy timeout increasing to: 400 ms.

done

U-Boot> boot    <---######################



USB device 0:

    Device 0: Vendor: MXT-USB Rev: 1308 Prod: Storage Device

            Type: Removable Hard Disk

            Capacity: 15343.0 MB = 14.9 GB (31422464 x 512)

... is now current device

Scanning usb 0:1...

Found EFI removable media binary efi/boot/bootaa64.efi

reading efi/boot/bootaa64.efi

75737 bytes read in 76 ms (972.7 KiB/s)

## Starting EFI application at 01000000 ...

Scanning disks on usb...

Scanning disks on mmc...

MMC Device 1 not found

MMC Device 2 not found

MMC Device 3 not found

Found 5 disks

>> OpenBSD/arm64 BOOTAA64 0.2

boot>

booting sd0a:/bsd: 3734688+568700+500888+672784 [86+438360+232975]=0x7c2c68

[ using 672704 bytes of bsd ELF symbol table ]

Copyright (c) 1982, 1986, 1989, 1991, 1993

        The Regents of the University of California.  All rights reserved.

Copyright (c) 1995-2017 OpenBSD. All rights reserved.
https://www.OpenBSD.org


OpenBSD 6.1 (GENERIC) #0: Sun Apr  2 17:05:03 AEST 2017

    j...@arm64.jsg.id.au:/usr/src/sys/arch/arm64/compile/GENERIC

real mem  = 989855744 (944MB)

avail mem = 931606528 (888MB)

mainbus0 at root: Raspberry Pi 3 Model B Rev 1.2

simplefb0 at mainbus0: 656x416

wsdisplay0 at simplefb0 mux 1

wsdisplay0: screen 0 added (std, vt100 emulation)

simplebus0 at mainbus0: "soc"

bcmintc0 at simplebus0

bcmdog0 at simplebus0

pluart0 at simplebus0

com0 at simple�].�.r��6550, no workingcom0: console

dwctwo0 at simplebus0

agtimer0 at simplebus0: tick rate 19200 KHz

simplebus1 at mainbus0: "clocks"

usb0 at dwctwo0: USB revision 2.0

uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
2.00/1.01
uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard Microsystems
produc2
smsc0 at uhub1 port 1 configuration 1 interface 0 "Standard Microsystems
SMSC953
smsc0: address b8:27:eb:c3:cc:1a

ukphy0 at smsc0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x0001fc
umass0 at uhub1 port 2 configuration 1 interface 0 "MXTronics MXT USB
Device" r4
umass0: using SCSI over Bulk-Only

scsibus0 at umass0: 2 targets, initiator 0

sd0 at scsibus0 targ 1 lun 0: <MXT-USB, Storage Device, 1308> SCSI0
0/direct ree
sd0: 15343MB, 512 bytes/sector, 31422464 sectors

vscsi0 at root

scsibus1 at vscsi0: 256 targets

softraid0 at root

scsibus2 at softraid0: 256 targets

bootfile: sd0a:/bsd

boot device: sd0

root on sd0a (a81499ded4c64177.a) swap on sd0b dump on sd0b

WARNING: /mnt was not properly unmounted

WARNING: CHECK AND RESET THE DATE!

Automatic boot in progress: starting file system checks.

/dev/sd0a (a81499ded4c64177.a): 1437 files, 21388 used, 223443 free (35
frags, )
/dev/sd0a (a81499ded4c64177.a): MARKING FILE SYSTEM CLEAN

/dev/sd0l (a81499ded4c64177.l): file system is clean; not checking

/dev/sd0d (a81499ded4c64177.d): file system is clean; not checking

/dev/sd0f (a81499ded4c64177.f): file system is clean; not checking

/dev/sd0g (a81499ded4c64177.g): file system is clean; not checking

/dev/sd0h (a81499ded4c64177.h): file system is clean; not checking

/dev/sd0k (a81499ded4c64177.k): file system is clean; not checking

/dev/sd0j (a81499ded4c64177.j): file system is clean; not checking

/dev/sd0e (a81499ded4c64177.e): file system is clean; not checking

setting tty flags

pf enabled

starting network

DHCPREQUEST on smsc0 to 255.255.255.255

DHCPACK from 192.168.80.1 (c8:3a:35:3b:c4:d0)

bound to 192.168.80.102 -- renewal in 43200 seconds.

reordering libraries:

 done.

openssl: generating isakmpd/iked RSA keys... done.

ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519

starting early daemons: syslogd pflogd ntpd.

starting RPC daemons:.

savecore: no core dump

checking quotas: done.

clearing /tmp

kern.securelevel: 0 -> 1

creating runtime link editor directory cache.

preserving editor files.

starting network daemons: sshd smtpd sndiod.

Path to firmware: http://firmware.openbsd.org/firmware/6.1/

No devices found which need firmware files to be downloaded.

starting local daemons: cron.

Sun Apr  2 16:26:36 JST 2017



OpenBSD/arm64 (foo.my.domain) (console)



login: root

Password:

OpenBSD 6.1 (GENERIC) #0: Sun Apr  2 17:05:03 AEST 2017



Welcome to OpenBSD: The proactively secure Unix-like operating system.



Please use the sendbug(1) utility to report bugs in the system.

Before reporting a bug, please try to reproduce it with the latest

version of the code.  With bug reports, please try to ensure that

enough information to reproduce the problem is enclosed, and if a

known fix for it exists, include that as well.



You have new mail.

#


----------
regards

Reply via email to