On 03/19/15 18:38, Stuart Henderson wrote: > On 2015-03-19, Lars <li...@srdn.de> wrote: >> I did something stupid while configuring pf and locked myself out of my >> server using ssh. >> So I connected an older lcd-screen and a usb keyboard to my server to >> get console access. Unfortunately the screen did no wake up and pressing >> keys on the keyboards didn't help. I waited around 1 minute but the >> screen didn't show anything. I rebooted the system by pressing the >> powerbutton to get a working screen. I don't think this is supposed to >> be right.
yes, there is NO screen saver on the text (or DRM) console with OpenBSD, thank goodness. That's one of my many hated "features" of Linux. > Is the dmesg below from a boot with the monitor connected or not? > Can you show the equivalent of these lines from the other type? Look in > /var/log/messages* for old boot messages. > >> root on sd0a (260fbbdcd0c7be61.a) swap on sd0b dump on sd0b >> drm: initializing kernel modesetting (RS880 0x1002:0x9712 >> 0x103C:0x1609). >> radeondrm0: VRAM: 32M 0x00000000C0000000 - 0x00000000C1FFFFFF (32M used) >> radeondrm0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF >> drm: PCIE GART of 512M enabled (table at 0x00000000C0040000). >> radeondrm0: 1680x1050 > > I'm wondering if drm picked a resolution during boot that doesn't work > with your monitor. If this is the cause, you could disable radeondrm > with config(8).. or as has often been the case with some drm configs, if no monitor is attached at boot it just doesn't work with /any/ known monitor. Same fix, but as I've run around and plugged some pretty capable and tolerant monitors into these "dead" video ports, I wouldn't spend a lot of time looking for a "better" monitor. Nick.
