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 > >
