I actually tried a 6.2 amd64 snap downloaded fresh yesterday first, then tried 6.1-RELEASE after that. When I installed 6.1-RELEASE, I bailed from the installer, attached to the existing softraid crypto volume, nuked the first 1M of the SR_CRYPTO volume -- sd2c in my case -- as in the FAQ and then re-partioned it, rather than re-creating that volume from scratch again.
The first photo is from the 6.2 snapshot and is mostly just to highlight the hilarity that ensues when you run native resolution on a Retina display. The next two are all from that second install of 6.1-RELEASE, installed atop the crypto volume I created with the 2017-09-21 snap. I did verify that the cursor glitches and keyboard goes unresponsive at the UKC prompt ( from boot -c ) even from the install images for 6.1 and yesterday's snap. Also, before the "Copyright (c) 1982..." kernel message, I see this both in the install kernels and otherwise and it is also shown in the image dump: kbc: cmd word write error I just did a fresh install from yesterday's snapshot without using FDE or doing anything fancy. Results are now mostly the same except for a brief intermission of flashing-question-folder (missing EFI, I presume) followed by the bootloader (which I can type in) and the screen going blank and the system going unresponsive in the same way as I reported in my first post. I'm more systems and security guy than a developer, but I don't mind helping where I can. I'm just out of ideas, so additional suggestions are welcome. On Fri, Sep 22, 2017 at 12:09 PM, Dave Voutila <vouti...@gmail.com> wrote: > Ax0n, > > That RTC error seems to come from a system dependent startclocks() > function, but it was modified in August by jcs@ removing the logic > that would even print that very error: > https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/ > amd64/isa/clock.c.diff?r1=1.24&r2=1.25 > > Commit message mentions it's probably a red herring. > > In your linked pictures it looks like you're installing a 6.2 snapshot > (older than 11 August?), but the image with the RTC BIOS error says > 6.1. The plot is indeed thickening. :-) > > On Thu, Sep 21, 2017 at 10:01 PM, Ax0n <a...@h-i-r.net> wrote: > > This one *should* be identical to the one I've been issued by my employer > > (on which I'm running OS X) -- in that case, it has the NVidia GeForce GT > > 750M and the Intel Iris Pro. The Plot Thickens. > > > > There's an error about /etc/boot.conf. The keyboard works fine at the FDE > > prompt, and at the boot> prompt. There's an RTC BIOS diagnostic error > before > > the kernel loads. At the UCK prompt, the cursor is glitching and the > > keyboard is unresponsive. External keyboard isn't helping. > > > > Photos here, if it matters: https://imgur.com/a/iL6T0 > > > > On Thu, Sep 21, 2017 at 7:22 PM, Dave Voutila <vouti...@gmail.com> > wrote: > >> > >> ax0n, > >> > >> Is that a model with both integrated Intel gpu and dedicated Radeon > >> gpu? Maybe look at drm(4) and try removing the radeon driver since the > >> intel one should work fine. > >> > >> The intel drivers work great on my early-2015 MBP (i5 Broadwell), but > >> then again it doesn't have any dedicated graphics. > >> > >> -Dave > >> > >> On Thu, Sep 21, 2017 at 6:19 PM, Ax0n <a...@h-i-r.net> wrote: > >> > I have a Mid-2015 MacBook Pro that I'm trying to get OpenBSD on. I > >> > installed from the latest snapshot and from -RELEASE (installXX.fs > >> > written > >> > to SD card). The install goes fine (using an axen(4) USB dongle for > >> > connectivity) but upon reboot, it gets part way through, then the > screen > >> > goes blank with the backlight on. Although I can briefly see the > axen(4) > >> > attach, it doesn't seem to get an IP address if I let it sit around > for > >> > a > >> > few minutes. I can't get the dmesg, and I can't determine what the > last > >> > message is before the screen blanks. It doesn't appear to respond to > the > >> > keyboard. > >> > > >> > Has anyone gotten this working? Google is pointing me to a few posts > >> > from > >> > the likes of jcs@ and others about systems that are either slightly > >> > newer > >> > or slightly older than mine. Any suggestions on getting a good dmesg > out > >> > of > >> > it? Devices I should consider disabling from UKC to get this thing off > >> > the > >> > ground? > >> > > >> > TIA- > >> > ax0n > > > > >