VESA mode
Hi I'm using the snapshots version in my computer and for about 2 weeks now I'm stuck in VESA mode. I was working pretty well since 26th september for "Intel HD Graphics 5500" but not anymore, any information about this? Regards, Sebastien dmesg : OpenBSD 5.9-beta (GENERIC.MP) #1778: Wed Dec 23 18:23:06 MST 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 16884772864 (16102MB) avail mem = 16368922624 (15610MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xacdfd000 (61 entries) bios0: vendor LENOVO version "J5ET43WW (1.14 )" date 02/10/2015 bios0: LENOVO 20DF004UFR acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI acpi0: wakeup devices LID_(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.15 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.15 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 798.15 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FS GSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 4 (EXP3) acpiprt4 at acpi0: bus 6 (EXP6) acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1 acpipwrres1 at acpi0: AMD3, resource for PEG_ acpipwrres2 at acpi0: AMD2, resource for PEG_ acpitz0 at acpi0: critical temperature is 127 degC acpibtn0 at acpi0: LID_ acpibat0 at acpi0: BAT0 model "LNV-45N1" serial 2079 type LION oem "SANYO" acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 798 MHz: speeds: 2401, 2400, 2300, 2100, 2000, 1900, 1700, 1600, 1400, 1300, 1200, 1000, 900, 800, 600, 500 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 5G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 5500" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1920x1080 wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (s
Re: VESA mode
Am Mon, 28 Dec 2015 17:53:45 + schrieb Sébastien Morand <seb.mor...@gmail.com>: > I'm using the snapshots version in my computer and for about 2 weeks > now I'm stuck in VESA mode. > > I was working pretty well since 26th september for "Intel HD Graphics > 5500" but not anymore, any information about this? http://marc.info/?l=openbsd-cvs=145068713628147 |CVSROOT: /cvs |Module name: xenocara |Changes by:kette...@cvs.openbsd.org2015/12/21 01:37:11 | |Modified files: | xserver/hw/xfree86/common: xf86pciBus.c | |Log message: |On Broadwell, default to using the modesetting driver. Our KMS support |on Broadwell is still a bit weak and the modesetting driver seems to |work better than the intel driver, while still providing 3D |acceleration and video playback support. | |ok phessler@, matthieu@, jsg@ You can of course override this in you xorg.conf I prefer the Intel driver too (even if it isn't always stable) so I created a small /etc/X11/xorg.conf: Section "Device" Identifier "Intel" Driver "intel" EndSection
Puzzled over setting non-VESA mode for intel in xorg.conf
I'm following the OPENBSD_5_8 tag for src and xenocara on a system that reports, vga1 at pci0 dev 2 function 0 "Intel HD Graphics 5500" rev 0x09 intagp at vga1 not configured pcidump reports that as, 0:2:0: Intel HD Graphics 5500 0x: Vendor ID: 8086 Product ID: 1616 I set machdep.allowaperture=2 and have been using xorg and it defaults to 1920x1080 on monitors for which that is fine. However, today I tried it on a monitor for which the best resolution is 1360x768 and I just can't get xorg to do that: On a Linux system (with a Radeon card) I just set an appropriate modeline in xorg.conf and the radeon driver happily takes it and gives me that mode. Indeed, even if I don't supply a modeline on my OpenBSD system, the Xorg.0.log still reports something similar from EDID, (II) VESA(0): Modeline "1366x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz e) However, as you can see, it's VESA looking at this. Whether I name "1366x768" or my other modeline or whatever, it just says "no mode of this name" and goes to 1920x1080. (Indeed, I can imagine it's not a VESA mode!) The intel driver does report itself, e.g., (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 (II) VESA: driver for VESA chipsets: vesa (II) Loading sub module "vbe" (II) LoadModule: "vbe" ... but then it's all VESA thereafter in the log. If I try setting Driver "intel" in xorg.conf it promptly fails, (EE) No devices detected. (EE) no screens found(EE) I'm happy to share fuller dmesg[1], xorg.conf, Xorg.0.log, etc. if that would help. (The xorg.conf that works for this monitor from Linux just sets the modeline.) But, from this summary, does anyone have a clue what's going on? Why's the intel driver not handling everything, instead leaving me stuck with vesa and not letting me set the mode myself? (Of course, xrandr in that environment reports only VESA modes.) [1] dmesg from an identical system is http://permalink.gmane.org/gmane.os.openbsd.misc/226800 ... is this even the correct place to ask? Is it an OpenBSD issue or a more general one with xorg's intel driver? (I don't know to what extent kernel support could be an issue.) -- Mark
Re: Puzzled over setting non-VESA mode for intel in xorg.conf
The intel xorg driver requires inteldrm for mode setting. Initial support for Broadwell/5500 was added to inteldrm after 5.8 and is available in -current/snapshots. On Mon, Dec 14, 2015 at 05:29:19PM +, Mark Carroll wrote: > I'm following the OPENBSD_5_8 tag for src and xenocara on a system that > reports, > > vga1 at pci0 dev 2 function 0 "Intel HD Graphics 5500" rev 0x09 > intagp at vga1 not configured > > pcidump reports that as, > > 0:2:0: Intel HD Graphics 5500 > 0x: Vendor ID: 8086 Product ID: 1616 > > I set machdep.allowaperture=2 and have been using xorg and it defaults > to 1920x1080 on monitors for which that is fine. However, today I tried > it on a monitor for which the best resolution is 1360x768 and I just > can't get xorg to do that: > > On a Linux system (with a Radeon card) I just set an appropriate > modeline in xorg.conf and the radeon driver happily takes it and gives > me that mode. Indeed, even if I don't supply a modeline on my OpenBSD > system, the Xorg.0.log still reports something similar from EDID, > > (II) VESA(0): Modeline "1366x768"x59.8 84.75 1366 1431 1567 1776 768 771 > 781 798 -hsync +vsync (47.7 kHz e) > > However, as you can see, it's VESA looking at this. Whether I name > "1366x768" or my other modeline or whatever, it just says "no mode of > this name" and goes to 1920x1080. (Indeed, I can imagine it's not a VESA > mode!) > > The intel driver does report itself, e.g., > > (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 > (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 > (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 > (II) VESA: driver for VESA chipsets: vesa > (II) Loading sub module "vbe" > (II) LoadModule: "vbe" > ... but then it's all VESA thereafter in the log. > > If I try setting Driver "intel" in xorg.conf it promptly fails, > > (EE) No devices detected. > (EE) no screens found(EE) > > I'm happy to share fuller dmesg[1], xorg.conf, Xorg.0.log, etc. if that > would help. (The xorg.conf that works for this monitor from Linux just > sets the modeline.) But, from this summary, does anyone have a clue > what's going on? Why's the intel driver not handling everything, instead > leaving me stuck with vesa and not letting me set the mode myself? (Of > course, xrandr in that environment reports only VESA modes.) > > [1] dmesg from an identical system is > http://permalink.gmane.org/gmane.os.openbsd.misc/226800 > > ... is this even the correct place to ask? Is it an OpenBSD issue or a > more general one with xorg's intel driver? (I don't know to what extent > kernel support could be an issue.) > > -- Mark
