David C. Rankin wrote:
On 06/03/2018 09:37 AM, Per Jessen wrote:
On 06/03/2018 07:15 AM, Per Jessen wrote:
Uh, it works on some machines, not all. I wonder if it might be dependent on the graphics driver. It shouldn't be, IIRC we are talking vesafb by default. Even when using one of the extended resolutions for the console. I know the X side will depend on the graphics card and EDID monitor info, but as long as the card does vesa, then the console frame-buffer shouldn't care. I see it working on HP Proliants with ATI Rage XL, but not on Supermicro boards with XGI Z7/Z9.
Strange, I have 2 older SuperMicro boards (one dual-quad-core Opteron, one quad-quad-core Opetron). Both successfully blank and powerdown.
They do have the radeon graphics, e.g.
fb: switching to radeondrmfb from VESA VGA Supports vblank timestamp caching Rev 2 (21.10.2013). Driver supports precise vblank timestamp query. radeon: irq initialized. Loading R100 Microcode
Check toward the end of dmesg and see what the non-blank/poweroff hardware is reporting.
[ 30.313212] xgifb: module is from the staging directory, the quality is unknown, you have been warned. [ 30.320733] xgifb 0000:0f:00.0: Relocate IO address: 6000 [00006030] [ 30.320892] xgifb 0000:0f:00.0: chipid = 30 [ 30.321035] xgifb: SR14=41 DramSzie 1000000 ChannelNum 1 [ 30.321204] xgifb 0000:0f:00.0: Framebuffer at 0xef000000, mapped to 0xffffc90002000000, size 16384k [ 30.321423] xgifb 0000:0f:00.0: MMIO at 0xee300000, mapped to 0xffffc90000600000, size 256k [ 30.357534] xgifb 0000:0f:00.0: No or unknown bridge type detected [ 30.357669] xgifb: Default mode is 800x600x16 (60Hz) [ 30.357897] fbcon: XGI (fb0) is primary device [ 30.369814] Console: switching to colour frame buffer device 100x37 I don't know how much support 'setterm' needs from the driver. -- Per Jessen, Zürich (18.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org