Hello Ozgur, if you are very stuck and you want to get you could set the console to com0 on the openbsd boot screen and manage it via serial (to get around the drm issue for now ) just make sure the bios screen you turn off logos (text boot up) and set the openbsd console settings to the same speed as your bios serial console settings (so that you have a seamless view of going from bios / post screen to the openbsd console as Jonathan said, if you set the boot up to legacy bios (rather than efi firmware) you will probably have better luck with the screen, dmesg would be very helpful in identifying the hardware config on your OpenBSD Box
Hope this helps, Tom Smyth On Wed, 22 Jan 2020 at 22:59, Jonathan Gray <j...@jsg.id.au> wrote: > On Wed, Jan 22, 2020 at 11:30:51PM +0300, Özgür Kazancci wrote: > > Hello everyone! Greetings to misc people! > > > > Got a brand new dedicated server with a hardware: Intel Xeon-E 2274G - > 64GB > > DDR4 ECC 2666MHz - 2x SSD NVMe 960GB > > and installed "brand new" OpenBSD 6.6 on it. (I'm managing it remotely > via > > KVM/IPMI) > > > > After the first boot, dmesg is outputting sequentally between few seconds > > delays: > > "wsdisplay0 at inteldrm0 mux 1 > > init: can't open /dev/console: Device not configured" and the system > doesn't > > boot at all. > > > > Please refer to the screenshot attached: https://ibb.co/sQbt7F7 > > > > And after few hours of forums/IRC-logs readings, I tried to try the > > suggestion of lots of similar-people: "disable inteldrm" > > > > To do that, during the boot I typed "boot -c", then got a brand new error > > (IPMI/KVM freezes, no more keyboard input): > > "kbc: cmd word write error" (with a weird cursor) > > Please refer to the screenshot attached: https://ibb.co/QchqhtY > > > > Anyways, wanted to skip that -for now-, rebooted the server again, and > > booted into bsd.rd, mounted the / and /usr on the harddisk, chrooted into > > there and did; > > "config -ef /bsd", then "disable inteldrm" and "quit" to save the > changes. > > Finally rebooted. > > > > The system booted up fine! Got the login prompt shell, logged in, well, > with > > -an another- brand new error :) > > > > "reorder_kernel: failed - see /usr/...GENERIC.MP/relink.log" > > > > I guess that was because I modified the kernel, anyway, wanted to skip > that > > too -for now-. Did what I always do the first: syspatch > > > > installed the patches, rebooted the system, aand...Tada! "inteldrm0 is > back, > > b1tch3z!" :) > > > > Dmesg has again: "init: can't open /dev/console: Device not configured" > and > > delays there. No boot, again. > > > > My questions are: > > > > How can I get the rid of the error "init: can't open /dev/console: Device > > not configured" to be able to boot into the system? > > > > if that was the only way (disabling inteldrm), would I repeat it each > time I > > issue syspatch? > > It would be helpful if you would include a full dmesg. > > 1024x768 is the default mode when there are no connected outputs. > > You should see > wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0 > > The way inteldrm claims the console changes depending on whether or not > you are booting via efi. > > -- Kindest regards, Tom Smyth.
