Date: Sun, 7 Jul 2019 10:49:40 +0200 From: Michael Tuexen <tuexen@freebsd.org> To: Mark Linimon <linimon@lonesome.com> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: autobooting FreeBSD on Black Bird Message-ID: <E8CC4607-3D53-4FC5-8068-E327C44B9B8B@freebsd.org> In-Reply-To: <20190706210858.GA12978@lonesome.com> References: <0694EB91-05BD-4E98-BE6C-B1114D7DAE83@freebsd.org> <20190706181345.GB4111@lonesome.com> <9D0BD037-29F5-46CB-AF90-EE4C0572C625@freebsd.org> <20190706203613.GA11399@lonesome.com> <F4C1BCE1-A017-4A7E-AB2F-56D6F3C13076@freebsd.org> <20190706210858.GA12978@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 6. Jul 2019, at 23:08, Mark Linimon <linimon@lonesome.com> wrote: >=20 > On Sat, Jul 06, 2019 at 10:55:32PM +0200, Michael Tuexen wrote: >> Tried both of them. But I couldn't see any bootable device. >> Would a keyboard work in combination with petitboot using a monitor. >=20 > Well ... here's the sequence of what I did. >=20 > First, I ran it headless and talked to petitboot via = obmc-console-client. > I think that's how I did the actual install and config but I did not = keep > sufficiently detailed notes. I *do* know that I used the USB stick = for > the install image, no matter when I did it. >=20 > Later, I plugged in kbd/mouse/monitor and have since been booting > through that method. (That's how I learned the trick of "you can't > use k/m/m unless you boot petitboot via that method.) >=20 > I'm starting to worry that you have a damaged board. Try it with > k/m/m and see what happens. When connecting a Monitor, I do see a similar output as I see using = obmc-console-client. I finally see the Petitboot Menu. But the input (arrow up/down, return) = is not accepted from the keyboard. So the system stays there. It looks like USB support = is not enabled... Best regards Michael >=20 > mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E8CC4607-3D53-4FC5-8068-E327C44B9B8B>