>>>>> >>>>> Are you intending to run it as a graphical workstation? If not, try "b -c" >>>>> at the bootloader prompt, then "disable inteldrm" and "quit". That is >>>>> likely >>>>> to get it booting - if so, you should be able to get a dmesg. (The on-disk >>>>> kernel can be edited with "config -ef /bsd"). >>>>> >>>> That worked and I'm able to boot and reboot box into openbsd, thanks much. >>>> Exactly when will I >>>> have to modify the boot command (to disable inteldrm) in order to continue >>>> booting, assume >>>> every >>>> time I upgrade from one release to another, and any time I install a patch >>>> that relinks to >>>> another >>>> kernel? >>> >>> Whenever you change the kernel. Note that syspatch won't work with a >>> modified kernel. >>> >>>> One thing I'm having an issue understanding is why openbsd appears not to >>>> see the full 8GB of >>>> RAM >>>> in this box. >>>> >>>> Here is the dmesg: >>>> OpenBSD 6.3 (GENERIC.MP) #6: Sun Jul 29 11:50:15 CEST 2018 >>>> >>>> r...@syspatch-63-i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP >>> >>> That's a 32-bit kernel. Try amd64 instead, bay trail supports 64-bit. >>> Whoi knows, maybe video will work without further tweaking there. (It does >>> work on other J1900 machines). >>> >> Ok, got it working on amd64, but with same issue as before on inteldrm, >> still have to disable >> it: > > Are you able to try booting a snapshot kernel? If you download one and > save to / under a different name, you can do "boot (filename)" at the > boot loader prompt. It may not help but is a useful extra datapoint > (and you can test quickly that without updating the whole OS to a snapshot). >
I can try, I take it go to: /pub/OpenBSD/snapshots/amd64/ and download bsd.mp and copy it as bsd.snapshot (for example) to /, reboot and do a "boot bsd.snapshot", then report back. I've never followed current so am unfamiliar with this, but think I've got it down... > If it still doesn't help, best I can suggest at this point is to send a > mail to b...@openbsd.org with the information from sendbug (run as root > to get some pci information etc that is only available as root). If mail > is setup on the system you can run it directly, but it's often easier to > write to a file and move to the mail client that way, use sendbug -P for > that. > Ok, let me work on this as well. I definitely would like to help get this resolved, My issue is I need to put this box in production soon (small home/office)... Thanks for your assistance Stuart! really enjoy using OpenBSD, going on ten+ years now, Not a power user by any imagination though... Jay
