U-boot still sees your mmc card as the default boot device. Try (in U-boot
prompt)

#setenv boot_targets usb0 mmc0 pxe dhcp
#saveenv
#printenv

On Sun, Apr 23, 2017 at 4:29 AM, Patrick YU <patric...@yhk.name> wrote:

> Thanks Soko -- setting to default boot on the OpenBSD partition didn't
> help.
> Instead, I had to specify the root device manually to the boot loader
> using the -a flag.  Without such, I notice the root device is still
> pointing to the SD card ??
>
>> boot device: sd0
>>> root on rd0a swap on rd0b dump on rd0b
>>>
>>
> At the bootloader, I use the flag -a
> OpenBSD/armv7 BOOTARM 0.5
> boot> b sd0a:/bsd -a
> Then OpenBSD proposes the root device to be sd0a, for me to confirm.  How
> can I fix this ?
>
> Issue now is pfctl invocations in /etc/rc is triggering
> pfctl: /dev/pf: Device not configured --> does the device pf in
> /etc/MAKEDEV require a different numbers for the my A10 device ??
>
> The /etc/rc boot-up continued with failed start-up of daemons:
>    starting early daemons: syslogd(failed) pflogd(failed).
>    starting RPC daemons:.
>    savecore: can't find device 20/14778624
>    checking quotas: done.
>    kvm_mkdb: can't open /dev/ksyms
>    clearing /tmp
>    kern.securelevel: 0 -> 1
>    creating runtime link editor directory cache.
>    preserving editor files.
>    starting network daemons: sshd(failed) smtpd(failed) sndiod(failed).
>    ifconfig: SIOCSIFGATTR: No such file or directory
>    starting local daemons: cron(failed).
>
> I had to commented-out  ntpd to let the boot-up arriving at the login:
> prompt !!
>
> Any advice / comment is appreciated !
>
> -- Patrick
> On 2017-04-21 09:22, soko.tica wrote:
>
>> There is a Linux files partition on your sd0 that is marked bootable. It
>> shouldn't be there. FAT32L should, I believe, be marked bootable.
>>
>> You probably haven't cleared up the disk before the installation properly.
>> Clear it by fdisk, mark all partitions blank (zero) and repeat the
>> installation.
>>
>> On Thu, Apr 20, 2017 at 5:26 AM, Patrick YU <patrickyu> wrote:
>>
>> After successfully installing on an Olinuxino A10 board via the SD card
>>> onto a Toshiba disk with the following MBR partition table, I rebooted
>>> and
>>> again offered to perform another OpenBSD installation.  Why ?  Thanks in
>>> advance for any enlightenment !
>>>
>>> -- Patrick
>>>
>>> # fdisk sd0
>>> Disk: sd0       geometry: 121601/255/63 [1953525168 Sectors]
>>> Offset: 0       Signature: 0xAA55
>>>             Starting         Ending         LBA Info:
>>>  #: id      C   H   S -      C   H   S [       start:        size ]
>>> ------------------------------------------------------------
>>> -------------------
>>>  0: 83      0  32  33 -  58743 224 41 [        2048:   943718400 ] Linux
>>> files*
>>>  1: 0C  58743 224 42 -  58746 109 51 [   943720448:       40960 ] FAT32L
>>>  2: A6  58746 109  52 - 118795 153  14 [   943761408:   964689920 ]
>>> OpenBSD
>>>  3: 00      0   0   0 -      0   0   0 [           0:           0 ]
>>> unused
>>>
>>> U-Boot 2017.03 (Apr 03 2017 - 11:14:00 -0600) Allwinner Technology
>>>
>>> CPU:   Allwinner A10 (SUN4I)
>>> Model: Olimex A10-OLinuXino-LIME
>>> I2C:   ready
>>> DRAM:  512 MiB
>>> MMC:   SUNXI SD/MMC: 0
>>> *** Warning - bad CRC, using default environment
>>>
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> SCSI:  Target spinup took 0 ms.
>>> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
>>> flags: ncq stag pm led clo only pmp pio slum part ccc apst
>>> Net:   eth0: ethernet@01c0b000
>>> starting USB...
>>> USB0:   USB EHCI 1.00
>>> USB1:   USB OHCI 1.0
>>> USB2:   USB EHCI 1.00
>>> USB3:   USB OHCI 1.0
>>> scanning bus 0 for devices... 2 USB Device(s) found
>>> scanning bus 2 for devices... 1 USB Device(s) found
>>> scanning bus 1 for devices... 1 USB Device(s) found
>>> scanning bus 3 for devices... 2 USB Device(s) found
>>>        scanning usb for storage devices... 0 Storage Device(s) found
>>> Hit any key to stop autoboot:  0
>>> switch to partitions #0, OK
>>> mmc0 is current device
>>> Scanning mmc 0:1...
>>> Found EFI removable media binary efi/boot/bootarm.efi
>>> reading efi/boot/bootarm.efi
>>> 64684 bytes read in 41 ms (1.5 MiB/s)
>>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>>> ## Starting EFI application at 42000000 ...
>>> Scanning disks on scsi...
>>> Scanning disks on usb...
>>> Scanning disks on mmc...
>>> MMC Device 1 not found
>>> MMC Device 2 not found
>>> MMC Device 3 not found
>>> Found 6 disks
>>>
>>> OpenBSD/armv7 BOOTARM 0.5
>>>>
>>>>>
>>>>> boot>
>>>>
>>> cannot open sd0a:/etc/random.seed: No such file or directory
>>> booting sd0a:/bsd: 2151556+7983908+438824 [80+301248+143324]=0xa84fd4
>>>
>>> ...
>>> sd0 at scsibus0 targ 0 lun 0: <ATA, TOSHIBA MQ01ABD1, AX00> SCSI3
>>> 0/direct
>>> fixed naa.5000039514a065a8
>>> sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
>>> ...
>>> sd1 at scsibus1 targ 1 lun 0: <Sandisk, SA08G, 0021> SCSI2 0/direct
>>> removable
>>> sd1: 7420MB, 512 bytes/sector, 15196160 sectors
>>> axe0 at uhub0 port 1 configuration 1 interface 0 "ASIX Electronics
>>> AX88772B" rev 2.00/0.01 addr 2
>>> axe0: AX88772B, address 00:00:00:00:00:01
>>> ukphy0 at axe0 phy 16: Generic IEEE 802.3u media interface, rev. 1: OUI
>>> 0x000ec6, model 0x0008
>>> boot device: sd0
>>> root on rd0a swap on rd0b dump on rd0b
>>> WARNING: preposterous clock chip time
>>> WARNING: CHECK AND RESET THE DATE!
>>> erase ^?, werase ^W, kill ^U, intr ^C, status ^T
>>>
>>> Welcome to the OpenBSD/armv7 6.1 installation program.
>>> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? shell
>>>
>>>

Reply via email to