PCEngines APU2c2

[Justin Sherrill]

By default I think the console goes to serial and the installer goes
to the first tty.  I'm not sure how to configure it differently.

You may be able to get it to auto-install using rconfig, though I have
not tried something like that before.  Alternately, install DragonFly
on the same drive in different hardware and transfer the drive over?

On Sat, Jun 11, 2016 at 10:56 PM, Chuck Musser <cmusser at sonic.net> wrote:
> Hi,
>
> I'm trying to install DragonFly on an apu2c2 board. This is a AMD-based system with Intel i211 Ethernet adapters and a mSATA interface. To do the install, I made a bootable USB stick with a 4.5 image (from today, Jun 11) and I'm interacting with the board over its serial console. It boots from the stick--you have set the baud rate to 115200 to interact with the BIOS, then change it to 9600 once you boot. When you log in as "installer", it says:
>
> login: installer
> Last login: Tue May  3 13:42:29 2016 on ttyd0
> Copyright (c) 2003-2016 The DragonFly Project.
> Copyright (c) 1992-2003 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>         The Regents of the University of California. All rights reserved.
>
> DragonFly v4.5.0.1187.g8bbe5-DEVELOPMENT (X86_64_GENERIC) #0: Sat Jun 11 10:54:11 UTC 2016
>
> Welcome to DragonFly!
>
> Starting installer.  Reading /etc/pfi.conf ...
> /usr/sbin/installer: cannot create /dev/ttyv0: Input/output error
> /usr/sbin/installer: cannot open /dev/ttyv0: No such file or directory
> Installer started
> -----------------
> + Creating DFUI connection on ``9999''
>
> + Connecting on ``9999''
>
> And it stays there for several minutes. After that:
>
> May  3 13:49:51 getty[968]: open /dev/ttyv0: No such file or directory
> May  3 13:49:51 getty[974]: open /dev/ttyv7: No such file or directory
> May  3 13:49:51 getty[971]: open /dev/ttyv4: No such file or directory
> May  3 13:49:51 getty[973]: open /dev/ttyv6: No such file or directory
> May  3 13:49:51 getty[970]: open /dev/ttyv3: No such file or directory
> May  3 13:49:51 getty[969]: open /dev/ttyv2: No such file or directory
> May  3 13:49:51 getty[972]: open /dev/ttyv5: No such file or directory
> May  3 13:49:51 getty[1000]: open /dev/ttyv6: No such file or directory
> May  3 13:49:51 getty[999]: open /dev/ttyv7: No such file or directory
> May  3 13:49:51 getty[1003]: open /dev/ttyv5: No such file or directory
> May  3 13:49:51 getty[1002]: open /dev/ttyv3: No such file or directory
> May  3 13:49:51 getty[1001]: open /dev/ttyv4: No such file or directory
> May  3 13:49:51 getty[1005]: open /dev/ttyv0: No such file or directory
> May  3 13:49:51 getty[1004]: open /dev/ttyv2: No such file or directory
>
> If you log in as "root", you can see that it recognizes the mSATA device (it's ad4 here). The Ethernet interfaces are discovered and work (I was able to SSH out, after assigning an address to one). So it seems like it might work, given some tweaks to the install process. Anyone know what might get the installer to work?
>
> Thanks,
>
> Chuck